A company with an on-premises data center is developing a new solution on AWS using Kubernetes. Development and test workloads run on Amazon EKS clusters in AWS. Production requires both the EKS control plane and data plane to remain on-premises, but the company prefers an AWS-managed Kubernetes solution with minimal operational overhead. Which option satisfies these requirements with the least operational overhead?

The correct option is to install an AWS Outposts server and deploy Amazon EKS with a local cluster configuration. This approach places both the EKS control plane and data plane (worker nodes) entirely on-premises on Outposts, fulfilling the requirement for on-premises operation while leveraging AWS-managed EKS. A local cluster configuration ensures the control plane runs locally, minimizing latency and dependency on the AWS Region for core Kubernetes operations. Installing Amazon EKS Anywhere on on-premises hardware (second option) is incorrect because it requires the customer to manage the Kubernetes control plane and underlying infrastructure, increasing operational overhead compared to AWS-managed EKS on Outposts. Deploying EKS on Outposts with an extended cluster configuration (third option) is incorrect because the EKS control plane would reside in the AWS Region, not on-premises, which violates the requirement for both control plane and data plane to be on-premises. Installing EKS Anywhere on an Outposts server (fourth option) is redundant and incorrect. EKS on Outposts already provides an AWS-managed Kubernetes experience on-premises; running EKS Anywhere on top of Outposts adds unnecessary complexity and management overhead.