amazon-ecs

According to Amazon ECR Service Limits , the maximum number of images per repository is 1,000. After exceeding this limit, the oldest image won't remove automatically. It blocks pushing to the repository. So I have to clean old images manually. Update: AWS introduced ECR Lifecycle Policies . We can now automate the cleanup with this. Having experienced this exact scenario, I can confirm that upon reaching the limit, AWS will block you from pushing with this very unhelpful error message: Error pushing to registry: Server error: 403 trying to push <repo>:<label> manifest You'll need to manage

I'm having hard times adding instances that are created in my VPC and on a private subnet(no internet gateway attached to it) to ECS cluster. Right now the only way I've managed to do this was by adding a public IP and have a NAT instance/gateway configured. How do you use ECS clusters with private subnets? Ionut I guess I've found the answer on the AWS documentation and it seems I need to use a NAT instance/Gateway :( Another source and also the official documentaion "...Container instances need external network access to communicate with the Amazon ECS service endpoint, so if your container

I'm getting this error when running a task on my Amazon Fargate cluster. Has anyone seen run into this before? Public IP is mandatory for Farget. For details https://github.com/aws/amazon-ecs-agent/issues/1128 Go to the docs for an answer to this one. https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_cannot_pull_image.html Since you are encountering a 500 error, I would heed the advice of the first error's description, "Connection timed out": When a Fargate task is launched, its elastic network interface requires a route to the internet to pull container images. If you receive

I'm trying to configure amazon-ecs-plugin for Jenkins using init.groovy script, but couldn't find and docs on it. I'm new to groovy based configuration automation Tried to get all the properties using import jenkins.model.* import com.cloudbees.jenkins.plugins.amazonecs.* ECSCloud.metaClass.properties.each {println it.name+":\t"+it.type } The Output: regionName: class java.lang.String searchName: class java.lang.String slaveTimoutInSeconds: int searchIndex: interface hudson.search.SearchIndex ACL: class hudson.security.ACL descriptor: class hudson.model.Descriptor credentialsId: class java

I am writing a terraform script for creating a ECS auto scaling cluster. I have created a cluster and added ec2 container instances in to it.My task definition file contains a image that is from a Private docker repository.I go through the aws official documentation and find a page for Private Registry Authentication and tried both of the ways as described there. using dockercfg the docker way I put my ecs.config file in the S3 bucket and during the instance boot time I passed the user data as #!/bin/bash yum install -y aws-cli aws s3 cp s3://<my_bucket_name>/ecs.config /etc/ecs/ecs.config In

I have a fargate task which I have scheduled to run with CloudWatch Event rules, and output a timestamp to a database on a successful run. It also outputs a logfile to CloudWatch for every time it runs. However, there was 1 time where the log file was not created, and the database not updated. I suspect the task was never even started, or had failed to start. In CloudWatch, the event rule shows trigger and invocation at the time I expected the task to run, so I assume the task at least attempted to start. My question is: is there any way I can debug or log information about the cluster failing