- Newest
- Most votes
- Most comments
Hi Sankar,
unfortunately you currently cannot change the AMI for a running EMR cluster.
While EMR does not have any provisions to apply patches on running instances, it can however run a bootstrap action where you can run an "yum update" or install required patches. Please note that bootstrap is only executed at the instance launch time. Regardless, EMR does run "yum update" for critical and security patches at the time of instance launch, whether that is at the time of cluster creation or on the new instances during a cluster resize.
However, AMI selected at the time of cluster launch will not be updated to the latest available AMI, for that you would have to relaunch the EMR cluster. Hence, the recommendation would be to use short lived EMR clusters wherever feasible.
Hi Ben,
Thank you for your clarification. I believe that, the configuration (AMI and other details) are stored (you may call as meta data) some place while provision emr cluster. that only used for managed auto-scale time.
can you share, where can i see this details in EMR cluster or some place?
Thanks, Sankar. R.
Relevant content
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago