Amazon Elastic Container Service (Amazon ECS) is a scalable, high performance container management service that supports Docker containers.
N/A
IBM Cloud Managed Istio
Score 8.7 out of 10
N/A
The IBM Cloud Kubernetes Service provides the Managed Istio installation add on, designed to provide additonal control over clusters and the microservices they comprise via automatic updates and lifecycle management of control plane components, and integration with platform logging and monitoring tools.
There is no additional charge for Amazon ECS. You pay for AWS resources (e.g., Amazon EC2 instances or Amazon EBS volumes) you create to store and run your application. You only pay for what you use, as you use it; there are no minimum fees and no upfront commitments.
—
More Pricing Information
Community Pulse
Amazon Elastic Container Service (Amazon ECS)
IBM Cloud Managed Istio
Features
Amazon Elastic Container Service (Amazon ECS)
IBM Cloud Managed Istio
Container Management
Comparison of Container Management features of Product A and Product B
Amazon Elastic Container Service (Amazon ECS)
8.1
Ratings
5% above category average
IBM Cloud Managed Istio
-
Ratings
Security and Isolation
9.00 Ratings
00 Ratings
Container Orchestration
8.50 Ratings
00 Ratings
Cluster Management
7.80 Ratings
00 Ratings
Storage Management
8.00 Ratings
00 Ratings
Resource Allocation and Optimization
7.30 Ratings
00 Ratings
Discovery Tools
7.30 Ratings
00 Ratings
Update Rollouts and Rollbacks
8.50 Ratings
00 Ratings
Self-Healing and Recovery
8.40 Ratings
00 Ratings
Analytics, Monitoring, and Logging
8.20 Ratings
00 Ratings
Platform-as-a-Service
Comparison of Platform-as-a-Service features of Product A and Product B
Amazon Elastic Container Service (Amazon ECS) is well suited where you need the ease of managing the clusters by letting AWS do the stuff for you. Obviously, whenever you want to run the docker based workloads, it is always better to go for either AWS ECS or AWS EKS. If you are interested in staying at AWS only and don't want to be cloud-agnostic, then go for AWS ECS instead of AWS EKS. AWS ECS is cheaper than AWS EKS and also more managed by AWS and better integrated with other AWS services. If you want to run those workloads as serverless, then AWS ECS Fargate is the best option to go with. If you already have a Kubernetes based setup that you want to migrate to AWS, then go for AWS EKS instead of AWS ECS.
It is a perfect application when you have multiple users and/or developers and you want to create rules and standards for access and the ability to change access levels. The reporting of usage is good, but adding more granularity into the metrics that have been used to measure are not specific enough. They provide detail but drilling into the detail would be more appropriate i.e. access to the baseline data.
Well Integrated - As with the majority of AWS services, ECS works will with any other AWS product (Route 53, CloudWatch, IAM, etc).
Easy to get started with - It is easy to get started building just about anything in AWS and using ECS is no exception to this rule. Be careful though -- AWS lets you do/build anything in any way you could think of and allowing yourself to shoot yourself in the foot is no exception.
The user interface sometimes seem to be confusing and cumbersome. It can be improved so that people can understand clearly which section to go for which functionality.
When a container fails, the error logs are not readily available on the ECS console. If it can be provided it would be easier to debug from there itself instead of going to our log manager.
Sometimes the old EC2 containers become stale and need to be restarted manually. There should be a notification for such scenarios. We have mostly been finding it out on our own and then fixing it by manually restarting EC2 instances.
If this could be proactively monitored and notified, it would be great.
Aside from some ECS-specific terms to learn at first, learning & starting to use ECS is relatively straightforward. AWS docs on the topic are also of high quality, with sound & relevant examples to follow. Troubleshooting container issues is also a breeze thanks to CloudWatch integration & helpful error messages on the AWS console.
Support is relatively good, although the documentation sometimes is lacking, as well as outdated in our experience, especially when we initiated the process of using this service. But once we found how to assemble things, we haven't really required support from anyone at AWS, the service works without problems so we haven't had the need to contact support, which speaks well of how ECS is built.
AWS Elastic Beanstalk is a good beginner level orchestration service but lacks container management and scaling capabilities. EC2 is again not a Managed cloud service. It is like just renting a computer on cloud and then managing it on our own. Compared to these ECS is a comprehensive solution that provides management, scaling, containerization and other service connectivity out of the box.
1) One-stop solution for all the complex network connectivity managed by [IBM Cloud Managed Istio]. 2) Nice dashboard to understand the flow. 3) Easy to troubleshoot the service if any one of the APIs is not responding. 4) We can integrate it with Azure Kubernetes service and other cloud provider Kubernetes services. 5) Monitoring the health of the pods can be easily configured and alerts can be triggered very accurately with this tool.
We run 8 web applications (demo instances) on a single machine. At a particular time, no more than 3 applications run simultaneously. So, we keep only required containers up. This helps us to provision small EC2 machines without compromising performance.
Overall Amazon ECS helps to have less number of dedicated machines as more than one solution can be deployed on a single instance. This reduces costs a lot.