Configure a private Kubernetes endpoint — EKS and Kubernetes

Your goal

Create a Kubernetes cluster configuration with a private API endpoint.

Why this matters

A Kubernetes cluster has management-endpoint settings before any app is deployed. You will create a private endpoint configuration and inspect it. This does not start a Kubernetes control plane or deploy pods.

Words you will use

Kubernetes manages container workloads. A pod runs one or more containers. A Deployment describes desired app copies. A Service gives pods a stable way to be reached.

How to proceed

Start a fresh emulator, read each numbered step, and enter the practice settings shown. Run the action, inspect its API receipt, then continue. Finish lab checks the emulator state again before saving your progress.

1. Prepare the network and cluster role

Create two subnets, a security group, and a role for EKS. These resources provide the configuration inputs for the cluster request in the next step.

2. Create the private endpoint configuration

Create an EKS cluster record with private endpoint access enabled and public endpoint access disabled. The emulator stores the cluster configuration; it does not run a Kubernetes control plane or pods.

3. Inspect the endpoint settings

Describe the cluster and inspect resourcesVpcConfig. Confirm the two endpoint access flags and the subnet IDs. Network settings are separate from Kubernetes user permissions.

Practice, then check your understanding

Perform the actions yourself and inspect the returned state. Errors keep your settings so you can retry. Starting another lab clears the previous live environment. Earned XP is kept, and signed-in achievements sync to your account. Replay does not award duplicate XP.

Read the official AWS documentation for service behavior and production details.