AWS eks documentation change
Summary
Updated placeholders in commands and fixed URL formatting
Security assessment
Routine documentation cleanup. No security-related content added or modified. Changes improve clarity but don't affect security posture.
Diff
diff --git a/eks/latest/userguide/argocd-troubleshooting.md b/eks/latest/userguide/argocd-troubleshooting.md index 558b93fa8..6d4b04bfe 100644 --- a//eks/latest/userguide/argocd-troubleshooting.md +++ b//eks/latest/userguide/argocd-troubleshooting.md @@ -29 +29 @@ You can view capability health and status issues in the EKS console or using the - 1. Open the Amazon EKS console at [https://console.aws.amazon.com/eks/home#/clusters](https://console.aws.amazon.com/eks/home#/clusters). + 1. Open the Amazon EKS console at https://console.aws.amazon.com/eks/home#/clusters. @@ -122 +122 @@ If an application shows `Progressing` but never reaches `Healthy`, check the app - kubectl get secret cluster-secret-name -n argocd -o yaml + kubectl get secret <replaceable>cluster-secret-name</replaceable> -n argocd -o yaml @@ -134,2 +134,2 @@ Verify the IAM Capability Role has CodeCommit permissions: - aws iam list-attached-role-policies --role-name my-argocd-capability-role - aws iam list-role-policies --role-name my-argocd-capability-role + 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> @@ -138,2 +138 @@ Verify the IAM Capability Role has CodeCommit permissions: - aws iam get-role-policy --role-name my-argocd-capability-role --policy-name policy-name - + aws iam get-role-policy --role-name <replaceable>my-argocd-capability-role</replaceable> --policy-name <replaceable>policy-name</replaceable> @@ -149 +148 @@ Verify repository credentials are correctly configured: - kubectl get secret -n argocd repo-secret-name -o yaml + kubectl get secret -n argocd <replaceable>repo-secret-name</replaceable> -o yaml @@ -157 +156 @@ Ensure the secret contains the correct authentication credentials (SSH key, toke - aws iam list-attached-role-policies --role-name my-argocd-capability-role + aws iam list-attached-role-policies --role-name <replaceable>my-argocd-capability-role</replaceable> @@ -160,2 +159 @@ Ensure the secret contains the correct authentication credentials (SSH key, toke - aws secretsmanager get-secret-value --secret-id arn:aws:secretsmanager:region-code:111122223333:secret:my-secret - + aws secretsmanager get-secret-value --secret-id <replaceable>arn:aws:secretsmanager:region-code:111122223333:secret:my-secret</replaceable> @@ -184 +182 @@ On the target cluster, check that the Argo CD Capability Role has an Access Entr - aws eks list-access-entries --cluster-name target-cluster + aws eks list-access-entries --cluster-name <replaceable>target-cluster</replaceable> @@ -188,3 +186,2 @@ On the target cluster, check that the Argo CD Capability Role has an Access Entr - --cluster-name target-cluster \ - --principal-arn arn:aws:iam::[.replaceable]111122223333:role/my-argocd-capability-role - + --cluster-name <replaceable>target-cluster</replaceable> \ + --principal-arn arn:aws:iam::[.replaceable]<literal>111122223333</literal>:role/<replaceable>my-argocd-capability-role</replaceable>