People also ask


  • Why can’t I see the public IPv4 address of my instance?

  • Therefore, if you inspect the properties of your network interface on your instance, for example, through ifconfig (Linux) or ipconfig (Windows), the public IPv4 address is not displayed. To determine your instance’s public IPv4 address from an instance, use instance metadata.

  • Can I create a VPC with a private IPv4 address range?

  • You can create a VPC with a publicly routable CIDR block that falls outside of the private IPv4 address ranges specified in RFC 1918. However, for the purposes of this documentation, we refer to private IPv4 addresses (or ‘private IP addresses’) as the IP addresses that are within the IPv4 CIDR range of your VPC.

  • Is there any IPv4 space that is not publicly announced?

  • Besides the original RFC 1918 space (which is now updated to RFC6890 ), there are several other blocks such as 192.0.2.0 that are not announced publicly. Furthermore, it’s possible that someone has valid IPv4 space that just isn’t announced in the public internet.

  • What is a private IPv4 address and how is it allocated?

  • A private IPv4 address is an IP address that’s not reachable over the Internet. You can use private IPv4 addresses for communication between instances in the same VPC. For more information about the standards and specifications of private IPv4 addresses, see RFC 1918. We allocate private IPv4 addresses to instances using DHCP.