Which design will meet these requirements?
Deploy a CI/CD pipeline that incorporates AMIs to contain the application and their configurations. Deploy the application by replacing Amazon EC2 instances.
Specify AWS Elastic Beanstalk to stage in a secondary environment as the deployment target for the CI/CD pipeline of the application. To deploy, swap the staging and production environment URLs.
Use AWS Systems Manager to re-provision the infrastructure for each deployment. Update the Amazon EC2 user data to pull the latest code artifact from Amazon S3 and use Amazon Route 53 weighted routing to point to the new environment.
Roll out the application updates as part of an Auto Scaling event using prebuilt AMIs. Use new versions of the AMIs to add instances. and phase out all instances that use the previous AMI version with the configured termination policy during a deployment event.
Explanations:
Using AMIs and replacing EC2 instances can lead to longer deployment times, which doesn’t support multiple releases per hour and may complicate rollback.
AWS Elastic Beanstalk allows for quick environment swaps, enabling rapid deployments and easy rollbacks, meeting both requirements effectively.
Using Systems Manager for infrastructure re-provisioning and user data updates could introduce delays, making it less suitable for rapid deployments and rollbacks.
While Auto Scaling and AMIs can help manage deployments, the process can be complex and may not facilitate quick rollbacks or freq
If memory serves me right, the answer is:
Specify AWS Elastic Beanstalk to stage in a secondary environment as the deployment target for the CI/CD pipeline of the application. To deploy, swap the staging and production environment URLs.
As far as I can tell, the answer is:
Specify AWS Elastic Beanstalk to stage in a secondary environment as the deployment target for the CI/CD pipeline of the application. To deploy, swap the staging and production environment URLs.