Simplified topic and section ID syntax.

Author: pgasca

latest/ug/automode/associate-workload.adoc

@@ -1,5 +1,5 @@
 [.topic]
-[[associate-workload,associate-workload.title]]
+[#associate-workload]
 = Control if a workload is deployed on EKS Auto Mode nodes
 :info_titleabbrev: Control deployment
 

latest/ug/automode/auto-configure-alb.adoc

@@ -1,5 +1,5 @@
 [.topic]
-[[auto-configure-alb,auto-configure-alb.title]]
+[#auto-configure-alb]
 = Create an IngressClass to configure an Application Load Balancer
 :info_titleabbrev: Create ingress class
 
@@ -133,7 +133,7 @@ kubectl delete ingress <ingress-name>
 
 EKS Auto Mode will automatically delete the associated load balancer in your {aws} account. 
 
-[[ingress-reference,ingress-reference.title]]
+[#ingress-reference]
 == IngressClassParams Reference
 
 The table below is a quick reference for commonly used configuration options. 

latest/ug/automode/auto-configure-nlb.adoc

@@ -1,5 +1,5 @@
 [.topic]
-[[auto-configure-nlb,auto-configure-nlb.title]]
+[#auto-configure-nlb]
 = Use Service Annotations to configure Network Load Balancers
 :info_titleabbrev: Create service
 

latest/ug/automode/auto-disable.adoc

@@ -1,5 +1,5 @@
 [.topic]
-[[auto-disable,auto-disable.title]]
+[#auto-disable]
 = Disable EKS Auto Mode
 
 include::../attributes.txt[]

latest/ug/automode/auto-elb-example.adoc

@@ -1,5 +1,5 @@
 [.topic]
-[[auto-elb-example,auto-elb-example.title]]
+[#auto-elb-example]
 = Deploy a Sample Load Balancer Workload to EKS Auto Mode
 :info_titleabbrev: Deploy load balancer
 
@@ -233,7 +233,7 @@ This will delete all resources in the namespace, including the deployment, servi
 ** Configures target groups for the pods
 ** Sets up routing rules to direct traffic to the service
 
-[[auto-elb-troubleshooting,auto-elb-troubleshooting.title]]
+[#auto-elb-troubleshooting]
 == Troubleshooting
 
 If the game doesn't load:

latest/ug/automode/auto-enable-existing.adoc

@@ -1,5 +1,5 @@
 [.topic]
-[[auto-enable-existing,auto-enable-existing.title]]
+[#auto-enable-existing]
 = Enable EKS Auto Mode on an existing cluster
 :info_titleabbrev: Enable on cluster
 
@@ -15,7 +15,7 @@ Verify you have the minimum required version of certain Amazon EKS Add-ons insta
 
 Before you begin, ensure you have administrator access to your Amazon EKS cluster and permissions to modify IAM roles. The steps in this topic guide you through enabling Auto Mode using either the {aws-management-console} or {aws} CLI.
 
-[[auto-enable-existing-console,auto-enable-existing-console.title]]
+[#auto-enable-existing-console]
 == {aws-management-console}
 
 You must be logged into the {aws} console with permission to manage IAM, EKS, and EC2 resources. 
@@ -100,7 +100,7 @@ aws eks update-cluster-config \
  --storage-config '{"blockStorage":{"enabled": true}}'
 ----
 
-[[auto-addons-required,auto-addons-required.title]]
+[#auto-addons-required]
 == Required Add-on Versions
 
 If you're planning to enable EKS Auto Mode on an existing cluster, you may need to update certain add-ons. Please note:

latest/ug/automode/auto-glossary.adoc

@@ -1,5 +1,5 @@
 [.topic]
-[[auto-glossary,auto-glossary.title]]
+[#auto-glossary]
 = Glossary
 :info_titleabbrev: Glossary
 

latest/ug/automode/auto-learn-iam.adoc

@@ -1,5 +1,5 @@
 [.topic]
-[[auto-learn-iam,auto-learn-iam.title]]
+[#auto-learn-iam]
 = Learn about identity and access in EKS Auto Mode
 :info_titleabbrev: Identity and access
 
@@ -11,7 +11,7 @@ When you configure EKS Auto Mode, you will need to set up these IAM roles with s
 
 In EKS Auto Mode, {aws} IAM roles are automatically mapped to Kubernetes permissions through EKS access entries, removing the need for manual configuration of `aws-auth` ConfigMaps or custom bindings. When you create a new auto mode cluster, EKS automatically creates the corresponding Kubernetes permissions using Access entries, ensuring that {aws} services and cluster components have the appropriate access levels within both the {aws} and Kubernetes authorization systems. This automated integration reduces configuration complexity and helps prevent permission-related issues that commonly occur when managing EKS clusters.
 
-[[auto-learn-cluster-iam-role,auto-learn-cluster-iam-role.title]]
+[#auto-learn-cluster-iam-role]
 == Cluster IAM role
 
 The Cluster IAM role is an {aws} Identity and Access Management (IAM) role used by Amazon EKS to manage permissions for Kubernetes clusters. This role grants Amazon EKS the necessary permissions to interact with other {aws} services on behalf of your cluster, and is automatically configured with Kubernetes permissions using EKS access entries.
@@ -37,7 +37,7 @@ For more information about Kubernetes access, see:
 
 * <<access-policy-permissions>>
 
-[[auto-learn-node-iam-role,auto-learn-node-iam-role.title]]
+[#auto-learn-node-iam-role]
 == Node IAM role
 
 The Node IAM role is an {aws} Identity and Access Management (IAM) role used by Amazon EKS to manage permissions for worker nodes in Kubernetes clusters. This role grants EC2 instances running as Kubernetes nodes the necessary permissions to interact with {aws} services and resources, and is automatically configured with Kubernetes RBAC permissions using EKS access entries.
@@ -74,12 +74,12 @@ For more information, see:
 * <<service-linked-role-permissions-eks>>
 
 
-[[tag-prop,tag-prop.title]]
+[#tag-prop]
 == Custom {aws} tags for EKS Auto resources 
 
 By default, the managed policies related to EKS Auto Mode do not permit applying user defined tags to Auto Mode provisioned {aws} resources. If you want to apply user defined tags to {aws} resources, you must attach additional permissions to the Cluster IAM Role with sufficient permissions to create and modify tags on {aws} resources. Below is an example of a policy that will allow unrestricted tagging access: 
 
-[[auto-tag-policy,auto-tag-policy.title]]
+[#auto-tag-policy]
 .View custom tag policy example
 [%collapsible, expand-section="_collapse_all_"]
 ====

latest/ug/automode/auto-migrate-karpenter.adoc

@@ -1,5 +1,5 @@
 [.topic]
-[[auto-migrate-karpenter,auto-migrate-karpenter.title]]
+[#auto-migrate-karpenter]
 = Migrate from Karpenter to EKS Auto Mode using kubectl
 :info_titleabbrev: Migrate from Karpenter
 

latest/ug/automode/auto-migrate-mng.adoc

@@ -1,5 +1,5 @@
 [.topic]
-[[auto-migrate-mng,auto-migrate-mng.title]]
+[#auto-migrate-mng]
 = Migrate from EKS Managed Node Groups to EKS Auto Mode
 :info_titleabbrev: Migrate from MNGs