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