Amazon Elastic Container Service Reviews

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.

Public Cloud

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.

My company uses Amazon EC2 Container Service as a backup.

The most valuable feature of the solution stems from the fact that it is very easy to set up. The solution is not that hard to get around for beginners. The solution's setup phase is good, even though you may not have so much knowledge of the platform.

The solution's stability is an area of concern where improvements are required.

I have been using Amazon EC2 Container Service for three years. I don't remember the version of the solution.

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

End users are unpredictable, so I think there will be issues in terms of limitations and network issues.

The scalability of the product is fine. I don't use the product's scalability since it is not that high.

I don't intentionally plan to increase the use of Amazon EC2 Container Service.

I have experience with OCloud.

The product's initial setup was very straightforward and not complex.

The solution can be deployed in less than an hour.

The deployment process of Amazon EC2 Container Service depends on why its users want to deploy the product in their environments. Make sure you have your infrastructure and IP setup in place. Once you have all the IPs and your infrastructure setup in place, you will be able to deploy Amazon EC2 Container Service within a few days. EC2 platform provides a very simple interface where you should use the IPs in your router in your virtual machine setup, and then the backup part of the solution should be good to use.

I myself manage the deployment and maintenance processes of Amazon EC2 Container Service.

I take care of the solution's deployment phase by myself

There is no need to pay anything towards the licensing costs of Amazon EC2 Container Service.

I feel that others should try Amazon EC2 Container Service, but it all depends on what others want to deploy from the platform offered by Amazon. Cost-wise, Amazon EC2 Container Service is an okay product. It is better to look at comparisons before proceeding to move to a vendor for a product.

I rate the overall tool a nine 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. 

Amazon Web Services (AWS)

We had a client who needed us to develop a simple application. The client specified the requirement for the application to be hosted on Amazon, leading us to utilize Amazon EC2 Container Service for this purpose.

We primarily employ the Linux platform in terms of architecture. It utilizes its database, MySQL. Additionally, for CI/CD processes, we rely on Amazon CodeBuild. Furthermore, we use Amazon S3 storage to store specific static files. Currently, the system is running smoothly, and we don't actively perform any maintenance tasks as everything is automated.

I would like the product to improve integration with different platforms.

I have been using the product since 2020.

The solution is stable. We did not encounter any downtime.

My company has around five users for the product. The solution is utilized by a government agency, serving as a procurement monitoring system for government projects, particularly in infrastructure development. The focus is primarily on road construction and building facilities for the government agency. It is scalable as it's easy to add additional resources or increase capacity. We can easily scale horizontally or vertically, and it comes with its load-balancing capability. This makes it straightforward to manage an increased volume of transactions. Our team is relatively small, consisting of about five to six members. Additionally, the client has an equivalent counterpart that provides operational support. On the operational side, the head office has a well-structured organizational setup, with individuals supporting operations and maintaining the data. In terms of technical aspects, there's also a counterpart responsible for monitoring the performance of the application and the platform on the client side.

AWS' technical support is very helpful.

The tool’s deployment is straightforward. We need to spin up the instance, select the platform, and choose the type of specific computer resources. The developers use Git, compress the file, and configure the pipeline to deploy the compressed application file. Additionally, they utilize a desktop button that automates the uploaded application's deployment on the EC2 instance.

Our technical team did the deployment using Bitbucket pipeline.

Amazon EC2 Container Service is cheap.

The organizational structure consists of a head office and regional offices. Each regional office has a designated point person responsible for user support in their respective region and division. Our primary scope involves the development of the application, deployment, and providing training. I rate the solution a ten out of ten. In our case, the requirements are straightforward. The console offers all the necessary information for basic operations. However, for those new to using the AWS tool, it's advisable to visit their training website to read and understand the instructions on how to set up and use the tool effectively. The basic setup is covered in the training resources.

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.

Public Cloud

Amazon Web Services (AWS)

I use Amazon EC2 Container Service to install system instances that need a container. I rely on it when I use microservices. 

I like the tool's availability and automated scalability. I need to define the port numbers, and when I have a large load of requests, I can get automated scalability. 

Amazon EC2 Container Service is easy to create and manage. I can use it easily on my CI/CD pipeline and deploy solutions. 

The product should improve its price. 

I have been using the product for three years. 

I rate Amazon EC2 Container Service's stability a ten out of ten. 

I rate the product's scalability a ten out of ten. 

The tool's deployment is easy. 

We have seen ROI with the tool's use. It saves time for my support and development teams. 

Amazon EC2 Container Service is a trustworthy infrastructure from Amazon. It speeds up delivery from the infrastructure and development teams. I rate it a ten out of ten. 

We use the solution for a web application like an e-commerce or a basic site. I have a business site.

EC2 is an initial level with a nominal cost. As a customer, we need to approach an EC2 tool. Additionally, other instances are available at slightly higher costs. Hence, once the business is established and running smoothly, we can upgrade to another instance.

We use the EC2 for testing purposes or as a starting point.

We need RAM, CPU, and install cPanel. cPanel is a separate third-party tool. If we install an EC2 tool, it would be an interface for managing files and databases, making it easier to maintain them.

I have been using Amazon EC2 Container Service as a customer and a partner for two to three years.

The product is stable. We need to skip the unnecessary servers or sometimes enable the autoscaling group feature to adjust based on conditions automatically.

I rate the solution’s stability an eight-point five out of ten.

We can increase the RAM, CPU, and hard disk for scalability.

We have used different hosting from different companies.

The initial setup is easy.

The solution's pricing is nominal. Also, it manages all the servers, mainly when certain servers might experience slowdowns. Amazon EC2 offers features that don't affect the website or application's performance.

If a customer requires a low-cost server, we suggest considering different options from various companies. Otherwise, we recommend exploring the offerings provided by Amazon EC2.

Overall, I rate the solution a nine out of ten.