Which configuration should the DevOps engineer add in the CloudFormation template to meet these requirements?
Add an AppSpec file with the CodeDeployDefault.ECSLinearl OPercentEveryl Minutes deployment configuration.
Add the AWS::CodeDeployBlueGreen transform and the AWS::CodeDeploy::BlueGreen hook parameter with the CodeDeployDefault.ECSLinear10PercentEvery1Minutes deployment configuration.
Add an AppSpec file with the ECSCanary10Percent5Minutes deployment configuration.
Add the AWS::CodeDeployBlueGreen transform and the AWS::CodeDepioy::BlueGreen hook parameter with the ECSCanary10Percent5Minutes deployment configuration.
Explanations:
The option specifies the use of theCodeDeployDefault.ECSLinear10PercentEvery1Minutesconfiguration, which is not applicable in a blue/green deployment setup using CodeDeploy with ECS. Instead, blue/green deployments require the use of the AWS::CodeDeployBlueGreen transform and specific hooks to manage traffic shifting properly.
This option correctly uses theAWS::CodeDeployBlueGreentransform and specifies theCodeDeployDefault.ECSLinear10PercentEvery1Minutesdeployment configuration. This configuration allows for shifting 10% of traffic every minute in a blue/green deployment scenario, ensuring high availability during the deployment window.
TheECSCanary10Percent5Minutesdeployment configuration is intended for canary deployments, not blue/green deployments. It shifts 10% of traffic every 5 minutes, which does not meet the requirement of shifting traffic every minute. Additionally, it does not use the necessary transforms or hooks for blue/green deployments.
Although this option mentions theAWS::CodeDeployBlueGreentransform, it incorrectly uses theECSCanary10Percent5Minutesdeployment configuration, which is not suitable for the required blue/green deployment strategy. This configuration is more appropriate for canary deployments, which do not meet the specified requirements of shifting traffic every minute.