Users can now specify a healthy percent of desired tasks that must be running before a deployment is declared successful, allowing subsequent pipelines and operations to proceed without waiting for full scaling completion.
This feature benefits workloads with constrained resources or long initialization times, such as GPU-accelerated tasks, and offers cleanup policies for source revision tasks to accommodate long-lived connections, enabling more flexible and efficient rollout strategies.
Source & further reading
Amazon ECS introduces Early Success Criteria for service deployments ↗Source published 2026-09-04. This report was prepared with AI assistance from the linked primary-source material. Claims and limitations should be checked against the original announcement or research.