remove github links and update build config

geoffcline · geoffcline · commit bcd0040ff99c · 2025-01-14T18:17:34.000Z
diff --git a/build-info.xml b/build-info.xml
@@ -5,7 +5,9 @@
       <pathslug>eks</pathslug>
       <title>Amazon EKS</title>
       <forumID>0</forumID>
-     <feedbackCTI>Amazon EKS</feedbackCTI>
+      <options>
+        <hide-github-link>0</hide-github-link>
+      </options>
       
       
 
@@ -19,12 +21,20 @@
           <version>latest</version>
           <asciidoc-source>latest/bpg</asciidoc-source>
           <locale>en_us</locale>
-<!--     
-          <options>
-          </options>
--->     
+
+          <github>
+            <user>aws</user>
+            <repo>aws-eks-best-practices</repo>
+            <branch>master</branch>
+            <source-folder>latest/bpg</source-folder>
+          </github>
+    
           <builds>
-            <html/>
+            <html />
+            <pdf />
+            <asciidoc>
+              <include-html-profiling>1</include-html-profiling>
+            </asciidoc> 
           </builds>
 
         </guide>
diff --git a/latest/bpg/autoscaling/cluster-autoscaler.adoc b/latest/bpg/autoscaling/cluster-autoscaler.adoc
@@ -634,4 +634,3 @@ Marcin Wielgus
 * https://github.com/aws/aws-node-termination-handler
 
 
-📝 https://github.com/aws/aws-eks-best-practices/tree/master/latest/bpg/autoscaling/cluster-autoscaler.adoc[Edit this page on GitHub]
diff --git a/latest/bpg/autoscaling/index.adoc b/latest/bpg/autoscaling/index.adoc
@@ -20,7 +20,7 @@ This guide provides advice about Cluster Autoscaling, including guidance for Kub
 [.topiclist]
 [[Topic List]]
 
-📝 https://github.com/aws/aws-eks-best-practices/tree/master/latest/bpg/autoscaling/index.adoc[Edit this page on GitHub]
+
 
 include::karpenter.adoc[leveloffset=+1]
 
diff --git a/latest/bpg/autoscaling/karpenter.adoc b/latest/bpg/autoscaling/karpenter.adoc
@@ -621,4 +621,4 @@ for your workload(s).
 Run Kubernetes Clusters for Less with Amazon EC2 Spot and Karpenter]
 
 
-📝 https://github.com/aws/aws-eks-best-practices/tree/master/latest/bpg/autoscaling/karpenter.adoc[Edit this page on GitHub]
+
diff --git a/latest/bpg/contribute.adoc b/latest/bpg/contribute.adoc
@@ -313,4 +313,3 @@ NOTE: This is a note admonition.
 
 
 
-📝 https://github.com/aws/aws-eks-best-practices/tree/master/latest/bpg/contribute.adoc[Edit this page on GitHub]
diff --git a/latest/bpg/cost/awareness.adoc b/latest/bpg/cost/awareness.adoc
@@ -225,4 +225,3 @@ Refer to the following resources to learn more about best practices for cost opt
 * https://github.com/rchakode/kube-opex-analytics[Kubernetes Opex Analytics]
 
 
-📝 https://github.com/aws/aws-eks-best-practices/tree/master/latest/bpg/cost/awareness.adoc[Edit this page on GitHub]
diff --git a/latest/bpg/cost/cfm_framework.adoc b/latest/bpg/cost/cfm_framework.adoc
@@ -64,4 +64,3 @@ Securing executive sponsorship for these types of activities is crucial for inte
 
 
 
-📝 https://github.com/aws/aws-eks-best-practices/tree/master/latest/bpg/cost/cfm_framework.adoc[Edit this page on GitHub]
diff --git a/latest/bpg/cost/cost_opt_compute.adoc b/latest/bpg/cost/cost_opt_compute.adoc
@@ -312,4 +312,4 @@ Some GPU hardware can be shared across multiple workloads so a single GPU can be
 * https://aws.amazon.com/blogs/containers/maximizing-gpu-utilization-with-nvidias-multi-instance-gpu-mig-on-amazon-eks-running-more-pods-per-gpu-for-enhanced-performance/[Maximizing GPU utilization with NVIDIA's Multi-Instance GPU (MIG) on Amazon EKS: Running more pods per GPU for enhanced performance]
 
 
-📝 https://github.com/aws/aws-eks-best-practices/tree/master/latest/bpg/cost/cost_opt_compute.adoc[Edit this page on GitHub]
+
diff --git a/latest/bpg/cost/cost_opt_networking.adoc b/latest/bpg/cost/cost_opt_networking.adoc
@@ -504,4 +504,3 @@ image:../images/after-results.png[After results]
 * https://aws.amazon.com/blogs/containers/understanding-data-transfer-costs-for-aws-container-services/[Understanding data transfer costs for AWS container services]
 
 
-📝 https://github.com/aws/aws-eks-best-practices/tree/master/latest/bpg/cost/cost_opt_networking.adoc[Edit this page on GitHub]
diff --git a/latest/bpg/cost/cost_opt_observability.adoc b/latest/bpg/cost/cost_opt_observability.adoc
@@ -354,4 +354,3 @@ For example, if you have traces that are 90 days old, https://aws.amazon.com/s3/
 * https://www.youtube.com/watch?v=YiegAlC_yyc[AWS re:Invent 2022 - Observability: Best practices for modern applications (COP344)]
 
 
-📝 https://github.com/aws/aws-eks-best-practices/tree/master/latest/bpg/cost/cost_opt_observability.adoc[Edit this page on GitHub]
diff --git a/latest/bpg/cost/cost_opt_storage.adoc b/latest/bpg/cost/cost_opt_storage.adoc
@@ -179,4 +179,3 @@ _To configure options for unused container and image garbage collection, tune th
 You can learn more about it in the Kubernetes https://kubernetes.io/docs/concepts/architecture/garbage-collection/#containers-images[documentation].
 
 
-📝 https://github.com/aws/aws-eks-best-practices/tree/master/latest/bpg/cost/cost_opt_storage.adoc[Edit this page on GitHub]
diff --git a/latest/bpg/cost/cost_optimization_index.adoc b/latest/bpg/cost/cost_optimization_index.adoc
@@ -68,4 +68,3 @@ include::cost_opt_observability.adoc[leveloffset=+1]
 
 
 
-📝 https://github.com/aws/aws-eks-best-practices/tree/master/latest/bpg/cost/cost_optimization_index.adoc[Edit this page on GitHub]
diff --git a/latest/bpg/cost/optimizing.adoc b/latest/bpg/cost/optimizing.adoc
@@ -81,4 +81,3 @@ Refer to the following resources to learn more about best practices for cost opt
 * https://learnk8s.io/research#choosing-node-size[Choose Right Node Size]
 
 
-📝 https://github.com/aws/aws-eks-best-practices/tree/master/latest/bpg/cost/optimizing.adoc[Edit this page on GitHub]
diff --git a/latest/bpg/index.adoc b/latest/bpg/index.adoc
@@ -74,4 +74,4 @@ correct it. The guidelines for submitting PRs can be found in our
 https://github.com/aws/aws-eks-best-practices/blob/master/CONTRIBUTING.md[Contributing
 Guidelines].
 
-📝 https://github.com/aws/aws-eks-best-practices/tree/master/latest/bpg/index.adoc[Edit this page on GitHub]
+
diff --git a/latest/bpg/networking/custom-networking.adoc b/latest/bpg/networking/custom-networking.adoc
@@ -133,4 +133,3 @@ NOTE: When the CNI prefix allocates a /28 prefix to an ENI, it has to be a conti
 Custom networking allows you to mitigate IP exhaustion issue, however it can't solve all the challenges. If you already using CG-NAT space for your cluster, or simply don't have the ability to associate a secondary CIDR with your cluster VPC, we suggest you to explore other options, like using an alternate CNI or moving to IPv6 clusters.
 
 
-📝 https://github.com/aws/aws-eks-best-practices/tree/master/latest/bpg/networking/custom-networking.adoc[Edit this page on GitHub]
diff --git a/latest/bpg/networking/index.adoc b/latest/bpg/networking/index.adoc
@@ -82,7 +82,7 @@ Outputs:
  ** Number of Warm IPs/ENIs per instance
  ** Number of Active IPs/ENIs per instance
 
-📝 https://github.com/aws/aws-eks-best-practices/tree/master/latest/bpg/networking/index.adoc[Edit this page on GitHub]
+
 
 include::subnets.adoc[leveloffset=+1]
 
diff --git a/latest/bpg/networking/ip-optimization-strategies.adoc b/latest/bpg/networking/ip-optimization-strategies.adoc
@@ -107,4 +107,3 @@ Learn more about these patterns here:
 * https://aws.amazon.com/blogs/networking-and-content-delivery/build-secure-multi-account-multi-vpc-connectivity-for-your-applications-with-amazon-vpc-lattice/[Build secure multi-account multi-VPC connectivity with Amazon VPC Lattice].
 
 
-📝 https://github.com/aws/aws-eks-best-practices/tree/master/latest/bpg/networking/ip-optimization-strategies.adoc[Edit this page on GitHub]
diff --git a/latest/bpg/networking/ipv6.adoc b/latest/bpg/networking/ipv6.adoc
@@ -127,4 +127,3 @@ EKS supports IPv6 for Pods running on Fargate. Pods running on Fargate will cons
 AWS Network Load Balancer does not support dual-stack UDP protocol address types. If you have strong requirements for low-latency, real-time streaming, online gaming, and IoT, we recommend running IPv4 clusters. To learn more about managing health checks for UDP services, please refer to https://aws.amazon.com/blogs/containers/how-to-route-udp-traffic-into-kubernetes/["`How to route UDP traffic into Kubernetes`"].
 
 
-📝 https://github.com/aws/aws-eks-best-practices/tree/master/latest/bpg/networking/ipv6.adoc[Edit this page on GitHub]
diff --git a/latest/bpg/networking/ipvs.adoc b/latest/bpg/networking/ipvs.adoc
@@ -170,4 +170,3 @@ UDP  ip-10-100-0-10.us-east-1 rr
 NOTE: This example output comes from an EKS cluster with a service IP address range of `10.100.0.0/16`.
 
 
-📝 https://github.com/aws/aws-eks-best-practices/tree/master/latest/bpg/networking/ipvs.adoc[Edit this page on GitHub]
diff --git a/latest/bpg/networking/loadbalancing.adoc b/latest/bpg/networking/loadbalancing.adoc
@@ -488,4 +488,3 @@ object.
 . API server deletes the Pod object.
 
 
-📝 https://github.com/aws/aws-eks-best-practices/tree/master/latest/bpg/networking/loadbalancing.adoc[Edit this page on GitHub]
diff --git a/latest/bpg/networking/monitoring.adoc b/latest/bpg/networking/monitoring.adoc
@@ -250,4 +250,3 @@ image::mon_cw_metrics.png[CW_NW_Performance]
 We can clearly see that there were no packets dropped as the value is zero. If you are using Nitro-based instances, you can create a similar dashboard for `conntrack_allowance_available` and pro-actively monitor the connections in your EC2 instance. You can further extend this by configuring alerts in Amazon Managed Grafana to send notifications to Slack, SNS, Pagerduty etc.
 
 
-📝 https://github.com/aws/aws-eks-best-practices/tree/master/latest/bpg/networking/monitoring.adoc[Edit this page on GitHub]
diff --git a/latest/bpg/networking/prefix-mode_linux.adoc b/latest/bpg/networking/prefix-mode_linux.adoc
@@ -92,4 +92,3 @@ Prefix mode works with VPC CNI version 1.9.0 and later. Downgrading of the Amazo
 It is highly recommended that you create new node groups to increase the number of available IP addresses rather than doing rolling replacement of existing worker nodes. Cordon and drain all the existing nodes to safely evict all of your existing Pods. To prevent service disruptions, we suggest implementing https://kubernetes.io/docs/tasks/run-application/configure-pdb[Pod Disruption Budgets] on your production clusters for critical workloads. Pods on new nodes will be assigned an IP from a prefix assigned to an ENI. After you confirm the Pods are running, you can delete the old nodes and node groups. If you are using managed node groups, please follow steps mentioned here to safely https://docs.aws.amazon.com/eks/latest/userguide/delete-managed-node-group.html[delete a node group].
 
 
-📝 https://github.com/aws/aws-eks-best-practices/tree/master/latest/bpg/networking/prefix-mode_linux.adoc[Edit this page on GitHub]
diff --git a/latest/bpg/networking/prefix-mode_windows.adoc b/latest/bpg/networking/prefix-mode_windows.adoc
@@ -105,4 +105,3 @@ That being said, you can use the migration strategy as described above to safely
 You can use our debugging guide https://github.com/aws/amazon-vpc-resource-controller-k8s/blob/master/docs/troubleshooting.md[here] to deep dive into the issue you are facing with prefix delegation on Windows.
 
 
-📝 https://github.com/aws/aws-eks-best-practices/tree/master/latest/bpg/networking/prefix-mode_windows.adoc[Edit this page on GitHub]
diff --git a/latest/bpg/networking/sgpp.adoc b/latest/bpg/networking/sgpp.adoc
@@ -171,4 +171,3 @@ kubectl rollout restart -n example-ns deployment example-pod
 ----
 
 
-📝 https://github.com/aws/aws-eks-best-practices/tree/master/latest/bpg/networking/sgpp.adoc[Edit this page on GitHub]
diff --git a/latest/bpg/networking/subnets.adoc b/latest/bpg/networking/subnets.adoc
@@ -176,4 +176,3 @@ AWS Cloud9 is a web-based IDE than can run securely in Private Subnets without i
 image::subnet_image-2.jpg[illustration of AWS Cloud9 console connecting to no-ingress EC2 instance.]
 
 
-📝 https://github.com/aws/aws-eks-best-practices/tree/master/latest/bpg/networking/subnets.adoc[Edit this page on GitHub]
diff --git a/latest/bpg/networking/vpc-cni.adoc b/latest/bpg/networking/vpc-cni.adoc
@@ -182,4 +182,3 @@ If you are using custom AMI, make sure to set iptables forward policy to ACCEPT
 The VPC CNI is backward compatible. The latest version works with all Amazon EKS supported Kubernetes versions. Additionally, the VPC CNI is offered as an EKS add-on (see "`Deploy VPC CNI Managed Add-On`" above). While EKS add-ons orchestrates upgrades of add-ons, it will not automatically upgrade add-ons like the CNI because they run on the data plane. You are responsible for upgrading the VPC CNI add-on following managed and self-managed worker node upgrades.
 
 
-📝 https://github.com/aws/aws-eks-best-practices/tree/master/latest/bpg/networking/vpc-cni.adoc[Edit this page on GitHub]
diff --git a/latest/bpg/reliability/application.adoc b/latest/bpg/reliability/application.adoc
@@ -796,4 +796,4 @@ X-Ray] or https://www.jaegertracing.io[Jaeger] that supports both
 to switch tools if you later adopt service mesh.
 
 
-📝 https://github.com/aws/aws-eks-best-practices/tree/master/latest/bpg/reliability/application.adoc[Edit this page on GitHub]
+
diff --git a/latest/bpg/reliability/controlplane.adoc b/latest/bpg/reliability/controlplane.adoc
@@ -384,4 +384,3 @@ EKS cluster endpoint access control]
 EKS under the hood (CON421-R1)]
 
 
-📝 https://github.com/aws/aws-eks-best-practices/tree/master/latest/bpg/reliability/controlplane.adoc[Edit this page on GitHub]
diff --git a/latest/bpg/reliability/dataplane.adoc b/latest/bpg/reliability/dataplane.adoc
@@ -536,4 +536,3 @@ aws ec2 describe-images --image-id ami-xxx --no-include-deprecated
 ....
 
 
-📝 https://github.com/aws/aws-eks-best-practices/tree/master/latest/bpg/reliability/dataplane.adoc[Edit this page on GitHub]
diff --git a/latest/bpg/reliability/index.adoc b/latest/bpg/reliability/index.adoc
@@ -125,7 +125,7 @@ file an issue or submit a PR in the GitHub repository. We intend to
 update the guide periodically as new features are added to the service
 or when a new best practice evolves.
 
-📝 https://github.com/aws/aws-eks-best-practices/tree/master/latest/bpg/reliability/index.adoc[Edit this page on GitHub]
+
 
 include::application.adoc[leveloffset=+1]
 
diff --git a/latest/bpg/scalability/cluster-services.adoc b/latest/bpg/scalability/cluster-services.adoc
@@ -101,4 +101,3 @@ If you are using CloudWatch and CloudWatch Logs you can add agent filtering usin
 To avoid losing logs and metrics you should send your data to a system that can buffer data in case of an outage on the receiving endpoint. With fluentbit you can use https://docs.fluentbit.io/manual/pipeline/outputs/firehose[Amazon Kinesis Data Firehose] to temporarily keep data which can reduce the chance of overloading your final data storage location.
 
 
-📝 https://github.com/aws/aws-eks-best-practices/tree/master/latest/bpg/scalability/cluster-services.adoc[Edit this page on GitHub]
diff --git a/latest/bpg/scalability/control-plane.adoc b/latest/bpg/scalability/control-plane.adoc
@@ -314,4 +314,3 @@ If you call the API without any arguments it will be the most resource intensive
 ----
 
 
-📝 https://github.com/aws/aws-eks-best-practices/tree/master/latest/bpg/scalability/control-plane.adoc[Edit this page on GitHub]
diff --git a/latest/bpg/scalability/data-plane.adoc b/latest/bpg/scalability/data-plane.adoc
@@ -222,4 +222,3 @@ Amazon recommends using immutable infrastructure that is built, tested, and prom
 Patching nodes will allow you to quickly roll out security updates and replace the instances on a regular schedule after your AMI has been updated. If you are using an operating system with a read-only root file system like https://flatcar-linux.org/[Flatcar Container Linux] or https://github.com/bottlerocket-os/bottlerocket[Bottlerocket OS] we recommend using the update operators that work with those operating systems. The https://github.com/flatcar/flatcar-linux-update-operator[Flatcar Linux update operator] and https://github.com/bottlerocket-os/bottlerocket-update-operator[Bottlerocket update operator] will reboot instances to keep nodes up to date automatically.
 
 
-📝 https://github.com/aws/aws-eks-best-practices/tree/master/latest/bpg/scalability/data-plane.adoc[Edit this page on GitHub]
diff --git a/latest/bpg/scalability/index.adoc b/latest/bpg/scalability/index.adoc
@@ -35,7 +35,7 @@ Scaling in Kubernetes is multi-dimensional and there are no specific settings or
 
 If you are scaling a single cluster beyond 1000 nodes or 50,000 pods we would love to talk to you. We recommend reaching out to your support team or technical account manager to get in touch with specialists who can help you plan and scale beyond the information provided in this guide.
 
-📝 https://github.com/aws/aws-eks-best-practices/tree/master/latest/bpg/scalability/index.adoc[Edit this page on GitHub]
+
 
 include::control-plane.adoc[leveloffset=+1]
 
diff --git a/latest/bpg/scalability/kcp_monitoring.adoc b/latest/bpg/scalability/kcp_monitoring.adoc
@@ -268,4 +268,3 @@ fields *@timestamp*, *@message*
 image::defrag.png[Defrag query]
 
 
-📝 https://github.com/aws/aws-eks-best-practices/tree/master/latest/bpg/scalability/kcp_monitoring.adoc[Edit this page on GitHub]
diff --git a/latest/bpg/scalability/kubernetes_slos.adoc b/latest/bpg/scalability/kubernetes_slos.adoc
@@ -161,4 +161,3 @@ Consider that the SLOs are focused on the performance of the Kubernetes componen
 The https://aws-observability.github.io/observability-best-practices/guides/containers/oss/eks/best-practices-metrics-collection/#control-plane-metrics[Observability Best Practices Guide] has examples of other Kubernetes metrics you can use to gain further insight.
 
 
-📝 https://github.com/aws/aws-eks-best-practices/tree/master/latest/bpg/scalability/kubernetes_slos.adoc[Edit this page on GitHub]
diff --git a/latest/bpg/scalability/node_efficiency.adoc b/latest/bpg/scalability/node_efficiency.adoc
@@ -280,4 +280,3 @@ To sum up the section, it is easy to conflate the following concepts:
 Great care must be taken to keep these concepts separated. Performance and scale are linked on a deep level. Unnecessary scaling creates performance problems, which in turn creates scaling problems.
 
 
-📝 https://github.com/aws/aws-eks-best-practices/tree/master/latest/bpg/scalability/node_efficiency.adoc[Edit this page on GitHub]
diff --git a/latest/bpg/scalability/quotas.adoc b/latest/bpg/scalability/quotas.adoc
@@ -252,4 +252,3 @@ You can review the EC2 rate limit defaults and the steps to request a rate limit
 * In EKS environment, etcd storage limit is *8 GiB* as per https://etcd.io/docs/v3.5/dev-guide/limit/#storage-size-limit[upstream guidance]. Please monitor metric `etcd_db_total_size_in_bytes` to track etcd db size. You can refer to https://github.com/etcd-io/etcd/blob/main/contrib/mixin/mixin.libsonnet#L213-L240[alert rules] `etcdBackendQuotaLowSpace` and `etcdExcessiveDatabaseGrowth` to setup this monitoring.
 
 
-📝 https://github.com/aws/aws-eks-best-practices/tree/master/latest/bpg/scalability/quotas.adoc[Edit this page on GitHub]
diff --git a/latest/bpg/scalability/scaling_theory.adoc b/latest/bpg/scalability/scaling_theory.adoc
@@ -115,4 +115,3 @@ To address a bottleneck in the system, we will take the approach of finding a me
 A good place to start with this process is the API server, as it allow us to see if there's a problem with a client application or the Control Plane.
 
 
-📝 https://github.com/aws/aws-eks-best-practices/tree/master/latest/bpg/scalability/scaling_theory.adoc[Edit this page on GitHub]
diff --git a/latest/bpg/scalability/workloads.adoc b/latest/bpg/scalability/workloads.adoc
@@ -128,4 +128,3 @@ filter @logStream like "kube-apiserver-audit"
 
 
 
-📝 https://github.com/aws/aws-eks-best-practices/tree/master/latest/bpg/scalability/workloads.adoc[Edit this page on GitHub]
diff --git a/latest/bpg/security/compliance.adoc b/latest/bpg/security/compliance.adoc
@@ -150,4 +150,3 @@ zero-trust container security platform, provides compliance reporting
 and custom compliance checks
 
 
-📝 https://github.com/aws/aws-eks-best-practices/tree/master/latest/bpg/security/compliance.adoc[Edit this page on GitHub]
diff --git a/latest/bpg/security/data.adoc b/latest/bpg/security/data.adoc
@@ -260,4 +260,3 @@ EKS Security Immersion Workshop - Data Encryption and Secrets
 Management]
 
 
-📝 https://github.com/aws/aws-eks-best-practices/tree/master/latest/bpg/security/data.adoc[Edit this page on GitHub]
diff --git a/latest/bpg/security/detective.adoc b/latest/bpg/security/detective.adoc
@@ -367,4 +367,3 @@ https://www.microsoft.com/security/blog/2021/03/23/secure-containerized-environm
 ATT&CK®].)
 
 
-📝 https://github.com/aws/aws-eks-best-practices/tree/master/latest/bpg/security/detective.adoc[Edit this page on GitHub]
diff --git a/latest/bpg/security/hosts.adoc b/latest/bpg/security/hosts.adoc
@@ -374,4 +374,3 @@ nodes.
 * https://eksctl.io/[eksctl]
 
 
-📝 https://github.com/aws/aws-eks-best-practices/tree/master/latest/bpg/security/hosts.adoc[Edit this page on GitHub]
diff --git a/latest/bpg/security/iam.adoc b/latest/bpg/security/iam.adoc
@@ -1414,4 +1414,4 @@ resources, including blogs and tools, for Kubernetes RBAC
 * https://github.com/uswitch/kiam[kiam]
 
 
-📝 https://github.com/aws/aws-eks-best-practices/tree/master/latest/bpg/security/iam.adoc[Edit this page on GitHub]
+
diff --git a/latest/bpg/security/image.adoc b/latest/bpg/security/image.adoc
@@ -508,4 +508,3 @@ zero-trust container security platform, provides container, image and
 registry scanning for vulnerabilities, secrets and compliance.
 
 
-📝 https://github.com/aws/aws-eks-best-practices/tree/master/latest/bpg/security/image.adoc[Edit this page on GitHub]
diff --git a/latest/bpg/security/incidents.adoc b/latest/bpg/security/incidents.adoc
@@ -256,4 +256,3 @@ Attack and Defense]
 Cluster by Exploiting RBAC Permissions]
 
 
-📝 https://github.com/aws/aws-eks-best-practices/tree/master/latest/bpg/security/incidents.adoc[Edit this page on GitHub]
diff --git a/latest/bpg/security/index.adoc b/latest/bpg/security/index.adoc
@@ -141,7 +141,7 @@ practices that align with DevOps processes and agile methodologies.
 https://catalog.workshops.aws/eks-security-immersionday/en-US[Amazon EKS
 Security Immersion Workshop]
 
-📝 https://github.com/aws/aws-eks-best-practices/tree/master/latest/bpg/security/index.adoc[Edit this page on GitHub]
+
 
 include::iam.adoc[leveloffset=+1]
 
diff --git a/latest/bpg/security/multiaccount.adoc b/latest/bpg/security/multiaccount.adoc
@@ -427,4 +427,3 @@ accounts are delivered directly to pods with IRSA or EKS Pod Identities
 |===
 
 
-📝 https://github.com/aws/aws-eks-best-practices/tree/master/latest/bpg/security/multiaccount.adoc[Edit this page on GitHub]
diff --git a/latest/bpg/security/multitenancy.adoc b/latest/bpg/security/multitenancy.adoc
@@ -598,4 +598,3 @@ to validate conformance to the guidelines.
 * https://www.weave.works/oss/flux/[Weave Flux]
 
 
-📝 https://github.com/aws/aws-eks-best-practices/tree/master/latest/bpg/security/multitenancy.adoc[Edit this page on GitHub]
diff --git a/latest/bpg/security/network.adoc b/latest/bpg/security/network.adoc
@@ -980,4 +980,3 @@ data loss prevention (DLP), web application firewall (WAF) and network
 threat signatures.
 
 
-📝 https://github.com/aws/aws-eks-best-practices/tree/master/latest/bpg/security/network.adoc[Edit this page on GitHub]
diff --git a/latest/bpg/security/pods.adoc b/latest/bpg/security/pods.adoc
diff --git a/latest/bpg/security/runtime.adoc b/latest/bpg/security/runtime.adoc
diff --git a/latest/bpg/upgrades/index.adoc b/latest/bpg/upgrades/index.adoc
diff --git a/latest/bpg/windows/ami.adoc b/latest/bpg/windows/ami.adoc
diff --git a/latest/bpg/windows/gmsa.adoc b/latest/bpg/windows/gmsa.adoc
diff --git a/latest/bpg/windows/hardening.adoc b/latest/bpg/windows/hardening.adoc
diff --git a/latest/bpg/windows/hardening_container_image.adoc b/latest/bpg/windows/hardening_container_image.adoc
diff --git a/latest/bpg/windows/images.adoc b/latest/bpg/windows/images.adoc
diff --git a/latest/bpg/windows/index.adoc b/latest/bpg/windows/index.adoc
diff --git a/latest/bpg/windows/licensing.adoc b/latest/bpg/windows/licensing.adoc
diff --git a/latest/bpg/windows/logging.adoc b/latest/bpg/windows/logging.adoc
diff --git a/latest/bpg/windows/monitoring.adoc b/latest/bpg/windows/monitoring.adoc
diff --git a/latest/bpg/windows/networking.adoc b/latest/bpg/windows/networking.adoc
diff --git a/latest/bpg/windows/oom.adoc b/latest/bpg/windows/oom.adoc
diff --git a/latest/bpg/windows/patching.adoc b/latest/bpg/windows/patching.adoc
diff --git a/latest/bpg/windows/scheduling.adoc b/latest/bpg/windows/scheduling.adoc
diff --git a/latest/bpg/windows/security.adoc b/latest/bpg/windows/security.adoc
diff --git a/latest/bpg/windows/storage.adoc b/latest/bpg/windows/storage.adoc
