1 Answer
- Newest
- Most votes
- Most comments
0
Hello.
I think the answer at the URL below will be helpful.
Your situation is reversed, but what you do is pretty much the same.
https://repost.aws/questions/QUuKuQIvQKTe2GH6c3SdTJlg/vpn-site-to-site-change-from-dynamic-routing-to-static-routing
Create a BGP Site to Site VPN to the same virtual private gateway and link the customer gateway.
Then remove the static route Site to Site VPN.
When deleting a Site to Site VPN with a static route, make sure that the route to the VPC is advertised in BGP before deleting it.
Relevant content
asked 2 years ago
- AWS OFFICIALUpdated 2 years ago

Very thanks for your response.
Do you have any idea about my seanrio?
Is it an error occurring in the AWS console? Creating a customer gateway for BGP in the AWS Management Console? Existing customer gateways cannot be used because they are already tied to a static Site to Site VPN.
Yes, while I was creating BGP site-to-site VPN, that error was given. like below "There already exists a VpnConnection with different tunnel option value IKEVersions between customer gateway and VPN gateway. cgw-id: cgw-0bce22146db4366b19, vgw-id: vgw-fe427123c13c18d4, vpn-id: vpn-24np4ff51d26afebb."
in other hand. i try to create new CGW in same ip and configuration using existing CGW. is doesn't create new CGW it only renams it old CGW name to new name given
is there any best way to migrate static route vpn to bgp route vpn with minimal downtime.