You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 5, 2019. It is now read-only.
EMR 5.7 introduced the possibility of using a custom AMI for launching EMR clusters.
It would be great to take advantage of this to both use up-to-date OS images (currently 5.8.0 uses a fairly stale 2017-03 amazon linux image) as well as potentially speeding up cluster provisioning by baking some or all of the bootstrapping code into the AMI itself.
The text was updated successfully, but these errors were encountered:
This could also be used to roll out new images to stage, test them, then deploy the image to prod (rather than messing with the S3-based bootstrap scripts).
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
EMR 5.7 introduced the possibility of using a custom AMI for launching EMR clusters.
It would be great to take advantage of this to both use up-to-date OS images (currently 5.8.0 uses a fairly stale 2017-03 amazon linux image) as well as potentially speeding up cluster provisioning by baking some or all of the bootstrapping code into the AMI itself.
The text was updated successfully, but these errors were encountered: