AWS eks documentation change
Summary
Updated custom networking documentation link to use official AWS documentation URL
Security assessment
The change only fixes a documentation reference URL and does not introduce or modify security-related content, despite mentioning security requirements in surrounding text.
Diff
diff --git a/eks/latest/best-practices/ipv6.md b/eks/latest/best-practices/ipv6.md index 319631fd5..b2f88f5bd 100644 --- a//eks/latest/best-practices/ipv6.md +++ b//eks/latest/best-practices/ipv6.md @@ -97 +97 @@ Managed node groups automatically calculate the maximum number of Pods for you. -If [custom networking](https://aws.github.io/aws-eks-best-practices/networking/custom-networking/) is currently enabled, Amazon EKS recommends re-evaluating your need for it with IPv6. If you chose to use custom networking to address the IPv4 exhaustion issue, it is no longer necessary with IPv6. If you are utilizing custom networking to satisfy a security requirement, such as a separate network for nodes and Pods, you are encouraged to submit an [EKS roadmap request](https://github.com/aws/containers-roadmap/issues). +If [custom networking](https://docs.aws.amazon.com/eks/latest/best-practices/custom-networking.html) is currently enabled, Amazon EKS recommends re-evaluating your need for it with IPv6. If you chose to use custom networking to address the IPv4 exhaustion issue, it is no longer necessary with IPv6. If you are utilizing custom networking to satisfy a security requirement, such as a separate network for nodes and Pods, you are encouraged to submit an [EKS roadmap request](https://github.com/aws/containers-roadmap/issues).