Amazon Elastic Container Service Reviews

I use the solution in my company since the front end of my application is deployed on Amazon Elastic Container Service. The back end of the application was deployed on Amazon EC2 for microservices. The front-end and microservices, like shipments, inventories, and a few other areas, are deployed on Amazon Elastic Container Service.

First and foremost, my company uses AWS Fargate, which is easy to handle considering that it is taken care of by AWS, especially in areas like troubleshooting. Triggering a deployment manually is very simple with Amazon Elastic Container Service since, in our company, we have to go to the particular service, update the service manually, and check the box called force a new deployment, which would trigger a deployment on all the services. Even if the deployment has to be done manually, it is not a tedious task as it is easy. The product has a concept called task definition, which makes it easy to handle environment variables.

Though not an issue in the product, one of the areas of concern that I have noticed is related to how the tool works. After the load balancer gets attached to Amazon Elastic Container Service clusters, I can't modify, remove, or replace it later. The tool would have been better if there was an option to replace a load balancer. If anyone attaches a wrong load balancer during the creation phase, it has to be brought down and created once again from scratch.

I have been using Amazon Elastic Container Service for two and a half to three years. My company is a customer of Amazon.

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

In terms of scalability, the product has autoscaling features along with Amazon EKS, which helps scale up the resources in an organization. Scalability-wise, I rate the solution a ten out of ten.

It is difficult for me to keep track of the number of users of the solution in my company because we have multiple groups in our organization who use it for integration purposes.

Earlier, the support team had some issues. Once or twice, I found a delay in the response time from the technical support's end due to a lack of resources or some other issues. Lately, I haven't experienced any issues with the product's support team since they have been very responsive.

I rate the technical support a ten out of ten.

The product's initial setup phase requires some level of understanding. I can vouch for the fact that AWS provides good and detailed documentation. Users don't have to go anywhere to understand any concept related to the product, and all they need to do is follow AWS documentation line-by-line to become professional at whatever services they want to use.

Although AWS has successfully captured over 60 percent of the market in the cloud part, the tool is competitively way cheaper for the resources it provides compared to the other solutions.

The tool's scheduler enhances your application's scalability and reliability since, with AWS Fargate, during the scale-up process, if my company runs 50 or 70 tasks or services and in case of failures or any problems during the runtime, AWS responsibly takes care of the problematic area. All I need to do is to push the code while managing the application side. At an infrastructure level, things are managed by Amazon with AWS Fargate. I am very confident about the performance and reliability that the product offers since the infrastructure part is taken care of by AWS.

The security measures in the product that are the most effective stems from the fact that it provides separate policies to be attached to your clusters at a task execution role level, and if it is not made manually, then you won't be able to access ECS tasks through a command line, making it a highly secure area.

Amazon Elastic Container Service, with other AWS services, streamlines our company's workload since during the creation of a task definition, you need to mention the task execution role, which is nothing but an IAM role, which will provide the privileges and the permissions as to what is required at your end.

I recommend the product to those who plan to use it.

To understand the initial stages can be easily understood by the user, it is good to go through its documentation and learn about the solution before buying the product. The struggle would be with the learning part and not the implementation part.

I rate the overall product a nine out of ten.

The tool helps us with maneuverability. Its most valuable feature is autoscaling. 

Amazon EC2 Container Service needs to improve the menu design. It needs to improve deployment with better documentation. 

I have been using the product for five 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 complex. 

Amazon EC2 Container Service has helped us save time. 

The tool's cost is good. 

I rate Amazon EC2 Container Service a nine 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.

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.

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.

We use the solution as a docker service to run the containers.

We use ECS whenever there are multiple programs to run. We can containerize the programs without worrying about the versions of the applications.

The solution's most valuable feature is its ability to run the containers directly on the cloud.

The solution could provide more reliability. There could be an option for the customers to manage the services. Also, there need to be more custom features that would allow customers to access the ECS containers and deploy them.

We have been using the solution for two years.

I rate the solution's stability a six out of ten.

The solution is scalable. I rate its scalability an eight out of ten.

The solution's technical support is good.

Positive

The solution's initial setup process is straightforward.

Even if the solution is costly, you will definitely see ROI if you have many applications.

The solution's cost could be reduced.

The solution has multiple versions. You can choose a version compatible with your system. I rate it a seven 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.