Senior DevOps Engineer at a tech services company with 10,001+ employees
Real User
Top 10
Oct 30, 2025
I appreciate the overall pricing model of AWS, where you pay based on usage, which allows for a clear understanding of costs associated with services. The setup cost is reduced significantly since Amazon EKS simplifies the laborious process of arranging the controller plane, which typically requires substantial human resources and effort. Licensing is straightforward, making it easy to start using the service.
Regarding the pricing aspect and the licensing cost of Amazon EKS, sometimes it is not clear. Most discussions revolve around the data transfer costs from one region to another, and there are certain concerns regarding GPU nodes. However, if you optimize your node usage, with tools such as Kubecost, you can analyze how effectively you utilize your nodes. If you manage to optimize usage, you won't face steep costs. Otherwise, the cloud provider will certainly benefit from inefficient usage. Ultimately, it's not out of the box—if you want to monitor costs effectively, applying separate tools and acting accordingly in advance is essential.
My opinion on the pricing and licensing of Amazon EKS is that it is quite varied, especially when doing projects in the African continent. It's quite expensive considering the local currency with respect to the conversions to dollars or euros, and if this could be lowered, it would help more deployments on our side with Amazon EKS.
Software Engineering Manager at a tech vendor with 1,001-5,000 employees
Real User
Top 20
Aug 29, 2025
The majority of my time setup cost was very affordable, taking just two hours. It was easy as I didn't have to worry about setting all the infrastructure underneath, just using what's there. This saved my time, allowing me to complete the project within several hours instead of days or weeks.
Regarding the pricing of Amazon EKS, if we discuss EKS itself, it's relatively cheap at $75 for deployment for the control plane. However, for running a Kubernetes cluster, you need more resources even for the simplest deployment of any modules. It could be very expensive, but it's mostly about how the architecture is built and how the team controls the resources. It's not about Amazon EKS directly, but related.
Regarding the cost of Amazon EKS, I would say it's relative to the organization based on release management processes; for big organizations where customer experience matters, such as in the retail segment, the cost can be very high due to numerous daily changes. For companies in telecom and retail, as Amazon is a pay-per-use service, our usage levels are high, so I would desire if Amazon could provide certain discounts or credits for customers who utilize a lot of resources.
My experience with pricing for Amazon EKS is limited as there's a separate team for that, and I do not have much knowledge of specifics. However, the pricing is based on the instance type we use in the EKS node group, so it should cover that aspect; their pricing is generally easy to understand in terms of instances.
DevOps Engineer | AWS and Terraform Specialist | Multicloud Experience at a agriculture with 11-50 employees
Real User
Top 10
Apr 28, 2025
We are making a significant effort to transform our usage of Amazon EKS, which was previously rated as eight or nine in terms of cost. Now, it stands at six or seven due to optimizing our workload.
Senior Java Consultant at a comms service provider with 1,001-5,000 employees
Real User
Top 5
Mar 21, 2025
The pricing structure is beneficial for large companies who pay for what they use, but it is not affordable for startups. Offering a free version could help small companies.
I do not have specific details on EKS's pricing and licensing compared to other services. However, in general, deploying in the cloud offers lower latency and high availability and reduces manual intervention and responsibility, leading to some operational efficiencies.
The product pricing depends on the specific requirements. For instance, clients between $3000-$4000 per month might find the pricing reasonable, with clusters priced around $70 to $80 plus additional costs. However, the actual pricing can vary based on the number of services utilized.
The product is available at such a huge scale in the market since the resources that are offered under the tool are competitively priced and available at a much cheaper rate compared to other solutions.
Sr. Software Engineer at a tech vendor with 10,001+ employees
MSP
Apr 28, 2023
The solution is cheaper than AKS. Its license costs $73. The customers have to pay extra depending on the instances they want to deploy for hosting the application. I rate its pricing as a four.
The solution is quite costly and developers will start exploring other solutions or moving their workloads to other clouds if costs aren't reduced. Our client pays the licensing fees so I don't have specifics about its cost, but I hear that the solution is expensive so I am rating it a five out of ten.
Cloud Architect & Devops engineer at KdmConsulting
Real User
Jul 9, 2022
The calculation of the pricing is dependent upon instance type. So when we make a cluster without defining any instance type, it will default enter a large instance type. So as per our requirement, we can create our node group and define our instance types per our workload.
Practice Director, Global Infrastructure Services at a computer software company with 10,001+ employees
Real User
Jan 19, 2022
We already have costs built into the service given by the particular vendor. If it is on-premise, we buy the software, and we pay some support costs and license costs. However, if it is on the cloud, it is a pay-per-use model.
The solution offers different pricing models. They charge in different ways - either per CPU hour or usage based on a machine type. When it comes to pricing, Google may be two cents cheaper, whoever, the difference makes it a bit of a wash. It might mean an extra five dollars or 20 dollars a month. The difference isn't enough to be too noticeable. All of the main competitors charge very competitive pricing. That said, when it comes to the CPUs, that's a Google proprietary technology. When we do machine learning, we do prefer working in Google Cloud, as we have the option to expand all the way to CPU and AWS doesn't have that option. It's a GPU-only system. Amazon's also pushing you towards their own machine learning tool, SageMaker, which we don't want to use. We want to use our own tool.
Amazon Elastic Kubernetes Service (Amazon EKS) is a fully managed Kubernetes service. Customers such as Intel, Snap, Intuit, GoDaddy, and Autodesk trust EKS to run their most sensitive and mission critical applications because of its security, reliability, and scalability.
EKS is the best place to run Kubernetes for several reasons. First, you can choose to run your EKS clusters using AWS Fargate, which is serverless compute for containers. Fargate removes the need to provision and manage...
I appreciate the overall pricing model of AWS, where you pay based on usage, which allows for a clear understanding of costs associated with services. The setup cost is reduced significantly since Amazon EKS simplifies the laborious process of arranging the controller plane, which typically requires substantial human resources and effort. Licensing is straightforward, making it easy to start using the service.
Regarding the pricing aspect and the licensing cost of Amazon EKS, sometimes it is not clear. Most discussions revolve around the data transfer costs from one region to another, and there are certain concerns regarding GPU nodes. However, if you optimize your node usage, with tools such as Kubecost, you can analyze how effectively you utilize your nodes. If you manage to optimize usage, you won't face steep costs. Otherwise, the cloud provider will certainly benefit from inefficient usage. Ultimately, it's not out of the box—if you want to monitor costs effectively, applying separate tools and acting accordingly in advance is essential.
My opinion on the pricing and licensing of Amazon EKS is that it is quite varied, especially when doing projects in the African continent. It's quite expensive considering the local currency with respect to the conversions to dollars or euros, and if this could be lowered, it would help more deployments on our side with Amazon EKS.
The majority of my time setup cost was very affordable, taking just two hours. It was easy as I didn't have to worry about setting all the infrastructure underneath, just using what's there. This saved my time, allowing me to complete the project within several hours instead of days or weeks.
Regarding the pricing of Amazon EKS, if we discuss EKS itself, it's relatively cheap at $75 for deployment for the control plane. However, for running a Kubernetes cluster, you need more resources even for the simplest deployment of any modules. It could be very expensive, but it's mostly about how the architecture is built and how the team controls the resources. It's not about Amazon EKS directly, but related.
The pricing is cheap, around two USD per day for one cluster, and I think it's a good price.
Regarding the cost of Amazon EKS, I would say it's relative to the organization based on release management processes; for big organizations where customer experience matters, such as in the retail segment, the cost can be very high due to numerous daily changes. For companies in telecom and retail, as Amazon is a pay-per-use service, our usage levels are high, so I would desire if Amazon could provide certain discounts or credits for customers who utilize a lot of resources.
My experience with pricing for Amazon EKS is limited as there's a separate team for that, and I do not have much knowledge of specifics. However, the pricing is based on the instance type we use in the EKS node group, so it should cover that aspect; their pricing is generally easy to understand in terms of instances.
We are making a significant effort to transform our usage of Amazon EKS, which was previously rated as eight or nine in terms of cost. Now, it stands at six or seven due to optimizing our workload.
The pricing structure is beneficial for large companies who pay for what they use, but it is not affordable for startups. Offering a free version could help small companies.
I do not have specific details on EKS's pricing and licensing compared to other services. However, in general, deploying in the cloud offers lower latency and high availability and reduces manual intervention and responsibility, leading to some operational efficiencies.
The product pricing depends on the specific requirements. For instance, clients between $3000-$4000 per month might find the pricing reasonable, with clusters priced around $70 to $80 plus additional costs. However, the actual pricing can vary based on the number of services utilized.
The product is available at such a huge scale in the market since the resources that are offered under the tool are competitively priced and available at a much cheaper rate compared to other solutions.
Amazon EKS is not a cheap solution.
Amazon EKS is expensive.
The tool's pricing is good.
The solution's pricing is fair enough and a little less costly.
I rate EKS seven out of 10 for affordability. Amazon EKS costs us $730 a year.
The solution is pricey. The tool's pricing is monthly.
The solution is cheaper than AKS. Its license costs $73. The customers have to pay extra depending on the instances they want to deploy for hosting the application. I rate its pricing as a four.
Amazon EKS is very cost-effective. I rate the pricing a ten on a scale of one to ten.
Amazon EKS has fair pricing. It's better in terms of pricing than other platforms.
The price could be cheaper. I would rate it as seven out of ten. There are no extra costs in addition to the standard license.
It's a subscription and depends on the cluster nodes and other effects. There are many calculation criteria for licensing.
The solution is quite costly and developers will start exploring other solutions or moving their workloads to other clouds if costs aren't reduced. Our client pays the licensing fees so I don't have specifics about its cost, but I hear that the solution is expensive so I am rating it a five out of ten.
The calculation of the pricing is dependent upon instance type. So when we make a cluster without defining any instance type, it will default enter a large instance type. So as per our requirement, we can create our node group and define our instance types per our workload.
My company paid for the license.
We already have costs built into the service given by the particular vendor. If it is on-premise, we buy the software, and we pay some support costs and license costs. However, if it is on the cloud, it is a pay-per-use model.
The solution is more expensive than other competitors and does not require a license.
The solution offers different pricing models. They charge in different ways - either per CPU hour or usage based on a machine type. When it comes to pricing, Google may be two cents cheaper, whoever, the difference makes it a bit of a wash. It might mean an extra five dollars or 20 dollars a month. The difference isn't enough to be too noticeable. All of the main competitors charge very competitive pricing. That said, when it comes to the CPUs, that's a Google proprietary technology. When we do machine learning, we do prefer working in Google Cloud, as we have the option to expand all the way to CPU and AWS doesn't have that option. It's a GPU-only system. Amazon's also pushing you towards their own machine learning tool, SageMaker, which we don't want to use. We want to use our own tool.