AWS eks documentation change
Summary
Corrected acronym from 'VPW' to 'VGW' (Virtual Private Gateway) in hybrid nodes networking documentation
Security assessment
This change fixes a typo in a networking acronym (VPW to VGW). While networking configuration can have security implications, this specific change is purely a documentation correction without altering security guidance or revealing any security issues.
Diff
diff --git a/eks/latest/userguide/hybrid-nodes-troubleshooting.md b/eks/latest/userguide/hybrid-nodes-troubleshooting.md index db5a43fa6..74dcb7267 100644 --- a//eks/latest/userguide/hybrid-nodes-troubleshooting.md +++ b//eks/latest/userguide/hybrid-nodes-troubleshooting.md @@ -245 +245 @@ Run `nodeadm debug` from your hybrid nodes to validate networking and credential -If applications, add-ons, or webhooks running on your hybrid nodes are not starting properly, you might have networking issues that block the communication to the pods. For the EKS control plane to contact webhooks running on hybrid nodes, you must configure your EKS cluster with a remote pod network and have routes for your on-premises pod CIDR in your VPC routing table with the target as your Transit Gateway (TGW), virtual private gateway (VPW), or other gateway you are using to connect your VPC with your on-premises network. For more information on the networking requirements for hybrid nodes, see [Prepare networking for hybrid nodes](./hybrid-nodes-networking.html). You additionally must allow this traffic in your on-premises firewall and ensure your router can properly route to your pods. See [Configure webhooks for hybrid nodes](./hybrid-nodes-webhooks.html) for more information on the requirements for running webhooks on hybrid nodes. +If applications, add-ons, or webhooks running on your hybrid nodes are not starting properly, you might have networking issues that block the communication to the pods. For the EKS control plane to contact webhooks running on hybrid nodes, you must configure your EKS cluster with a remote pod network and have routes for your on-premises pod CIDR in your VPC routing table with the target as your Transit Gateway (TGW), virtual private gateway (VGW), or other gateway you are using to connect your VPC with your on-premises network. For more information on the networking requirements for hybrid nodes, see [Prepare networking for hybrid nodes](./hybrid-nodes-networking.html). You additionally must allow this traffic in your on-premises firewall and ensure your router can properly route to your pods. See [Configure webhooks for hybrid nodes](./hybrid-nodes-webhooks.html) for more information on the requirements for running webhooks on hybrid nodes.