Networking | AWS Reference Notes

This page was generated from content adapted from the

Regions and Zones

Considerations Some AWS resources might not be available in all Regions. Ensure that you can create the resources that you need in the desired Regions before you launch an instance.
Considerations

Note 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.
Note Instances that access other instances through their public NAT IP address are charged for regional or Internet data transfer, depending on whether the instances are in the same Region.
Considerations

Note Changing the subnet settings doesn't change the configuration of EC2 instances that are already launched in the subnet.
Important To change the Use resource based naming as guest OS hostname setting, you must first stop the instance. To change the Answer DNS hostname IPv4 (A record) request or Answer DNS hostname IPv6 (AAAA record) requests settings, you don't have to stop the instance. To modify any of the settings for non-EBS backed EC2 instance types, you cannot stop the instance. You must terminate the instance and launch a new instance with the desired Hostname type and DNS Hostname configurations.

Note The following steps describe how to bring your own IP address range for use in Amazon EC2 only. For steps to bring your own IP address range for use in AWS Global Accelerator, see in the AWS Global Accelerator Developer Guide.
Note A ROA is not required for non-publicly advertised IPv6 address space.
Note The Common Name is not needed for AWS provisioning. It can be any internal or public domain name.
Important If you are creating a ROA object for Amazon VPC IP Address Manager (IPAM), when you create the ROAs, for IPv4 CIDRs you must set the maximum length of an IP address prefix to /24. For IPv6 CIDRs, if you are adding them to an advertisable pool, the maximum length of an IP address prefix must be /48. This ensures that you have full flexibility to divide your public IP address across AWS Regions. IPAM enforces the maximum length you set. For more information about BYOIP addresses to IPAM, see in the Amazon VPC IPAM User Guide.
Note This step is not required for non-publicly advertised IPv6 address space.
Important You can only specify whether an address range is publicly advertised during provisioning. You cannot change the advertisable status later on.

Note The OS-bypass capabilities of EFAs are not supported on Windows instances. If you attach an EFA to a Windows instance, the instance functions as an Elastic Network Adapter, without the added EFA capabilities.
Note Ubuntu 20.04 supports peer direct support when used with dl1.24xlarge instances.

Note You can tag a placement group on creation using the command line tools only.

Important Path MTU Discovery does not guarantee that jumbo frames will not be dropped by some routers. An internet gateway in your VPC will forward packets up to 1500 bytes only. 1500 MTU packets are recommended for internet traffic.