AWS eks documentation change
Summary
Updated link text from 'Control network access to cluster API server endpoint' to 'Cluster API server endpoint'
Security assessment
This is a documentation link text update with no changes to security recommendations. The guidance about enabling private endpoints remains unchanged.
Diff
diff --git a/eks/latest/userguide/fargate-getting-started.md b/eks/latest/userguide/fargate-getting-started.md index ac25522c4..8a60f6f9b 100644 --- a//eks/latest/userguide/fargate-getting-started.md +++ b//eks/latest/userguide/fargate-getting-started.md @@ -15 +15 @@ This topic describes how to get started running Pods on AWS Fargate with your Am -If you restrict access to the public endpoint of your cluster using CIDR blocks, we recommend that you also enable private endpoint access. This way, Fargate Pods can communicate with the cluster. Without the private endpoint enabled, the CIDR blocks that you specify for public access must include the outbound sources from your VPC. For more information, see [Control network access to cluster API server endpoint](./cluster-endpoint.html). +If you restrict access to the public endpoint of your cluster using CIDR blocks, we recommend that you also enable private endpoint access. This way, Fargate Pods can communicate with the cluster. Without the private endpoint enabled, the CIDR blocks that you specify for public access must include the outbound sources from your VPC. For more information, see [Cluster API server endpoint](./cluster-endpoint.html).