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