AWS eks documentation change
Summary
Updated command examples with standardized placeholders and fixed error message formatting
Security assessment
Changes are documentation improvements (placeholder consistency, error message formatting) without security implications. No vulnerabilities or security features addressed.
Diff
diff --git a/eks/latest/userguide/hybrid-nodes-troubleshooting.md b/eks/latest/userguide/hybrid-nodes-troubleshooting.md index db5a43fa6..ff4e44caa 100644 --- a//eks/latest/userguide/hybrid-nodes-troubleshooting.md +++ b//eks/latest/userguide/hybrid-nodes-troubleshooting.md @@ -49,2 +49 @@ When running `nodeadm install`, if you see issues at various stages of the insta - nodeadm install K8S_VERSION --credential-provider CREDS_PROVIDER --timeout 20m0s - + nodeadm install K8S_VERSION --credential-provider CREDS_PROVIDER --timeout <replaceable>20m0s</replaceable> @@ -94 +93 @@ Confirm that you’ve properly configured your `RemoteNodeNetworks` to include a - aws eks describe-cluster --name CLUSTER_NAME --region REGION_NAME --query cluster.remoteNetworkConfig.remoteNodeNetworks + aws eks describe-cluster --name <replaceable>CLUSTER_NAME</replaceable> --region <literal>REGION_NAME</literal> --query cluster.remoteNetworkConfig.remoteNodeNetworks @@ -215,2 +214 @@ Run `nodeadm debug` from your hybrid nodes to validate networking and credential - kubectl describe node NODE_NAME - + kubectl describe node <replaceable>NODE_NAME</replaceable> @@ -226,2 +224 @@ Run `nodeadm debug` from your hybrid nodes to validate networking and credential - kubectl describe pod POD_NAME - + kubectl describe pod <replaceable>POD_NAME</replaceable> @@ -232,2 +229 @@ Run `nodeadm debug` from your hybrid nodes to validate networking and credential - kubectl logs POD_NAME - + kubectl logs <replaceable>POD_NAME</replaceable> @@ -451 +447 @@ For both AWS SSM hybrid activations and AWS IAM Roles Anywhere, you can validate - "Arn": "arn:aws:sts::<aws-account-id>:assumed-role/<hybrid-nodes-iam-role/<node-name>" + "Arn": "<shared id="region.arn"/>sts::<aws-account-id>:assumed-role/<hybrid-nodes-iam-role/<node-name>" @@ -491,2 +487 @@ You can check the connection status of the instances that are registered with SS - aws ssm get-connection-status --target mi-012345678abcdefgh - + aws ssm get-connection-status --target <replaceable>mi-012345678abcdefgh</replaceable> @@ -506 +501 @@ If you see an error registering your instance with AWS SSM, confirm the `region` - ERROR Registration failed due to error registering the instance with AWS SSM. InvalidActivation + ERROR Registration failed due to error registering the instance with <shared id="AWS"/> SSM. InvalidActivation @@ -530 +525 @@ When running `nodeadm init`, if you see an error registering the instance with S - ERROR Registration failed due to error registering the instance with AWS SSM. ActivationExpired + ERROR Registration failed due to error registering the instance with <shared id="AWS"/> SSM. ActivationExpired