Reliability Pillar AWS Well-Architected Framework Reliability Pillar AWS Well-Architected Framework

Reliability Pillar AWS Well-Architected Framework Reliability Pillar AWS Well-Architected Framework

Reliability Pillar AWS Well-Architected Framework Reliability Pillar AWS Well-Architected Framework Reliability Pillar: AWS Well-Architected Framework Copyright © Amazon Web Services, Inc. and/or its affiliates. All rights reserved. Amazon's trademarks and trade dress may not be used in connection with any product or service that is not Amazon's, in any manner that is likely to cause confusion among customers, or in any manner that disparages or discredits Amazon. All other trademarks not owned by Amazon are the property of their respective owners, who may or may not be affiliated with, connected to, or sponsored by Amazon. Reliability Pillar AWS Well-Architected Framework Table of Contents Abstract and Introduction ................................................................................................................... 1 Abstract .................................................................................................................................... 1 Introduction .............................................................................................................................. 1 Reliability .......................................................................................................................................... 2 Design Principles ........................................................................................................................ 2 Definitions ................................................................................................................................. 2 Resiliency, and the Components of Reliability ........................................................................ 3 Availability ........................................................................................................................ 3 Disaster Recovery (DR) Objectives ........................................................................................ 6 Understanding Availability Needs ................................................................................................. 7 Foundations ....................................................................................................................................... 8 Manage Service Quotas and Constraints ....................................................................................... 8 Resources .......................................................................................................................... 9 Plan your Network Topology ....................................................................................................... 9 Resources ........................................................................................................................ 13 Workload Architecture ...................................................................................................................... 14 Design Your Workload Service Architecture .................................................................................. 14 Resources ........................................................................................................................ 16 Design Interactions in a Distributed System to Prevent Failures ...................................................... 16 Resources ........................................................................................................................ 18 Design Interactions in a Distributed System to Mitigate or Withstand Failures ................................... 19 Resources ........................................................................................................................ 23 Change Management ........................................................................................................................ 24 Monitor Workload Resources ...................................................................................................... 24 Resources ........................................................................................................................ 27 Design your Workload to Adapt to Changes in Demand ................................................................. 27 Resources ........................................................................................................................ 28 Implement Change ................................................................................................................... 29 Additional deployment patterns to minimize risk: ................................................................. 31 Resources ........................................................................................................................ 32 Failure Management ......................................................................................................................... 33 Back up Data ........................................................................................................................... 33 Resources ........................................................................................................................ 34 Use Fault Isolation to Protect Your Workload ............................................................................... 35 Resources ........................................................................................................................ 39 Design your Workload to Withstand Component Failures ............................................................... 40 Resources ........................................................................................................................ 42 Test Reliability ......................................................................................................................... 43 Resources ........................................................................................................................ 46 Plan for Disaster Recovery (DR) .................................................................................................. 46 Resources ........................................................................................................................ 48 Example Implementations for Availability Goals ................................................................................... 50 Dependency Selection ............................................................................................................... 50 Single-Region Scenarios ............................................................................................................ 50 2 9s (99%) Scenario ......................................................................................................... 51 3 9s (99.9%) Scenario ....................................................................................................... 52 4 9s (99.99%) Scenario ..................................................................................................... 54 Multi-Region Scenarios .............................................................................................................. 56 3½ 9s (99.95%) with a Recovery Time between 5 and 30 Minutes .......................................... 56 5 9s (99.999%) or Higher Scenario with a Recovery Time under 1 minute ................................. 59 Resources ................................................................................................................................ 61 Documentation ................................................................................................................ 61 Labs ................................................................................................................................ 62 External Links .................................................................................................................. 62 iii Reliability Pillar AWS Well-Architected Framework Books .............................................................................................................................. 62 Conclusion ....................................................................................................................................... 63 Contributors .................................................................................................................................... 64 Further Reading ............................................................................................................................... 65 Document Revisions .......................................................................................................................... 66 Appendix A: Designed-For Availability for Select AWS Services ............................................................... 68 iv Reliability Pillar AWS Well-Architected Framework Abstract Reliability Pillar - AWS Well- Architected Framework Publication date: July 2020 (Document Revisions (p. 66)) Abstract The focus of this paper is the reliability pillar of the AWS Well-Architected Framework. It provides guidance to help customers apply best practices in the design, delivery, and maintenance of Amazon Web Services (AWS) environments. Introduction The AWS Well-Architected Framework helps you understand the pros and cons of decisions you make while building workloads on AWS. By using the Framework you will learn architectural best practices for designing and operating reliable, secure, efficient, and cost-effective workloads in the cloud. It provides a way to consistently measure your architectures against best practices and

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    75 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us