Pricing overview
Amazon Elastic Kubernetes Service (Amazon EKS) is a managed Kubernetes service that lets you run Kubernetes applications without managing, securing, or scaling a Kubernetes control plane. With Amazon EKS, there are no minimum fees or upfront commitments. Amazon EKS has per cluster pricing based on Kubernetes cluster version support, pricing for Amazon EKS Auto Mode, and per vCPU pricing for Amazon EKS Hybrid Nodes. You also pay for the resources you use to run your applications on Kubernetes worker nodes such as Amazon EC2 instances, Amazon EBS volumes, and public IPv4 addresses.
AWS Pricing Calculator
Calculate your Amazon EKS and architecture cost in a single estimate.
Pricing details
Amazon EKS cluster pricing
All Amazon EKS clusters have a per cluster per hour fee based on the cluster’s Kubernetes version. A Kubernetes version is under standard support for the first 14 months after it’s released in Amazon EKS. Once a Kubernetes version is past the end of standard support date, it enters extended support for the next 12 months, enabling you to stay at a given Kubernetes version for longer for an additional cost. To learn more about Kubernetes version support in Amazon EKS, visit the Amazon EKS documentation.
| Kubernetes Version Support Tier | Pricing |
|---|---|
| Standard Kubernetes version support | $0.10 per cluster per hour |
| Extended Kubernetes version support | $0.60 per cluster per hour |
Amazon EKS Auto Mode
This pricing applies to Amazon EKS clusters where EKS Auto Mode is enabled. You pay for Amazon EKS Auto Mode based on the duration and type of Amazon EC2 instances launched and managed by EKS Auto Mode. The Amazon EKS Auto Mode prices below are in addition to the Amazon EC2 instance price, which covers the EC2 instances themselves. Like EC2 instance charges, EKS Auto Mode charges are billed per-second, with a one-minute minimum. While you can leverage the full range of Amazon EC2 instance purchase options with EKS Auto Mode, including On Demand, one- and three-year Reserved Instances, Compute Savings Plans, and Spot Instances, the EKS Auto Mode charges are independent of the EC2 instance purchase option.
Amazon EKS Hybrid Nodes pricing
With Amazon EKS Hybrid Nodes, you can use your on-premises and edge infrastructure as nodes in Amazon EKS clusters to unify your Kubernetes management across cloud, on-premises, and edge environments. Amazon EKS Hybrid Nodes are charged per vCPU per hour based on the resources of the nodes as reported to Kubernetes. Billing for Amazon EKS Hybrid Nodes starts when nodes join the cluster and stops when nodes are removed from the cluster. Amazon EKS Hybrid Nodes pricing tiers are applied to aggregate monthly vCPU-hour usage in the same AWS Region, within the account. If you’re using consolidated billing in AWS Organizations, pricing tiers are applied to the aggregate monthly vCPU-hours of your Amazon EKS Hybrid Nodes running in the same AWS Region, across the accounts in the organization. You are charged the hybrid nodes fee if you use Amazon EC2 instances for your hybrid nodes infrastructure. To learn more about Amazon EKS Hybrid Nodes, visit the Amazon EKS documentation.
| Usage Range | Pricing |
|---|---|
| First 576,000 monthly vCPU-hours | $0.020 per vCPU per hour |
| Next 576,000 monthly vCPU-hours | $0.014 per vCPU per hour |
| Next 4,608,000 monthly vCPU-hours | $0.010 per vCPU per hour |
| Next 5,760,000 monthly vCPU-hours | $0.008 per vCPU per hour |
| Over 11,520,000 monthly vCPU-hours | $0.006 per vCPU per hour |
Other AWS services pricing
When using Amazon EKS, you pay separately for the AWS resources you use to run your applications on Kubernetes worker nodes. For example, if you are running Kubernetes worker nodes as Amazon EC2 instances with Amazon EBS volumes and public IPv4 addresses, you are charged for the instance capacity through Amazon EC2, the volume capacity through Amazon EBS, and the IPv4 address through Amazon VPC. Visit the respective pricing pages of the AWS services you are using with your Kubernetes applications for detailed pricing information.
Amazon EKS local clusters on AWS Outposts has the same Amazon EKS cluster fee for standard Kubernetes version support and does not have extended Kubernetes version support. The Amazon EKS cluster fee is not included in the AWS Outposts pricing for both Amazon EKS extended and local cluster deployment options. Visit the AWS Outposts pricing page for information on AWS Outposts pricing.
If you are using AWS Fargate, pricing is calculated based on the vCPU and memory resources used from the time you start to download your container image until the Amazon EKS pod terminates, rounded up to the nearest second. A minimum charge of one minute applies. Visit the AWS Fargate pricing page for more information on AWS Fargate pricing.
Pricing examples
-
Example 1: Extended support
You create an Amazon EKS cluster on a Kubernetes version the day Amazon EKS releases it, and you run the cluster for the next 26 months without upgrading the control plane version. You pay $0.10 per hour during the first 14 months when the version is in standard support. After 14 months, the Kubernetes version transitions to extended support. You now pay $0.60 per hour for the remaining 12 months. During the 26-monthperiod, on average, you will pay $0.33 per hour to run this cluster.
Support type Usage (Months) Price (per cluster per hour) Standard 14 $0.10 Extended 12 $0.60 Average cost for 26 months of support $0.33 -
Example 2: Hybrid Nodes Data Center Use Case
Your company is in the process of modernizing on-premises applications to run in containers. Some of your applications will move to the cloud but others must remain on premises. You have a small platform engineering team that is responsible for running Kubernetes clusters for business units to use to run their applications. You choose to use Amazon EKS Hybrid Nodes to reduce the time your team spends managing Kubernetes.There are 3 business units onboarding to your platform. Business unit 1 will run 10 nodes, 8 vCPU per node. Business unit 2 will run 5 nodes, 4vCPU per node. Business unit 3 will run 3 nodes, 16 vCPU per node. You will use separate Amazon EKS clusters for each business unit and will use Kubernetes versions under standard support. The monthly cost breakdown for each business unit is shown in the table below. Note, the vCPU-hours are all charged at the rate of $0.02 per vCPU per hour because the usage does not exceed 576,000 monthly vCPU-hours.
Cluster Nodes vCPU/node Hours/month vCPU-hours Cluster charge Node charge Total charge Business Unit 1 1 10 8 730 58,400 $73.00 $1,168.00 $1,241.00 Business Unit 2 1 5 4 730 14,600 $73.00 $292.00 $365.00 Business Unit 3 1 3 16 730 35,040 $73.00 $700.80 $773.80 Total Monthly EKS charges 108,040 $219.00 $2,233.80 $2,379.80 -
Example 3: Hybrid Nodes Edge Use Case
Your company is looking to improve the application delivery and operations in 50 factories located around the world. Your team is responsible for defining, deploying, and maintaining the Kubernetes-based platform that will host applications in each factory. You choose to use Amazon EKS Hybrid Nodes to reduce the infrastructure requirements for each site and to more easily manage the scale of your deployments that span the world.
Each cluster you deploy will have 3 nodes with 8 vCPU per node. You will use separate Amazon EKS clusters for each factory so you can independently update and scale each cluster. The monthly cost breakdown for deployment is shown in the table below. Note, 576,000 vCPU-hours are charged at the rate of $0.02 per vCPU per hour and 300,000 vCPU-hours are charged at the rate of $0.014 per vCPU per hour.
Clusters Nodes vCPU/node Hours/month vCPU-hours Cluster charge Node charge Total charge Factory platform 50 150 8 730 876,000 $3,650.00 $15,720.00 $19,370.00 -
Example 4: EKS Auto Mode
You are looking to deploy a new containerized application to Amazon EKS. You chose Amazon EKS Auto Mode to reduce the effort required to manage the infrastructure of your EKS cluster.
The containerized applications is comprised of three Kubernetes pods, or sets of containers, one that delivers a web-based front end user interface to end-users which needs 0.5 vCPU and 1GB of memory, another that is responsible for the backend of the web application which needs 2 vCPU and 5GB of memory, and another that runs periodic batch data processing jobs which needs 1 vCPU and 8 GB of memory. On average, you expect the frontend to need 6 pods to meet demand, the backend to need 10 pods, and 2 data processing pods. Except for the batch data processing pods, each pod is also configured to run across a minimum of two Availability Zones, for high-availability.
You deploy your application in the US West (Oregon) region. EKS Auto Mode calculates that the most cost-effective EC2 instances to meet the needs of your application are a mix of c6a.2xlarge, c6a.4xlarge, m5a.2xlarge, and m5a.xlarge. EKS Auto Mode charges a management fee that varies based on the EC2 instance type launched, in addition to your regular EC2 instance costs. Below shows the total costs for EKS Auto Mode, including the regular EC2 instance costs, for each hour and each month your application runs:
Qty EC2 Instance EKS Auto Mode c6a.2xlarge 1 $0.306 $0.03672 c6a.4xlarge 1 $0.612 $0.07344 m5a.2xlarge 1 $0.344 $0.04128 m5a.xlarge 1 $0.172 $0.02064 Total per Hour $1.434 $0.17208 Total per Month $1,046.82 $125.62