AWS eks documentation change
Summary
Updated legacy Cloud Provider documentation link to use latest version reference
Security assessment
The change updates a version-specific URL but maintains the same security context about principle of least privilege. No new security guidance or vulnerability fixes are introduced.
Diff
diff --git a/eks/latest/userguide/cross-service-confused-deputy-prevention.md b/eks/latest/userguide/cross-service-confused-deputy-prevention.md index e10b106a8..b492083b8 100644 --- a//eks/latest/userguide/cross-service-confused-deputy-prevention.md +++ b//eks/latest/userguide/cross-service-confused-deputy-prevention.md @@ -33 +33 @@ If the `aws:SourceArn` value does not contain the account ID, such as an Amazon -An Amazon EKS cluster IAM role is required for each cluster. Kubernetes clusters managed by Amazon EKS use this role to manage nodes and the [legacy Cloud Provider](https://kubernetes-sigs.github.io/aws-load-balancer-controller/v2.7/guide/service/annotations/#legacy-cloud-provider) uses this role to create load balancers with Elastic Load Balancing for services. These cluster actions can only affect the same account, so we recommend that you limit each cluster role to that cluster and account. This is a specific application of the AWS recommendation to follow the _principle of least privilege_ in your account. +An Amazon EKS cluster IAM role is required for each cluster. Kubernetes clusters managed by Amazon EKS use this role to manage nodes and the [legacy Cloud Provider](https://kubernetes-sigs.github.io/aws-load-balancer-controller/latest/guide/service/annotations/#legacy-cloud-provider) uses this role to create load balancers with Elastic Load Balancing for services. These cluster actions can only affect the same account, so we recommend that you limit each cluster role to that cluster and account. This is a specific application of the AWS recommendation to follow the _principle of least privilege_ in your account.