We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Downsides: the resulting AMI ends up in a non-deterministic state from build to build.
Upsides: the resulting AMI always has up to date packages, including security-relevant ones like openssl.
openssl
Thoughts?
The text was updated successfully, but these errors were encountered:
Is it bad practice to execute these commands in the user-data of an instance using the resulting AMI?
Sorry, something went wrong.
@jzonthemtn - I wouldn't say it's bad practice, just be sure you're aware of the impacts.
The big ones being:
All three work against the benefits of 'baking' an AMI in the first place.
Thanks, @ozzyjohnson!
No branches or pull requests
Downsides: the resulting AMI ends up in a non-deterministic state from build to build.
Upsides: the resulting AMI always has up to date packages, including security-relevant ones like
openssl
.Thoughts?
The text was updated successfully, but these errors were encountered: