A company is planning to use AWS CodeDeploy to deploy an application to Amazon Elastic Container Service (Amazon ECS). During the deployment of a new version of the application, the company initially

The ECSCanary10Percent15Minutes predefined configuration is purpose-built for Amazon ECS deployments using a canary strategy. It initially routes 10% of production traffic to the new version, holds that state for 15 minutes to allow monitoring and validation, and then completes the deployment by shifting the remaining 90% in a single step - precisely meeting both the 10% initial exposure and the 15-minute interval requirements.

This configuration targets AWS Lambda, not ECS, and shifts 10% of traffic with only a 5-minute interval before completing - neither the compute platform nor the wait time matches the requirements.

This configuration also targets Lambda rather than ECS; despite having a 15-minute interval in the name, it cannot be applied to an ECS deployment.

The ECSLinear10PercentEvery1Minutes configuration uses a linear strategy that shifts traffic in 10% increments every 1 minute - it would take 9 additional minutes to reach 100% and does not match the single-step completion after 15 minutes.