Relative Content

Tag Archive for amazon-web-servicesamazon-ecs

AWS ECS Graceful Deploy new Image

We deploy our batch processes to ECS Fargate by pushing a new container, and then forcing a deployment on the service. This does not allow us to do a graceful shutdown in the current running tasks which are working jobs. We do a force deployment because at some point recently, just having the task restart through a container shutdown does not pull a fresh image.. (We are able to signal the current running tasks so they will exit when finished with their workload)

Why does ECS binpack strategy on memory always scale up a new EC2 instance despite available resources?

I’m using ECS with an Auto Scaling group as a capacity provider to deploy tasks on EC2. I’ve set the task placement strategy to binpack based on memory. However, I’ve noticed that ECS always scales up a new EC2 instance to deploy a new task, even if an existing instance has enough CPU and memory available. Consequently, there is only one task per EC2 instance. I expect that all tasks should be placed on a single EC2 instance if it has sufficient memory.

cannot create cluster in AWS Amazon Elastic Container Service

I am trying to create a cluster in AWS Amazon Elastic Container Service, so a clicked on create cluster button, entered “defaut” as name and default namespace and with AWS Fargate (serveless) ticked, and when I click create button, I have the following error message:
There was an error creating cluster default.
Stack [Infra-ECS-Cluster-default-7505d64a] already exists

ECS Task Failure Alerts Notification

I have ECS Services running and I want to setup a alert on Task count failure.
That is if during new deployments the container is not stable and Tasks are failing .
I want to generate a Alert Notification if the failure count is more than 5 times.