What CI/CD configuration meets all of the requirements?
Configure CodePipeline with a deploy stage using AWS CodeDeploy configured for in-place deployment. Monitor the newly deployed code, and, if there are any issues, push another code update.
Configure CodePipeline with a deploy stage using AWS CodeDeploy configured for blue/green deployments. Monitor the newly deployed code, and, if there are any issues, trigger a manual rollback using CodeDeploy.
Configure CodePipeline with a deploy stage using AWS CloudFormation to create a pipeline for test and production stacks. Monitor the newly deployed code, and, if there are any issues, push another code update.
Configure the CodePipeline with a deploy stage using AWS OpsWorks and in-place deployments. Monitor the newly deployed code, and, if there are any issues, push another code update.
Explanations:
In-place deployment with AWS CodeDeploy can lead to downtime and is not suitable for quick rollbacks. If an issue arises, while another code update can be pushed, it does not provide a reliable way to quickly revert to a previous stable version.
Blue/green deployments with AWS CodeDeploy allow for quick, minimal-downtime rollouts and easy rollbacks if issues arise. The new version is deployed to a separate environment, allowing for monitoring before switching traffic. If problems occur, a manual rollback can be performed to revert to the previous version instantly.
Using AWS CloudFormation to create a pipeline for test and production stacks does not directly address the need for rapid deployment and rollback capabilities for patches. CloudFormation is more suited for infrastructure as code rather than CI/CD deployment practices.
AWS OpsWorks is not primarily designed for CI/CD and using in-place deployments may result in downtime. Similar to Option A, it lacks the efficiency for quick rollback, as it does not inherently provide a mechanism for managing multiple versions effectively.