AWS eks documentation change
Summary
Updated AWS CLI commands by removing XML-style placeholders (<replaceable> and <literal> tags) and replacing them with plain text variables. Added line breaks for formatting.
Security assessment
Changes are purely cosmetic/documentation formatting improvements. No security vulnerabilities, configurations, or features are mentioned. Modifications only affect example command syntax without altering security implications of the networking setup.
Diff
diff --git a/eks/latest/userguide/hybrid-nodes-networking.md b/eks/latest/userguide/hybrid-nodes-networking.md index f1d44d8d5..7ea0a7e77 100644 --- a//eks/latest/userguide/hybrid-nodes-networking.md +++ b//eks/latest/userguide/hybrid-nodes-networking.md @@ -131 +131 @@ The network interfaces provisioned by Amazon EKS have a description of the forma - --query 'NetworkInterfaces[?(VpcId == <replaceable>VPC_ID</replaceable> && contains(Description,<literal>Amazon EKS</literal>))].PrivateIpAddress' + --query 'NetworkInterfaces[?(VpcId == VPC_ID && contains(Description,Amazon EKS))].PrivateIpAddress' @@ -143 +143,2 @@ The following steps use the AWS CLI. You can also create these resources in the - aws ec2 create-vpc --cidr-block <replaceable>VPC_CIDR</replaceable> + aws ec2 create-vpc --cidr-block VPC_CIDR + @@ -147 +148 @@ The following steps use the AWS CLI. You can also create these resources in the - aws ec2 modify-vpc-attribute --vpc-id <replaceable>VPC_ID</replaceable> --enable-dns-hostnames + aws ec2 modify-vpc-attribute --vpc-id VPC_ID --enable-dns-hostnames @@ -159 +160 @@ Create at least 2 subnets. Amazon EKS uses these subnets for the cluster network - --query 'AvailabilityZones[?(RegionName == <literal>us-west-2</literal>)].ZoneName' + --query 'AvailabilityZones[?(RegionName == us-west-2)].ZoneName' @@ -164,3 +165,4 @@ Create at least 2 subnets. Amazon EKS uses these subnets for the cluster network - --vpc-id <replaceable>VPC_ID</replaceable> \ - --cidr-block <replaceable>SUBNET_CIDR</replaceable> \ - --availability-zone <replaceable>AZ</replaceable> + --vpc-id VPC_ID \ + --cidr-block SUBNET_CIDR \ + --availability-zone AZ + @@ -181,3 +183,4 @@ Run the following command to attach a Transit Gateway. Replace `VPC_ID` with the - --vpc-id <replaceable>VPC_ID</replaceable> \ - --subnet-ids <replaceable>SUBNET_ID1 SUBNET_ID2</replaceable> \ - --transit-gateway-id <replaceable>TGW_ID</replaceable> + --vpc-id VPC_ID \ + --subnet-ids SUBNET_ID1 SUBNET_ID2 \ + --transit-gateway-id TGW_ID + @@ -191,2 +194,3 @@ Run the following command to attach a Transit Gateway. Replace `VPN_ID` with the - --vpn-gateway-id <replaceable>VPN_ID</replaceable> \ - --vpc-id <replaceable>VPC_ID</replaceable> + --vpn-gateway-id VPN_ID \ + --vpc-id VPC_ID + @@ -199 +203,2 @@ You can modify the main route table for the VPC or you can create a custom route - aws ec2 create-route-table --vpc-id <replaceable>VPC_ID</replaceable> + aws ec2 create-route-table --vpc-id VPC_ID + @@ -224,3 +229,4 @@ The examples below show how to create routes for your on-premises node and pod C - --route-table-id <replaceable>RT_ID</replaceable> \ - --destination-cidr-block <replaceable>REMOTE_NODE_CIDR</replaceable> \ - --transit-gateway-id <replaceable>TGW_ID</replaceable> + --route-table-id RT_ID \ + --destination-cidr-block REMOTE_NODE_CIDR \ + --transit-gateway-id TGW_ID + @@ -232,3 +238,4 @@ The examples below show how to create routes for your on-premises node and pod C - --route-table-id <replaceable>RT_ID</replaceable> \ - --destination-cidr-block <replaceable>REMOTE_POD_CIDR</replaceable> \ - --transit-gateway-id <replaceable>TGW_ID</replaceable> + --route-table-id RT_ID \ + --destination-cidr-block REMOTE_POD_CIDR \ + --transit-gateway-id TGW_ID + @@ -243 +250,2 @@ Run the following command for each of the subnets you created in the previous st - aws ec2 associate-route-table --route-table-id <replaceable>RT_ID</replaceable> --subnet-id <replaceable>SUBNET_ID</replaceable> + aws ec2 associate-route-table --route-table-id RT_ID --subnet-id SUBNET_ID + @@ -281 +289 @@ If you need to create additional security groups or modify the automatically cre - --group-name <replaceable>SG_NAME</replaceable> \ + --group-name SG_NAME \ @@ -283 +291,2 @@ If you need to create additional security groups or modify the automatically cre - --vpc-id <replaceable>VPC_ID</replaceable> + --vpc-id VPC_ID + @@ -287 +296 @@ If you need to create additional security groups or modify the automatically cre - --group-id <replaceable>SG_ID</replaceable> \ + --group-id SG_ID \