(ec2): Update default AmazonLinuxImage to use AMAZON_LINUX_2
See original GitHub issueBreaking Change feature/request.
The ec2.AmazonLinuxImage
defaults to using the latest Amazon Linux image which reached end-of-life at the end of 2020. I’d suggest updating the default image to ec2.AmazonLinuxGeneration.AMAZON_LINUX_2
Environment
- CDK CLI Version: 1.90.0 (build 7edba31)
- Module Version: 1.90.1
- Node.js Version: v15.9.0
- OS: macOS Big Sur 11.2.1
- Language (Version): typescript 4.1.5
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
AWS | Amazon Linux AMI
The Amazon Linux AMI is a supported and maintained Linux image provided by Amazon Web Services for use on Amazon Elastic Compute Cloud...
Read more >Run Amazon Linux 2 as a virtual machine on premises
By default, the Amazon Linux 2 VM image creates an ec2-user user account. You use the user-data configuration file to set the password...
Read more >Amazon Linux - Amazon Elastic Compute Cloud
Amazon Linux is a Linux image provided by AWS for use on Amazon EC2. ... in the Amazon Linux AMI, or in the...
Read more >Amazon Linux AMI FAQs
The Amazon Linux AMI is a supported and maintained Linux image provided by Amazon Web Services for use on Amazon Elastic Compute Cloud...
Read more >Amazon Linux 2 FAQs
AWS provides an Amazon Machine Image (AMI) for Amazon Linux 2 that you can use to launch an instance from the Amazon EC2...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The feature flag mechanism is a good way to achieve this. Adding it to the
FEATURE_FLAGS_EXPIRED
list on thev2-main
branch is the way to go. I’ve captured this here - https://github.com/aws/aws-cdk/blob/master/CONTRIBUTING.md#cdkv2.The only diff between the two branches would be the docs where the the
@default
is documented differently.Anything else we should consider @rix0rrr ?
That sounds like a plan. If we’re going to make this change though, it can’t be in a mad PR dash just before v2 gets released.
The way to do that in a controlled fashion is to add a feature flag which flips the default. We can then change the flag’s default value for v2.
We also need @nija-at in here for a good discussion on how these kinds of defaults changes can be seamlessly merged into v2.