No more typing reviews! Try our Samantha, our new voice AI agent.

Amazon Elastic Container Service vs Google Cloud Run comparison

Why PeerSpot?
 

Comparison Buyer's Guide

Executive Summary

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 Elastic Container Se...
Ranking in Container Management
12th
Ranking in Containers as a Service (CaaS)
1st
Average Rating
8.4
Reviews Sentiment
6.0
Number of Reviews
53
Ranking in other categories
No ranking in other categories
Google Cloud Run
Ranking in Container Management
13th
Ranking in Containers as a Service (CaaS)
4th
Average Rating
8.6
Reviews Sentiment
2.2
Number of Reviews
5
Ranking in other categories
No ranking in other categories
 

Featured Reviews

Bharat Prajapati - PeerSpot reviewer
Lead DevSecOps Engineer & Founder of Spiderthings Solutions at a computer software company with 51-200 employees
Containerization has unified diverse microservices and delivers faster, cost‑efficient deployments
Amazon Elastic Container Service offers many features including VPC Lattice, service discovery, service connect option for internal communications, and private hosted zones via Cloud Map, with multiple features within Amazon Elastic Container Service Fargate container itself, including EC2, Fargate, and Spot Instance.Out of those features, the one that has made the biggest difference for my team and workflow is the ease of scaling, logging, monitoring, and easy deployments, as well as being self-managed by AWS, facilitating multiple things such as internal communication and private networking. I would add that there is a namespace service where I am using service discovery, with a few more networking-related features, including VPC Resolver, which impacts our VPC and Amazon Elastic Container Service environment to control incoming and outgoing traffic. Amazon Elastic Container Service has impacted my organization positively by being very helpful, cost-optimized, and easy to deploy; from a developer perspective, user perspective, and DevOps team perspective, it accommodates everyone, whether they are a fresher, intermediate, or advanced user, thanks to its easy UI features. I have seen specific outcomes including time savings and the removal of code dependency on DevOps when using Amazon Elastic Container Service, contributing to saving time, cost, and many other benefits, with these being the two major points. Regarding Amazon Elastic Container Service's AI capabilities, I think its governance and security are solid due to features including ARM-specific secret management, IAM-specific containerization, task role, task execution role, and read-only EBS related elements within container mounting volumes, showcasing multiple security features provided within the UI. When it comes to the accuracy and reliability of outputs from Amazon Elastic Container Service's AI capabilities, I find it far better, especially since AWS launched their AI-related help bot, generating accurate answers that help resolve and debug issues.
Vyas Shubham - PeerSpot reviewer
Senior Quality Analyst at a consultancy with 51-200 employees
Serverless containers have transformed how we deploy microservices and event-driven workloads
There are a few areas that could be improved. We have experienced cold start latency because when scaling from zero, the first request is slow. It also impacts user experience for real-time applications. The improvement we require is faster cold starts or smarter pre-warming options. There are also limitations with long-running workloads. It is not ideal for very long or always-running processes, and request timeouts are somewhat restrictive. The improvement we want is better support for persistent workloads without workarounds. We have also identified improvements needed in debugging and observability complexity because logs and monitoring are available, but they feel scattered at times, and debugging distributed microservices is harder. The improvement we require is more unified and developer-friendly debugging tools.

Quotes from Members

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

Pros

"A really good feature of ECS is the integration with AWS services, especially the networking services like Elastic Load Balancer, Service Mesh, and Service Map, which simplifies the service discovery process."
"The solution is user-friendly."
"The most valuable feature of the solution is its scalability."
"Amazon EC2 Container Service is a flexible product from Amazon. You can put it in the Auto Scaling group for high availability. There are also a lot of choices for pricing."
"It has helped our organization greatly and especially on weekends because we have many transactions as our users are buying some kind of tools and paying online."
"The solution is quite scalable and allows you to launch multiple EC2s within minutes."
"Amazon Elastic Container Service serves the function it's supposed to serve."
"Amazon EC2 Container Service is a stable solution."
"Google Cloud Run has positively impacted our organization by saving us five thousand dollars per month based on scheduling our infrastructure from nine p.m. to nine a.m. for shutdown and starting, as well as stopping the MongoDB clusters."
"Google Cloud Run has positively impacted my organization in numerous ways, such as significant cost efficiency and reduced overhead since we only pay for the resources that we use."
"Google Cloud Run is a very good tool that I use for deploying applications; its ease of deployment, auto scaling features, and resource optimization are very nice features that help individuals deploy their apps and solutions into the cloud without any hiccups."
"Google Cloud Run and the Google Cloud environment positively impact my organization by providing almost 99.9% availability for applications, which instills confidence in the organization and users by reducing the dependency on the physical network and allowing access to applications and data."
"Google Cloud Run has impacted my organization positively through faster deployment and development, where developers can deploy applications quickly without worrying about infrastructure, push the app live with just containers, speed up time to market significantly, launch features faster and iterate more often, pay only when code runs without maintaining idle servers, reduce cloud costs dramatically for applications with low or unpredictable traffic, automatically scale based on traffic spikes to handle sudden loads without manual intervention so our business does not lose users during peak hours, and let developers focus on business logic instead of DevOps."
 

Cons

"Amazon EC2 Container Service needs to improve the menu design. It needs to improve deployment with better documentation."
"The documentation and usage for the users can be better because for new users it can be very hard to understand and use the solution. They can add small images and accessories."
"The orchestration of the workloads running in ECS needs improvement."
"The solution's user experience and management are really bad."
"It's a complex tool and should be simplified."
"The solution's pricing could be improved."
"The solution could provide more reliability."
"I think that it would help if the vendor provided more use cases and explanations as to how ECS can be utilized."
"There are a few areas that could be improved. We have experienced cold start latency because when scaling from zero, the first request is slow."
"If speaking about improvements for Google Cloud Run, I think they could reduce the cold starts and manage to configure a set number of minimum instances to keep the instances in a warm phase."
"There are a few areas where Google Cloud Run could improve."
"One area where Google Cloud Run could be better is the cold start; when a container scales, it starts from zero and takes a moment to boot up before it can serve the request."
"When it starts from idle to full run, it scales slowly, causing slowness in the service deployed; sometimes some of the APIs fail to respond."
 

Pricing and Cost Advice

"The tool's cost is good."
"On a scale of one to ten, where one is low price and ten is high price, I rate Amazon EC2 Container Service’s pricing a four or five out of ten."
"I rate the product's pricing an eight on a scale of one to ten, where one is cheap, and ten is expensive."
"The solution's cost could be reduced."
"Amazon Elastic Container Service has a decent price, which is neither cheap nor expensive."
"There is no need to pay anything towards the licensing costs of Amazon EC2 Container Service."
"The tool's licensing is monthly."
"I don't exactly deal with the pricing. We have a separate Infra team that deals with the pricing. They are more into the scalability part. Based on our requirements, the pricing will increase. The automation teams will test some of the benefits to see how can we can optimize the cost. They'll have a security manager connection and some alerts based upon the usage to see how to reduce the building cost based upon the installations."
Information not available
report
Use our free recommendation engine to learn which Containers as a Service (CaaS) solutions are best for your needs.
912,930 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Construction Company
15%
Financial Services Firm
15%
Computer Software Company
14%
Outsourcing Company
10%
Construction Company
38%
Outsourcing Company
12%
Wholesaler/Distributor
8%
Media Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business29
Midsize Enterprise7
Large Enterprise21
By reviewers
Company SizeCount
Small Business6
Large Enterprise3
 

Questions from the Community

What needs improvement with Amazon EC2 Container Service?
As for how Amazon Elastic Container Service can be improved, I currently find there is not much lacking since I can identify everything I need from Amazon Elastic Container Service container itself...
What is your primary use case for Amazon EC2 Container Service?
My main use case for Amazon Elastic Container Service is deploying microservices-based applications with different technologies.A quick specific example of a project or application I have deployed ...
What advice do you have for others considering Amazon EC2 Container Service?
I would rate Amazon Elastic Container Service as a nine out of ten.I give it a nine out of ten because, although it is not a direct alternative, it is indirectly an alternative to Kubernetes, which...
What needs improvement with Google Cloud Run?
If speaking about improvements for Google Cloud Run, I think they could reduce the cold starts and manage to configure a set number of minimum instances to keep the instances in a warm phase. Addit...
What is your primary use case for Google Cloud Run?
In my day-to-day work, I use Google Cloud Run for managing and running cluster and containerized applications on the Google Kubernetes Engine and Google Console. I have created multiple application...
What advice do you have for others considering Google Cloud Run?
If any organization has a lot of load on their Google Kubernetes Engine or on Google Cloud, they can easily switch to Google Cloud Run and should start using it because it will help them in many wa...
 

Also Known As

Amazon ECS, Amazon EC2 Container Service
Google Cloud Functions, Google Run, GCF
 

Overview

 

Sample Customers

Ubisoft, GoPro, TIBCO, Remind
Information Not Available
Find out what your peers are saying about Amazon Elastic Container Service vs. Google Cloud Run and other solutions. Updated: August 2026.
912,930 professionals have used our research since 2012.