Is there a way to create a VPN with an external IP already defined?

Question

So I need to create a VPN, but every time I do it, I'm getting a new external IP.

Is there a way/configuration/service to use the same IP, like I do it with elastics ips?

Why I need this? I'm not going to maintain my VPN always available, so I'm going to create it and then delete it every time...

I know I can use domains to do it... But is there another way?

Best regards

Eze.

Answer

AWS will allocate two public Outside IP Addresses when the VPN connection is created. It is not possible to choose the Outside IP Address when creating a Site-to-Site VPN connection.

That being said, If you only 'modify' the VPN connection options, the VPN endpoint IP addresses on the AWS side do not change, and the tunnel options do not change. Your VPN connection will be temporarily unavailable for a brief period while the VPN connection is updated.

Answer

But if you use an IaC tools like Terraform, there are reasons where the resource will be replaced by terraform (terraform will delete the resource and create a new one). So a new set of outside IP addresses will be created by AWS. And that would be fatal, because these IPs are configures on the customer side and if they simply change, the VPN will suddenly stop working.

Do I have the possibility to create a feature wish to use an EIP for that?

Is there a way to create a VPN with an external IP already defined?

Relevant content