amazon-ecs

We want to create ScheduledTasks in AWS ECS via CloudFormation. Is there a programmatic way to create via boto or cloudformation? In order to define a scheduled ECS task in CloudFormation, you need to define a "AWS::Events::Rule" resource with an ECS task as a target. "TaskSchedule": { "Type": "AWS::Events::Rule", "Properties": { "Description": "dump data every workday at 10", "Name": "dump-data", "ScheduleExpression": "cron(0 10 ? * MON-FRI *)", "State": "ENABLED", "Targets": [ { "Id": "dump-data-ecs-task", "RoleArn": { "Fn::GetAtt": ["TaskSchedulerRole", "Arn"] }, "EcsParameters": {

I want to stop EC2 instances after office hours to save costs. How can I do the same with ECS instances? Even if I stop all tasks/services, the instance is still there? Do I stop the EC2 instance directly? From EC2 Management Console Click Auto Scaling Groups from the left menu. Select the group from the list. Click edit on the details tab. Set desired property to ' 0 '. After clicking save it is all done. The Auto Scaling Group is smart enough to shut down all instances. If you have the cluster set to a minimum number of nodes with an asg. If you turn off the nodes the asg will start another

I am using Amazon Web Services EC2 Container Service with an Application Load Balancer for my app. When I deploy a new version, I get 503 Service Temporarily Unavailable for about 2 minutes. It is a bit more than the startup time of my application. This means that I cannot do a zero-downtime deployment now. Is there a setting to not use the new tasks while they are starting up? Or what am I missing here? UPDATE: The health check numbers for the target group of the ALB are the following: Healthy threshold: 5 Unhealthy threshold: 2 Timeout: 5 seconds Interval: 30 seconds Success codes: 200 OK

I am following the instructions at https://docs.docker.com/compose/django/ to get a basic dockerized django app going. I am able to run it locally without a problem but I am having trouble to deploy it to AWS using Elastic Beanstalk. After reading here , I figured that I need to translate docker-compose.yml into Dockerrun.aws.json for it to work. The original docker-compose.yml is version: '2' services: db: image: postgres web: build: . command: python manage.py runserver 0.0.0.0:8000 volumes: - .:/code ports: - "8000:8000" depends_on: - db and here is what I translated so far {

i am new to aws and encountred some problem while trying to create a EC2 service in a ECS cluster. i was able to successfully create a brand new service (service1) in cluster1, but afterwards, i decided to delete cluster1 and create cluster2. The problem came when i try to re-create service1 in cluster2. whenever i try to add the service, i will get the following error creation failed: Service already exists. (Service: AWSServiceDiscovery; Status Code: 400; Error Code: ServiceAlreadyExists; Request ID: d854025e-ebcc-11e8-84ab-b3bac906f2ef) anyone know how to resolve this problem? i have tried

I want to automate the deployment of my application by having my ECS service launch with the latest Docker image. From what I've read, the way to deploy a new image version is as follows: Create a new task revision (after updating the image on your Docker repository). Update the service and specify the new revision. This seems to work, but I want to do this all through CLI so I can script it. #2 seems easy enough to do through the AWS CLI with update-service , but I don't see a way to do #1 without specifying the entire Task JSON all over again as with register-task-definition (my JSON will