V1962397029

pgasca · pgasca · commit 5cde0b21f0e6 · 2025-10-29T19:57:12.000Z
diff --git a/latest/ug/manage-access/aws-access/pod-configuration.adoc b/latest/ug/manage-access/aws-access/pod-configuration.adoc
@@ -20,7 +20,7 @@ If a Pod needs to access {aws} services, then you must configure it to use a Kub
 * Version `2.12.3` or later or version `1.27.160` or later of the {aws} Command Line Interface ({aws} CLI) installed and configured on your device or {aws} CloudShell. To check your current version, use `aws --version | cut -d / -f2 | cut -d ' ' -f1`. Package managers such `yum`, `apt-get`, or Homebrew for macOS are often several versions behind the latest version of the {aws} CLI. To install the latest version, see link:cli/latest/userguide/cli-chap-install.html[Installing, updating, and uninstalling the {aws} CLI,type="documentation"] and link:cli/latest/userguide/cli-configure-quickstart.html#cli-configure-quickstart-config[Quick configuration with aws configure,type="documentation"] in the _{aws} Command Line Interface User Guide_. The {aws} CLI version that is installed in {aws} CloudShell might also be several versions behind the latest version. To update it, see link:cloudshell/latest/userguide/vm-specs.html#install-cli-software[Installing {aws} CLI to your home directory,type="documentation"] in the _{aws} CloudShell User Guide_.
 * The `kubectl` command line tool is installed on your device or {aws} CloudShell. The version can be the same as or up to one minor version earlier or later than the Kubernetes version of your cluster. For example, if your cluster version is `1.29`, you can use `kubectl` version `1.28`, `1.29`, or `1.30` with it. To install or upgrade `kubectl`, see <<install-kubectl>>.
 * An existing `kubectl` `config` file that contains your cluster configuration. To create a `kubectl` `config` file, see <<create-kubeconfig>>.
-. Use the following command to create a deployment manifest that you can deploy a Pod to confirm configuration with. Replace the [.replaceable]`example values` with your own values.
+. Use the following command to create a deployment manifest that you can deploy a Pod to confirm configuration with. Replace the example values with your own values.
 +
 [source,yaml,subs="verbatim,attributes"]
 ----
diff --git a/latest/ug/manage-access/aws-access/pod-id-configure-pods.adoc b/latest/ug/manage-access/aws-access/pod-id-configure-pods.adoc
@@ -17,7 +17,7 @@ If a Pod needs to access {aws} services, then you must configure it to use a Kub
 * The latest version of the {aws} CLI installed and configured on your device or {aws} CloudShell. You can check your current version with `aws --version | cut -d / -f2 | cut -d ' ' -f1`. Package managers such `yum`, `apt-get`, or Homebrew for macOS are often several versions behind the latest version of the {aws} CLI. To install the latest version, see link:cli/latest/userguide/cli-chap-install.html[Installing, updating, and uninstalling the {aws} CLI,type="documentation"] and link:cli/latest/userguide/cli-configure-quickstart.html#cli-configure-quickstart-config[Quick configuration with aws configure,type="documentation"] in the {aws} Command Line Interface User Guide. The {aws} CLI version installed in the {aws} CloudShell may also be several versions behind the latest version. To update it, see link:cloudshell/latest/userguide/vm-specs.html#install-cli-software[Installing {aws} CLI to your home directory,type="documentation"] in the {aws} CloudShell User Guide.
 * The `kubectl` command line tool is installed on your device or {aws} CloudShell. The version can be the same as or up to one minor version earlier or later than the Kubernetes version of your cluster. For example, if your cluster version is `1.29`, you can use `kubectl` version `1.28`, `1.29`, or `1.30` with it. To install or upgrade `kubectl`, see <<install-kubectl>>.
 * An existing `kubectl` `config` file that contains your cluster configuration. To create a `kubectl` `config` file, see <<create-kubeconfig>>.
-. Use the following command to create a deployment manifest that you can deploy a Pod to confirm configuration with. Replace the [.replaceable]`example values` with your own values.
+. Use the following command to create a deployment manifest that you can deploy a Pod to confirm configuration with. Replace the example values with your own values.
 +
 [source,yaml,subs="verbatim,attributes"]
 ----
diff --git a/latest/ug/manage-access/k8s-access/auth-configmap.adoc b/latest/ug/manage-access/k8s-access/auth-configmap.adoc
@@ -282,7 +282,7 @@ NOTE: If you receive an error stating "``Error from server (NotFound): configmap
 ** A `mapRoles` section that maps the IAM node instance to Kubernetes groups so that nodes can register themselves with the cluster and the `my-console-viewer-role` IAM role that is mapped to a Kubernetes group that can view all Kubernetes resources for all clusters. For a list of the IAM and Kubernetes group permissions required for the `my-console-viewer-role` IAM role, see <<view-kubernetes-resources-permissions>>.
 ** A `mapUsers` section that maps the `admin` IAM user from the default {aws} account to the `system:masters` Kubernetes group and the `my-user` user from a different {aws} account that is mapped to a Kubernetes group that can view Kubernetes resources for a specific namespace. For a list of the IAM and Kubernetes group permissions required for the `my-user` IAM user, see <<view-kubernetes-resources-permissions>>.
 +
-Add or remove lines as necessary and replace all [.replaceable]`example values` with your own values.
+Add or remove lines as necessary and replace all example values with your own values.
 +
 [source,yaml,subs="verbatim,attributes"]
 ----
diff --git a/latest/ug/manage-access/k8s-access/authenticate-oidc-identity-provider.adoc b/latest/ug/manage-access/k8s-access/authenticate-oidc-identity-provider.adoc
@@ -43,7 +43,7 @@ You can associate an identity provider using `eksctl` or the {aws-management-con
 [#identity-associate-eksctl]
 === Associate an identity provider using eksctl 
 
-. Create a file named [.replaceable]`associate-identity-provider.yaml` with the following contents. Replace the [.replaceable]`example values` with your own. The values in the `identityProviders` section are obtained from your OIDC identity provider. Values are only required for the `name`, `type`, `issuerUrl`, and `clientId` settings under `identityProviders`.
+. Create a file named `associate-identity-provider.yaml` with the following contents. Replace the example values with your own. The values in the `identityProviders` section are obtained from your OIDC identity provider. Values are only required for the `name`, `type`, `issuerUrl`, and `clientId` settings under `identityProviders`.
 +
 [source,yaml,subs="verbatim,attributes"]
 ----
diff --git a/latest/ug/ml/node-efa.adoc b/latest/ug/ml/node-efa.adoc
@@ -83,7 +83,7 @@ us-west-2a    us-west-2c    us-west-2b
 Note the Availability Zones returned for use in later steps. When you deploy nodes to a cluster, your VPC must have subnets with available IP addresses in one of the Availability Zones returned in the output.
 . Create a node group using `eksctl`. You need version `{eksctl-min-version}` or later of the `eksctl` command line tool installed on your device or {aws} CloudShell. To install or update `eksctl`, see https://eksctl.io/installation[Installation] in the `eksctl` documentation.
 +
-.. Copy the following contents to a file named [.replaceable]`efa-cluster.yaml`. Replace the [.replaceable]`example values` with your own. You can replace [.replaceable]`p5.48xlarge` with a different instance, but if you do, make sure that the values for `availabilityZones` are Availability Zones that were returned for the instance type in step 1.
+.. Copy the following contents to a file named [.replaceable]`efa-cluster.yaml`. Replace the example values with your own. You can replace `p5.48xlarge` with a different instance, but if you do, make sure that the values for `availabilityZones` are Availability Zones that were returned for the instance type in step 1.
 +
 [source,yaml,subs="verbatim,attributes"]
 ----
diff --git a/latest/ug/networking/cni-iam-role.adoc b/latest/ug/networking/cni-iam-role.adoc
@@ -138,7 +138,7 @@ aws iam attach-role-policy \
   --policy-arn {arn-aws}iam::111122223333:policy/AmazonEKS_CNI_IPv6_Policy \
   --role-name AmazonEKSVPCCNIRole
 ----
-... Run the following command to annotate the `aws-node` service account with the ARN of the IAM role that you created previously. Replace the [.replaceable]`example values` with your own values.
+... Run the following command to annotate the `aws-node` service account with the ARN of the IAM role that you created previously. Replace the example values with your own values.
 +
 [source,bash,subs="verbatim,attributes"]
 ----
diff --git a/latest/ug/networking/cni-increase-ip-addresses-procedure.adoc b/latest/ug/networking/cni-increase-ip-addresses-procedure.adoc
@@ -59,7 +59,7 @@ IMPORTANT: Managed node groups enforces a maximum number on the value of `maxPod
 +
 Specify the parameters in one of the following options. To determine which option is right for you and what value to provide for it, see https://github.com/aws/amazon-vpc-cni-k8s/blob/master/docs/prefix-and-ip-target.md[WARM_PREFIX_TARGET, WARM_IP_TARGET, and MINIMUM_IP_TARGET] on GitHub.
 +
-You can replace the [.replaceable]`example values` with a value greater than zero.
+You can replace the example values with a value greater than zero.
 +
 *** `WARM_PREFIX_TARGET`
 +
@@ -161,7 +161,7 @@ This can happen due to fragmentation of existing secondary IP addresses spread o
 ----
 kubectl edit configmap -n kube-system amazon-vpc-cni -o yaml
 ----
-.. Replace the [.replaceable]`example values` with a value greater than zero and add the entries that you require to the `data` section of the `ConfigMap`. If you set a value for either `warm-ip-target` or `minimum-ip-target`, the value overrides any value set for `warm-prefix-target`.
+.. Replace the example values with a value greater than zero and add the entries that you require to the `data` section of the `ConfigMap`. If you set a value for either `warm-ip-target` or `minimum-ip-target`, the value overrides any value set for `warm-prefix-target`.
 +
 [source,yaml,subs="verbatim,attributes"]
 ----
diff --git a/latest/ug/networking/deploy-ipv6-cluster.adoc b/latest/ug/networking/deploy-ipv6-cluster.adoc
@@ -138,7 +138,7 @@ aws sts get-caller-identity
 ====
 
 
-Replace all [.replaceable]`example values` in the steps of this procedure with your own values.
+Replace all example values in the steps of this procedure with your own values.
 
 .. Run the following commands to set some variables used in later steps. Replace [.replaceable]`region-code` with the {aws} Region that you want to deploy your resources in. The value can be any {aws} Region that is supported by Amazon EKS. For a list of {aws} Regions, see link:general/latest/gr/eks.html[Amazon EKS endpoints and quotas,type="documentation"] in the {aws} General Reference guide. Replace [.replaceable]`my-cluster` with a name for your cluster. The name can contain only alphanumeric characters (case-sensitive) and hyphens. It must start with an alphanumeric character and can't be longer than 100 characters. The name must be unique within the {aws} Region and {aws} account that you're creating the cluster in. Replace [.replaceable]`my-nodegroup` with a name for your node group. The node group name can't be longer than 63 characters. It must start with letter or digit, but can also include hyphens and underscores for the remaining characters. Replace [.replaceable]`111122223333` with your account ID.
 +
@@ -387,7 +387,7 @@ kube-dns   ClusterIP   fd30:3087:b6c2::a   <none>        53/UDP,53/TCP   57m   k
 .. (Optional) <<sample-deployment,Deploy a sample application>> or deploy the <<aws-load-balancer-controller,{aws} Load Balancer Controller>> and a sample application to load balance HTTP applications with <<alb-ingress>> or network traffic with <<network-load-balancing>> to `IPv6` Pods.
 .. After you've finished with the cluster and nodes that you created for this tutorial, you should clean up the resources that you created with the following commands. Make sure that you're not using any of the resources outside of this tutorial before deleting them.
 +
-... If you're completing this step in a different shell than you completed the previous steps in, set the values of all the variables used in previous steps, replacing the [.replaceable]`example values` with the values you specified when you completed the previous steps. If you're completing this step in the same shell that you completed the previous steps in, skip to the next step.
+... If you're completing this step in a different shell than you completed the previous steps in, set the values of all the variables used in previous steps, replacing the example values with the values you specified when you completed the previous steps. If you're completing this step in the same shell that you completed the previous steps in, skip to the next step.
 +
 [source,bash,subs="verbatim,attributes"]
 ----
diff --git a/latest/ug/networking/lbc-helm.adoc b/latest/ug/networking/lbc-helm.adoc
@@ -19,7 +19,7 @@ For more information, see <<automode>>.
 
 This topic describes how to install the {aws} Load Balancer Controller using Helm, a package manager for Kubernetes, and `eksctl`. The controller is installed with default options. For more information about the controller, including details on configuring it with annotations, see the https://kubernetes-sigs.github.io/aws-load-balancer-controller/[{aws} Load Balancer Controller Documentation] on GitHub.  
 
-In the following steps, replace the [.replaceable]`example values` with your own values.
+In the following steps, replace the example values with your own values.
 
 [#lbc-prereqs]
 == Prerequisites
diff --git a/latest/ug/networking/lbc-manifest.adoc b/latest/ug/networking/lbc-manifest.adoc
@@ -19,7 +19,7 @@ For more information, see <<automode>>.
 
 This topic describes how to install the controller by downloading and applying Kubernetes manifests. You can view the full https://kubernetes-sigs.github.io/aws-load-balancer-controller/latest/[documentation] for the controller on GitHub.  
 
-In the following steps, replace the [.replaceable]`example values` with your own values.
+In the following steps, replace the example values with your own values.
 
 [#lbc-manifest-prereqs]
 == Prerequisites
diff --git a/latest/ug/networking/sg-pods-example-deployment.adoc b/latest/ug/networking/sg-pods-example-deployment.adoc
@@ -60,7 +60,7 @@ kubectl apply -f my-security-group-policy.yaml
 ----
 . Deploy a sample application with a label that matches the [.replaceable]`my-role` value for [.replaceable]`podSelector` that you specified in a previous step.
 +
-.. Copy the following contents to your device. Replace the [.replaceable]`example values` with your own and then run the modified command. If you replace [.replaceable]`my-role`, make sure that it's the same as the value you specified for the selector in a previous step.
+.. Copy the following contents to your device. Replace the example values with your own and then run the modified command. If you replace [.replaceable]`my-role`, make sure that it's the same as the value you specified for the selector in a previous step.
 +
 [source,yaml,subs="verbatim,attributes"]
 ----
diff --git a/latest/ug/nodes/create-managed-node-group.adoc b/latest/ug/nodes/create-managed-node-group.adoc
@@ -115,7 +115,7 @@ For more information, see https://aws.github.io/aws-eks-best-practices/security/
 If you want to block Pod access to IMDS, then specify the necessary settings in the launch template.
 
 [loweralpha]
-.. Copy the following contents to your device. Replace the [.replaceable]`example values` and then run the modified command to create the `eks-nodegroup.yaml` file. Several settings that you specify when deploying without a launch template are moved into the launch template. If you don't specify a `version`, the template's default version is used.
+.. Copy the following contents to your device. Replace the example values and then run the modified command to create the `eks-nodegroup.yaml` file. Several settings that you specify when deploying without a launch template are moved into the launch template. If you don't specify a `version`, the template's default version is used.
 +
 [source,yaml,subs="verbatim,attributes"]
 ----
diff --git a/latest/ug/nodes/delete-managed-node-group.adoc b/latest/ug/nodes/delete-managed-node-group.adoc
@@ -32,14 +32,14 @@ You can delete a managed node group with:
 
 *Delete a managed node group with `eksctl`*
 
-Enter the following command. Replace every [.replaceable]`example value` with your own values.
+Enter the following command. Replace every `<example value>` with your own values.
 
 [source,bash,subs="verbatim,attributes"]
 ----
 eksctl delete nodegroup \
-  --cluster my-cluster \
-  --name my-mng \
-  --region region-code
+  --cluster <my-cluster> \
+  --name <my-mng> \
+  --region <region-code>
 ----
 
 For more options, see https://eksctl.io/usage/nodegroups/#deleting-and-draining-nodegroups[Deleting and draining nodegroups] in the `eksctl` documentation.
@@ -59,16 +59,16 @@ For more options, see https://eksctl.io/usage/nodegroups/#deleting-and-draining-
 *Delete a managed node group with {aws} CLI*
 
 
-. Enter the following command. Replace every [.replaceable]`example value` with your own values.
+. Enter the following command. Replace every `<example value>` with your own values.
 +
 [source,bash,subs="verbatim,attributes"]
 ----
 aws eks delete-nodegroup \
-  --cluster-name my-cluster \
-  --nodegroup-name my-mng \
-  --region region-code
+  --cluster-name <my-cluster> \
+  --nodegroup-name <my-mng> \
+  --region <region-code>
 ----
-. Use the arrow keys on your keyboard to scroll through the response output. Press the `q` key when you're finished.
+. If `cli_pager=` is set in the CLI config, use the arrow keys on your keyboard to scroll through the response output. Press the `q` key when you're finished.
 
 +
 For more options, see the `link:cli/latest/reference/eks/delete-nodegroup.html[delete-nodegroup,type="documentation"]` command in the _{aws} CLI Command Reference_.
diff --git a/latest/ug/nodes/launch-node-bottlerocket.adoc b/latest/ug/nodes/launch-node-bottlerocket.adoc
@@ -46,7 +46,7 @@ eksctl version
 
 For instructions on how to install or upgrade `eksctl`, see https://eksctl.io/installation[Installation] in the `eksctl` documentation.NOTE: This procedure only works for clusters that were created with `eksctl`.
 
-. Copy the following contents to your device. Replace [.replaceable]`my-cluster` with the name of your cluster. The name can contain only alphanumeric characters (case-sensitive) and hyphens. It must start with an alphanumeric character and can't be longer than 100 characters. The name must be unique within the {aws} Region and {aws} account that you're creating the cluster in. Replace [.replaceable]`ng-bottlerocket` with a name for your node group. The node group name can't be longer than 63 characters. It must start with letter or digit, but can also include hyphens and underscores for the remaining characters. To deploy on Arm instances, replace [.replaceable]`m5.large` with an Arm instance type. Replace [.replaceable]`my-ec2-keypair-name` with the name of an Amazon EC2 SSH key pair that you can use to connect using SSH into your nodes with after they launch. If you don't already have an Amazon EC2 key pair, you can create one in the {aws-management-console}. For more information, see link:AWSEC2/latest/UserGuide/ec2-key-pairs.html[Amazon EC2 key pairs,type="documentation"] in the _Amazon EC2 User Guide_. Replace all remaining [.replaceable]`example values` with your own values. Once you've made the replacements, run the modified command to create the `bottlerocket.yaml` file.
+. Copy the following contents to your device. Replace [.replaceable]`my-cluster` with the name of your cluster. The name can contain only alphanumeric characters (case-sensitive) and hyphens. It must start with an alphanumeric character and can't be longer than 100 characters. The name must be unique within the {aws} Region and {aws} account that you're creating the cluster in. Replace [.replaceable]`ng-bottlerocket` with a name for your node group. The node group name can't be longer than 63 characters. It must start with letter or digit, but can also include hyphens and underscores for the remaining characters. To deploy on Arm instances, replace [.replaceable]`m5.large` with an Arm instance type. Replace [.replaceable]`my-ec2-keypair-name` with the name of an Amazon EC2 SSH key pair that you can use to connect using SSH into your nodes with after they launch. If you don't already have an Amazon EC2 key pair, you can create one in the {aws-management-console}. For more information, see link:AWSEC2/latest/UserGuide/ec2-key-pairs.html[Amazon EC2 key pairs,type="documentation"] in the _Amazon EC2 User Guide_. Replace all remaining example values with your own values. Once you've made the replacements, run the modified command to create the `bottlerocket.yaml` file.
 +
 If specifying an Arm Amazon EC2 instance type, then review the considerations in <<arm-ami,Amazon EKS optimized Arm Amazon Linux AMIs>> before deploying. For instructions on how to deploy using a custom AMI, see https://github.com/bottlerocket-os/bottlerocket/blob/develop/BUILDING.md[Building Bottlerocket] on GitHub and https://eksctl.io/usage/custom-ami-support/[Custom AMI support] in the `eksctl` documentation. To deploy a managed node group, deploy a custom AMI using a launch template. For more information, see <<launch-templates>>.
 +
diff --git a/latest/ug/nodes/launch-node-ubuntu.adoc b/latest/ug/nodes/launch-node-ubuntu.adoc
diff --git a/latest/ug/nodes/launch-windows-workers.adoc b/latest/ug/nodes/launch-windows-workers.adoc
diff --git a/latest/ug/outposts/eks-outposts-self-managed-nodes.adoc b/latest/ug/outposts/eks-outposts-self-managed-nodes.adoc
diff --git a/latest/ug/security/enable-kms.adoc b/latest/ug/security/enable-kms.adoc
diff --git a/latest/ug/workloads/alb-ingress.adoc b/latest/ug/workloads/alb-ingress.adoc
diff --git a/latest/ug/workloads/copy-image-to-repository.adoc b/latest/ug/workloads/copy-image-to-repository.adoc
diff --git a/latest/ug/workloads/network-load-balancing.adoc b/latest/ug/workloads/network-load-balancing.adoc

Original file line number	Diff line number	Diff line change
`@@ -20,7 +20,7 @@ If a Pod needs to access {aws} services, then you must configure it to use a Kub`
`20`	`20`	* Version `2.12.3` or later or version `1.27.160` or later of the {aws} Command Line Interface ({aws} CLI) installed and configured on your device or {aws} CloudShell. To check your current version, use `aws --version \| cut -d / -f2 \| cut -d ' ' -f1`. Package managers such `yum`, `apt-get`, or Homebrew for macOS are often several versions behind the latest version of the {aws} CLI. To install the latest version, see link:cli/latest/userguide/cli-chap-install.html[Installing, updating, and uninstalling the {aws} CLI,type="documentation"] and link:cli/latest/userguide/cli-configure-quickstart.html#cli-configure-quickstart-config[Quick configuration with aws configure,type="documentation"] in the _{aws} Command Line Interface User Guide_. The {aws} CLI version that is installed in {aws} CloudShell might also be several versions behind the latest version. To update it, see link:cloudshell/latest/userguide/vm-specs.html#install-cli-software[Installing {aws} CLI to your home directory,type="documentation"] in the _{aws} CloudShell User Guide_.
`21`	`21`	* The `kubectl` command line tool is installed on your device or {aws} CloudShell. The version can be the same as or up to one minor version earlier or later than the Kubernetes version of your cluster. For example, if your cluster version is `1.29`, you can use `kubectl` version `1.28`, `1.29`, or `1.30` with it. To install or upgrade `kubectl`, see <<install-kubectl>>.
`22`	`22`	* An existing `kubectl` `config` file that contains your cluster configuration. To create a `kubectl` `config` file, see <<create-kubeconfig>>.
`23`		-. Use the following command to create a deployment manifest that you can deploy a Pod to confirm configuration with. Replace the [.replaceable]`example values` with your own values.
	`23`	`+. Use the following command to create a deployment manifest that you can deploy a Pod to confirm configuration with. Replace the example values with your own values.`
`24`	`24`	`+`
`25`	`25`	`[source,yaml,subs="verbatim,attributes"]`
`26`	`26`	`----`
Original file line number	Diff line number	Diff line change
`@@ -17,7 +17,7 @@ If a Pod needs to access {aws} services, then you must configure it to use a Kub`
`17`	`17`	* The latest version of the {aws} CLI installed and configured on your device or {aws} CloudShell. You can check your current version with `aws --version \| cut -d / -f2 \| cut -d ' ' -f1`. Package managers such `yum`, `apt-get`, or Homebrew for macOS are often several versions behind the latest version of the {aws} CLI. To install the latest version, see link:cli/latest/userguide/cli-chap-install.html[Installing, updating, and uninstalling the {aws} CLI,type="documentation"] and link:cli/latest/userguide/cli-configure-quickstart.html#cli-configure-quickstart-config[Quick configuration with aws configure,type="documentation"] in the {aws} Command Line Interface User Guide. The {aws} CLI version installed in the {aws} CloudShell may also be several versions behind the latest version. To update it, see link:cloudshell/latest/userguide/vm-specs.html#install-cli-software[Installing {aws} CLI to your home directory,type="documentation"] in the {aws} CloudShell User Guide.
`18`	`18`	* The `kubectl` command line tool is installed on your device or {aws} CloudShell. The version can be the same as or up to one minor version earlier or later than the Kubernetes version of your cluster. For example, if your cluster version is `1.29`, you can use `kubectl` version `1.28`, `1.29`, or `1.30` with it. To install or upgrade `kubectl`, see <<install-kubectl>>.
`19`	`19`	* An existing `kubectl` `config` file that contains your cluster configuration. To create a `kubectl` `config` file, see <<create-kubeconfig>>.
`20`		-. Use the following command to create a deployment manifest that you can deploy a Pod to confirm configuration with. Replace the [.replaceable]`example values` with your own values.
	`20`	`+. Use the following command to create a deployment manifest that you can deploy a Pod to confirm configuration with. Replace the example values with your own values.`
`21`	`21`	`+`
`22`	`22`	`[source,yaml,subs="verbatim,attributes"]`
`23`	`23`	`----`
Original file line number	Diff line number	Diff line change
@@ -282,7 +282,7 @@ NOTE: If you receive an error stating "``Error from server (NotFound): configmap
`282`	`282`	** A `mapRoles` section that maps the IAM node instance to Kubernetes groups so that nodes can register themselves with the cluster and the `my-console-viewer-role` IAM role that is mapped to a Kubernetes group that can view all Kubernetes resources for all clusters. For a list of the IAM and Kubernetes group permissions required for the `my-console-viewer-role` IAM role, see <<view-kubernetes-resources-permissions>>.
`283`	`283`	** A `mapUsers` section that maps the `admin` IAM user from the default {aws} account to the `system:masters` Kubernetes group and the `my-user` user from a different {aws} account that is mapped to a Kubernetes group that can view Kubernetes resources for a specific namespace. For a list of the IAM and Kubernetes group permissions required for the `my-user` IAM user, see <<view-kubernetes-resources-permissions>>.
`284`	`284`	`+`
`285`		-Add or remove lines as necessary and replace all [.replaceable]`example values` with your own values.
	`285`	`+Add or remove lines as necessary and replace all example values with your own values.`
`286`	`286`	`+`
`287`	`287`	`[source,yaml,subs="verbatim,attributes"]`
`288`	`288`	`----`
Original file line number	Diff line number	Diff line change
@@ -43,7 +43,7 @@ You can associate an identity provider using `eksctl` or the {aws-management-con
`43`	`43`	`[#identity-associate-eksctl]`
`44`	`44`	`=== Associate an identity provider using eksctl`
`45`	`45`
`46`		-. Create a file named [.replaceable]`associate-identity-provider.yaml` with the following contents. Replace the [.replaceable]`example values` with your own. The values in the `identityProviders` section are obtained from your OIDC identity provider. Values are only required for the `name`, `type`, `issuerUrl`, and `clientId` settings under `identityProviders`.
	`46`	+. Create a file named `associate-identity-provider.yaml` with the following contents. Replace the example values with your own. The values in the `identityProviders` section are obtained from your OIDC identity provider. Values are only required for the `name`, `type`, `issuerUrl`, and `clientId` settings under `identityProviders`.
`47`	`47`	`+`
`48`	`48`	`[source,yaml,subs="verbatim,attributes"]`
`49`	`49`	`----`
Original file line number	Diff line number	Diff line change
`@@ -83,7 +83,7 @@ us-west-2a us-west-2c us-west-2b`
`83`	`83`	`Note the Availability Zones returned for use in later steps. When you deploy nodes to a cluster, your VPC must have subnets with available IP addresses in one of the Availability Zones returned in the output.`
`84`	`84`	. Create a node group using `eksctl`. You need version `{eksctl-min-version}` or later of the `eksctl` command line tool installed on your device or {aws} CloudShell. To install or update `eksctl`, see https://eksctl.io/installation[Installation] in the `eksctl` documentation.
`85`	`85`	`+`
`86`		-.. Copy the following contents to a file named [.replaceable]`efa-cluster.yaml`. Replace the [.replaceable]`example values` with your own. You can replace [.replaceable]`p5.48xlarge` with a different instance, but if you do, make sure that the values for `availabilityZones` are Availability Zones that were returned for the instance type in step 1.
	`86`	+.. Copy the following contents to a file named [.replaceable]`efa-cluster.yaml`. Replace the example values with your own. You can replace `p5.48xlarge` with a different instance, but if you do, make sure that the values for `availabilityZones` are Availability Zones that were returned for the instance type in step 1.
`87`	`87`	`+`
`88`	`88`	`[source,yaml,subs="verbatim,attributes"]`
`89`	`89`	`----`
Original file line number	Diff line number	Diff line change
`@@ -138,7 +138,7 @@ aws iam attach-role-policy \`
`138`	`138`	`--policy-arn {arn-aws}iam::111122223333:policy/AmazonEKS_CNI_IPv6_Policy \`
`139`	`139`	`--role-name AmazonEKSVPCCNIRole`
`140`	`140`	`----`
`141`		-... Run the following command to annotate the `aws-node` service account with the ARN of the IAM role that you created previously. Replace the [.replaceable]`example values` with your own values.
	`141`	+... Run the following command to annotate the `aws-node` service account with the ARN of the IAM role that you created previously. Replace the example values with your own values.
`142`	`142`	`+`
`143`	`143`	`[source,bash,subs="verbatim,attributes"]`
`144`	`144`	`----`
Original file line number	Diff line number	Diff line change
@@ -59,7 +59,7 @@ IMPORTANT: Managed node groups enforces a maximum number on the value of `maxPod
`59`	`59`	`+`
`60`	`60`	`Specify the parameters in one of the following options. To determine which option is right for you and what value to provide for it, see https://github.com/aws/amazon-vpc-cni-k8s/blob/master/docs/prefix-and-ip-target.md[WARM_PREFIX_TARGET, WARM_IP_TARGET, and MINIMUM_IP_TARGET] on GitHub.`
`61`	`61`	`+`
`62`		-You can replace the [.replaceable]`example values` with a value greater than zero.
	`62`	`+You can replace the example values with a value greater than zero.`
`63`	`63`	`+`
`64`	`64`	*** `WARM_PREFIX_TARGET`
`65`	`65`	`+`
`@@ -161,7 +161,7 @@ This can happen due to fragmentation of existing secondary IP addresses spread o`
`161`	`161`	`----`
`162`	`162`	`kubectl edit configmap -n kube-system amazon-vpc-cni -o yaml`
`163`	`163`	`----`
`164`		-.. Replace the [.replaceable]`example values` with a value greater than zero and add the entries that you require to the `data` section of the `ConfigMap`. If you set a value for either `warm-ip-target` or `minimum-ip-target`, the value overrides any value set for `warm-prefix-target`.
	`164`	+.. Replace the example values with a value greater than zero and add the entries that you require to the `data` section of the `ConfigMap`. If you set a value for either `warm-ip-target` or `minimum-ip-target`, the value overrides any value set for `warm-prefix-target`.
`165`	`165`	`+`
`166`	`166`	`[source,yaml,subs="verbatim,attributes"]`
`167`	`167`	`----`
Original file line number	Diff line number	Diff line change
`@@ -138,7 +138,7 @@ aws sts get-caller-identity`
`138`	`138`	`====`
`139`	`139`
`140`	`140`
`141`		-Replace all [.replaceable]`example values` in the steps of this procedure with your own values.
	`141`	`+Replace all example values in the steps of this procedure with your own values.`
`142`	`142`
`143`	`143`	.. Run the following commands to set some variables used in later steps. Replace [.replaceable]`region-code` with the {aws} Region that you want to deploy your resources in. The value can be any {aws} Region that is supported by Amazon EKS. For a list of {aws} Regions, see link:general/latest/gr/eks.html[Amazon EKS endpoints and quotas,type="documentation"] in the {aws} General Reference guide. Replace [.replaceable]`my-cluster` with a name for your cluster. The name can contain only alphanumeric characters (case-sensitive) and hyphens. It must start with an alphanumeric character and can't be longer than 100 characters. The name must be unique within the {aws} Region and {aws} account that you're creating the cluster in. Replace [.replaceable]`my-nodegroup` with a name for your node group. The node group name can't be longer than 63 characters. It must start with letter or digit, but can also include hyphens and underscores for the remaining characters. Replace [.replaceable]`111122223333` with your account ID.
`144`	`144`	`+`
`@@ -387,7 +387,7 @@ kube-dns ClusterIP fd30:3087:b6c2::a <none> 53/UDP,53/TCP 57m k`
`387`	`387`	.. (Optional) <<sample-deployment,Deploy a sample application>> or deploy the <<aws-load-balancer-controller,{aws} Load Balancer Controller>> and a sample application to load balance HTTP applications with <<alb-ingress>> or network traffic with <<network-load-balancing>> to `IPv6` Pods.
`388`	`388`	`.. After you've finished with the cluster and nodes that you created for this tutorial, you should clean up the resources that you created with the following commands. Make sure that you're not using any of the resources outside of this tutorial before deleting them.`
`389`	`389`	`+`
`390`		-... If you're completing this step in a different shell than you completed the previous steps in, set the values of all the variables used in previous steps, replacing the [.replaceable]`example values` with the values you specified when you completed the previous steps. If you're completing this step in the same shell that you completed the previous steps in, skip to the next step.
	`390`	`+... If you're completing this step in a different shell than you completed the previous steps in, set the values of all the variables used in previous steps, replacing the example values with the values you specified when you completed the previous steps. If you're completing this step in the same shell that you completed the previous steps in, skip to the next step.`
`391`	`391`	`+`
`392`	`392`	`[source,bash,subs="verbatim,attributes"]`
`393`	`393`	`----`