Which deployment option for Amazon EKS helps you create and operate Kubernetes clusters on your on-premises infrastructure?

Which deployment option for Amazon EKS helps you create and operate Kubernetes clusters on your on-premises infrastructure?

• A. Amazon EKS Distro
• B. Amazon Elastic Container Service
• C. Amazon EKS Anywhere
• D. Amazon EKS

Answer: (C)

The idea being tested is extending the management and orchestration capabilities of EKS to your own premises. EKS Anywhere is the option built for that, letting you create and operate Kubernetes clusters on on-premises infrastructure while using the same Kubernetes tooling and versions as EKS. It gives you a consistent experience with the familiar AWS/EKS workflows, but runs inside your data center or private cloud instead of in AWS. Amazon EKS itself is the managed Kubernetes service in the cloud, so it’s not on-prem. EKS Distro provides the Kubernetes components that underlie EKS and can be run in various environments, but it’s a Kubernetes distribution rather than a full on-prem deployment option with the same integrated EKS management experience. Amazon Elastic Container Service focuses on ECS, a different orchestrator, not Kubernetes.

The idea being tested is extending the management and orchestration capabilities of EKS to your own premises. EKS Anywhere is the option built for that, letting you create and operate Kubernetes clusters on on-premises infrastructure while using the same Kubernetes tooling and versions as EKS. It gives you a consistent experience with the familiar AWS/EKS workflows, but runs inside your data center or private cloud instead of in AWS.

Amazon EKS itself is the managed Kubernetes service in the cloud, so it’s not on-prem. EKS Distro provides the Kubernetes components that underlie EKS and can be run in various environments, but it’s a Kubernetes distribution rather than a full on-prem deployment option with the same integrated EKS management experience. Amazon Elastic Container Service focuses on ECS, a different orchestrator, not Kubernetes.