Amazon Elastic Container Service Reviews

We use Amazon Elastic Container Service as a hosting technology. My organization operates in the legal sector, and we use ECS to handle legal workloads.

Amazon Elastic Container Service makes horizontal scaling easy and is especially effective when working under the ECS service. Most modern workloads can be deployed on Fargate containers, abstracting away the hardware. We do not need to think about physical servers anymore, which is a significant advantage. This approach reduces costs since it eliminates the need to maintain idle service processing units. Additionally, it provides excellent horizontal scalability.

We use Amazon EC2 Container Service to take complete workloads to the cloud for various applications.

Amazon EC2 Container Service has reduced our infrastructure cost. We migrate some workloads from our on-premises data center to the cloud, where it runs as per the requirement, and we don't have to pay upfront. This helps reduce both the CapEx and OpEx. Some of those managed services help us to reduce the OpEx. On-demand computing efficiently manages the CapEx.

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.

The Amazon EC2 Container Service involves lifting and shifting the on-site environment into AWS. It's a simple copying of your applications since you don't create new virtual machines.

Amazon EC2 Container Service offers great flexibility with a wide range of options, allowing you to choose powerful, smaller, bigger, faster, secure, or dedicated machines based on your needs. We have no concerns about EC2 containers, and the only potential downside is if you move your data center to AWS without leveraging advanced features like serverless or automatic scaling, it might be more expensive. The key is to optimize and make use of all the cloud features for cost efficiency and improved performance.      

I use the solution for Jenkins web server, CloudFormation, and TerraForm. I use it for Linux and Mac servers. The list is endless.

The most valuable feature is the volume size they offer. Where I'm from, having a lot of storage is a problem, and the cloud provides you that much more. You could set a volume of maybe 20 gigabytes. If you use the right AMI ID, you get it at no extra cost. You just have to be very diligent when you're setting it up.

Another thing I love is the variety of AMI IDs that are out there, from Ubuntu to Amazon Linux to Mac and so on. There are so many AMI IDs that can service whatever problem the client has.

My company deals with Amazon EC2 Container Service as a performance container management service and fault management system for telecommunication networks.

The most valuable feature of the solution is its scalability. In terms of storage resources, the solutions need to be quick to provide users with options for growth. Based on prediction, the product sometimes allows you to grow or scale up quickly.

We had a new product, and we used Amazon Elastic Container Service to do a proof of concept for it.

We used Amazon Elastic Container Service for deploying a web application.

Amazon Elastic Container Service is more stable. We didn't do a stress test on the solution, but I could say it cost much less as compared to EC2. We would have needed three or four EC2 instances for the same application, but we could do it on a single incident EC2 container.

I am a cloud consultant working with Devoteam, a consulting company. I specialize in AWS and work with a large range of customers using AWS as their cloud platform. 

Depending on the clients I am working with, I use several services, including compute services like EC2 instances, VPC for networking, serverless services like Lambda functions, EventBridge for event-driven architecture, and Kubernetes infrastructure using Amazon Elastic Kubernetes Service (EKS).

Moving to Amazon ECS, particularly in Fargate mode, allowed our customer to benefit from not having to manage the underlying infrastructure. This accelerated the deployment of the containers on Amazon’s platform and allowed for easier integration with CI/CD pipelines, thereby improving operational efficiency.