Allow passing in the transit_gateway_id to the module so that we can allow traffic to and through multiple VPCs with single site-to-site vpn.
Expected Behavior
Allow traffic to flow through to multiple VPCs without the need to setup multiple site-to-site vpns for each vpc because every vpn gateway only is attached to single vpc.
Use Case
Currently we cannot setup a VPN with transit gateway id, we can only setup with vpn virtual private gateway which is only attached to one 1 VPC. If we allow transit_gateway_id to be set then we can allow traffic to multiple vpcs via site-to-site vpn because its possible to attach multiple vpcs to single transit gateway.
Have a question? Please checkout our Slack Community or visit our Slack Archive.
Describe the Feature
Allow passing in the
transit_gateway_idto the module so that we can allow traffic to and through multiple VPCs with single site-to-site vpn.Expected Behavior
Allow traffic to flow through to multiple VPCs without the need to setup multiple site-to-site vpns for each vpc because every vpn gateway only is attached to single vpc.
Use Case
Currently we cannot setup a VPN with transit gateway id, we can only setup with vpn virtual private gateway which is only attached to one 1 VPC. If we allow
transit_gateway_idto be set then we can allow traffic to multiple vpcs via site-to-site vpn because its possible to attach multiple vpcs to single transit gateway.Describe Ideal Solution
We can allow passing in just
transit_gateway_idand let user setup transit-gateway outside of the module using the https://github.com/cloudposse/terraform-aws-transit-gatewayAlternatives Considered
Explain what alternative solutions or features you've considered.
Additional Context
In the
resource "aws_vpn_connection"transit_gateway_id - (Optional) The ID of the EC2 Transit Gateway.