Thanks, @khorvath. That's helpful. Is there any way to obtain the AWS key pairs that are generated for each cluster? ... View more

This worked on v1.3. Thank you so much, @rdoktorics! I also was able to use the modified aws-images.yml file on the latest build of master without changing any Profile or config, so that can be an option for us to consider as well. Also, is there any documentation for how to pre-configure an AMI for Cloudbreak to be able to deploy nodes successfully? Does it handle the standard HDP pre-config steps at all? We'd like to use RHEL, if possible. Thanks again! Best, Michael ... View more

Hi @rdoktorics, Thanks for the tip. I have tried creating and editing the etc/aws-images.yml file as the docs describe, stopped and restarted Cloudbreak, but it's still defaulting to the same AMI as before (us-west-1:ami-3a750e5a). From what I can tell, the AMI is pulled into the code when the application is built. See here: https://github.com/sequenceiq/cloudbreak/blob/46bc01c25300460a275ef08121d6f4a566ec0db0/cloud-aws/aws-images.tmpl and https://github.com/sequenceiq/cloudbreak/blob/46bc01c25300460a275ef08121d6f4a566ec0db0/cloud-aws/src/main/resources/aws-images.yml In my case, Cloudbreak always uses the AMI defined in version 55 of this atlas: https://atlas.hashicorp.com/api/v1/artifacts/sequenceiq/cloudbreak/amazon.image/search FYI, I am using the pre-built cloud image of Cloudbreak 1.3 in us-west-1 on AWS. Is there something else I'm missing? Best, Michael *EDIT: Added Cloudbreak version for clarity. ... View more