Is it possible to assign a public IP range to your VPC?
We have a need to use a third party vendor to manage a new VPC instance that's also owned & managed by the same vendor.
We'll then establish a VPN tunnel to the VPC.
Our preference is for the vendor to assign a public range that they already own, instead of finding a private range in the RFC1918, so that we don't need to worry about conflict, or NAT.
However, vendor's now saying it's not possible to assign a public IP range to the VPC.
I looked at the AWS user guide, and it also seems to say you can only assign public IP to Internet facing interfaces.
http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/vpc-ip-addressing.html
Was wondering if anyone has actually made this work? (using public IP that you own within your AWS VPC instance for internal/VPN communications)
TIA
We have a need to use a third party vendor to manage a new VPC instance that's also owned & managed by the same vendor.
We'll then establish a VPN tunnel to the VPC.
Our preference is for the vendor to assign a public range that they already own, instead of finding a private range in the RFC1918, so that we don't need to worry about conflict, or NAT.
However, vendor's now saying it's not possible to assign a public IP range to the VPC.
I looked at the AWS user guide, and it also seems to say you can only assign public IP to Internet facing interfaces.
http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/vpc-ip-addressing.html
Was wondering if anyone has actually made this work? (using public IP that you own within your AWS VPC instance for internal/VPN communications)
TIA
Facebook
Twitter