A company hosts a production web application on AWS Elastic Beanstalk using an Auto Scaling group behind an Application Load Balancer. A SysOps Administrator needs to deploy a critical application update. The deployment strategy must ensure zero downtime, deploy the update to brand new instances for clean isolation, and allow for a rapid rollback by terminating the new instances if the deployment fails. Furthermore, the administrator must avoid the overhead of managing a separate Elastic Beanstalk environment or performing a DNS CNAME swap. Which deployment policy should the SysOps Administrator select to meet these requirements?
- ARolling deployment
- Immutable deploymentCevap
- CAll-at-once deployment
- DBlue/Green deployment
Cevap
The correct deployment policy is an immutable deployment.
The immutable deployment strategy satisfies all the requirements. It creates a temporary Auto Scaling group to launch a full set of new instances running the new version within the same environment. Traffic is cut over only after health checks pass, ensuring zero downtime. If the deployment fails, the rollback is rapid and simple: Elastic Beanstalk terminates the temporary Auto Scaling group, leaving the original instances untouched.
Adım Adım Çözüm
Anahtar Kavram
AWS Elastic Beanstalk immutable deployments isolate application updates on new EC2 instances in a temporary Auto Scaling group within the same environment to ensure zero downtime and rapid rollback.