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

Amazon Elastic Container Service vs Google Kubernetes Engine comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Oct 13, 2024
 

Categories and Ranking

Amazon Elastic Container Se...
Ranking in Container Management
7th
Average Rating
8.4
Reviews Sentiment
6.7
Number of Reviews
48
Ranking in other categories
Containers as a Service (CaaS) (1st)
Google Kubernetes Engine
Ranking in Container Management
8th
Average Rating
8.0
Reviews Sentiment
7.6
Number of Reviews
36
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of December 2024, in the Container Management category, the mindshare of Amazon Elastic Container Service is 2.3%, down from 3.3% compared to the previous year. The mindshare of Google Kubernetes Engine is 2.9%, down from 3.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Container Management
 

Featured Reviews

Salvador Fernández - PeerSpot reviewer
Helps to maintain a global file system but improvement is needed in backup
Implementing the product has helped me monitor the parameters. I utilize tools like CloudWatch and AWS systems to track these parameters. If any issues arise, I alert our developer team to address and resolve them. The product helps to have a global file system. Also, it helps in data replication from region to region.
Abhilash Gopidas - PeerSpot reviewer
The auto-scaling feature helps during peak hours, but the support is not great
The product has no downtime. Automated scaling is a valuable feature. During peak hours, the datasets are on a higher volume. We need scaling in place. Otherwise, there's a degradation in the performance. We might sometimes miss data, or there will be no data sync between systems. Auto-scaling helps deal with performance needs during peak hours. There's no lag time for processing data.

Quotes from Members

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

Pros

"The solution is easy to scale and implement and provides performance monitoring and management tools."
"It has an Auto Scaling group feature. We can use this feature to have an Auto Scaling group to specify a minimum and maximum count for all types of configurations. Based on the specified values, Amazon Elastic Container Service scales the required CPU environmental metrics."
"For Amazon EC2 Container Service, providing the ability for users to select specific processor, memory, disk, and interface types might be an ideal feature. But, the practicality of offering all possible physical combinations is nearly impossible due to the underlying physical machines. AWS and Azure organize options into groups based on essential components like powerful processors or critical interfaces, considering physical restrictions. While expanding these choices is conceivable, it may not be feasible from a financial and practical perspective. Customers generally comprehend this limitation, as even in their own data centers, exact physical machine requirements are often a result of a combination of factors such as price, availability, and new machine generations."
"I like Amazon EC2 Container Service's elasticity."
"We primarily employ the Linux platform in terms of architecture. It utilizes its database, MySQL. Additionally, for CI/CD processes, we rely on Amazon CodeBuild. Furthermore, we use Amazon S3 storage to store specific static files. Currently, the system is running smoothly, and we don't actively perform any maintenance tasks as everything is automated."
"Scalability and availability are the most valuable features of Amazon Elastic Container Service."
"The tool's most valuable feature is the ability to create revisions on the configurations."
"Amazon ECS allows users to deploy and manage container applications like microservices or web applications on Amazon clusters. It's easy to install and designed for AWS targets, serving as a serverless container platform. It offers features such as automatic scanning, load balancing, and service discovery to help users manage their container applications."
"The most beneficial feature is the ability to separate each project and manage permissions more effectively."
"The solution is more user-friendly than AWS or Azure. I can also easily scale out the service in the future when the number of customers grows. GKE is the leader of Kubernetes service and it can be easily updated. I love the tool's user interfaces."
"The initial setup is very easy. We can create our cluster using the command line, or using our console."
"The product’s dashboard is very intuitive."
"I am impressed with the product's output scaling."
"The features are typical Kubernetes, but Google One offers a better GUI-based deployment. It's more sophisticated and integrates well with other services, providing a better customer experience."
"GKE's plugin management and configuration sync are excellent features. The amount of data it provides is good, and I've been able to integrate it with the things I need."
"We used automation for the initial setup. It was okay. So it wasn't too complex."
 

Cons

"Support could be better with response time and knowledge of staff."
"I also believe there are limitations in terms of upgrading. The software has the concept of dedicated servers that you can manage. However, an issue arises when you can't match one operating system with another that you've already purchased. You can't simply merge them; instead, you have to buy a completely new one. This limitation has caused some challenges for us."
"Visualization is an important factor for me, and I don't think that the visuals within ECS are good enough because it doesn't show you all the details you might need to see at a glance."
"The solution must improve backup and compatibility around OS like Windows and Mac."
"For Amazon EC2 Container Service, providing the ability for users to select specific processor, memory, disk, and interface types might be an ideal feature. But, the practicality of offering all possible physical combinations is nearly impossible due to the underlying physical machines. AWS and Azure organize options into groups based on essential components like powerful processors or critical interfaces, considering physical restrictions. While expanding these choices is conceivable, it may not be feasible from a financial and practical perspective. Customers generally comprehend this limitation, as even in their own data centers, exact physical machine requirements are often a result of a combination of factors such as price, availability, and new machine generations."
"The product should improve its price."
"They could provide easier options for third-party integrations similar to internal AWS services."
"The existing domain-joined capability the solution provides during the initial boot-up of the compute should be streamlined and made a little robust."
"The console for this solution could be improved because it is very limited."
"Their documentation is a little here and there. Sometimes, the information is not clear or updated. Their documentation should be a little bit better."
"The solution does not have a visual interface."
"The tool's configuration features need improvement."
"While the GKE cluster is secure, application-level security is an essential aspect that needs to be addressed. The security provided by GKE includes the security of communication between nodes within the cluster and the basic features of Kubernetes security. However, these features may not be sufficient for the security needs of an enterprise. Additional security measures must be added to ensure adequate protection. It has become a common practice to deploy security tools within a Kubernetes cluster. It would be ideal if these tools were included as part of the package, as this is a standard requirement in the industry. Thus, application-level security should be integrated into GKE for improved security measures."
"The primary area for improvement would be the complexity involved when working with Google Kubernetes Engine, especially when using Terraform."
"Our critique is that we have to do too much work to get the cluster production-ready."
"The user interface is a bit confusing sometimes. You need to navigate between the various consoles we have. It's hard to figure out where things are. It's frustrating. The documentation could be a bit better."
 

Pricing and Cost Advice

"Licensing can be purchased directly from AWS or used with existing licenses, depending on the company's preference. The licensing structure is complex and depends on factors such as machine size, number of processors, and Container size. Companies have dedicated staff members managing license considerations full-time to find the most cost-effective options. Also, I have seen some companies opt for a combination of AWS and Azure, using more of Azure for Microsoft licenses due to potentially lower costs compared to AWS."
"The solution is expensive, but not too much."
"The solution is pricey."
"Amazon EC2 Container Service is worth the money."
"Our client is paying between $400 and $500 USD per month for this service."
"The solution's cost could be reduced."
"Amazon Elastic Container Service is an expensive solution."
"Amazon Elastic Container Service's price is good."
"The pricing for GKE is dependent on the type of machine or virtual machine (VM) that is selected for the nodes in the cluster. There is a degree of flexibility in choosing the specifications of the machine, such as the number of CPUs, GPUs, and so on. Google provides a variety of options, allowing the user to create the desired cluster composition. However, the cost can be quite steep when it comes to regional clusters, which are necessary for high availability and failover. This redundancy is crucial for businesses and is required to handle an increase in requests in case of any issues in one region, such as jumping to a different region in case of a failure in the Toronto region. While it may be tempting to choose the cheapest type of machines, this may result in a limited capacity and user numbers, requiring over-provisioning to handle additional requests, such as those for a web application."
"The product is a little bit expensive."
"It is competitive, and it is not expensive. It is almost competitive with AWS and the rest of the cloud solutions. We are spending around 3K USD per month. There are four projects that are currently running, and each one is incurring a cost of around 3K USD."
"Currently, it costs around $1000 per month which sorted our deployment. So once we get more clients, having a huge suffix, costs can go up."
"This is an open source solution, so there is no pricing or licensing."
"We are planning to use external support, and hire a commercial partner for it."
"Its pricing is good. They bill us only per user. That's nice."
"The price for Google Kubernetes Engine could be lower - I'd rate its pricing at three out of five."
report
Use our free recommendation engine to learn which Container Management solutions are best for your needs.
824,053 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
32%
Computer Software Company
14%
Government
8%
Manufacturing Company
6%
Financial Services Firm
22%
Computer Software Company
13%
Manufacturing Company
8%
Retailer
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

What do you like most about Amazon Elastic Container Service?
Implementing the product has helped me monitor the parameters. I utilize tools like CloudWatch and AWS systems to track these parameters. If any issues arise, I alert our developer team to address ...
What needs improvement with Amazon Elastic Container Service?
The solution must improve backup and compatibility around OS like Windows and Mac.
What is your experience regarding pricing and costs for Google Kubernetes Engine?
For pricing, Google is considered cheaper compared to AWS, making it suitable for smaller to medium companies concerning cost. I would rate the cost around four out of ten, where ten is the higher ...
What needs improvement with Google Kubernetes Engine?
The management UI could be improved. When looking at the web interface, it feels kind of slow due to the many features involved. The interface could definitely be faster.
 

Also Known As

Amazon ECS, Amazon EC2 Container Service
GKE
 

Overview

 

Sample Customers

Ubisoft, GoPro, TIBCO, Remind
Philips Lighting, Alpha Vertex, GroupBy, BQ
Find out what your peers are saying about Amazon Elastic Container Service vs. Google Kubernetes Engine and other solutions. Updated: December 2024.
824,053 professionals have used our research since 2012.