-
Hello Nauman Jamil Qazi,
Thanks for the feedback.
The term “External Amazon RDS database” refers to a single RDS instance that is created and managed independently from the Elastic Beanstalk environments. In this setup, both the blue/green stacks (or production and QA environments) share the same RDS database. The key point is that “external” highlights the database’s separation from the Elastic Beanstalk environment itself, rather than implying multiple databases.
On the other hand, having a “separate Amazon RDS database for each stack” means that each Elastic Beanstalk environment, such as blue/green, has its own distinct RDS instance, each configured with Multi-AZ. This setup results in two physically separate databases, which can lead to data divergence and inconsistencies. Such issues create significant risks.
Hence, the correct answer is: Migrate the application source code to GitHub and set up the AWS Connector for GitHub. Use CodeBuild to set up automatic unit and functional tests. Set up two stacks in Elastic Beanstalk with an external Amazon RDS database with Multi-AZ deployments configuration. Deploy the current application version on the two environments. Configure CodeBuild to deploy the succeeding application revision to Elastic Beanstalk. Use a blue/green strategy for deployment.
I hope this helps! Let us know if you need further assistance.
Regards,
JR @ Tutorials Dojo
