Closed gfawcett22 closed 1 year ago
Thanks for opening this issue. We are investigating this issue.
In v3.1 we do not support changes to main route table. By design we remove the routes from the explicit route table associated with the subnet where the user deletes the "Attach-to-tgw" tag.
This is a valid behavior for the subnets associated with a single main route table.
Describe the bug
If a VPC has multiple subnets attached to the TGW via the
Attach-to-tgw
tag and one of the tags are removed to remove a single subnet, the default route for the VPC is removed even though additional subnets are still attached to the TGW.To Reproduce
Attach-to-tgw
tag0.0.0.0/0
in the VPC route table and multiple subnets are attached to the TGW.Attach-to-tgw
tag from a single subnetExpected behavior
Default Route is only removed when all subnets are detached.
Please complete the following information about the solution:
To get the version of the solution, you can look at the description of the created CloudFormation stack. For example, "(SO0009) - The AWS CloudFormation template for deployment of the aws-centralized-logging. Version v1.0.0". You can also find the version from releases
Screenshots If applicable, add screenshots to help explain your problem (please DO NOT include sensitive information).
Additional context The error is being caused here in the vpc_handler. I'm wondering if
self.event.get("Action") == "RemoveSubnet"
should not be there.