VPN Connection Public IP

0

During the VPN setup, a customer provide us the form request without specifying their VPN router public IP. They will provide their VPN Public IP after we complete the form (including AWS tunnel public IP end point).

As per my understanding when we create site to site VPN connection we do the following:

  1. Setup VGW
  2. Create CGW (including customer VPN router public IP)
  3. Then create the VPN connection by pointing to the corresponding CGW. We can only know the AWS VPN connection public IP.

This will be cyclic process as we don't have customer public IP in the first hand. Any idea how to overcome this situation? Can we reserve or allocate AWS VPN pubic IP first?

AWS
專家
Tedy_T
已提問 4 年前檢視次數 612 次
1 個回答
0
已接受的答案

I think I will go with the following workaround:

  1. Create dummy CGW (with dummy IP public
  2. Create VPN Connection & get the tunnel IP Public to be shared to customer
  3. Later on when customer already share their VPN router IP public, we create 2nd CGW & modify the VPN Connection to pointing to the 2nd CGW.

Just tested this approach and it can be done, we can retain our 2 tunnel IP Public

AWS
專家
Tedy_T
已回答 4 年前

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南