Closed arongate closed 12 months 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
+1
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
+1 up.
Same issue here - is there a work around for this for the time being?
Yep, I was able to do the following to work around this issue for all of the subnet types (public, private, database) by doing this:
resource "aws_route" "vpn_client_route" {
route_table_id = element(module.vpc.private_route_table_ids, count.index)
destination_cidr_block = "10.0.0.0/24"
transit_gateway_id = <transit gateway id>
}
+1
Same issue here - is there a work around for this for the time being?
Did you get any solution to this?
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
All,
as a workaround, you can move the necessary resources (subnets, route tables, associations) outside the module and control them yourself: https://developer.hashicorp.com/terraform/tutorials/configuration-language/move-config
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
+1
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? No π
Is this functionality available in the AWS provider for Terraform? See CHANGELOG.md, too. Yes β :
Is your request related to a problem? Please describe.
when we have multi subnets one for each availability zone, we actually can't configure routing scope in a the same availability zone as two public or intra subnets will shared the same route table
Describe the solution you'd like.
add flag to create dedicated route table for each subnets. Something like
intra_dedicated_route_table
orpublic_dedicated_route_table
. These variable will defaults tofalse
for backward compatibility reason.Describe alternatives you've considered.
Not using the module.
Additional context
Empty