-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
Support tags on NAT Gateways per AZ #1141
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
Comments
This issue has been automatically marked as stale because it has been open 30 days |
Shouldn't be closed, we are still discussing it under the PR! |
This issue has been automatically marked as stale because it has been open 30 days |
It should not be marked as stale! |
This issue has been automatically marked as stale because it has been open 30 days |
This issue was automatically closed because of stale in 10 days |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Is your request related to a new offering from AWS?
No
Is your request related to a problem? Please describe.
No
Describe the solution you'd like.
Be able to specify NAT gateway tags per AZ, just like in other VPC resources.
Describe alternatives you've considered.
There is none from what I have searched.
Additional context
Already resolved by #1140
The text was updated successfully, but these errors were encountered: