Use Amazon Linux 2 AMI with working cloud init #995
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
There's an issue with the more recent 20220218 release that instances using AWS Nitro to fail to run cloud-init. We'll revert this commit when a fix is issued to the latest AMI
pda
approved these changes
Mar 2, 2022
| "source_ami_filter": { | ||
| "filters": { | ||
| "name": "amzn2-ami-hvm-2.0.*-gp2", | ||
| "name": "amzn2-ami-hvm-2.0.20220207.1-{{user `arch`}}-gp2", |
Member
There was a problem hiding this comment.
Assuming that 2.0.20220207.1 segment is the same for all arch that we support (which I'm fairly happy to assume) then that looks good as a temporary solve 👍🏼
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There's an issue confirmed by AWS support with the more recent 20220218 release where instances using AWS Nitro to fail to run cloud-init, so this PR adjusts our Packer AMI build process to use the 20220207 AL2 AMI as the base image, which doesn't have the issue.
We'll revert this PR when AWS support have confirmed that the issue is resolved.