• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

public IP space in AWS VPC?

Cooky

Golden Member
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
 
What you're wanting to do doesn't seem possible. You will need to find a private subnet that you're not currently using and give that to your vendor so they can assign that to the newly created VPC and then you can VPN into that.
 
Back
Top