Skip to content

Project

Amazon Elastic Container Service

Amazon ECS is a fully managed container orchestration service on AWS for running and scaling Docker containers across clusters.

Known aliases

  • Amazon ECS
  • Amazon Elastic Container Service
  • AWS ECS
  • ECS
  • Elastic Container Service

Current stories

buildOne report1 publisher

Amazon ECS now drains and cycles instances whose GPUs report hardware faults

Amazon ECS now reads GPU health from NVIDIA's DCGM and drains and cycles faulty instances on its own, the ECS team wrote in The New Stack. For GPU fleets on Managed Instances, the detect-drain-replace loop that operators used to script is now AWS's job.

Publishers:thenewstack.io

Reality

Evidence35
Adoption
Not scored
Hype gap+20
Incentives80
Confidence40
buildOne report1 publisher

ECS earlySuccessCriteria ends automatic rollback once a partial rolling deployment reports success

Amazon ECS's earlySuccessCriteria can close a rolling deployment at 90 of 100 healthy tasks, ending automatic rollback for the service at that point. EventBridge and CloudTrail log that early finish exactly like a full rollout, so anything reading those events cannot tell a 90-task fleet from a 100-task one.

Publishers:dev.to

Reality

Evidence55
Adoption
Not scored
Hype gap0
Incentives
Not scored
Confidence50
buildOne report1 publisher

Nova Forge's serverless RL is GA. The reward function is still yours to get wrong

AWS has generalised the orchestration for multi-turn reinforcement fine-tuning. The part that decides what the model learns is still code somebody on your team has to write and audit.

Publishers:aws.amazon.com

Reality

Evidence45
Adoption
Not scored
Hype gap+10
Incentives75
Confidence50
buildOne report1 publisher

The App Runner exit starts with two IAM roles you write yourself

A dev.to walkthrough says AWS App Runner no longer accepts new services, and the Amazon ECS Express Mode path it demonstrates opens with an execution role, an infrastructure role, and a public container image.

Publishers:dev.to

Reality

Evidence45
Adoption12
Hype gap+25
Incentives22
Confidence48
buildOne report1 publisher

The default MCP deployment buys a Kubernetes operational surface for request/response traffic

A dev.to writeup makes the case for trying Bedrock Agents or AgentCore Runtime before containers, and for putting real limits on the gateway, because a looping agent spends money without ever raising an error.

Publishers:dev.to

Reality

Evidence28
Adoption
Not scored
Hype gap+18
Incentives32
Confidence36
buildOne report1 publisher

AWS prices the HPA concurrency flag into its dedicated EKS control plane

The 40x is arithmetic on an upstream default of five goroutines. It only transfers if every HPA evaluation really costs about 100ms. The reasoning that holds regardless is why a shared API server could not be handed the same setting.

Publishers:dev.to

Reality

Evidence31
Adoption14
Hype gap+38
Incentives63
Confidence37
buildOne report1 publisher

Graviton5's 25% per-vCPU gain builds the cost case for pricier R9g reservations

AWS rates its new Graviton5 R9g instances up to 25% better per vCPU than R8g but ships the launch without prices, which leaves break-even arithmetic and your own load test as the only evidence you have.

Publishers:aws.amazon.com

Reality

Evidence30
Adoption15
Hype gap+38
Incentives85
Confidence55
buildOne report1 publisher

ECS Express Mode bakes 5% of traffic for three minutes before it shifts the rest

Express Mode turns a container image and two role ARNs into an HTTPS service on Fargate. The engineering question it leaves behind is which of its inherited defaults match your workload and which will quietly fight it.

Publishers:thenewstack.io

Reality

Evidence45
Adoption
Not scored
Hype gap+25
Incentives88
Confidence55
buildOne report1 publisher

Natera's voice scheduler: the hard parts were sockets, filler speech and when to ask for ID

AWS says three integration decisions carry Natera's phlebotomy booking agent. The reported numbers are good, and they cover a narrower job than "booked appointment".

Publishers:aws.amazon.com

Reality

Evidence40
Adoption34
Hype gap+18
Incentives84
Confidence56
buildOne report1 publisher

Express Mode builds the ALB you skipped, and owns the knobs you used to write

AWS's November release provisions the load balancer, scaling policies and alarms that a hands-on Terraform comparison admits it never configured. The control points go with them.

Publishers:dev.to

Reality

Evidence38
Adoption24
Hype gap+22
Incentives58
Confidence42
buildOne report1 publisher

Autoscaling Is the One Config Surface With Two Writers and No Merge

Scaling policies on ECS, ASG, VMSS and MIG are separate API objects with last-writer-wins semantics. That is why inherited scaling behavior stays wrong, and why nobody gets told when it changes.

Publishers:dev.to

Reality

Evidence42
Adoption
Not scored
Hype gap+14
Incentives22
Confidence46