View a markdown version of this page

IPv6-only Subnets in a Dual Stack Amazon Amazon VPC - Dual Stack and IPv6-only Amazon Amazon VPC Reference Architectures

IPv6-only Subnets in a Dual Stack Amazon Amazon VPC

Publication date: June 23, 2022 (Diagram history)

This architecture shows how to integrate IPv6-only subnets in your dual stack Amazon VPC. IPv6-only subnets can coexist with IPv4-only and dual stack subnets in the same Amazon VPC.

IPv6-only subnets in a dual stack Amazon Amazon VPC architecture

Architecture diagram showing IPv6-only subnets coexisting with IPv4-only and dual stack subnets in an Amazon VPC.

The following numbered items describe the key components in this architecture:

  1. To create IPv6-only subnets, you start with a dual stack Amazon Amazon VPC. The Amazon VPC needs to have a secondary IPv6 CIDR associated with it.

  2. IPv6-only subnets only have an IPv6 CIDR associated with them, and do not need associated IPv4 CIDRs. IPv6-only subnets are bound to an Availability Zone the same as dual stack or IPv4-only subnets.

  3. IPv6-only subnets can coexist in the same Amazon VPC as IPv4-only subnets and dual stack subnets. You can also choose to have dual stack VPCs with IPv6-only subnets, but keep in mind that the primary Amazon VPC CIDR is an IPv4 CIDR.

  4. When you create an Amazon EC2 instance in the IPv6-only subnet, the IPv6 address is either automatically assigned from the subnet CIDR through DHCPv6, or you can manually configure it.

  5. IPv6-only resources in IPv6-only subnets can communicate natively over IPv6 with other IPv6-only resources or dual stack resources in other subnets in the Amazon VPC.

  6. IPv4-only resources in the IPv4-only subnets can communicate natively over IPv4 with other IPv4-only resources or dual stack resources in other subnets in the Amazon VPC.

Note

IPv6-only resources in the IPv6-only subnets cannot communicate with IPv4-only resources in other subnets in the Amazon VPC.

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.

ChangeDescriptionDate

Initial publication

Reference architecture diagram first published.

June 23, 2022

Initial publication

Reference architecture diagram first published.

June 23, 2022

Initial publication

Reference architecture diagram first published.

June 23, 2022

Initial publication

Reference architecture diagram first published.

June 23, 2022

Initial publication

Reference architecture diagram first published.

June 23, 2022

Initial publication

Reference architecture diagram first published.

June 23, 2022

Initial publication

Reference architecture diagram first published.

June 23, 2022

Initial publication

Reference architecture diagram first published.

June 23, 2022

Initial publication

Reference architecture diagram first published.

June 23, 2022

Initial publication

Reference architecture diagram first published.

June 23, 2022

Initial publication

Reference architecture diagram first published.

June 23, 2022

Initial publication

Reference architecture diagram first published.

June 23, 2022

Initial publication

Reference architecture diagram first published.

June 23, 2022

Initial publication

Reference architecture diagram first published.

June 23, 2022

Initial publication

Reference architecture diagram first published.

June 23, 2022

Initial publication

Reference architecture diagram first published.

June 23, 2022

Initial publication

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.