No clean up occurs about aws-transit-vpc HOT 7 CLOSED

For this first version, yes. It's something we would like to add to the solution in a future version, but wanted to get customer feedback about what sort of clean-up workflow they would like (or expect) to have in place for the following reasons:

1. The solution currently automates the "northern" connections to VPCs, but does not automate the "southern" connections to customer networks. We are confident that newly created connections will not break additional customer configuration (because incremental "northern" connections are wrapped in their own VRF). However, we wanted to be careful about removing configurations because it's possible that a combination of adding/removing both automated and custom configuration could have unforeseen consequences.
2. We were not sure what workflow customers would expect for deprovisioning. We thought of the approach you mentioned (e.g. remove the tag or change the tag value to "false"). But would customers prefer to simply delete the VGW rather than specially tag it before deletion?
3. This solution is designed to support multiple accounts, which adds complexity to deprovisioning logic and decisions.

As a simple approach, a spoke VGW could be deleted, which will essentially leave the CSR with unused VRF connections. For some deployments, the extra configuration will be negligible, or could be cleaned up manually if desired.

How would you like clean-up to be triggered? Is simply removing (or modifying) the VGW tag sufficient?

from aws-transit-vpc.

Hi Steve,

Thanks for getting back to me.

I'd imagine clean up being triggered on tag removal, tag value change, or vgw removal would be fine.

from aws-transit-vpc.

Agreed on tag removal or value change.

from aws-transit-vpc.

ditto.... I would also like to see the clean-up triggered on the VGW tag removal.

from aws-transit-vpc.

I created a fork for testing clean-up as well as the ability to configure spoke preferred paths (for active/standby path creation rather than active/active). Clean up will occur if the transit VPC tag does not exist, or if it has any other value rather than the configured value (by default it is transitvpc:spoke = true). Removing the tag or setting the value to "false", , or anything other than "true" will result in the VPN connections for that VGW getting deleted and the tunnel configuration removed from the CSRs.
https://github.com/stevemorad/aws-transit-vpc

After I get some testing feedback, I'll merge the changes back into this repo.

from aws-transit-vpc.

wow @stevemorad thank you very much! Long live the amazon customer obsession.
I'll give this a blast during the week and let you know how I get on.

from aws-transit-vpc.

Updated code has been committed that now provide cleaning up spoke VPCs if the spoke tag does not equal the expected tag value. Also, we added the ability to specify a preferred path if you want to configure the CSRs in an active/standby configuration rather than active/active for each spoke.

from aws-transit-vpc.