AWS Red/Black Deployment Strategy: Common Misconceptions

Not True for Red/Black Deployment

Prev Question Next Question

Question

Your manager has assigned you a task to implement a Red/Black deployment strategy for a new project deployed in EC2 instances.

You created two similar environments in AWS.

Each environment contains an ELB with an Auto Scaling group attached.

One environment is used to run the live traffic, and the other one will install the new software release.

And the traffic is switched between two environments by updating the DNS records in Route 53

Which description is NOT true for this Red/Black deployment?

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D.

Correct Answer - B.

The Red/Black deployment is a newer term being used by Netflix.

About its implementations on AWS, please refer to https://d1.awsstatic.com/whitepapers/AWS_Blue_Green_Deployments.pdf.

Option A is incorrect: Because when issues happen, the deployment can roll back to the original one.

This is one major advantage of the Red/Black deployment strategy.

Option B is CORRECT because, for the Red/Black deployment, the DNS switch can happen only to one environment at a time.

Option C is INCORRECT because, with the Red/Black deployment, only one version of the environment ( either Red or Black ) can receive traffic at a time.

Option D is incorrect: Because two similar environments are existing at the same time.

When the new environment is being tested, the old environment still serves traffic.

This is different from in-place deployment which has a downtime when the upgrade is ongoing.

Red/Black deployment is a deployment strategy that involves creating two identical environments, with one environment (Red) serving live traffic and the other environment (Black) being used to install new software releases. Once the new software is installed and tested in the Black environment, the traffic is switched from the Red environment to the Black environment using DNS record updates in Route 53.

Answer A is true. If issues arise during the deployment, rollback can be easily achieved by modifying Route 53 to shift traffic back to the original environment. This allows for a quick and easy rollback in case of any issues or errors that may arise during the deployment process.

Answer B is false. It is not recommended to switch the DNS record to both the live traffic and new software release environment simultaneously. This can cause traffic to be split between the two environments, which can lead to unpredictable behavior and potential issues during the deployment process.

Answer C is true. The recommended approach is to use Amazon Route53 to divert traffic to only one of the environments (i.e) either the live traffic or the one that installs the new software release at a single point of time. This ensures that the traffic is directed to only one environment at a time, reducing the risk of errors or issues during the deployment process.

Answer D is true. There is no downtime in a Red/Black deployment as the old environment can still serve traffic when the new environment is not ready yet. This ensures that users are not affected by any downtime during the deployment process.

In summary, Red/Black deployment is a deployment strategy that involves creating two identical environments, with one environment serving live traffic and the other environment used to install new software releases. Traffic is switched between the two environments using DNS record updates in Route 53. To minimize the risk of errors and issues during the deployment process, it is recommended to divert traffic to only one of the environments at a time, and the old environment can still serve traffic when the new environment is not ready yet.