Try our new research platform with insights from 80,000+ expert users

Amazon EKS vs HashiCorp Nomad comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Oct 13, 2024

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Amazon EKS
Ranking in Container Management
2nd
Average Rating
8.6
Reviews Sentiment
7.3
Number of Reviews
46
Ranking in other categories
Container Security (14th)
HashiCorp Nomad
Ranking in Container Management
13th
Average Rating
8.0
Reviews Sentiment
7.1
Number of Reviews
2
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of January 2025, in the Container Management category, the mindshare of Amazon EKS is 19.3%, down from 19.6% compared to the previous year. The mindshare of HashiCorp Nomad is 3.1%, up from 3.0% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Container Management
 

Featured Reviews

Venkatramanan C.S. - PeerSpot reviewer
Amazon EKS: Why It Shines, Where It Struggles, and How It Can Improve
* EKS incurs an additional management fee ($0.10 per hour per cluster) along with EC2 or Fargate costs.May be expensive for smaller workloads compared to alternatives like AWS ECS.Requires expertise to configure and manage Kubernetes resources effectively.Networking (e.g., setting up VPCs, subnets, and service endpoints) can be complex.Simplifies managing multiple Kubernetes clusters, especially for organizations with hybrid or multi-region setups.Integrated dashboards for Kubernetes metrics, logs, and traces.Simplifies observability without needing third-party tools.
Zeeshan Akhtar - PeerSpot reviewer
Has out of the box features , which is good for companies that don't want to spend too much time on research
I've noticed a few UI issues. For example, when monitoring services and tasks, sometimes the tasks keep disconnecting. If you open the shell in HashiCorp Nomad using the exit button, it often disconnects, and you have to log in again. Sometimes, when I check the logs in the UI for microservices tasks, I encounter an issue where the logs are not visible. However, if I log in again after some time, refresh the page, or check a different container, the logs usually appear. These logs are being generated, as I can see them being shipped to my LogView. I'm not sure if this is a product issue or something related to our deployment, but I've noticed it.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"Initial setup is straightforward. It only takes 15 minutes to deploy."
"The tool works well with the nodes in AWS. It's scalability is also good in terms of architecture."
"The solution is easy-to-set up."
"Break down your application into small modules to improve resiliency"
"EKS provides autoscaling functionality."
"The scalability has really helped us a lot in enhancing the customer experience and ensuring quick results."
"AWS cloud services are flexible and have thorough documentation. AWS also has data centers all over the world."
"The serverless capability of Amazon EKS is quite valuable."
"You could get most of HashiCorp Nomad's features from other microservice orchestrators like Kubernetes. The tool's advantage is its ease of use and integration with services like Envoy. With Kubernetes, you must think about many things, like UI integration, which vault to use, and how to discover the service. With the tool, many things come out of the box, making it easy to start. For example, using the Ingress proxy with the tool is quite easy, while it's trickier with Kubernetes."
"If you face an issue with an image during deployment, the solution will automatically revert to the last stable image."
 

Cons

"The management of the nodes in Amazon EKS should be improved."
"I'd like to see the solution add a service catalog."
"I'm having difficulty getting my AWS clusters to communicate with my local machine."
"I am not impressed with the tool's Amazon console. It also needs to add security features."
"It's difficult to connect to some of the clusters."
"Setup depends on what kind of architecture you have"
"An area for improvement in Amazon EKS is the user experience. The platform could be more user-friendly. Only an expert can manage and use it."
"The solution should include a popup for clusters so that all relevant information is visible at the bottom of a page."
"It would be good to have a UI interface so that developers could receive notifications for jobs in a bad state."
"I've noticed a few UI issues. For example, when monitoring services and tasks, sometimes the tasks keep disconnecting. If you open the shell in HashiCorp Nomad using the exit button, it often disconnects, and you have to log in again. Sometimes, when I check the logs in the UI for microservices tasks, I encounter an issue where the logs are not visible. However, if I log in again after some time, refresh the page, or check a different container, the logs usually appear. These logs are being generated, as I can see them being shipped to my LogView. I'm not sure if this is a product issue or something related to our deployment, but I've noticed it."
 

Pricing and Cost Advice

"The tool's pricing is good."
"Amazon EKS is very cost-effective."
"The solution is cheaper than one of its competitors."
"Cloud based pay-as-you-go pricing"
"I rate Amazon EKS’s pricing a nine out of ten."
"The solution's pricing is fair enough and a little less costly."
"Amazon EKS is expensive."
"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."
Information not available
report
Use our free recommendation engine to learn which Container Management solutions are best for your needs.
831,997 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
21%
Computer Software Company
14%
Manufacturing Company
8%
Insurance Company
7%
Financial Services Firm
19%
Computer Software Company
17%
Government
9%
Comms Service Provider
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

What do you like most about Amazon EKS?
The product's most valuable features are scalability, observability, and performance.
What is your experience regarding pricing and costs for Amazon EKS?
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 i...
What needs improvement with Amazon EKS?
* EKS incurs an additional management fee ($0.10 per hour per cluster) along with EC2 or Fargate costs.May be expensive for smaller workloads compared to alternatives like AWS ECS.Requires expertis...
What needs improvement with HashiCorp Nomad?
Sometimes, the job is in a bad state, and we don't get any notifications. It would be good to have a UI interface so that developers could receive notifications for jobs in a bad state.
What is your primary use case for HashiCorp Nomad?
We use HashiCorp Nomad mainly to deploy our images in the form of jobs. It is also used for load balancing, containerization, and instance deployment.
What advice do you have for others considering HashiCorp Nomad?
I would recommend HashiCorp Nomad to other users because it is the best tool for deployment. It is easy for a beginner to learn to use HashiCorp Nomad for the first time. Any developer with a decen...
 

Also Known As

Amazon Elastic Kubernetes Service
No data available
 

Overview

 

Sample Customers

GoDaddy, Pearson, FICO, Intuit, Verizon, Honeywell, Logicworks, RetailMeNot, LogMeIn, Conde Nast, mercari, Trainline, Axway
Information Not Available
Find out what your peers are saying about Amazon EKS vs. HashiCorp Nomad and other solutions. Updated: January 2025.
831,997 professionals have used our research since 2012.