Amazon Elastic Container Service Reviews

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.

The best thing about Amazon Elastic Container Service is its availability and reliability.

There don't seem to be any improvements needed for ECS at the moment. I will consider them once I get my projects running smoothly and understand the costs better.

I have been using Amazon Elastic Container Service for six months.

I would rate the stability of ECS as an eight out of ten. While it is generally stable, there have been some issues, especially when working on client projects where troubleshooting was needed. Stability can be affected if someone doesn't have Terraform installed, as it is crucial for provisioning. It is essential to have good knowledge of what you are doing when using ECS. Overall, it is a good service, but some factors like Terraform's expertise can impact stability.

I would rate the scalability of ECS as a nine out of ten. While I haven't explored all its features extensively, based on what I have used so far, it is highly scalable and capable of handling increased workloads effectively. In our organization, quite a few users use ECS for various tasks, similar to how many users access certain files or resources. However, this information isn't available to everyone in the company, and it is restricted to specific departments or teams. Our company has a substantial client base that relies on ECS for their needs.

I have not had any need to contact technical support.

The initial setup of ECS is generally straightforward, but it is essential to have some command-line experience to avoid potential mistakes. The deployment time for ECS varies depending on your internet speed, but it typically takes a maximum of five minutes. It works well with Terraform and Kubernetes, allowing you to create resources efficiently. Overall, it is a user-friendly and efficient tool for managing containers.

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 like Amazon EC2 Container Service's elasticity. 

The solution needs to improve backup and pricing. 

I have been working with the solution for five years. 

The solution is stable. 

The product is very scalable and we have around 400 users for it. 

The tool's setup is easy and I would rate it a ten out of ten. The tool's deployment is fast and takes around one day to complete. If deployment is for an enterprise, then you need to go through the architecture. You need to go to the dashboard and put in all the required details to deploy it. 

Amazon EC2 Container Service is priced high. 

Amazon EC2 Container Service is a good platform since you can run multiple things on it. I would rate it a ten out of ten. 

We use Amazon Elastic Container Service (ECS) for efficient container orchestration. We start by creating Docker containers and then storing them in ECS. It facilitates container deployment, offering flexibility between serverless execution and traditional EC2 instances. It enables automated deployments, providing an option to edit them as needed through integrated CI/CD pipelines.

The product's most valuable feature is service discovery functionality. It is an excellent feature impacting cost reduction. It facilitates the seamless connection of backend services to the front end, utilizing local domains. Additionally, the integration of with Atmos, another service management tool by AWS, enhances its functionality. It shows the impactful configuration provided by the AWS team.

There is room for improvement, particularly in logging and monitoring for the product, while integrating external third-party tools like Elastic Log Kibana and Grafana or Primatius. They could provide easier options for third-party integrations similar to internal AWS services.

We have been using Amazon Elastic Container Service for two years.

The platform has high stability with no downtime for any services. In case of unavailability, we can refer to AWS documentation or contact the technical support team for SLA services.

The scalability depends on specific user cases. It helps us handle increased traffic or workload. When clients require login deployments due to application version or UI component changes, we utilize CodeDeploy in conjunction with AWS CodePipeline for deployment. While there is no downtime during these deployments, scaling the application might take some time due to scheduling considerations.

The technical support team is very friendly.

The initial setup is easy. AWS manages the deployment with predefined configurations.

They offer a pay-as-you-go pricing model for the product. It is inexpensive compared to Kubernetes, which considers a minimum number of microservices.

The new users would need help to deploy the CI/CD pipeline for the product. They need to follow proper documentation. It also provides some settings for automated deployment.

We integrated ECS for a logistics project. It is working fine without any downtime for five microservices.

I rate it an eight 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.

It depends on the specific needs and requirements. For example, if it's for customer care on Windows Server, they need to onboard the EC2.

Performance is our top priority. So, if we need to deploy on a high-specification machine, we can choose it from the software. If we just need a low-specification one, we can just choose it based on the requirement handling software configuration.

There is room for improvement in the licensing costs. There can be better licensing costs. 

We have been providing this service for two years. 

I would rate the stability a nine out of ten. 

It offers good scalability. You can scale down and scale up easily. You can easily adjust resources based on your needs, whether public or private deployments. Complex configurations are not required for scaling or scheduling tasks.

We have two customers using this solution. 

The technical support team is knowledgeable and customer-friendly. They offer prompt and helpful assistance.

I have experience with Alibaba Cloud and Cisco's container platform. However, I prefer the Amazon EC2 Container Service for its ease of use, scalability, and integration with AWS services.

However, Alibaba is on-premises, and EC2 is on the cloud. The best option depends on regulations. Some industries and competitors have regulations that require on-premises solutions, while others allow cloud solutions. The specific needs and regulations will determine the best option for each client.

It depends on the data manager and the specific client. 

The initial setup is straightforward. Deployment takes approximately 5-10 minutes. 

You simply access the portal, choose the appropriate configuration, and upload your code. No complex technical knowledge is required.

The licensing is expensive. The licensing is available on a monthly basis, yearly basis, and a pay-as-you-go licensing model. 

It's user-friendly and requires minimal technical expertise. Overall, I would rate the solution a nine out of ten. 

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.

We use Amazon EC2 Container Service to host a variety of applications for our clients. We use ECS to test machines, production machines, and other environments.

The security is good with 24/7 availability along with location. The cloud services are readily available. For example, if all three or four servers hosted in the cloud fail at once, the service will be transferred to other machines. This is one of the things that makes me most likely to use this cloud service.

Amazon EC2 Container Service's security can be improved. For example, ECS should be integrated with multiple teams and cloud providers to make it more accessible and secure. Additionally, AWS should provide more security policies for ECS resources to prevent unauthorized access. Support could also be improved.

I have been using Amazon EC2 Container Service for more than two years. We are using the latest version of the solution.

The product is stable. The security line has been deployed. I have never experienced any instability. I rate the solution’s stability an eight out of ten.

The solution is scalable.

Some people are good and are helping us.

Neutral

The initial setup is easy. Generally, everything is written in clear and understandable language. If you know English, you can clearly understand all of these things. You can also change the language, so it's not too complex.

The solution is expensive, but not too much.

Overall, I rate the solution an eight out of ten.

Our primary use case for this tool is mainly for backup from operational data.

It has helped the company provide a stable and reliable environment.

The most valuable feature, after using Amazon EC2 Container Service for two years, is to set the availability and also for network throughput.

There is room for improvement in the pricing of Amazon EC2 Container Service. Also, mainly on the network issues to access the container.

We have been using Amazon EC2 Container Service in a specific project here for two years. However, we don't use the latest version. 

Amazon EC2 Container Service is stable. I would rate the stability ten out of ten.

The solution has some limitations. Mainly the network issues with accessing the container. Hence, I would rate the scalability of Amazon EC2 Container Service a seven out of ten.

The customer service and support team is good. We can find all the information on the online portal.

Amazon EC2 Container Service is very good and easy to use. It also integrates with Okta Solutions.

It was really important to our project to have a stable environment on the cloud that would be reliable. It was important. It is not easy to give a number to this, but for sure, it has value.

We emphasize that utilizing any cloud solution with payments in dollars is a huge amount for our liaison here.

For someone who wants to use Amazon EC2 Container Service, I would say it is a very good solution. Especially for people who have to plan a lot in advance to define exactly what they need and to plan the capacity and also the way they will use the institute and also order possible solutions connected to them so they can plan for their costs.

Overall, I would rate Amazon EC2 Container Service solution as an eight out of ten