Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

Change AMI used for autoscaling

Change AMI used for autoscaling

New Contributor

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!

4 REPLIES 4

Re: Change AMI used for autoscaling

Expert Contributor

Hi,

This will be a new feature in CB 2.8 and will work exactly as you've described.

Re: Change AMI used for autoscaling

New Contributor

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

Re: Change AMI used for autoscaling

Expert Contributor

Really soon, hopefully in August.

Re: Change AMI used for autoscaling

@Matt Cable

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:

  • notice the AMI is of your custom, updated AMI and the original AMI
  • for each region you use, search the available LaunchConfigurations in the given region created with the original AMI
  • create a copy based on each found such LaunchConfiguration, with two differences:
    • The name should be renames
    • The ImageId should be set to the id of your new AMI
  • Search for all the AutoScalingGroups created with the previously found LaunchConfiguration
  • Update the found AutoScalingGroup by replacing the original LaunchConfiguration to the newly created one with the migrated AMI-id
  • Deletes the original LaunchConfiguration

After these steps, all your subsequent upscales will use your new AMI.

Hope this helps!

Don't have an account?
Coming from Hortonworks? Activate your account here