Today, Amazon Elastic Kubernetes Service (Amazon EKS) introduces customer-routed control plane egress, a capability that lets you route outbound Kubernetes API server traffic through your own Amazon VPC. This includes admission webhook callbacks, OpenID Connect (OIDC) provider lookups, and aggregate API server requests. With customer-routed control plane egress, this traffic flows through your VPC, where you control the routing, security groups, and egress path.
Organizations with data perimeter requirements, compliance mandates, or private network infrastructure can use customer-routed control plane egress to reach private OIDC providers and webhook servers that are accessible only within their VPC, and control how that traffic routes through their network. To get started, set controlPlaneEgressMode to CUSTOMER_ROUTED when creating a new cluster or updating an existing cluster. To enforce this configuration organization-wide, use the eks:controlPlaneEgressMode IAM condition key with AWS Organizations Service Control Policies.
Customer-routed control plane egress is available at no additional cost in all AWS Regions where Amazon EKS is available. To learn more, see Configure control plane egress routing in the Amazon EKS User Guide.
Categories: general:products/amazon-eks,marketing:marchitecture/containers
Source: Amazon Web Services
Latest Posts
- Amazon MSK Express brokers now support Intelligent Rebalancing on existing clusters
- Announcing the general availability of a new AWS Local Zone in Hanoi, Vietnam
- AWS Compute Optimizer enhances EBS volume recommendations with additional performance metrics
- (Updated) Use sensitivity labels to block all connected experiences that analyze content in Word, Excel, and PowerPoint [MC1297982]
