Amazon Elastic Container Service Reviews

I use servers to make web services, mainly to complement the WordPress solution.

EC2 and anything else on the AWS container is reliable. I can trust it.

It's quick and easy to have the solution working.

The solution needs to be more usable. It has a node interface, and it would be better if it could be renewed. It's the same thing with WordPress, Google, and any other company doing the same thing. It would be very good if Amazon went to the front by winning that war of usability.

I've used Amazon EC2 Container Service for 20 years.

The solution is much more stable than IBM. I rate the solution's stability a ten out of ten.

Amazon Container Service is all about scalability. You should use AWS instead of something else.

It was straightforward to deploy the solution.

The ROI depends on the business. Big companies see an ROI with it, and small companies don't.

The solution is pricey. There are three things a solution can be or have: it can be quick, cheap, or have quality. We can't have three at the same time. If you have money and time, you have quality, which is the case with Amazon. Amazon is pricey, but we can do things quickly, and there's quality.

However, you can have the free tier with Amazon, where it will work for small companies, but only for a short time. If you only want a small VPS, use Google, which will be free forever.

If choosing the solution, contact an expert. I rate Amazon EC2 Container Service a ten out of ten.

Amazon Elastic Container Service is where we deploy our microservices. All of our banking services are hosted on Amazon Elastic Container Service.

The time to market that we need to deliver the solutions for our customers was drastically reduced because of Amazon Elastic Container Service.

Scalability and availability are the most valuable features of Amazon Elastic Container Service. It removes a lot of work from our infrastructure team to ensure that the structure is available when we have a pick, for example, of the utilization from our clients. In case of problems, we also have the recycling of the services that are conducted and managed by the AWS environment.

The solution's pricing could be improved. With Amazon Elastic Container Service, you spend a lot of money in the long term.

I have been using Amazon Elastic Container Service for three years.

I rate Amazon Elastic Container Service ten out of ten for stability.

I rate Amazon Elastic Container Service ten out of ten for scalability.

The solution's initial setup is very easy.

Amazon Elastic Container Service saves our organization time and money in the short term.

Amazon Elastic Container Service is deployed on-cloud in our organization.

Amazon Elastic Container Service is a very good solution if you are in a startup business and need to deploy things faster and comply with the regulators. I would recommend Amazon Elastic Container Service to other users.

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

We have hosted 50 websites using Amazon Elastic Container Service. The websites are used by our end customers and internal employees as well.

ECS is a useful platform.

The orchestration of the workloads running in ECS needs improvement. Additionally, they should automate the auto-scaling features for containers.

We have been using Amazon Elastic Container Service since 2019.

I rate the product’s stability a seven out of ten.

I rate the product’s scalability an eight out of ten.

In the beginning, when it was a new service, there was not a lot of documentation and online support available. So, we regularly contacted the product’s technical support and development team.

ECS’s initial setup process is complex as we have to follow many manual steps. I rate the process a seven out of ten. It takes a few minutes to a few hours to complete.

The platform is inexpensive.

I rate Amazon Elastic Container Service a seven out of ten. I advise others to use AWS EKS than ECS.

I am using AWS ECS combined with AWS Fargate in order to orchestrate our containers. To explain what that means, I will give an example. Suppose you are running a microservices architecture in which you have multiple containers within multiple services. ECS is the tool that helps you orchestrate all of that, by providing you with the ability to scale up / down your containers and monitor them. Also, with ECS, you can identify any problems or bugs with your containers.

We had a microservices architecture operating in this manner, and we needed some kind of solution to help us manage and orchestrate all our containers. Here we had a choice between something like Kubernetes or ECS, and we chose to use ECS because we didn't have a very large or complex architecture with many containers. Instead, we only have a few containers, yet they still needed orchestration in many ways, which ECS was able to provide.

For me, the best feature of ECS is Fargate because I don't have to manage anything. Instead, everything is managed by AWS and all I have to do, in essence, is configure my containers and deploy them.

That said, whether this feature is appropriate for everyone depends on the sensitivity of your data. I was able to make good use of Fargate since I do not have especially sensitive data running on the containers.

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.

Another aspect that could be improved is that our monitoring within ECS depends on other services like CloudWatch, for example, and with this arrangement you have to constantly switch between screens when navigating around. Because of this, it's difficult to take a look at your monitoring data, or even just to set up, and it can be very frustrating.

Perhaps it would be possible to improve this situation by having the ability to include everything on one status page. For example, if there is a service or container that is exhibiting a bug or is in some type of loopback mode, when I click on it, I could be shown the screen with all the errors displayed right there.

I didn't see any issues, especially in regards to ECS with Fargate. There are two ways you can run ECS; one way is with EC2 (Elastic Cloud Compute) and the other is Fargate. When you run ECS with EC2, it means that you manage your own servers and your own containers. However, with Fargate, AWS manages all the servers and containers behind the account. For some people, it might be the case that when you're using ECS with EC2, your issues are more related to your own management methods rather than anything to do with AWS itself.

I contacted support one time when I needed to find some information related to launching containers. I wanted to find out how to access certain container data, such as container ID and so on. Once I reached their support, they managed to help me find this information.

The quality of support you receive depends on your subscription because when you have an enterprise subscription, their response is very quick. However, when you are not part of an enterprise, they might not help you right away. Regardless, when we're talking about how well they help, they are indeed able to offer technical solutions and they are straightforward about it. 

Positive

The setup is not that hard. When I began using it, I found that it's not very intuitive, but at the same time it's not difficult.

I would suggest, however, that AWS offer more courses or tutorials on how to use it. I know that they teach how to use ECS through their certifications, but even a few two to three minute tutorials on their YouTube channel would help people a lot. Personally, I had to look through many resources to find good knowledge on it, but when you eventually find the solution, it gets more intuitive. 

When it comes to how long it takes to deploy your containers within ECS or their orchestration tools, this really depends on your architecture, and how you have set things up. If you have set everything up properly, it takes only a matter of minutes to have your application up and running.

I don't know the exact amount we were charged for our use of ECS, but I do know that it can be costly, especially when there is a bug or an error caused by default configurations. When you configure your containers to be launched with special configurations, such as with CloudWatch events, sometimes they fail to launch and they enter into a locked state. Each time this happens, all the configuration behind the container creates itself again, making it such that the costs can quickly go up if you have any bugs in your configuration.

Besides that issue, I would say it's not that expensive, but can still be costly in a way.

We considered using Kubernetes instead of ECS, but we went with ECS because our architecture and amount of containers did not warrant the complexity of using Kubernetes.

My advice, first of all, is to do your research, and do it in detail. Verify that ECS really satisfies all your requirements, especially when you are also using Fargate because with Fargate you are not managing the servers yourself. A good tip is to watch some tutorials that already exist online, so you can start your process with that.

To be honest, using a tool like Kubernetes to orchestrate your containers can be a very difficult process, especially when setting up Kubernetes clusters, and there are a lot of small things that you need to do and understand. However, compared to Kubernetes, ECS is very intuitive and extremely quick to learn. This is why I would definitely recommend ECS over Kubernetes if you don't have a highly complex microservices architecture and you simply need to set up your containers quickly.

I would recommend ECS mainly for its stability and its ease-of-use in helping to manage containers, despite that there are some improvements that they could make, such as better visualization and other improvements to the technology itself in order to orchestrate even more complex architecture.

Overall, I would rate AWS ECS a six out of ten.

My company uses Amazon EC2 Container Service as a backup.

The most valuable feature of the solution stems from the fact that it is very easy to set up. The solution is not that hard to get around for beginners. The solution's setup phase is good, even though you may not have so much knowledge of the platform.

The solution's stability is an area of concern where improvements are required.

I have been using Amazon EC2 Container Service for three years. I don't remember the version of the solution.

It is a stable solution. Stability-wise, I rate the solution a seven or eight out of ten.

End users are unpredictable, so I think there will be issues in terms of limitations and network issues.

The scalability of the product is fine. I don't use the product's scalability since it is not that high.

I don't intentionally plan to increase the use of Amazon EC2 Container Service.

I have experience with OCloud.

The product's initial setup was very straightforward and not complex.

The solution can be deployed in less than an hour.

The deployment process of Amazon EC2 Container Service depends on why its users want to deploy the product in their environments. Make sure you have your infrastructure and IP setup in place. Once you have all the IPs and your infrastructure setup in place, you will be able to deploy Amazon EC2 Container Service within a few days. EC2 platform provides a very simple interface where you should use the IPs in your router in your virtual machine setup, and then the backup part of the solution should be good to use.

I myself manage the deployment and maintenance processes of Amazon EC2 Container Service.

I take care of the solution's deployment phase by myself

There is no need to pay anything towards the licensing costs of Amazon EC2 Container Service.

I feel that others should try Amazon EC2 Container Service, but it all depends on what others want to deploy from the platform offered by Amazon. Cost-wise, Amazon EC2 Container Service is an okay product. It is better to look at comparisons before proceeding to move to a vendor for a product.

I rate the overall tool a nine out of ten.

The product enables users to easily run and manage containers on scalable infrastructure.

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.

Amazon ECS comprises components like task definition, which acts as a blueprint for applications, specifying details like the Docker image, CPU, and memory resources. Containers are lightweight, portable executable packages containing everything needed to run an application or service. It defines how containers should be managed, ensuring the desired number of tasks are running and automatically scaling based on demand.

The best thing about Amazon ECS is that it's a fully managed service. It offers scalability, high availability, cost-effective flexibility, and integration with other AWS services. Additionally, it provides some security features.

We noticed a problem where our container doesn't always run, and the traffic in our secured license exceeds 100%, leading to increased container costs. We are working to understand and reduce this traffic to control costs.

I have been working with the product for two years. 

Amazon ECS is used by seven users in my company. 

My company uses GKE and Amazon ECS. We chose the product as per client requirements. 

The tool's deployment is easy. 

Amazon ECS is expensive. 

In our company, the process for creating Amazon ECS services involves having a repository in it. If there's a need to edit variables or resources, we pull the repository to our local terminal, make the necessary edits, and push the changes back to the repository. Subsequently, we deploy using Jenkins. You can easily define the number of containers running in your cluster and manage them. Autoscaling and load balancing are handled automatically by AWS. 

We create clusters, which are logical groups of container systems where tasks can be placed. We can create clusters using the AWS Management Console, AWS CLI, or SDKs. During the setup, we decide whether to use an ECS-optimized Amazon Machine Image for launching instances or create a launch configuration for an autoscaling group.

I rate the product a seven out of ten. 

We use Amazon Elastic Container Service to deploy containers.

The solution is easy to scale and implement and provides performance monitoring and management tools.

The more containers there are, the more expensive the solution becomes.

With Amazon Elastic Container Service, we lack full control over the infrastructure. Since it is a managed service for container orchestration, it may limit our control over certain infrastructure functions. This limitation can be a concern if you require deep control over your container or have specific infrastructure requirements.

I have been using Amazon Elastic Container Service for seven years.

Amazon Elastic Container Service is a stable solution.

Amazon Elastic Container Service is a scalable solution.

The technical support team is not knowledgeable enough to provide us with solutions everytime. The support team joins the call, but they provide solutions only six to seven out of ten times we contact them. They say they are unsure how to do it the rest of the time.

The solution’s initial setup is easy.

Since Amazon Elastic Container Service is a cloud-based solution, we do not need to handle the infrastructure, and it provides auto-scalable functionality.

Amazon Elastic Container Service is an expensive solution.

I recommend that users choose Amazon Elastic Kubernetes Service (EKS) instead of Amazon Elastic Container Service (ECS).

Overall, I rate Amazon Elastic Container Service an eight out of ten.

I use Amazon EC2 Container Service to install system instances that need a container. I rely on it when I use microservices. 

I like the tool's availability and automated scalability. I need to define the port numbers, and when I have a large load of requests, I can get automated scalability. 

Amazon EC2 Container Service is easy to create and manage. I can use it easily on my CI/CD pipeline and deploy solutions. 

The product should improve its price. 

I have been using the product for three years. 

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

I rate the product's scalability a ten out of ten. 

The tool's deployment is easy. 

We have seen ROI with the tool's use. It saves time for my support and development teams. 

Amazon EC2 Container Service is a trustworthy infrastructure from Amazon. It speeds up delivery from the infrastructure and development teams. I rate it a ten out of ten.