Question

Difficulty: MediumDeployment Strategies and Execution

A company has a critical web application running on Amazon ECS with AWS Fargate. A SysOps Administrator needs to configure a deployment strategy for a new release that ensures zero downtime, provides the ability to run verification tests on the new version before routing production traffic to it, and supports rapid rollback to the previous version in the event of an application error. Which two actions should the SysOps Administrator perform to implement a deployment strategy that meets these requirements? (Select TWO.)

  1. Configure the Amazon ECS service to use the AWS CodeDeploy deployment controller.Answer
  2. Create an AWS CodeDeploy deployment group with a blue/green deployment type, specifying a test listener on the Application Load Balancer to verify the new version.Answer
  3. C
    Configure the Amazon ECS service to use the rolling update deployment controller with a minimum healthy percent of 100% to handle rollback automatically.
  4. D
    Set up a CloudFormation stack update using an in-place deployment strategy with rollback triggers configured to monitor the ECS tasks.
  5. E
    Create a Systems Manager Patch Group to automate the rollout of the new container image to the Fargate tasks during a maintenance window.

Answer

To meet the requirements, the SysOps Administrator should configure the Amazon ECS service to use the AWS CodeDeploy deployment controller and create an AWS CodeDeploy deployment group with a blue/green deployment type, specifying a test listener on the Application Load Balancer to verify the new version.
Configuring the ECS service deployment controller to use CodeDeploy enables blue/green deployment capabilities. The CodeDeploy deployment group manages the transition of traffic from the old task set (blue) to the new task set (green). By configuring a test listener on the Application Load Balancer, the administrator can route test traffic to the green deployment to verify the application's health before redirecting production traffic, ensuring zero downtime and providing a fast path to rollback if issues are detected.

Step-by-Step Solution

1
Modify the ECS service definition to set the deployment controller type to CODE_DEPLOY.
Delegates the routing of traffic between task sets to AWS CodeDeploy.
By default, ECS uses its own rolling update controller which does not support advanced traffic routing or verification testing on a separate listener.
2
Create an AWS CodeDeploy application and deployment group targeting the ECS service.
Establishes the deployment group that defines how traffic will shift.
The deployment group configures the blue/green environment settings and rollback alarms.
3
Configure the deployment group with a production listener and a test listener on the Application Load Balancer.
Enables preview traffic routing to the new (green) task set via the test port before production traffic cutover.
This allows verification tests to run on the live green task set while production users continue accessing the stable blue task set, and enables instant rollback if tests fail.

Key Concept

Implementing Blue/Green deployments on Amazon ECS using AWS CodeDeploy for zero-downtime releases, validation testing, and rapid rollbacks.
Rate this question