Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VPC now supports private IPv6 via IPAM #595

Open
mkarakas opened this issue Oct 17, 2024 · 1 comment
Open

VPC now supports private IPv6 via IPAM #595

mkarakas opened this issue Oct 17, 2024 · 1 comment
Labels
correction Data is inaccurate

Comments

@mkarakas
Copy link
Contributor

Describe the problem
A clear and concise description of what is wrong with the documentation.

As of August 2024, VPCs now support private IPv6/ULA addresses with IPAM: https://aws.amazon.com/about-aws/whats-new/2024/08/aws-private-ipv6-addressing-vpcs-subnets/

As such below should be reworked:

"VPCs do not support assigning private IPv6 addresses from the Unique Local Address (ULA) range as defined by RFC 4193 (fd00::/8 or fc00::/8). This is true even when you would like to assign an IPv6 CIDR owned by you. Egressing to the internet from Private Subnets is supported by implementing an egress-only internet gateway (EIGW) in a VPC, allowing outbound traffic while blocking all incoming traffic."

References
https://aws.github.io/aws-eks-best-practices/networking/ipv6/

@mkarakas mkarakas added the correction Data is inaccurate label Oct 17, 2024
@dumlutimuralp
Copy link
Contributor

@Tim-AWS you can assign this issue to me. I will be working on it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
correction Data is inaccurate
Projects
None yet
Development

No branches or pull requests

2 participants