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.
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.
My advice to new users would be to have a good understanding of how ECS works, especially in the command line. While the web interface is helpful, knowing how to work with the command line is crucial, especially when dealing with provisioning and managing resources on virtual machines. The more you learn about the command line, the better you will be at efficiently working with ECS and providing effective solutions. Knowledge in this area is highly valuable. Overall, I would rate the solution a nine out of ten.
I rate Amazon Elastic Container Service an eight out of ten. If you are beginning to use cloud services, ECS is the best and easy-to-use product you can go for.
We had virtualized the solution, and we were using it on EC2. The solution has a great offering for docker images. We didn't have to work from scratch. We could go to the marketplace and directly get the image from there. Overall, I rate Amazon Elastic Container Service an eight out of ten.
Learn what your peers think about Amazon Elastic Container Service. Get advice and tips from experienced pros sharing their opinions. Updated: April 2024.
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.
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 advice for our clients is that before creating the infrastructure, take steps to analyze your needs, and gather the requirements. You want to know what the requirements are, and what resource utilization you have. Suppose, for example, that your requirements are for two CPU cores and one terabyte of RAM. If you are not aware of the actual requirements of the application and the user then you work with the unknown and run the risk of setting up an infrastructure with a high level of resources. This will be costly. Our approach is to take some time to understand the application and the resource requirements before the setup. After analyzing, we draw the diagram to prepare the plan and then set up the infrastructure. The biggest lesson that I have learned from using this product is that it is highly available, cost-effective, and reliable. I get all three of these benefits from this technology. I would rate this solution a nine out of ten.
DevOps Engineer at a financial services firm with 10,001+ employees
Real User
2020-08-23T08:17:29Z
Aug 23, 2020
I would recommend Amazon Elastic Container Service. They have a big R&D team, and they'll be providing good features for customers. I think AWS has been pretty good on this R&D thing. I would like to appreciate their team, which continuously looks into customer satisfaction and comes up with a new bunch of services every time. They're moving to a customer-centric approach. We aren't looking into specific new features. We are in the testing phase currently. If they are releasing some new features, we should definitely use them based on our requirements. I would rate Amazon Elastic Container Service an eight out of ten.
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 rate Amazon ECS a nine out of ten.
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.
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.
My advice to new users would be to have a good understanding of how ECS works, especially in the command line. While the web interface is helpful, knowing how to work with the command line is crucial, especially when dealing with provisioning and managing resources on virtual machines. The more you learn about the command line, the better you will be at efficiently working with ECS and providing effective solutions. Knowledge in this area is highly valuable. Overall, I would rate the solution a nine out of ten.
I rate Amazon Elastic Container Service an eight out of ten. If you are beginning to use cloud services, ECS is the best and easy-to-use product you can go for.
We had virtualized the solution, and we were using it on EC2. The solution has a great offering for docker images. We didn't have to work from scratch. We could go to the marketplace and directly get the image from there. Overall, I rate Amazon Elastic Container Service an eight out of ten.
I rate Amazon Elastic Container Service a seven out of ten. I advise others to use AWS EKS than ECS.
The solution has multiple versions. You can choose a version compatible with your system. I rate it a seven out of ten.
I would rate the overall product a nine out of ten.
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.
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.
I would rate Amazon ECS nine out of 10. Amazon is amazing. I give them full marks all around.
I would recommend this solution for anyone thinking to implement it. I rate this product an eight out of 10.
My advice for our clients is that before creating the infrastructure, take steps to analyze your needs, and gather the requirements. You want to know what the requirements are, and what resource utilization you have. Suppose, for example, that your requirements are for two CPU cores and one terabyte of RAM. If you are not aware of the actual requirements of the application and the user then you work with the unknown and run the risk of setting up an infrastructure with a high level of resources. This will be costly. Our approach is to take some time to understand the application and the resource requirements before the setup. After analyzing, we draw the diagram to prepare the plan and then set up the infrastructure. The biggest lesson that I have learned from using this product is that it is highly available, cost-effective, and reliable. I get all three of these benefits from this technology. I would rate this solution a nine out of ten.
I would recommend Amazon Elastic Container Service. They have a big R&D team, and they'll be providing good features for customers. I think AWS has been pretty good on this R&D thing. I would like to appreciate their team, which continuously looks into customer satisfaction and comes up with a new bunch of services every time. They're moving to a customer-centric approach. We aren't looking into specific new features. We are in the testing phase currently. If they are releasing some new features, we should definitely use them based on our requirements. I would rate Amazon Elastic Container Service an eight out of ten.