Closed tjhiggins closed 1 year ago
This issue has been automatically marked as stale because it has been open 30 days with no activity. Remove stale label or comment or this issue will be closed in 10 days
A welcome feature
This issue has been automatically marked as stale because it has been open 30 days with no activity. Remove stale label or comment or this issue will be closed in 10 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?
Yes, but it is supported by Terraform already: https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/nat_gateway
Is your request related to a problem? Please describe.
We need to be able to route otherwise unrouteable backend space through private RFC1918 "frontend" NAT GWs.
Re-opening since the previous feature request was closed without resolution: https://github.com/terraform-aws-modules/terraform-aws-vpc/issues/694
Describe the solution you'd like.
We would like to be able to specify connectivity_type = "private" When creating a NAT GW. We would like the backend route tables to route through that Private NAT GW. It appears we can already chose not to create an Internet Gateway, but would like to use a Transit Gateway, but that could be a separately configured item.
Describe alternatives you've considered.
We've considered manually creating the Transit GW & NAT GW pieces in this situation, but would prefer to have as much of these deployments as possible in TF