Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

AWS re:Invent 2016: State of the Union: Containers (CON316)

707 views

Published on

Join us to learn about the latest developments from Amazon ECS and the container ecosystem. Deepak Singh, General Manager of AWS Container Services, discusses the evolution of containers on AWS and shares our vision for continued innovation in this space. You also hear about how other companies are using the AWS container platform to innovate and build new businesses.

Published in: Technology
  • Be the first to comment

AWS re:Invent 2016: State of the Union: Containers (CON316)

  1. 1. © 2016, Amazon Web Services, Inc. or its Affiliates. All rights reserved.
  2. 2. Agenda Overview
  3. 3. solve? Overview ECS
  4. 4. Overview ECS There is no software to:
  5. 5. Overview ECS Load Balancing MonitoringID & Access NetworkingLogging Auto Scaling Deep integration
  6. 6. Common Use Cases Overview ECS
  7. 7. Using ECS Companies
  8. 8. managed platform Overview ECS
  9. 9. A Year In Review
  10. 10. A Year In Review
  11. 11. production scale?
  12. 12. Well Architected Framework
  13. 13. Well Architected Framework Security Reliability Performance efficiency Cost optimization Operational excellence
  14. 14. Well Architected Framework
  15. 15. Well Architected By Design
  16. 16. Security Security at all layers Traceability Response automation Least privilege access
  17. 17. Security By Design AWS Compute Storage Database Networking Edge locations Regions Availability Zones AWS Global Infrastructure Responsible for security of the cloud CUSTOMER Customer Data Platform, Applications, IAM Operating system, network and firewall configuration, VPC Server-side encryption (file system and/or data) Network traffic protection (encryption/integrity/identity) Client-side encryption & data integrity authentication Responsible for security in the cloud
  18. 18. Security By Design
  19. 19. Security By Design
  20. 20. Operational Excellence
  21. 21. Operational Excellence By Design
  22. 22. Operational Excellence By Design
  23. 23. Operational Excellence By Design
  24. 24. Reliability
  25. 25. Reliability By Design
  26. 26. Reliability By Design
  27. 27. Reliability By Design
  28. 28. Reliability By Design
  29. 29. Right-sizing resources Reduce operational burden Performance Efficiency & Cost Optimization
  30. 30. Right-sizing resources Reduce operational burden Efficiency & Optimization By Design
  31. 31. Efficiency & Optimization By Design Anatomy of Task Placement Cluster Constraints Custom Constraints Placement Strategies Apply Filter Satisfy CPU, memory, and port requirements Filter for location, instance-type, AMI, or custom attribute constraints Identify instances that meet spread or binpack placement strategy Select final container instances for placement
  32. 32. Efficiency & Optimization By Design New Placement Constraints Name Example AMI ID attribute:ecs.ami-id == ami-eca289fb Availability Zone attribute:ecs.availability-zone == us-east-1a Instance Type attribute:ecs.instance-type == t2.small Distinct Instances type=“distinctInstances” Custom attribute:stack == prod
  33. 33. Efficiency & Optimization By Design Supported Placement Strategies Binpacking Spread Affinity Distinct Instance
  34. 34. Serving Maps at Scale on AWS
  35. 35. 3 billion probes = 100 million miles per day
  36. 36. Growth in Three Areas
  37. 37. C4 R3 M4R3 R3 R3 R3 R3 M4 M4 M4 M4 M4 C4 C4 C4 C4 C4 Map Service Search Service Directions Service
  38. 38. C4 ECS Cluster R3 M4R3 R3 R3 R3 R3 M4 M4 M4 M4 M4 C4 C4 C4 C4 C4 Map Service Search ServiceDirections Service
  39. 39. R3 R3 R3 R3 R3 R3 Git SHA 56fb514 R3 R3 R3 R3 R3 R3 Git SHA 168f73e
  40. 40. C4 ECS Cluster R3 R3 R3 R3 R3 R3 M4 M4 M4 M4 M4 M4 C4 C4 C4 C4 C4 Map Service Search ServiceDirections Service Spot Fleet C4 C4 R3 R3
  41. 41. 25% Fewer instances 80-90% Savings per month on EC2
  42. 42. 21 Services 2000 Tasks 1.3 billion Requests per day
  43. 43. Foundational Technology
  44. 44. Foundational Technology ECRECS Dynamo DB S3EC2
  45. 45. Amazon EMR long pole
  46. 46. AWS Batch
  47. 47. AWS Batch Architecture ECS Cluster AWS Batch Compute Environment EC2 EC2 EC2 EC2 EC2 EC2 EC2 EC2 Job Queue EC2 Auto-Scaling or Spot Fleet ECS RunTask ECS RunTask AWS Batch Scheduler Jobs AWS Customer Account
  48. 48. AWS Batch Job Lifecycle Submitted We have received your job Pending Waiting on dependent jobs to complete Runnable No more dependencies. Waiting for compute resources Starting Scheduling your job to a compute resource Running Your job is currently running Succeeded Your job ran successfully
  49. 49. more control
  50. 50. ECS More Control
  51. 51. Introducing
  52. 52. Blox Introducing Developers
  53. 53. open source Blox Introducing
  54. 54. Blox Introducing
  55. 55. Blox Runs locally, on-premises, in an EC2 instance, in a container on AWS, or wherever you want Calls ECS API to deploy container State sync Query
  56. 56. Vision The Blox developers
  57. 57. Roadmap The Blox
  58. 58. Open Source http://blox.github.io
  59. 59. Netflix 100k instances in 3 regions across 12 Availability Zones Adopted microservices for more agility Started to move to containers in 2016 History of relying on AWS to shed operational heavy lifting Saw the velocity of features in ECS Worked with ECS team to integrate Titus into ECS Plan to leverage ECS to host all container workloads
  60. 60. MiniCon Overview
  61. 61. © 2016, Amazon Web Services, Inc. or its Affiliates. All rights reserved.

×