AWS eks documentation change
Summary
Corrected grammar ('aren't' to 'are not', 'don't' to 'do not') and fixed IAM ARN formatting in a policy example
Security assessment
Changes are grammatical improvements and code formatting fixes. The IAM policy example modification doesn't alter security semantics - it just corrects placeholder syntax without changing permissions or security implications.
Diff
diff --git a/eks/latest/userguide/ack-troubleshooting.md b/eks/latest/userguide/ack-troubleshooting.md index f8697ef63..ef8a08747 100644 --- a//eks/latest/userguide/ack-troubleshooting.md +++ b//eks/latest/userguide/ack-troubleshooting.md @@ -7 +7 @@ -Capability is ACTIVE but resources aren’t being createdResources created in AWS but not showing in KubernetesCross-account resources not being createdNext steps +Capability is ACTIVE but resources are not being createdResources created in AWS but not showing in KubernetesCross-account resources not being createdNext steps @@ -15,2 +14,0 @@ To contribute to this user guide, choose the **Edit this page on GitHub** link t -This topic provides troubleshooting guidance for the EKS Capability for ACK, including capability health checks, resource status verification, and IAM permission issues. - @@ -19 +17 @@ This topic provides troubleshooting guidance for the EKS Capability for ACK, inc -EKS Capabilities are fully managed and run outside your cluster. You don’t have access to controller logs or controller namespaces. Troubleshooting focuses on capability health, resource status, and IAM configuration. +EKS Capabilities are fully managed and run outside your cluster. You do not have access to controller logs or controller namespaces. Troubleshooting focuses on capability health, resource status, and IAM configuration. @@ -21 +19 @@ EKS Capabilities are fully managed and run outside your cluster. You don’t hav -## Capability is ACTIVE but resources aren’t being created +## Capability is ACTIVE but resources are not being created @@ -23 +21 @@ EKS Capabilities are fully managed and run outside your cluster. You don’t hav -If your ACK capability shows `ACTIVE` status but resources aren’t being created in AWS, check the capability health, resource status, and IAM permissions. +If your ACK capability shows `ACTIVE` status but resources are not being created in AWS, check the capability health, resource status, and IAM permissions. @@ -111 +109 @@ For more on resource adoption, see [ACK concepts](./ack-concepts.html). -If resources aren’t being created in a target AWS account when using IAM Role Selectors, verify the trust relationship and IAMRoleSelector configuration. +If resources are not being created in a target AWS account when using IAM Role Selectors, verify the trust relationship and IAMRoleSelector configuration. @@ -152 +151 @@ Verify that the IAMRoleSelector was successfully matched to your resource by che -If the condition is `False` or missing, the IAMRoleSelector’s namespace selector doesn’t match the resource’s namespace. Verify the selector’s `namespaceSelector` matches your resource’s namespace labels. +If the condition is `False` or missing, the IAMRoleSelector’s namespace selector does not match the resource’s namespace. Verify the selector’s `namespaceSelector` matches your resource’s namespace labels. @@ -165 +164 @@ The Capability Role needs `sts:AssumeRole` and `sts:TagSession` permissions for - "Resource": "arn:aws:iam::[.replaceable]`444455556666`:role/[.replaceable]`cross-account-ack-role`" + "Resource": [.replaceable]`"arn:aws:iam::444455556666:role/cross-account-ack-role"`