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.)
- CodeDeployDefault.ECSCanary10Percent5MinutesCevap
- CodeDeployDefault.ECSLinear10PercentEvery1MinuteCevap
- CCodeDeployDefault.ECSAllAtOnce
- DCodeDeployDefault.OneAtATime
- ECodeDeployDefault.HalfAtATime
Cevap
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.
Adım Adım Çözüm
Anahtar Kavram
AWS CodeDeploy deployment configurations for Amazon ECS support gradual traffic shifting (canary and linear) to validate new container versions before shifting all traffic.
Tahmini Süre:1m 30s