-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
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
aws-ec2: Support Amazon Linux 2023 #24873
Comments
@sharp-pixel , Thanks for reaching out with this feature request. I am marking this as P2 which means our team won't be able to work on it immediately. However if you would like to contribute to making this change, here is contributing guide to get started. We use +1s to help prioritize our work, and would be happy to re-evaluate this issue based on community feedback. You can reach out to the cdk.dev community on Slack to solicit support for re-prioritization. |
I have attempted to make this PR in the past. It seems like the CDK team is unwilling to implement Amazon Linux 2023 via the current enums and classes as it incompatible with the previous way linux 2022 was built. A whole new set of enums and classes will likely have to be built. When you run the integration tests without adding items to the Kernel enum, you will find that Amazon Linux 2023 can't be resolved through SSM as it is using a different kernel version To make things even more interesting with the current implementation, Amazon Linux 2022 instances will actually fail to deploy. During the transition between preview -> general availability, the kernel version was bumped from 5.10 to 5.15 (so the SSM param for 5.10 that is currently being referenced does not exist anymore either). |
Thanks for your input @sktan. I don't see the problem is adding an entry in the Kernel enum though. |
I simply followed https://docs.aws.amazon.com/linux/al2023/ug/get-started.html to get the correct names. |
This PR introduces 3 new methods on `MachineImage` corresponding to the 3 available generations of amazon linux. We will be deprecating the `latestAmazonLinux` method in favor of these separate methods per generation. Each generation is a slightly different format, and having them separate is more clear to the user what `latest` means. closes #21011, closes #24873, closes #23523 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
|
This PR introduces 3 new methods on `MachineImage` corresponding to the 3 available generations of amazon linux. We will be deprecating the `latestAmazonLinux` method in favor of these separate methods per generation. Each generation is a slightly different format, and having them separate is more clear to the user what `latest` means. closes #21011, closes #24873, closes #23523 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
…comment was wrong, 2023 ami not implemented in cdk yet :(
Is there any news? |
Look at the example shown on https://docs.aws.amazon.com/cdk/api/v2/docs/aws-cdk-lib.aws_ec2.AmazonLinux2023Kernel.html |
Describe the feature
Amazon Linux 2023 has been released on March 15, 2023: https://aws.amazon.com/about-aws/whats-new/2023/03/amazon-linux-2023/
Currently, CDK supports Amazon Linux 2022 which was in preview and not a thing anymore.
We should support Amazon Linux 2023 as both latest Amazon Linux version and specifically.
Use Case
Create an EC2 instance with AL2023
Proposed Solution
Add AL2023 to the enumeration of supported Amazon Linux versions.
Use the corresponding AMIs to provision the EC2 instance.
Other Information
No response
Acknowledgements
CDK version used
2.72.0
Environment details (OS name and version, etc.)
macOS 13.3
The text was updated successfully, but these errors were encountered: