Time mode set 3, ElasticBeanStalk question, answer explanation, please check

[joseph]

in the answer explanation part of this question

An online brokerage firm used AWS Elastic Beanstalk in deploying their cryptocurrency trading platform. After one year, a new version of their trading platform is ready to be deployed. Which of the following is not a valid deployment policy that you can use in Elastic Beanstalk?

In the answer explanation, you have mentioned

Take note that Swap Environment URLs is one of the actions available in Elastic Beanstalk when you are performing a blue/green deployment.

It should be given as not available in Elastic Beanstalk

[TutorialsDojo-Support]

Hi Joseph,

Thank you for your feedback.

When you are deploying your application on your current Elastic Beanstalk environment, you have the following options for deployments.

All at once, Rolling, Rolling with additional batch, and Immutable

Elastic Beanstalk deployments: https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/using-features.deploy-existing-version.html

“Swap Environment URLs” environment URLs is not an option when you deploy a new version on the current environment. However, this option is available on a different scenario, such as on blue/green deployment strategy.

You have two completely separate Elastic Beanstalk environments, one is running the older version, while the other is running the newer version of the application.

On the Elastic Beanstalk web console, you can click on one of the environments and click Actions > Swap Environment URLs. This way, the DNS CNAMES for the environments will be swapped, effectively allowing you to route requests to the newer environment. This is available on Elastic Beanstalk (it’s just not a deployment policy).

Regards,

Kenneth Samonte @ Tutorials Dojo