AWS eks documentation change
Summary
Fixed typo in documentation link text from '{aws}' to 'AWS' in EKS Pod Identity comparison table
Security assessment
Change is purely a documentation formatting correction with no security implications. No security features or vulnerabilities are mentioned in the context of this change.
Diff
diff --git a/eks/latest/userguide/service-accounts.md index 27cfde2f3..eee39c919 100644 --- a/eks/latest/userguide/service-accounts.md +++ b/eks/latest/userguide/service-accounts.md @@ -100 +100 @@ Role scalability | EKS Pod Identity doesn’t require users to define trust rel -Role reusability | AWS STS temporary credentials supplied by EKS Pod Identity include role session tags, such as cluster name, namespace, service account name. Role session tags enable administrators to author a single IAM role that can be used with multiple service accounts, with different effective permission, by allowing access to AWS resources based on tags attached to them. This is also called attribute-based access control (ABAC). For more information, see [Grant Pods access to {aws} resources based on tags](./pod-id-abac.html). | AWS STS session tags are not supported. You can reuse a role between clusters but every pod receives all of the permissions of the role. +Role reusability | AWS STS temporary credentials supplied by EKS Pod Identity include role session tags, such as cluster name, namespace, service account name. Role session tags enable administrators to author a single IAM role that can be used with multiple service accounts, with different effective permission, by allowing access to AWS resources based on tags attached to them. This is also called attribute-based access control (ABAC). For more information, see [Grant Pods access to AWS resources based on tags](./pod-id-abac.html). | AWS STS session tags are not supported. You can reuse a role between clusters but every pod receives all of the permissions of the role.