Created 08-10-2018 02:02 PM
Is it possible to change the AMI that will be used when scaling a cluster through Cloudbreak?
Here's the longer scenario:
- Using a custom AMI that has various hardening changes applied, let's call it AMI-11111
- I build a cluster using this AMI, everything is good.
- Over time, we apply various OS patches, primarily to address security vulnerabilities.
- If we need to scale the cluster in the future, it will use the original AMI, which will have the vulnerabilities. Instead, would prefer to use an updated AMI (i.e AMI-22222) that already has the security patches applied.
Is this possible? Or is there a better way to handle this scenario?
Thanks!
Created 08-10-2018 02:27 PM
Hi,
This will be a new feature in CB 2.8 and will work exactly as you've described.
Created 08-10-2018 02:46 PM
Nice! Is there a ballpark estimate on when 2.8 will be available? Not looking for an exact date or anything, just a sense for when it might be out. Thanks again
Created 08-10-2018 02:49 PM
Really soon, hopefully in August.
Created 08-13-2018 08:15 AM
If you are willing to complete some very easy manual steps, there is another way to go, as Cloudbreak uses separate autoscaling groups for each hostgroup:
You should:
After these steps, all your subsequent upscales will use your new AMI.
Hope this helps!