Abstract
Although every container orchestration framework uses its own specific language for its concepts, they all try to solve the same issues. That’s why you’ll find some similarities between Amazon EC2 Container Service (ECS) and Kubernetes but also a couple of differences in the way they solve the issues. One strong point in favor of ECS is that because it’s a native AWS (Amazon Web Services) technology, it is completely integrated with the other components, such as VPC (Virtual Private Cloud), EC2, ELBs (Elastic Load Balancers), and Route53. The main issue with ECS is that it is coupled to AWS, and currently you can’t run an ECS cluster on other cloud providers, which makes sense since it’s an Amazon technology.
This is a preview of subscription content, log in via an institution.
Buying options
Tax calculation will be finalised at checkout
Purchases are for personal use only
Learn about institutional subscriptionsAuthor information
Authors and Affiliations
Rights and permissions
Copyright information
© 2016 Pablo Acuña
About this chapter
Cite this chapter
Acuña, P. (2016). Amazon EC2 Container Service. In: Deploying Rails with Docker, Kubernetes and ECS. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-2415-1_4
Download citation
DOI: https://doi.org/10.1007/978-1-4842-2415-1_4
Published:
Publisher Name: Apress, Berkeley, CA
Print ISBN: 978-1-4842-2414-4
Online ISBN: 978-1-4842-2415-1
eBook Packages: Professional and Applied ComputingProfessional and Applied Computing (R0)Apress Access Books