Amazon Elastic Container Service Reviews

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 easy to use. When you have nodes like Python, it's easy to plug and play.

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.

I have been using the solution for two years.

It is a stable solution. I rate it eight out of ten.

It is not a very scalable solution. I rate it five out of ten.

The technical support team is good but if you are looking for any documentation then it is not very helpful.

The initial setup is easy and it is deployed on the cloud. 

I have seen ROI with the product's use. 

The pricing is good.

I rate the solution an eight out of ten.

We are using the solution to run our apps and services. We make use of Docker to run our API services. So, we use ECS as the container service to run all of our Docker images.

Its most valuable feature is the ability to work with Docker images. We just have to give it a Docker image and run some parameters. It keeps the process going for us. It's been great. We don't have to worry about where and how it gets deployed. We just know that it's going to run and we can contact it at a particular address. It integrates perfectly with AWS's service mapping feature and allows one ECS container to contact any other ECS container using a service name. It's almost like an internal DNS thing. If we want to expose it to the internet, we just put a load balancer. It passes requests from the load balancer to the relative ECS services. It also helps for scaling–we just have to add one in a new container. That's pretty cool.

I see they have changed the console a bit to make it easier to use. Probably, they should include automated graphing, and monitoring solutions. Currently, I have to set up all of those by myself.

We have been using the solution since October 2021.

The whole engineering team of six people at our organization uses the solution.

There were some issues with the setup. It wasn't the easiest to get going as opposed to something like SFTP Gateway. It's a learning curve. You need to learn what a cluster is, what a task is, and what a service is. There are no industry standard concepts that could be applied to different technologies. You need to learn ECS-specific concepts. It's similar to Docker Swarm or other resource management technologies like Kubernetes. They have similar concepts, so if you come from that world, you might understand it a bit easier. There is some AWS-specific stuff that you just need to learn. Once you get over that learning curve, then it works pretty nicely. I would rate the setup procedure as a four out of ten.

The price of ECS is not bad. It is based on usage. It works on a per-hour pricing model.

I would definitely recommend the solution. Once you get the procedure right and set a pattern, it just works. I have used different use cases, languages, and frameworks. Everything works nicely once you get the pattern right. The solution scales by itself, and you can set the threshold of how to scale it. Once it goes to 80% of CPU for five minutes, it scales up automatically, and then if the CPU usage goes down, it scales down. You don't have to pay for that upscale cost over time. You need not have to worry about servers or machines. You just have to worry about your containers. It's great.

Also, deploying to ECS is pretty easy via whatever CI you use. It's generally quite easy. It also integrates with Amazon's ECR service, which holds the Docker images used for the services and containers. It works nicely with the ECS.

If you have credentials or secrets that you might want to use as environment variables in your applications, you could inject them at run time into your containers. ECS caters to this with a pretty easy task definition like syntax. You just have to specify the secret name in the task definition and ECS will know when it starts, and when it needs to pull this secret into the container at run time. Thus it's not vulnerable to an attack where someone can snoop on your task definition. It's not in plain text and it only works if you give your container explicit permission to pull the secret.

I would rate the solution as an eight out of ten.

We deploy applications inside the EC2.

The solution has good performance. 

I would like fewer updates.

I have been using this solution for six months. We use the latest version.

I would rate the stability a ten out of ten. 

I would rate the scalability a ten out of ten.

The initial setup is straightforward. 

I deployed the solution myself. One might require engineers and developers for the deployment process. 

Overall, I would rate the solution a ten out of ten. All the current features are perfect.

I would definitely recommend using the solution.

We host our production application on EC2. We host the application and take regular backups to create mirrors for our customers. We also use the solution’s firewall to save us against any threat.

The most valuable feature of the tool is its ease of usage. We spin off new servers and host our applications on those servers. The best thing I like about the product is hosting. It is super easy. Features for creating a server and hosting it is all builtin within the solution. I don't have to build a backup service. It is already available. I don't have to build a database as well. It is already built. I can just use any existing DB and then connect it directly to the DB instances and use it. Everything is ready to use.

We’ve been hosting our production application on the product. The most important criterion for us is downtime. In seven years, we have not faced a single second of downtime. It is the greatest thing. We have had zero downtime in the last seven years. Nothing can be better than that.

Billing is extremely complex. The whole concept of billing is so complicated that we never understand it. There is an upfront cost, and there is a network cost. It is impossible for me to calculate the cost, understand it, and inform the client about it.

We are never sure of our end cost. Sometimes the cost blows up and ends up being five times more than what we calculated. There is no way to understand the cost. I want the solution to have a better billing system and dashboard to understand the billing.

The solution could be more intuitive. If I'm using a service and my backup has gone down, there should be a notification or suggestion to help me understand what I can do. It should explain how I could have avoided the issue. EC2 is huge, and we'll never know all its services. The tool should have a way of suggesting to me what I can do better.

It can be through notifications, tutorials or through their customer service team. The product could provide CI/CD services in the future.

I have been using the product for seven years.

The tool’s stability is perfect.

The tool is scalable. It can be scaled according to our needs. I rate the scalability a ten out of ten. In our company, more than 100 people use the solution.

The technical support team is pretty good. The response time is very quick.

We have used Azure, and it provides similar services. However, we do not have a lot of experience in Azure.

The initial setup is super simple.

I rate the pricing a five out of ten.

The billing is really painful. The product must provide some intuitive notification to inform us if we are not doing something the best way. Overall, I rate the solution an eight out of ten.

Our primary use case for this tool is mainly for backup from operational data.

It has helped the company provide a stable and reliable environment.

The most valuable feature, after using Amazon EC2 Container Service for two years, is to set the availability and also for network throughput.

There is room for improvement in the pricing of Amazon EC2 Container Service. Also, mainly on the network issues to access the container.

We have been using Amazon EC2 Container Service in a specific project here for two years. However, we don't use the latest version. 

Amazon EC2 Container Service is stable. I would rate the stability ten out of ten.

The solution has some limitations. Mainly the network issues with accessing the container. Hence, I would rate the scalability of Amazon EC2 Container Service a seven out of ten.

The customer service and support team is good. We can find all the information on the online portal.

Amazon EC2 Container Service is very good and easy to use. It also integrates with Okta Solutions.

It was really important to our project to have a stable environment on the cloud that would be reliable. It was important. It is not easy to give a number to this, but for sure, it has value.

We emphasize that utilizing any cloud solution with payments in dollars is a huge amount for our liaison here.

For someone who wants to use Amazon EC2 Container Service, I would say it is a very good solution. Especially for people who have to plan a lot in advance to define exactly what they need and to plan the capacity and also the way they will use the institute and also order possible solutions connected to them so they can plan for their costs.

Overall, I would rate Amazon EC2 Container Service solution as an eight out of ten

We use the solution to host applications and run applications.

The solution is quite scalable and allows you to launch multiple EC2s within minutes.

I have been using Amazon EC2 Container Service for more than three years.

I rate the solution a nine out of ten for stability.

Amazon EC2 Container Service is a highly scalable solution. A lot of users are using the solution in our organization.

I rate the solution ten out of ten for scalability.

The solution’s initial setup is pretty easy.

Amazon EC2 Container Service is worth the money.

Amazon EC2 Container Service is a cloud-based solution. I would recommend the solution to other users because it is scalable and stable. We can turn down the solution and start it again in a minute.

Overall, I rate Amazon EC2 Container Service ten out of ten.

We use Amazon EC2 Container Service for Kubernetes and hosting sites. 

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. 

The product can become expensive if you don't choose what you want. 

I have been using the product for two years. 

I rate Amazon EC2 Container Service's stability a nine out of ten. 

I rate the tool's scalability a nine out of ten. 

Amazon EC2 Container Service's deployment is easy and takes three minutes to complete. 

I rate Amazon EC2 Container Service an eight out of ten. 

The solution is to compute instances. Basically, it's a debit. It's a host. For example, if you need a computer that you want to install your enterprise application, instead of buying a server on-premise, you can spin up an instance online.

I like the per-second billing. Every second I use is billed. Any other time I am not using it, it's not billed, so it's better. It’s cheaper. It's good.

It’s easy to set up.

The solution is stable.

The solution can still be expensive, even with per-second billing.

We’ve used the solution for the last year.

The solution is extremely stable and reliable. There are no bugs or glitches. it doesn’t crash or freeze.

It is very scalable.

We started with AWS this year. We have one client so far.

Technical support is perfect.

The solution is very straightforward. The initial setup is very cheap also.

It's very easy to replace. You don't need a lot of teams to do it. One person can do everything.

We are integrators and can handle the initial setup.

You pay for only the time you have used the on-demand service. For example, if you are using software that does a lot of computation or analyzing your data for your company, you only pay for that time spent analyzing that data. The rest of the time, you don't pay for it.

Although I like the per second billing, the cost of it, even if you are being billed per second, it is still higher than competitor products.

We are integrators. We use a lot of Amazon products.

I would rate the solution eight out of ten.

I would recommend a competitor's product. I would recommend, for example, Oracle Compute Instances or Oracle Cloud. I wouldn't recommend AWS EC2 due to the cost. It can get out of control. For example, once I left my EC2 on for a few days with some services running, and in three days I lost a thousand dollars. It's quite costly if you are not very careful.