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
Docker
Score 8.3 out of 10
N/A
Docker Enterprise was sold to Mirantis in 2019; that product is now sold as Mirantis Kubernetes Engine. But Docker now offers a 2-product suite that includes Docker Desktop, which they present as a fast way to containerize applications on a desktop; and, Docker Hub, a service for finding and sharing container images with a team and the Docker community, a repository of container images with an array of…
$0
unlimited public repositories
Pricing
Amazon Elastic Kubernetes Service (EKS)
Docker
Editions & Modules
Amazon EKS Cluster
$.10
per hour of each cluster created
Free
$0
unlimited public repositories
Pro
$5.00
per month per user
Team
$7.00
per month per user
Business
$21
per month per user
Offerings
Pricing Offerings
Amazon EKS
Docker
Free Trial
No
No
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Amazon Elastic Kubernetes Service (EKS)
Docker
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
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 …
It is easy to use. we can manage multiple images in docker hub. Docker desktop is for accessing images in our desktop. It is very much user friendly as compare to podman.
Docker is by far the industry leader and mainstay when it comes to virtual machines, its really hard to justify using another service like Vagrant. The upcoming monetization of Docker desktop should make things interesting though.
We need a solution where initially we can use an OS to trigger our pipeline to be used by terraform and then later in ansible. After doing all work it automatically get exited and we can reclaim the space of our VM. So we created a gitlab pipeline and at the initial stage we …
The features and capabilities provided by Docker are incomparable and much vast in nature. Docker is much light weight and easy to onboard into the tech stack. It is also well supported by Container orchestration systems like Kubernetes which will be critical when applications …
Did use containerd or LXC for brief evaluation in the past, but settled on Docker and only see Docker as the mainstay for most organizations I worked in, as the container tool of choice so far. Docker is matured, feature-rich, and reliable enough to be the main choice all …
The reason why we are still using Docker right now is due to that is the best among its peers and suits our needs the best. However, the trend we foresee for the future might indicate Amazon lambda could potentially fit our needs to code enviornmentless in the near future.
Docker provides is effective container management and orchestration platform. It is highly suitable for Linux environments and allows the easy and quick deployment of production applications Other alternatives use replication and management of the virtual machines. Docker …
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.
You are going to be able to find the most resources and examples using Docker whenever you are working with a container orchestration software like Kubernetes. There will always some entropy when you run in a container, a containerized application will never be as purely performant as an app running directly on the OS. However, in most scenarios this loss will be negligible to the time saved in deployment, monitoring, etc.
I have been using Docker for more than 3 years and it really simplifies the modern application development and deployment. I like the ability of Docker to improve efficiency, portability and scalability for developers and operations teams. Another reason for giving this rating is because Docker integrates CI/CD pipelines very well
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.
We need a solution where initially we can use an OS to trigger our pipeline to be used by terraform and then later in ansible. After doing all work it automatically get exited and we can reclaim the space of our VM. So we created a gitlab pipeline and at the initial stage we defined a docker file which will be our base image and we performed all our activities inside that image to build infrastructure using terraform. Integration we have done in our gitlab pipeline and finally we remove the docker image so that the space can be reclaimed immediately.
It is the only tool in our toolset that has not [had] any issues so far. That is really a mark of reliability, and it's a testimony to how well the product is made, and a tool that does its job well is a tool well worth having. It is the base tool that I would say any organisation must have if they do scalable deployment.
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.