Question

Difficulty: EasyDeployment Strategy Design

A solutions architect is designing a deployment strategy for a new microservice that will run on AWS Fargate. The business requirements state that any new version of the microservice must receive traffic gradually to monitor for initial errors before all traffic is shifted. If the new version fails health checks, the deployment must automatically roll back. Which two AWS CodeDeploy deployment configurations should the solutions architect choose to meet these requirements? (Select two.)

  1. CodeDeployDefault.ECSCanary10Percent5MinutesAnswer
  2. CodeDeployDefault.ECSLinear10PercentEvery1MinuteAnswer
  3. C
    CodeDeployDefault.ECSAllAtOnce
  4. D
    CodeDeployDefault.OneAtATime
  5. E
    CodeDeployDefault.HalfAtATime

Answer

The correct options are CodeDeployDefault.ECSCanary10Percent5Minutes and CodeDeployDefault.ECSLinear10PercentEvery1Minute because they are natively supported ECS deployment configurations that shift traffic gradually and support automatic rollbacks.
The correct options represent native ECS deployment configurations. Canary10Percent5Minutes shifts 10 percent of traffic and waits 5 minutes before shifting the remaining traffic. Linear10PercentEvery1Minute shifts 10 percent of traffic every minute until 100 percent is reached. Both configurations allow for monitoring and trigger automatic rollback if CloudWatch alarms or health checks fail during the deployment.

Step-by-Step Solution

1
Identify the compute platform and deployment requirements.
The microservice runs on AWS Fargate (ECS) and requires gradual traffic shifting with automatic rollbacks.
This narrows the choice of CodeDeploy configurations to those compatible with Amazon ECS and Fargate.
2
Filter out configurations that are incompatible with the compute platform.
Configurations like 'OneAtATime' and 'HalfAtATime' are for EC2/On-Premises and are discarded.
CodeDeploy has distinct configurations for EC2/On-Premises, AWS Lambda, and Amazon ECS.
3
Evaluate the remaining ECS configurations against the gradual routing requirement.
Canary and linear configurations route traffic gradually, whereas 'AllAtOnce' shifts all traffic immediately.
Only Canary and Linear configurations satisfy the requirement to shift traffic gradually to allow monitoring.

Key Concept

AWS CodeDeploy deployment configurations for Amazon ECS support gradual traffic shifting (canary and linear) to validate new container versions before shifting all traffic.
Estimated Time:1m 30s
Rate this question