Se ha denunciado esta presentación.
Utilizamos tu perfil de LinkedIn y tus datos de actividad para personalizar los anuncios y mostrarte publicidad más relevante. Puedes cambiar tus preferencias de publicidad en cualquier momento.

Build Workflows with Amazon CloudFront, Amazon Route 53, & Lambda@Edge (CTD407-R2) - AWS re:Invent 2018

799 visualizaciones

Publicado el

In this session, learn how to build highly available and redundant, multi-origin workflows with Amazon CloudFront, Amazon Route 53, and Lambda@Edge.

  • Inicia sesión para ver los comentarios

  • Sé el primero en recomendar esto

Build Workflows with Amazon CloudFront, Amazon Route 53, & Lambda@Edge (CTD407-R2) - AWS re:Invent 2018

  1. 1. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved. Build Workflows with Amazon CloudFront, Amazon Route 53, & Lambda@Edge Archit Jain Software Development Engineer Amazon C T D 4 0 7 Alexander Korobeynikov Software Development Engineer Amazon
  2. 2. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved. Problems • Building fault tolerant multiple-origin setup systems • Building low latency websites which serve content from nearest location
  3. 3. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved. What is Amazon Route 53 (Route 53)? Users Elastic IP address
  4. 4. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved. What is Amazon CloudFront ? Users
  5. 5. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved. What is Lambda@Edge? Users Viewer request Viewer response Origin request Origin response Generate response
  6. 6. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved. Using CloudFront & Route 53 with multi origin When should you use it? • Multiple non–Amazon Simple Storage Service (Amazon S3) origins • Health check & latency based routing to nearest servers Users Elastic IP address
  7. 7. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved. Using CloudFront with native origin failover capability When should you use it? • Primary-secondary origin setup • Ability to failover for every request Users 4xx/5xx 200 OK Secondary origin Primary origin
  8. 8. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved. When should you use it? • Location based origin selection • Select origin based on request parameters • Content generation with Lambda@Edge Origin request Users Re-define origin Origin as updated in origin request function Using Amazon CloudFront with Lambda@Edge
  9. 9. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved. Comparison Route 53 CloudFront origin fallback Lambda@Edge Select nearest origin (latency) ✔︎ ✔︎ Multi-region Amazon S3 origin ✔︎ ✔︎ Failover on every origin errors ✔︎ Health check ✔︎
  10. 10. © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved. Questions
  11. 11. Thank you! © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved. Archit Jain Software Development Engineer Amazon Alexander Korobeynikov Software Development Engineer Amazon
  12. 12. Please complete the session survey in the mobile app. ! © 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved.

×