Containers at AWS: State of the Union
Download as PPTX, PDF0 likes141 views
The document discusses container services at AWS. It begins with an overview of Amazon Elastic Container Service (ECS), which provides a managed orchestration service to deploy and manage containers across a cluster of EC2 instances. It then covers how AWS addresses trends toward broader compute abstractions and operationalizing open source software. Finally, it introduces AWS Fargate, which removes the need for customers to manage the underlying infrastructure for containers.
Ad
More Related Content
What's hot (8)
Similar to Containers at AWS: State of the Union (13)
Ad
More from Massimo Ferre' (13)
Ad
Recently uploaded (20)
Containers at AWS: State of the Union
- 1. Containers at AWS: State of the Union Incontro DevOps Italia – March 9th 2018 Massimo Re Ferrè Principal Solutions Architect @ Amazon Web Services © 2018, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
- 2. Agenda • Introduction • Where it all started: Amazon ECS (Elastic Container Service) • Megatrends at AWS (and their ramification in AWS containers based services) • Broad compute abstractions • Operationalize Open Source SW on behalf of the customer • Everything is going “Serverless” (one abstraction at a time) • Containers as first class citizens • Conclusions
- 3. Agenda • Introduction • Where it all started: Amazon ECS (Elastic Container Service) • Megatrends at AWS (and their ramification in AWS containers based services) • Broad compute abstractions • Operationalize Open Source SW on behalf of the customer • Everything is going “Serverless” (one abstraction at a time) • Containers as first class citizens • Conclusions
- 4. Single-instance containers deployments OS Instance Easy, all is good
- 5. Multi-instance containers deployments OS Instance OS Instance OS Instance OS Instance OS Instance OS Instance OS Instance Hard, not very practical and not scalable
- 6. Multi-instance containers deployments Orchestrator OS Instance OS Instance OS Instance OS Instance OS Instance OS Instance OS Instance Agent Agent Agent Agent Agent AgentAgent
- 7. Multi-instance containers deployments OS Instance OS Instance OS Instance OS Instance OS Instance OS Instance OS Instance Agent Agent Agent Agent Agent AgentAgent Orchestrator
- 8. Multi-instance containers deployments OS Instance OS Instance OS Instance OS Instance OS Instance OS Instance OS Instance Agent Agent Agent Agent Agent AgentAgent Orchestrator How do we solve the data plane problem? How do we solve the control plane problem?
- 9. Agenda • Introduction • Where it all started: Amazon ECS (Elastic Container Service) • Megatrends at AWS (and their ramification in AWS containers based services) • Broad compute abstractions • Operationalize Open Source SW on behalf of the customer • Everything is going “Serverless” (one abstraction at a time) • Containers as first class citizens • Conclusions
- 10. Amazon Elastic Container Service (ECS) • Managed service • Solves the control plane (i.e. “orchestrator”) problem for the customer • Highly scalable • You only pay for the data plane resources you consume • Integrated with other AWS services (e.g. Amazon CloudWatch etc.)
- 11. Elastic Container Service (ECS): the user view EC2 Container Instance EC2 Container Instance EC2 Container Instance EC2 Container Instance EC2 Container Instance EC2 Container Instance EC2 Container Instance Agent Agent Agent Agent Agent AgentAgent ECS Control Plane (managed service) ECS Cluster Resource
- 12. mytaxi • 50 microservices - 10 containers/service • Costs down 40% by using Spot Instances • Faster Deployment Times https://aws.amazon.com/solutions/case-studies/mytaxi/ “ In November 2015 we moved our Docker container architecture to Amazon ECS, and for the first time ever in December we were able to celebrate a new year in which our system could handle the huge number of requests without any crashes or interruptions—an accomplishment that we were extremely proud of. We had faced the biggest night on the calendar without any downtime.”
- 13. Agenda • Introduction • Where it all started: Amazon ECS (Elastic Container Service) • Megatrends at AWS (and their ramification in AWS containers based services) • Broad compute abstractions • Operationalize Open Source SW on behalf of the customer • Everything is going “Serverless” (one abstraction at a time) • Containers as first class citizens • Conclusions
- 14. Compute Abstractions at AWS AWS Lambda Amazon EC2 Metal Amazon ECS AWS Batch physicalseverVMcontainerfunction Amazon Lightsail Levelofabstraction Provider space (managed by AWS) Consumer space (managed by the customer)
- 15. Agenda • Introduction • Where it all started: Amazon ECS (Elastic Container Service) • Megatrends at AWS (and their ramification in AWS containers based services) • Broad compute abstractions • Operationalize Open Source SW on behalf of the customer • Everything is going “Serverless” (one abstraction at a time) • Containers as first class citizens • Conclusions
- 16. AWS Pattern #1 • Build services “from the ground up” • Engineer for scale • Integrate deeply with all other AWS services • Own your roadmap • Deliver as a managed service for customers Examples: Amazon DynamoDB, Amazon ECS, Amazon S3, etc. How do I spot these services? Rule of thumb: those WITH NO version attached
- 17. AWS Pattern #2 • Take successful Open Source projects • Operate them applying best practices and architectural excellence • Honor the exposure of the standard interfaces and UX • Deliver as a managed service for customers Examples: Amazon RDS, Amazon Elasticsearch, etc. , EKS How do I spot these services? Rule of thumb: those WITH versions attached
- 18. Amazon EKS • Managed service for the K8s control plane (master, keyvalue store, etc..) • Upgrades and software lifecycle • Highly available setup
- 19. Amazon EKS tenets I t i s K u b e r n e t e s U p s t r e a m P r o d u c t i o n w o r k l o a d s S e r v i c e i n t e g r a t i o n s
- 20. Agenda • Introduction • Where it all started: Amazon ECS (Elastic Container Service) • Megatrends at AWS (and their ramification in AWS containers based services) • Broad compute abstractions • Operationalize Open Source SW on behalf of the customer • Everything is going “Serverless” (one abstraction at a time) • Containers as first class citizens • Conclusions
- 21. Enter Fargate AWS Lambda Amazon EC2 Metal AWS Batch AWS Fargate Amazon EKS physicalseverVMcontainerfunction Amazon Lightsail Levelofabstraction Provider space (managed by AWS) Consumer space (managed by the customer) Amazon ECS
- 22. AWS Fargate • AWS is managing the data plane for you • No need for the customer to manage EC2 container instances and clusters • Fargate is an infra managed service for other AWS services to consume • E.g. ECS (today), EKS (announced) • There is no (public) API nor AWS Console entry for Fargate • The charging unit becomes the container
- 23. AWS Fargate (in practice)
- 24. Agenda • Introduction • Where it all started: Amazon ECS (Elastic Container Service) • Megatrends at AWS (and their ramification in AWS containers based services) • Broad compute abstractions • Operationalize Open Source SW on behalf of the customer • Everything is going “Serverless” (one abstraction at a time) • Containers as first class citizens • Conclusions
- 25. Classic approach and deployment models EC2 Container Instance Task/Pod VPC Subnet IAM Role Internal Network Bridge / NAT layer Internal IP Address Deployed to a fleet of physical servers you never really worried about VPC IP Address Security Group
- 26. Assigning roles to Tasks EC2 Container Instance VPC Subnet IAM Role Internal Network Bridge / NAT layer VPC IP Address Task/Pod Internal IP Address https://aws.amazon.com/blogs/compute/help-secure-container-enabled-applications-with-iam-roles-for-ecs-tasks/ Deployed to a fleet of physical servers you never really worried about Security Group
- 27. Enabling direct VPC connectivity EC2 Container Instance VPC Subnet IAM Role VPC IP Address Task/Pod VPC IP Address https://aws.amazon.com/blogs/compute/under-the-hood-task-networking-for-amazon-ecs/ Deployed to a fleet of physical servers you never really worried about Security Group
- 28. Abstracting the data plane VPC Subnet Deployed to a fleet of EC2 instances you should not worry aboutFargate IAM Role VPC IP Address Task/Pod This looks a lot like EC2 (just one level of abstraction up) https://aws.amazon.com/blogs/aws/aws-fargate/ Security Group
- 29. Agenda • Introduction • Where it all started: Amazon ECS (Elastic Container Service) • Megatrends at AWS (and their ramification in AWS containers based services) • Broad compute abstractions • Operationalize Open Source SW on behalf of the customer • Everything is going “Serverless” (one abstraction at a time) • Containers as first class citizens • Conclusions
- 30. Final Thoughts • Containers are becoming a new legit compute unit • Take all you know and level it up • Ask yourself: “what abstraction level is good for me?” • Metal? VM? Container? Function? What? • Containers are here to stay but may not be your final destination • Think Lambda • We want AWS to be the best place to run containers • In all shape or forms and at ANY abstraction level
- 31. Container services availability as of March 9th • ECS: officially available in all regions • EKS: currently in preview for selected customers • https://pages.awscloud.com/amazon-eks-preview.html • Consuming Fargate from ECS: officially available in US East • Consuming Fargate from EKS: availability scheduled for 2018
- 32. Thank You! Mail: [email protected] Twitter: @mreferre