Amazon ECS introduces Early Success Criteria for service deployments
Amazon ECS now supports Early Success Criteria for rolling service deployments, allowing users to define when a deployment is considered successful based on healthy task percentages, enabling faster deployment completion and unlocking subsequent operations.
Amazon Elastic Container Service (Amazon ECS) now supports early success criteria for rolling update strategies. Users can set the healthy percent of tasks running and in healthy state for a target service revision to define deployment success. For example, with 100 desired tasks and a 90% healthy percent, Amazon ECS marks the deployment as successful once 90 tasks are healthy, while the remaining tasks continue to launch via normal service scaling. This benefits workloads running on specialized hardware or constrained capacity, such as GPU-accelerated inference workloads. Early success criteria also allow control over the deployment rollback monitoring period, enabling the next scale-out to proceed via normal service scaling while protecting the deployment until the set criteria are met. Users can choose to clean up the source service revision as BLOCKING or DEFERRED. With BLOCKING, the source revision cleanup completes before declaring success. With DEFERRED, success is declared when criteria are met, and source revision tasks are drained asynchronously outside the deployment, which is useful for services with active long-lived connections or task scale-in protection. This feature is available for all AWS commercial and AWS GovCloud (US) regions with rolling update strategies and can be configured for new and existing Amazon ECS services using the AWS Management Console, AWS CLI, AWS SDKs, and infrastructure-as-code tools.
Why it matters
Amazon ECS is a service for managing containerized applications, and this update increases flexibility in the deployment process, particularly useful for workloads with constrained hardware resources.