# Amazon EKS Distro

Cloud service · AWS. Updated 2026-11-12. Page: https://blowstack.com/tools/cloud-services-hub/amazon-eks-distro

> Amazon EKS Distro is an open-source Kubernetes distribution provided by Amazon Web Services (AWS) that enables users to create reliable and secure Kubernetes clusters on-premises or in the cloud, compatible with Amazon EKS.

## 8 key features of Amazon EKS Distro

Amazon EKS Distro is Amazon's Kubernetes distribution that provides a reliable, scalable, and secure foundation for running containerized applications, incorporating the same versions of Kubernetes and its dependencies as Amazon EKS.

1. **Kubernetes Conformance**: Amazon EKS Distro is fully conformant with the Kubernetes open source project, ensuring that workloads that run on EKS Distro will be compatible with other conformant versions of Kubernetes.
2. **Open Source**: Amazon EKS Distro is an open-source distribution, allowing users to inspect, customize, and enhance their Kubernetes installations using the source code.
3. **Amazon EKS Compatibility**: Designed to be compatible with Amazon EKS, allowing users to easily migrate workloads between Amazon EKS on AWS and their on-premises environments running EKS Distro.
4. **Security Updates**: Amazon provides timely security updates and patches for EKS Distro, helping users keep their Kubernetes environments secure.
5. **Community Support**: Leverages the wide community support of Kubernetes, offering users access to a large ecosystem of extensions and add-ons, as well as community expertise for troubleshooting and optimization.
6. **Integrated Development Experience**: Works seamlessly with AWS development tools and services, providing an integrated experience for developers building, deploying, and managing Kubernetes applications.
7. **Scalability**: Built for scalability, allowing organizations to efficiently manage and scale their Kubernetes clusters as their applications and workloads grow.
8. **Container Runtime Options**: Supports multiple container runtimes, giving users the flexibility to choose the runtime that best fits their needs.

## Where Amazon EKS Distro is used

Amazon EKS Distro is utilized for creating and operating Kubernetes clusters on-premise or in the cloud, allowing for consistent cluster management, application deployment, and scaling across various environments.

1. **Deploying Microservices**: Amazon EKS Distro provides a reliable and scalable foundation for deploying microservices-based applications. By leveraging Kubernetes orchestration capabilities, development teams can efficiently manage, scale, and update microservices across a variety of environments, ensuring high availability and resilience of applications.
2. **Hybrid Cloud and On-Premises Workloads**: Organizations can use Amazon EKS Distro to manage Kubernetes workloads both in the cloud and on-premises, creating a consistent and unified environment. This seamless integration helps in leveraging the flexibility of cloud resources while maintaining data sovereignty or leveraging existing on-premises investments.
3. **Continuous Integration/Continuous Deployment (CI/CD) Pipelines**: By integrating Amazon EKS Distro with existing CI/CD tools and practices, developers can automate the deployment process, ensuring that new code changes are smoothly rolled out with minimal manual intervention. This accelerates the development cycle and improves the reliability of deployments.
4. **Machine Learning Workload Management**: Amazon EKS Distro can be used to manage the complex and resource-intensive workloads associated with machine learning projects. It provides the scalability and flexibility needed to train models, handle large datasets, and adjust resources on-demand, facilitating faster experimentation and deployment of machine learning models.
5. **Multi-Tenancy with Kubernetes**: Enterprises can leverage Amazon EKS Distro to implement multi-tenancy within their Kubernetes environment, allowing different teams or projects to share the same cluster resources securely and efficiently. This approach optimizes resource utilization and reduces operational costs by avoiding the need to provision separate clusters for each tenant.

## How Amazon EKS Distro is priced

As of my last update in April 2023, Amazon EKS Distro itself is an open-source distribution offered at no direct cost, but users may incur infrastructure charges depending on where it is deployed.

- **Direct Costs**: Amazon EKS Distro itself does not incur any direct costs from AWS, as it is essentially the same open-source Kubernetes software distribution that Amazon EKS uses. However, users will have to manage and bear the costs of the underlying infrastructure required to run it, such as AWS EC2 instances or any other compute resources, and any associated networking or storage resources.
- **Indirect Costs**: Users of Amazon EKS Distro must consider indirect costs related to the operation and management of their Kubernetes clusters. This includes expenses associated with deploying, monitoring, scaling, updating, and securing the clusters. While EKS Distro does not charge for these tasks, they do require manual intervention or automation, potentially leading to increased costs in manpower or third-party tools.
- **Support Costs**: While Amazon EKS Distro itself is free, AWS offers a range of support plans that provide varying degrees of assistance, from basic technical support to more in-depth architectural guidance. These plans are priced as a percentage of total AWS usage but are optional. Organizations with complex deployments or mission-critical applications might consider these plans to ensure prompt access to AWS support.

## Services Amazon EKS Distro works with

- **[Amazon EC2](https://blowstack.com/tools/cloud-services-hub/amazon-ec2)**: Amazon EC2 provides the compute infrastructure for running EKS Distro Kubernetes worker nodes.
- **[Amazon S3](https://blowstack.com/tools/cloud-services-hub/amazon-s3)**: Amazon S3 can be used for storing artifacts, cluster state information, and other persistent storage needs essential for EKS Distro operations.
- **[Amazon CloudWatch](https://blowstack.com/tools/cloud-services-hub/amazon-cloudwatch)**: Amazon EKS Distro clusters can send container logs and infrastructure metrics to CloudWatch using the CloudWatch agent and Fluent Bit. Container Insights supports self-managed Kubernetes on Amazon EC2 for monitoring node, pod, and container resource usage.
- **[Amazon Data Firehose](https://blowstack.com/tools/cloud-services-hub/amazon-kinesis-data-firehose)**: Amazon EKS Distro clusters can use Fluent Bit's Firehose output to deliver container logs to Amazon Data Firehose. Firehose can then buffer and deliver those logs to a configured destination.
- **[Amazon EC2 Auto Scaling](https://blowstack.com/tools/cloud-services-hub/amazon-ec2-auto-scaling)**: Amazon EKS Distro clusters running on EC2 can use Kubernetes Cluster Autoscaler with EC2 Auto Scaling groups. The autoscaler adjusts worker-node capacity when pods cannot be scheduled or nodes are underutilized.
- **[Amazon EKS Anywhere](https://blowstack.com/tools/cloud-services-hub/amazon-eks-anywhere)**: Amazon EKS Anywhere uses Amazon EKS Distro's Kubernetes components to create and operate clusters outside the managed EKS service. It adds tooling for cluster provisioning, upgrades, and lifecycle management.
- **[Amazon Elastic Block Store (Amazon EBS)](https://blowstack.com/tools/cloud-services-hub/amazon-elastic-block-store-(amazon-ebs))**: Amazon EKS Distro clusters on EC2 can use the Amazon EBS CSI driver to provision and attach EBS volumes for Kubernetes persistent volumes. This provides persistent block storage for workloads such as databases.
- **[Amazon Elastic Container Registry (Amazon ECR)](https://blowstack.com/tools/cloud-services-hub/amazon-elastic-container-registry-(amazon-ecr))**: Amazon EKS Distro publishes its component container images through Amazon ECR Public. Clusters can also pull application images from private ECR repositories using appropriately configured registry credentials or the Kubernetes ECR credential provider.
- **[Amazon Elastic File System (Amazon EFS)](https://blowstack.com/tools/cloud-services-hub/amazon-elastic-file-system-(amazon-efs))**: Amazon EKS Distro clusters can use the Amazon EFS CSI driver to mount EFS file systems as Kubernetes persistent volumes. Multiple pods can share the same persistent file storage.
- **[Amazon Elastic Kubernetes Service (Amazon EKS)](https://blowstack.com/tools/cloud-services-hub/amazon-elastic-kubernetes-service-(amazon-eks))**: Amazon EKS uses the Kubernetes components distributed through Amazon EKS Distro. A self-managed EKS Distro cluster can also register through EKS Connector so its configuration and workloads can be viewed in the EKS console.
- **[Amazon FSx](https://blowstack.com/tools/cloud-services-hub/amazon-fsx-(for-all-types))**: Amazon EKS Distro clusters can use compatible CSI drivers to access Amazon FSx file systems. For example, the Amazon FSx for Lustre CSI driver provisions and mounts Lustre-backed persistent volumes for compute-intensive Kubernetes workloads.
- **[Amazon Managed Service for Prometheus](https://blowstack.com/tools/cloud-services-hub/amazon-managed-service-for-prometheus)**: Amazon EKS Distro clusters can forward Prometheus metrics to Amazon Managed Service for Prometheus using a Prometheus remote-write configuration or an AWS Distro for OpenTelemetry collector. This provides managed storage and querying for cluster and application metrics.
- **[Amazon OpenSearch Service](https://blowstack.com/tools/cloud-services-hub/amazon-opensearch-service)**: Amazon EKS Distro clusters can use Fluent Bit or Fluentd to forward Kubernetes container logs to Amazon OpenSearch Service. Logs can then be searched and analyzed centrally rather than retained only on worker nodes.
- **[Amazon Route 53](https://blowstack.com/tools/cloud-services-hub/amazon-route-53)**: Amazon EKS Distro clusters can use ExternalDNS with its Route 53 provider to maintain DNS records from Kubernetes Services and Ingress resources. For example, creating an Ingress can automatically create the corresponding application hostname.
- **[Amazon VPC](https://blowstack.com/tools/cloud-services-hub/amazon-vpc)**: Amazon EKS Distro clusters running on EC2 can use the Amazon VPC CNI plugin for Kubernetes to assign VPC IP addresses to pods. This connects pod networking directly to the VPC network.
- **[AWS Distro for OpenTelemetry](https://blowstack.com/tools/cloud-services-hub/aws-distro-for-opentelemetry)**: Amazon EKS Distro clusters can run AWS Distro for OpenTelemetry collectors to collect application traces and Kubernetes metrics. Collectors can export that telemetry to destinations such as CloudWatch, AWS X-Ray, and Amazon Managed Service for Prometheus.
- **[AWS Identity and Access Management (IAM)](https://blowstack.com/tools/cloud-services-hub/aws-identity-and-access-management-(iam))**: Amazon EKS Distro clusters can use AWS IAM Authenticator to authenticate Kubernetes API requests with IAM identities. Administrators configure mappings from IAM roles or users to Kubernetes users and groups, with Kubernetes RBAC controlling their permissions.
- **[AWS Key Management Service (AWS KMS)](https://blowstack.com/tools/cloud-services-hub/aws-key-management-service-(aws-kms))**: A self-managed Amazon EKS Distro control plane can use the AWS KMS encryption provider with Kubernetes envelope encryption. This protects Kubernetes API data, such as Secrets stored in etcd, using a KMS key.
- **[AWS Private Certificate Authority](https://blowstack.com/tools/cloud-services-hub/aws-private-certificate-authority)**: Amazon EKS Distro clusters can use the AWS Private CA Issuer plugin for cert-manager to obtain certificates from AWS Private Certificate Authority. Kubernetes workloads can request and renew private TLS certificates through certificate resources.
- **[AWS Secrets Manager](https://blowstack.com/tools/cloud-services-hub/aws-secrets-manager)**: Amazon EKS Distro clusters deployed through EKS Anywhere can use the AWS Secrets and Configuration Provider with the Secrets Store CSI Driver and a configured IAM authentication mechanism. This mounts Secrets Manager secrets into pods without embedding their values in application images.
- **[AWS Security Token Service (AWS STS)](https://blowstack.com/tools/cloud-services-hub/aws-security-token-service-(aws-sts))**: Amazon EKS Distro clusters using AWS IAM Authenticator rely on STS to validate the IAM identity behind a Kubernetes authentication token. The authenticator uses a signed STS GetCallerIdentity request to establish the caller's identity.
- **[AWS X-Ray](https://blowstack.com/tools/cloud-services-hub/aws-x-ray)**: Amazon EKS Distro workloads can send distributed traces to AWS X-Ray through an in-cluster AWS Distro for OpenTelemetry collector or X-Ray daemon. This allows requests spanning multiple Kubernetes services to be traced together.
- **[Elastic Load Balancing (ELB)](https://blowstack.com/tools/cloud-services-hub/elastic-load-balancing-(elb))**: Amazon EKS Distro clusters on AWS can use the AWS Load Balancer Controller to provision load balancers from Kubernetes resources. The controller can create Application Load Balancers for Ingress resources and Network Load Balancers for supported LoadBalancer Services.

## What is Amazon EKS Distro

Amazon EKS Distro stands as a discernible milestone in the cloud computing and containerization domain. Initiated by Amazon Web Services (AWS), it mirrors the exact software that powers AWS Elastic Kubernetes Service (EKS), which facilitates running Kubernetes on AWS without needing to install, operate, and maintain your own Kubernetes control plane or nodes.

EKS Distro is designed to let developers leverage a consistent Kubernetes environment not just in the AWS Cloud but across on-premises environments, providing a seamless pathway for applications to migrate or extend from on-premises to cloud. Running containers in production environments demands stability, high performance, and a robust ecosystem of tools and services. Recognizing these requirements, Amazon EKS Distro is built to provide an open-source, community-driven Kubernetes distribution that is battle-tested and hardened, reflecting Amazon's operational expertise in managing thousands of clusters in AWS EKS.

It does not provide out-of-the-box integration with AWS services; organizations configure those integrations themselves. EKS Distro encompasses Kubernetes components, such as the Kubernetes master and node services and etcd (the primary data store for Kubernetes), but does not provide cluster lifecycle management tools.

One of the significant advantages of Amazon EKS Distro is its compatibility with the EKS Console, CLI, and API, ensuring a uniform user experience and control mechanism across both AWS and on-premises environments. This compatibility simplifies tasks like monitoring, scaling, and updating clusters, thereby enabling DevOps teams to concentrate more on development rather than operations. Moreover, it is engineered to receive the same timely security patches and updates that AWS applies to EKS in the cloud. This approach ensures that EKS Distro users benefit from the rapid response to security vulnerabilities that AWS is known for, providing peace of mind regarding the security posture of their Kubernetes clusters.

Amazon EKS Distro also facilitates an ecosystem where developers and businesses can build or adapt applications that are portable across any Kubernetes environment, ensuring that investments in application architecture and development are preserved without vendor lock-in concerns. Enterprises can easily align their development and production environments, reducing the discrepancies that often lead to bugs or unexpected behavior in production deployments. In conclusion, by delivering an open, reliable, and secure Kubernetes distribution with a direct lineage to AWS EKS, Amazon EKS Distro represents a strategic tool for any organization that is serious about adopting or extending their use of containerization.

Whether running in the cloud, on-premises, or in a hybrid setting, EKS Distro offers the versatility, power, and assurance needed to deploy and manage containerized applications with confidence.
