Dual Stack Amazon Amazon VPC Internet Connectivity
Publication date: June 23, 2022 (Diagram history)
This architecture shows how to enable IPv4 and IPv6 internet connectivity for your Amazon Amazon VPC. It demonstrates how to configure public and private subnets with dual stack addressing, using an internet gateway for public connectivity and an egress-only internet gateway for private IPv6 outbound access.
Dual stack Amazon Amazon VPC internet connectivity architecture
The following numbered items describe the key components in this architecture:
-
Associate an IPv6 Classless Inter-Domain Routing (CIDR) block to your Amazon Amazon VPC. This can be an AWS-assigned CIDR, or part of a Bring Your Own IPv6 Addresses (BYOIPv6) pool.
-
Associate an egress-only internet gateway (EIGW) to the Amazon VPC. This is the target for the IPv6 default route of private dual stack subnets.
-
Compute resources in public dual stack subnets use the internet gateway for dual-stack IPv4 and IPv6 internet connectivity. They can directly initiate outbound internet connections and accept inbound internet connections, to and from IPv4 and IPv6 hosts in the internet, using their associated Elastic IPv4 address or IPv6 addresses from the subnet CIDR. Note that security groups must allow both IPv4 and IPv6 traffic.
-
Resources in private dual stack subnets use the public NAT gateway in each Availability Zone for outbound IPv4 internet connectivity. The NAT gateway allows only outbound IPv4 connections to be opened from private Amazon Elastic Compute Cloud instances to internet IPv4 destinations, and the associated return traffic.
-
The NAT gateways send the translated IPv4 packets to the internet gateway, which sends the traffic out to the internet, to the respective IPv4 destinations.
-
Resources in private dual stack subnets use the egress-only internet gateway for outbound IPv6 internet connectivity. The egress-only internet gateway allows only outbound IPv6 connections to be opened from private Amazon EC2 instances to internet IPv6 destinations, and the associated return traffic.
Further reading
For additional information, see the following resources:
Diagram history
To be notified about updates to this reference architecture diagram, subscribe to the RSS feed.
| Change | Description | Date |
|---|---|---|
Initial publication | Reference architecture diagram first published. | June 23, 2022 |
Reference architecture diagram first published. | June 23, 2022 | |
Reference architecture diagram first published. | June 23, 2022 | |
Reference architecture diagram first published. | June 23, 2022 | |
Reference architecture diagram first published. | June 23, 2022 | |
Reference architecture diagram first published. | June 23, 2022 | |
Reference architecture diagram first published. | June 23, 2022 | |
Reference architecture diagram first published. | June 23, 2022 | |
Reference architecture diagram first published. | June 23, 2022 | |
Reference architecture diagram first published. | June 23, 2022 | |
Reference architecture diagram first published. | June 23, 2022 | |
Reference architecture diagram first published. | June 23, 2022 | |
Reference architecture diagram first published. | June 23, 2022 | |
Reference architecture diagram first published. | June 23, 2022 | |
Reference architecture diagram first published. | June 23, 2022 | |
Reference architecture diagram first published. | June 23, 2022 | |
Reference architecture diagram first published. | June 23, 2022 |
Note
To subscribe to RSS updates, you must have an RSS plugin enabled for the browser you are using.
