AWS eks documentation change
Summary
Replaced placeholders in troubleshooting commands with concrete examples and fixed ARN formatting
Security assessment
Changes are limited to example command syntax improvements (e.g., replacing <replaceable> tags). No security weaknesses or new security features are documented. The updates maintain existing troubleshooting procedures without security implications.
Diff
diff --git a/eks/latest/userguide/argocd-troubleshooting.md b/eks/latest/userguide/argocd-troubleshooting.md index d6cc27480..f99e8b977 100644 --- a//eks/latest/userguide/argocd-troubleshooting.md +++ b//eks/latest/userguide/argocd-troubleshooting.md @@ -122 +122 @@ If an application shows `Progressing` but never reaches `Healthy`, check the app - kubectl get secret <replaceable>cluster-secret-name</replaceable> -n argocd -o yaml + kubectl get secret cluster-secret-name -n argocd -o yaml @@ -134,2 +134,2 @@ Verify the IAM Capability Role has CodeCommit permissions: - aws iam list-attached-role-policies --role-name <replaceable>my-argocd-capability-role</replaceable> - aws iam list-role-policies --role-name <replaceable>my-argocd-capability-role</replaceable> + aws iam list-attached-role-policies --role-name my-argocd-capability-role + aws iam list-role-policies --role-name my-argocd-capability-role @@ -138 +138,2 @@ Verify the IAM Capability Role has CodeCommit permissions: - aws iam get-role-policy --role-name <replaceable>my-argocd-capability-role</replaceable> --policy-name <replaceable>policy-name</replaceable> + aws iam get-role-policy --role-name my-argocd-capability-role --policy-name policy-name + @@ -148 +149 @@ Verify repository credentials are correctly configured: - kubectl get secret -n argocd <replaceable>repo-secret-name</replaceable> -o yaml + kubectl get secret -n argocd repo-secret-name -o yaml @@ -156 +157 @@ Ensure the secret contains the correct authentication credentials (SSH key, toke - aws iam list-attached-role-policies --role-name <replaceable>my-argocd-capability-role</replaceable> + aws iam list-attached-role-policies --role-name my-argocd-capability-role @@ -159 +160,2 @@ Ensure the secret contains the correct authentication credentials (SSH key, toke - aws secretsmanager get-secret-value --secret-id <replaceable>arn:aws:secretsmanager:region-code:111122223333:secret:my-secret</replaceable> + aws secretsmanager get-secret-value --secret-id arn:aws:secretsmanager:region-code:111122223333:secret:my-secret + @@ -182 +184 @@ On the target cluster, check that the Argo CD Capability Role has an Access Entr - aws eks list-access-entries --cluster-name <replaceable>target-cluster</replaceable> + aws eks list-access-entries --cluster-name target-cluster @@ -186,2 +188,3 @@ On the target cluster, check that the Argo CD Capability Role has an Access Entr - --cluster-name <replaceable>target-cluster</replaceable> \ - --principal-arn arn:aws:iam::[.replaceable]<literal>111122223333</literal>:role/<replaceable>my-argocd-capability-role</replaceable> + --cluster-name target-cluster \ + --principal-arn arn:aws:iam::[.replaceable]111122223333:role/my-argocd-capability-role +