TrustRadius

Amazon Elastic Kubernetes Service (EKS) vs. Kubernetes

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
Amazon EKS
Score 8.4 out of 10
N/A
Amazon Elastic Kubernetes Service (Amazon EKS) is a managed container service to run and scale Kubernetes applications in the cloud or on-premises, available on AWS or on-premise through Amazon EKS Anywhere.
$0.10
per hour of each cluster created
Kubernetes
Score 9.3 out of 10
N/A
Kubernetes is an open-source container cluster manager.N/A
Pricing
Amazon Elastic Kubernetes Service (EKS)Kubernetes
Editions & Modules
Amazon EKS Cluster
$.10
per hour of each cluster created
No answers on this topic
Offerings
Pricing Offerings
Amazon EKSKubernetes
Free Trial
NoNo
Free/Freemium Version
NoNo
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional Details——
More Pricing Information
Community Pulse
Amazon Elastic Kubernetes Service (EKS)Kubernetes
Considered Both Products
Amazon EKS
Verified User
Anonymous
Chose Amazon EKS
Depends on the public cloud using and better integrations within the cloud native services. Using AWS cloud for majority of the platform so it was better to use the same vendor service
Verified User
Anonymous
Chose Amazon EKS
It feels like AWS is behind the EKS race, the only advantage I'm able to see right now is the support of IPv6, however, trying to promote AWS alternatives that are different from the market and more like a vendor locking solutions like ECS/Fargate have kept AWS behind and …
Kubernetes
Verified User
Anonymous
Chose Kubernetes
It stacks well against OpenShift. The only downside for OpenShift is the multiple operators and the custom logic implemented in the product, plus the upgrades, which tend to be a bit longer due to the more complex implementation. Overall, these are similar products but with a …
Verified User
Anonymous
Chose Kubernetes
Nomad is a simpler, more down-to-earth alternative to Kubernetes. In some sense, it is more similar to Amazon's ECS, but with more bells and whistles. For use cases not requiring the whole complexity of Kubernetes platform, Nomad can provide a much simpler and at the same time …
Verified User
Anonymous
Chose Kubernetes
We evaluated Docker Swarm as usage of docker is very distributed in our company. But docker swarm has not as many features as kubernetes and we have large, complex architectures which require good scalability and robustness - this is a huge strength of kubernetes compared to …
AL
Agustin Lacorazza
Infraestructure and Security Leader
Chose Kubernetes
Well, me and me team select Kubernetes for the natural solution and the easily assignation of resources to deploy a solution than could have multiple clients in the same infrastructure, so, for each one client we are running a set of different pods, and that's why we select …
PS
Pradeep Sharma
Senior Specialist
Chose Kubernetes
Kubernetes cluster is cable to manage multiple nodes on on-premises or cloud infrastructure. In Kubernetes, we can easily add new nodes when ever required. We can easily update and rollback our application hosted on Kubernetes with the help of rolling and blue green deployment. …
Verified User
Anonymous
Chose Kubernetes
Most of the required features for any orchestration tool or framework, which is provided by Kubernetes. After understanding all modules and features of the K8S, it is the best fit for us as compared with others out there.
Verified User
Anonymous
Chose Kubernetes
I didn't have too much experience or exposure to OpenShift but I do remember that in certain areas our organization found Kubernetes to be more useful and met our needs in comparison to OpenShift. Although I can't compare, I think it's easier to customize Kubernetes because of …
Verified User
Anonymous
Chose Kubernetes
Kubernetes is very unique. I do not think there are any competitors to take over its leading place. And you can always use Kuberntes with other tools to make the whole system better. Kubernetes is backed up by Google and has been tested over the years. It is reliable, fast, and …
Verified User
Anonymous
Chose Kubernetes
When planning our latest product we tried out many hosted container service and a few local tools. These included services run by Google, Microsoft, and Amazon and tools from companies like Docker and Apache. We ended up selecting Kubernetes because it was compatible with all …
Verified User
Anonymous
Chose Kubernetes
I used OpenShift v2 - which was pre-Kubernetes. (It now uses Kubernetes under the hood - but keeps it fairly hidden). Kubernetes was a ton more stable and easier to use. No more custom CLI to use in order to script together deployments. No more messy ‘push your entire code …
Verified User
Anonymous
Chose Kubernetes
Docker Swarm is not as advanced as Kubernetes and there are no out of the box solutions for auto scaling and deployment strategies. Docker swarm doesnot have much experience with production deployments at scale. Swarm has a smaller community, and less frequent releases as …
Adam Eivy | TrustRadius Reviewer
Adam Eivy
Developer Solutions Architect
Chose Kubernetes
With AWS ECS, you have to provision the virtual hardware, then use that hardware as a pool for your container service. Each service has to be built out and scaled independently. Kubernetes allows us to use a cluster of machines like a big pool of resources, scaling and shipping …
Verified User
Anonymous
Chose Kubernetes
Kubernetes is a great alternative to cloud hosted expensive solutions. It is extremely well documented and maintained. It is probably the best home-grown solution available for container infrastructure management.
Jake Luby | TrustRadius Reviewer
Jake Luby
Lead Engineer
Chose Kubernetes
We already had an enterprise Kubernetes 8 set up, so once we got our namespace it took me about 2 weeks to go from not knowing anything to having a self-contained jar in a container, running on Kubernetes 8. In comparison, it took me two weeks to install Java on a blank server …
AK
Asad Khan
Technical CARE Specialist
Chose Kubernetes
As I said earlier also -
- K8s manage the workloads better as compared to OpenStack in terms of reliability, observability & reachability.
- K8s is not limited to only a single networking or storage solution as compared to OpenStack.
Features
Amazon Elastic Kubernetes Service (EKS)Kubernetes
Container Management
Comparison of Container Management features of Product A and Product B
Amazon Elastic Kubernetes Service (EKS)
8.9
Ratings
14% above category average
Kubernetes
8.4
Ratings
8% above category average
Security and Isolation9.00 Ratings8.50 Ratings
Container Orchestration8.00 Ratings9.50 Ratings
Cluster Management8.00 Ratings9.50 Ratings
Storage Management9.00 Ratings7.00 Ratings
Resource Allocation and Optimization9.00 Ratings7.50 Ratings
Discovery Tools8.00 Ratings8.50 Ratings
Update Rollouts and Rollbacks9.00 Ratings8.50 Ratings
Self-Healing and Recovery10.00 Ratings8.50 Ratings
Analytics, Monitoring, and Logging10.00 Ratings8.00 Ratings
Best Alternatives
Amazon Elastic Kubernetes Service (EKS)Kubernetes
Small Businesses
Portainer
Portainer
Score 9.6 out of 10
Portainer
Portainer
Score 9.6 out of 10
Medium-sized Companies
Red Hat OpenShift
Red Hat OpenShift
Score 9.3 out of 10
Red Hat OpenShift
Red Hat OpenShift
Score 9.3 out of 10
Enterprises
Red Hat OpenShift
Red Hat OpenShift
Score 9.3 out of 10
Red Hat OpenShift
Red Hat OpenShift
Score 9.3 out of 10
All AlternativesView all alternativesView all alternatives
User Ratings
Amazon Elastic Kubernetes Service (EKS)Kubernetes
Likelihood to Recommend
9.0
(0 ratings)
9.5
(0 ratings)
Usability
9.0
(0 ratings)
8.0
(0 ratings)
User Testimonials
Amazon Elastic Kubernetes Service (EKS)Kubernetes
Likelihood to Recommend
Well suited for microservices architecture but can be a bit costly if less number of microservices or monolithic architecture hosted to be hosted on containers. Use of hybrid cluster instances also works well using both normal and fargate instances. Also the integration of audit and diagnostic logs of master nodes helps to reduce the unwanted access related issues.
Verified User
Anonymous
Read full review
Along with all the best features and support by k8s, the automatic container scheduling to worker nodes and also self-healing containers which is what I like the most. On the other side, when I was installing the k8s cluster on CentOS 8, it was quite difficult for me, but never mind it is working as we expected and it is a one-time effort. Especially, in my case, there are more than 7 application containers required to run and communicate with each other, so for us, Kubernetes is an optimal solution.
Verified User
Anonymous
Read full review
Pros
  • Upgrade the kubernetes clusters to the latest version with a single click
  • Auto scaling policies to automatically scale the nodes
  • Detailed logs and events on the cluster within the EKS clusters portal, cloudwatch logs and metrics
Verified User
Anonymous
Read full review
  • Complex cluster management can be done with simple commands with strong authentication and authorization schemes
  • Exhaustive documentation and open community smoothens the learning process
  • As a user a few concepts like pod, deployment and service are sufficient to go a long way
Nitin Pasumarthy | TrustRadius Reviewer
Nitin Pasumarthy
Web & Network Performance
Read full review
Cons
  • AWSIAM integration with Kubernetes RBAC could be better.
  • Enabling some add-ons like service mesh, and monitoring will be nice instead of having to install them yourself after the creation of the cluster.
  • EKS bootstrap time could be faster ...
Verified User
Anonymous
Read full review
  • Local development, Kubernetes does tend to be a bit complicated and unnecessary in environments where all development is done locally.
  • The need for add-ons, Helm is almost required when running Kubernetes. This brings a whole new tool to manage and learn before a developer can really start to use Kubernetes effectively.
  • Finicy configmap schemes. Kubernetes configmaps often have environment breaking hangups. The fail safes surrounding configmaps are sadly lacking.
Verified User
Anonymous
Read full review
Likelihood to Renew
No answers on this topic
The Kubernetes is going to be highly likely renewed as the technologies that will be placed on top of it are long term as of planning. There shouldn't be any last minute changes in the adoption and I do not anticipate sudden change of the core underlying technology. It is just that the slow process of technology adoption that makes it hard to switch to something else.
Verified User
Anonymous
Read full review
Usability
Cluster maintanence is reduced, easier to deploy resources, great observability insights
Verified User
Anonymous
Read full review
It is an eminently usable platform. However, its popularity is overshadowed by its complexity. To properly leverage the capabilities and possibilities of Kubernetes as a platform, you need to have excellent understanding of your use case, even better understanding of whether you even need Kubernetes, and if yes - be ready to invest in good engineering support for the platform itself
Verified User
Anonymous
Read full review
Alternatives Considered
It feels like AWS is behind the EKS race, the only advantage I'm able to see right now is the support of IPv6, however, trying to promote AWS alternatives that are different from the market and more like a vendor locking solutions like ECS/Fargate have kept AWS behind and focusing on the wrong things. EKS needs to really improve its integration with the Kubernetes ecosystem and have an enterprise solution for monitoring, backups, and service mesh.
Verified User
Anonymous
Read full review
As I said earlier also - - K8s manage the workloads better as compared to OpenStack in terms of reliability, observability & reachability. - K8s is not limited to only a single networking or storage solution as compared to OpenStack. - Networking (which is a key concept) is much simpler in K8s as compared to OpenStack. - It is possible to upgrade your applications without downtime in K8s but in OpenStack, you either have to divert the traffic or face an outage because you have to delete the whole stack & then recreate it.
Asad Khan | TrustRadius Reviewer
Asad Khan
Technical CARE Specialist
Read full review
Return on Investment
  • Migrating all our workloads from ec2 VMs to containers running in Kubernetes has been a huge improvement for the management and resilience of our Infrastructure.
  • EKS Upgrade process to a new version seems to be taking very long ....
  • EKS creation time usually takes over 10 minutes in us-east-1, we would like faster creation times to be under 5 minutes.
Verified User
Anonymous
Read full review
  • Because of microservices, Kubernetes makes it easy to find the cost of each application easily.
  • Like every new technology, initially, it took more resources to educate ourselves but over a period of time, I believe it's going to be worth it.
Verified User
Anonymous
Read full review
ScreenShots