AWS Security ChangesHomeSearch

AWS eks documentation change

Service: eks · 2026-01-25 · Documentation low

File: eks/latest/best-practices/hybrid-nodes-app-network-traffic.md

Summary

Fixed markup syntax in iptables rules documentation (changed XML-like emphasis tags to **)

Security assessment

The changes are purely formatting improvements to documentation examples with no security implications. No security context or vulnerability addressed.

Diff

diff --git a/eks/latest/best-practices/hybrid-nodes-app-network-traffic.md b/eks/latest/best-practices/hybrid-nodes-app-network-traffic.md
index 9a18e363e..7f1e92048 100644
--- a//eks/latest/best-practices/hybrid-nodes-app-network-traffic.md
+++ b//eks/latest/best-practices/hybrid-nodes-app-network-traffic.md
@@ -73,12 +73,12 @@ Inspecting the `KUBE-SERVICES` chain we can see the rules for the various cluste
-    KUBE-SVL-NZTS37XDTDNXGCKJ  tcp  --  anywhere    172.16.189.136  /* kube-system/hubble-peer:peer-service cluster IP <emphasis role="strong">/
-    KUBE-SVC-2BINP2AXJOTI3HJ5  tcp  --  anywhere    172.16.62.72    /</emphasis> default/metallb-webhook-service cluster IP <emphasis role="strong">/
-    KUBE-SVC-LRNEBRA3Z5YGJ4QC  tcp  --  anywhere    172.16.145.111  /</emphasis> default/redis-leader cluster IP <emphasis role="strong">/
-    KUBE-SVC-I7SKRZYQ7PWYV5X7  tcp  --  anywhere    172.16.142.147  /</emphasis> kube-system/eks-extension-metrics-api:metrics-api cluster IP <emphasis role="strong">/
-    KUBE-SVC-JD5MR3NA4I4DYORP  tcp  --  anywhere    172.16.0.10     /</emphasis> kube-system/kube-dns:metrics cluster IP <emphasis role="strong">/
-    KUBE-SVC-TCOU7JCQXEZGVUNU  udp  --  anywhere    172.16.0.10     /</emphasis> kube-system/kube-dns:dns cluster IP <emphasis role="strong">/
-    KUBE-SVC-ERIFXISQEP7F7OF4  tcp  --  anywhere    172.16.0.10     /</emphasis> kube-system/kube-dns:dns-tcp cluster IP <emphasis role="strong">/
-    KUBE-SVC-ENODL3HWJ5BZY56Q  tcp  --  anywhere    172.16.7.26     /</emphasis> default/frontend cluster IP <emphasis role="strong">/
-    KUBE-EXT-ENODL3HWJ5BZY56Q  tcp  --  anywhere    <LB-IP>    /</emphasis> default/frontend loadbalancer IP <emphasis role="strong">/
-    KUBE-SVC-NPX46M4PTMTKRN6Y  tcp  --  anywhere    172.16.0.1      /</emphasis> default/kubernetes:https cluster IP <emphasis role="strong">/
-    KUBE-SVC-YU5RV2YQWHLZ5XPR  tcp  --  anywhere    172.16.228.76   /</emphasis> default/redis-follower cluster IP <emphasis role="strong">/
-    KUBE-NODEPORTS             all  --  anywhere    anywhere        /</emphasis> kubernetes service nodeports; NOTE: this must be the last rule in this chain */
+    KUBE-SVL-NZTS37XDTDNXGCKJ  tcp  --  anywhere    172.16.189.136  /* kube-system/hubble-peer:peer-service cluster IP **/
+    KUBE-SVC-2BINP2AXJOTI3HJ5  tcp  --  anywhere    172.16.62.72    /** default/metallb-webhook-service cluster IP **/
+    KUBE-SVC-LRNEBRA3Z5YGJ4QC  tcp  --  anywhere    172.16.145.111  /** default/redis-leader cluster IP **/
+    KUBE-SVC-I7SKRZYQ7PWYV5X7  tcp  --  anywhere    172.16.142.147  /** kube-system/eks-extension-metrics-api:metrics-api cluster IP **/
+    KUBE-SVC-JD5MR3NA4I4DYORP  tcp  --  anywhere    172.16.0.10     /** kube-system/kube-dns:metrics cluster IP **/
+    KUBE-SVC-TCOU7JCQXEZGVUNU  udp  --  anywhere    172.16.0.10     /** kube-system/kube-dns:dns cluster IP **/
+    KUBE-SVC-ERIFXISQEP7F7OF4  tcp  --  anywhere    172.16.0.10     /** kube-system/kube-dns:dns-tcp cluster IP **/
+    KUBE-SVC-ENODL3HWJ5BZY56Q  tcp  --  anywhere    172.16.7.26     /** default/frontend cluster IP **/
+    KUBE-EXT-ENODL3HWJ5BZY56Q  tcp  --  anywhere <LB-IP>    /** default/frontend loadbalancer IP **/
+    KUBE-SVC-NPX46M4PTMTKRN6Y  tcp  --  anywhere    172.16.0.1      /** default/kubernetes:https cluster IP **/
+    KUBE-SVC-YU5RV2YQWHLZ5XPR  tcp  --  anywhere    172.16.228.76   /** default/redis-follower cluster IP **/
+    KUBE-NODEPORTS             all  --  anywhere    anywhere        /** kubernetes service nodeports; NOTE: this must be the last rule in this chain */
@@ -94,3 +94,3 @@ Inspecting the chain of the frontend service for the application we can see the
-    KUBE-SEP-EKXE7ASH7Y74BGBO  all  --  anywhere  anywhere    /* default/frontend -> 10.86.2.103:80 <emphasis role="strong">/ statistic mode random probability 0.33333333349
-    KUBE-SEP-GCY3OUXWSVMSEAR6  all  --  anywhere  anywhere    /</emphasis> default/frontend -> 10.86.2.179:80 <emphasis role="strong">/ statistic mode random probability 0.50000000000
-    KUBE-SEP-6GJJR3EF5AUP2WBU  all  --  anywhere  anywhere    /</emphasis> default/frontend -> 10.86.3.47:80 */
+    KUBE-SEP-EKXE7ASH7Y74BGBO  all  --  anywhere  anywhere    /* default/frontend -> 10.86.2.103:80 **/ statistic mode random probability 0.33333333349
+    KUBE-SEP-GCY3OUXWSVMSEAR6  all  --  anywhere  anywhere    /** default/frontend -> 10.86.2.179:80 **/ statistic mode random probability 0.50000000000
+    KUBE-SEP-6GJJR3EF5AUP2WBU  all  --  anywhere  anywhere    /** default/frontend -> 10.86.3.47:80 */