I use the product for Azure folders, which act as a shared folder between the servers. I utilize it as a network file system for storing logs and managing software across all the servers in various availability zones. I have two instances: one for production and another for QA and testing purposes. I mount this file system across all virtual machines, creating a unified storage solution for logs, outputs, and other data generated by various jobs and tasks.
I use Amazon ECS to easily set up and manage resources for my applications, similar to Kubernetes but simpler. I work with ECS through the command line, and I installed a tool called QCTL to make it even more user-friendly. With ECS, I can write code to describe my applications, and then I can quickly deploy them. It is a very efficient way to handle containerized applications, whether it is a simple website or a complex system.
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.
Learn what your peers think about Amazon Elastic Container Service. Get advice and tips from experienced pros sharing their opinions. Updated: December 2024.
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.
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.
Practice Director, Global Infrastructure Services at Wipro Limited
Real User
2021-09-22T18:55:00Z
Sep 22, 2021
It lets us manage a cluster of containers in the cloud without really having to worry about managing the platform. We're currently serving around 50 customers.
I have set up Container Service environments for various clients using different cloud providers, including AWS. I have used the Amazon Elastic Container Service in this capacity. One of my clients from Israel is running web-based applications that are using PostgreSQL as the backend database connection. I think that it is a user-learning software, and they provide it to big companies to give KT sessions for new employees. They use the Totara application and for that, we have set up the infrastructure including VBA and database applications. We also manage their Amazon Route 53, and we have set up Jenkins for CICD purposes.
DevOps Engineer at a financial services firm with 10,001+ employees
Real User
2020-08-23T08:17:29Z
Aug 23, 2020
We are using Amazon Elastic Container Service for Docker-based configuration. Previously, we had to manually go into an instance and then issue all Docker agents and instances. Now, we are using Amazon ECS to automate all of our Docker containers. We are deploying our microservices architecture in the ECS container install. We are using ECS as a service.
Amazon Elastic Container Service (Amazon ECS) is a highly scalable, high-performance container orchestration service that supports Docker containers and allows you to easily run and scale containerized applications on AWS. Amazon ECS eliminates the need for you to install and operate your own container orchestration software, manage and scale a cluster of virtual machines, or schedule containers on those virtual machines.
I use the product for Azure folders, which act as a shared folder between the servers. I utilize it as a network file system for storing logs and managing software across all the servers in various availability zones. I have two instances: one for production and another for QA and testing purposes. I mount this file system across all virtual machines, creating a unified storage solution for logs, outputs, and other data generated by various jobs and tasks.
We use Amazon Elastic Container Service to deploy containers.
Amazon Elastic Container Service is where we deploy our microservices. All of our banking services are hosted on Amazon Elastic Container Service.
I use Amazon ECS to easily set up and manage resources for my applications, similar to Kubernetes but simpler. I work with ECS through the command line, and I installed a tool called QCTL to make it even more user-friendly. With ECS, I can write code to describe my applications, and then I can quickly deploy them. It is a very efficient way to handle containerized applications, whether it is a simple website or a complex system.
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.
We have hosted 50 websites using Amazon Elastic Container Service. The websites are used by our end customers and internal employees as well.
We use the solution as a docker service to run the containers.
We use the product for website and email database hosting.
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.
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.
It lets us manage a cluster of containers in the cloud without really having to worry about managing the platform. We're currently serving around 50 customers.
We use this product for our workflows. We launch an ECS cluster on-demand to run a job and shut down the cluster after the job is completed.
I have set up Container Service environments for various clients using different cloud providers, including AWS. I have used the Amazon Elastic Container Service in this capacity. One of my clients from Israel is running web-based applications that are using PostgreSQL as the backend database connection. I think that it is a user-learning software, and they provide it to big companies to give KT sessions for new employees. They use the Totara application and for that, we have set up the infrastructure including VBA and database applications. We also manage their Amazon Route 53, and we have set up Jenkins for CICD purposes.
We are using Amazon Elastic Container Service for Docker-based configuration. Previously, we had to manually go into an instance and then issue all Docker agents and instances. Now, we are using Amazon ECS to automate all of our Docker containers. We are deploying our microservices architecture in the ECS container install. We are using ECS as a service.