More on this book
Kindle Notes & Highlights
When architecting solutions you make trade-offs between pillars based upon your business context,
Security and Operational Excellence are generally not traded-off against other pillars.
When you make a capacity decision before you deploy a system, you might end up sitting on expensive idle resources or dealing with the performance implications of limited capacity. With cloud computing, these problems can go away.
In the cloud, the capability to automate and test on demand lowers the risk of impact from design changes.
(For example, if you store 10,000 objects with Amazon S3, you can on average expect to incur a loss of a single object once every 10,000,000 years.)
Combining tagged resources with entity lifecycle tracking (employees, projects) makes it possible to identify orphaned resources or projects that are no longer generating value to the business and should be decommissioned. You can set up billing alerts to notify you of predicted overspending, and the AWS Simple Monthly Calculator allows you to calculate your data transfer costs.
AWS customers should evaluate their AWS service needs and request appropriate changes to their limits for each region used.