-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
ec2: Upgrade NatInstanceProvider #28907
Comments
Yes this is very important. Thank you @tmokmss |
I would like to work on this issue if it's not been worked on yet. But I have some clarifying questions before I can get started with the implementation. Reading the description, it seems that the default
I'm a bit confused on how it relates to the commands you linked in this doc. |
@GavinZZ The old NAT instance AMI is published from AWS and it's based on the deprecated Amazon Linux. We were able to use the AMI to launch an NAT instance without additional configuration. Now, however, there is currently no official "NAT instance AMI" that is under maintenance. Instead we can probably just launch an instance from AL2023 AMI and configure it via EC2 userdata using the commands in the doc. To prevent breaking changes, I guess the old NAT AMI should still remain unchanged. Maybe we need |
Makes sense. Thanks for the clarification. |
### Issue # (if applicable) Closes #28907 ### Reason for this change Current NAT instance image has reached EOL on Dec 31 2023. ### Description of changes If NAT instances are a better match for your use case than NAT gateways, you can create your own NAT AMI from a current version of Amazon Linux as described in [Create a NAT AMI](https://docs.aws.amazon.com/vpc/latest/userguide/VPC_NAT_Instance.html#create-nat-ami). ### Description of how you validated changes New unit and integration tests *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
|
Describe the feature
The current
NatInstanceProvider
uses the AWS official NAT instance AMI, which has already reached EOL on Dec 31 2023.It'd be great if CDK provides an easy way to configure a modern NAT instance.
Use Case
NAT Instances are still popular since they can be much cheaper than NAT Gateways.
Proposed Solution
We can create a NAT instance from AL2023 AMI by using these commands in this doc.
I think CDK can internally use ec2 userdata to configure them and abstract all the complexities away from users.
Other Information
No response
Acknowledgements
CDK version used
2.124.0
Environment details (OS name and version, etc.)
macOS
The text was updated successfully, but these errors were encountered: