Ecs on CuraDevOps

Amazon ECS adds automatic detection and repair of impaired agent connectivity

Tue, 25 Aug 2026 11:19:32 +0000

Platform/SRE — Plan: A new GA ECS capability worth adopting this quarter: Fargate and Managed Instances now auto-drain and replace impaired instances, while EC2-based ECS surfaces the new AGENT_CONNECTIVITY health event that teams must wire into their own instance-replacement automation. No deadline, but teams running ECS on EC2 should build the event-driven replacement workflow to gain equivalent resilience.
CI/CD — Skip
Leader — Skip

Fri, 24 Jul 2026 12:15:09 +0000

Platform/SRE — Plan: GA feature that reduces cross-AZ data transfer costs and latency for ECS Service Connect; existing services need a one-time redeployment to activate it. Schedule the redeployment across affected ECS services this quarter to capture the cost and latency benefit.
CI/CD — Skip
Leader — Skip

Wed, 22 Jul 2026 12:23:02 +0000

Platform/SRE — Plan: This GA feature surfaces previously opaque ECS service-side deployment events — state transitions, circuit-breaker rollbacks, Managed Daemon updates — directly into CloudWatch, S3, or Firehose. Platform teams running ECS should evaluate opting in at the cluster level to reduce MTTR on deployment incidents without waiting on AWS Support.
CI/CD — Learn: ECS Action Logs expose service-side operations that can help diagnose failures in pipeline-triggered deployments, but no pipeline changes are required — this is an opt-in ECS console/CloudWatch feature, not a build or artifact system change.
Leader — Skip