Summary
You can use AWS to design, build, or run almost any application that you would in a traditional datacenter. But just treating AWS as a traditional data center would be a mistake. AWS allows you to implement a given scenario in a variety of ways, and each way comes with its own advantages and disadvantages.
Recall the shared responsibility model you learned about in Chapter 4, “Understanding the AWS Environment.” Both you and AWS are responsible for different aspects of your application running on AWS. By adhering to the principles laid out in the five pillars of the Well-Architected Framework, you can clearly see where your responsibility begins and ends for each AWS resource that you plan to use.
Use the pillars to evaluate the trade-offs for different design decisions. For example, suppose you want to host a static website. On the one hand, you could host the site using S3, leaving AWS with the responsibility for ensuring its reliability, security, and performance...
