Migrate Your AWS Site-to-Site VPN Connections from a Virtual Private Gateway to an AWS Transit Gateway
We are excited to announce AWS Site-to-Site Virtual Private Network (VPN) connections can now be moved from a virtual private gateway to an AWS Transit Gateway without having to make any changes on your customer gateway. Transit Gateways enable you to easily scale connectivity across thousands of Amazon Virtual Private Clouds (Amazon VPCs), AWS accounts, and on-premises networks.
We are excited to announce AWS Site-to-Site Virtual Private Network (VPN) connections can now be moved from a virtual private gateway to an AWS Transit Gateway without having to make any changes on your customer gateway. Transit Gateways enable you to easily scale connectivity across thousands of Amazon Virtual Private Clouds (Amazon VPCs), AWS accounts, and on-premises networks.
Using the new ModifyVpnConnection API or through the management console, you can update the target gateway of a VPN connection. This preserves the endpoint's IP addresses on AWS, as well as tunnel options such as inside-tunnel classless inter-domain routing (CIDR) and pre-shared keys. Your VPN connection will be temporarily unavailable while we provision the new endpoints. This also allows other gateway transitions, such as AWS Transit Gateway to virtual private gateway, one Transit Gateway to another, or between two virtual private gateways.
This feature is now available in these AWS Regions: US East (N. Virginia), US East (Ohio), US West (Oregon), US West (N. California), EU (Ireland), EU (Frankfurt), EU (London), EU (Paris), Asia Pacific (Singapore), Asia Pacific (Tokyo), Asia Pacific (Sydney), Asia Pacific (Seoul), Asia Pacific (Mumbai), Canada (Central), AWS GovCloud (US), and AWS GovCloud (US-East). For more information about AWS Site-to-Site VPN, see the product page and documentation. For details and pricing information of AWS Transit Gateway, see the product page.