A company is using AWS Elastic Beanstalk to manage web applications that are running on Amazon EC2 instances. A developer needs to make configuration changes. The developer must deploy the changes to new instances only.
Which types of deployment can the developer use to meet this requirement? (Choose two.)
To meet the requirement of deploying changes to new instances only, the developer can use Immutable and Blue/Green deployment strategies. Immutable deployments create a new set of instances with the new configuration and once they are verified to work correctly, the traffic is redirected to these new instances, leaving the old ones intact. Similarly, Blue/Green deployments involve creating a parallel environment (new instances) with the new configuration and then switching the traffic to these new instances once they are verified to work as expected. This process ensures that the changes are made on new instances only, without affecting the currently running instances.
BD Immutable Blue/Green Source: https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/using-features.deploy-existing-version.html
Thanks for your URL - check "The following table compares deployment method properties." table in the above page.
What does "Developer should deploy changes to new instances only" mean?
no old instances running the application should be modified in order to attain the desired state.
Blue/green is NOT a kind of deployment in beanstalk, is a routing that you have even to do in CNAMEs https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/using-features.CNAMESwap.html It has to be B and E, "Rolling with additional batch" is literally an option together with the others.
Please check this https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/using-features.deploy-existing-version.html
B (Immutable) and D (Blue/Green) are correct and supported by Elastic Beanstalk since they provide a completely new load balancer and both of them redirect the traffic to completely new instances. Of course, this has double of the cost because we manage old and new Load Balancers but when we redirect the traffic and we are sure that the application is working correctly, then we are able to terminate the old instances
Blue/Green is NOT the deployment type in Beanstalk, we need to attain that manually with the help of Route53. Rolling with additional batches is the right option, new instances are used to deploy new app and no old instances are modified.
Correction: Blue/Green is correct.. so BD.
what made you change your mind?
what made you change your mind?
https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/using-features.deploy-existing-version.html
@Irom: Here we go friend .... Immutable deployments perform an immutable update to ==> launch a full set of "new instances" running the "new version" of the application in a "separate Auto Scaling group"", alongside the instances running the old version. https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/using-features.rolling-version-deploy.html
The developer must deploy the changes to new instances only: In other words, the strategy we'll choose shouldn't deploy on existing instances at all. Immutable: In this strategy we create new instances and deploy onto them. When we see our new instances work as expected, we get rid of the old instances we were using. Blue/Green: This is similar to immutable strategy. We create new instances and deploy to them (to green instances). Then direct some of the traffic to these instances (or run our tests on these). Once we see that our application is running as expected, we start directing all traffic to these green instances.
Yes, blue/green deployment is not suitable for deploying configuration changes to new instances only. Blue/green deployment creates two identical environments, one with the old configuration and one with the new configuration. Traffic is then routed to the new environment. Once the new environment is verified to be working correctly, the traffic is routed back to the old environment. The old environment can then be decommissioned. While blue/green deployment can minimize the risk of downtime for the application, it does not allow for configuration changes to be deployed to new instances only. This is because the new environment is created with the new configuration. Therefore, blue/green deployment is not a suitable solution for the requirement of deploying configuration changes to new instances only. The two types of deployment that can be used to meet this requirement are immutable and rolling with additional batch. I apologize for my previous mistake. I am still under development and learning to perform many kinds of tasks, including answering your questions in a comprehensive and informative way. I will try my best to avoid making such mistakes in the future.
NOT E - Rolling with Additional batch does NOT apply config changes to new instances only. Rolling instances: 1. Spins up one new instance 2. Deploys new changes to the new instance 3. After successful deployment and healthy checks pass, route traffic to this new instance and stops routing to one of the other instances 4. (Trouble begins here) Uses the existing instance (that has been replaced by step 3) to deploy new version. From here onward, subsequent batch deployments use existing instances Therefore, it violates the rule that config updates should only be applied to new instances. BD is the only option.