The Network Orchestration for AWS Transit Gateway solution automates the process of setting up and managing transit networks in distributed AWS environments. It creates a web interface to help control, audit, and approve (transit) network changes.
This creates an issue in automating association and propagation of VPN attachments using CloudFormation.
It would be really helpful if STNO can handle VPN attachments as well similar to Subnets (support for Associate-with and Propagate-to tags and EventBridge events).
Currently Cloudformation has an open issue https://github.com/aws-cloudformation/aws-cloudformation-coverage-roadmap/issues/308 where Transit Gateway attachment ID for VPN is not exposed on AWS::EC2::VPCEndpoint resource attached to Transit Gateway.
This creates an issue in automating association and propagation of VPN attachments using CloudFormation.
It would be really helpful if STNO can handle VPN attachments as well similar to Subnets (support for Associate-with and Propagate-to tags and EventBridge events).