Building something that works is only half the job. A cloud engineer also has to keep it affordable and keep it running. Cloud bills grow quietly: an oversized server, a forgotten test environment or unused storage can add up month after month. Cost optimization is the habit of matching what you pay for to what you actually use, with tools such as budgets and alerts and pricing options such as Savings Plans and Spot instances.
Reliability is about keeping your application available when things go wrong, because servers fail, zones go down and people make mistakes. You'll learn how the Well-Architected Framework guides good design, how to build for high availability across multiple zones, and how to plan for disaster recovery using recovery time (RTO) and recovery point (RPO) objectives. Cost and reliability often pull in opposite directions, so a good design finds the right balance. This is the last module, so after these videos, put everything together in the Projects.
An overview of the framework that guides secure, reliable and cost-effective cloud design.
Practical ways to reduce your AWS bill by matching what you pay for to what you use.
An AWS walkthrough of creating a budget and getting alerts before spending gets out of hand.
The design principles for building systems that keep working and recover from failures.
RTO and RPO, and the four recovery strategies: backup and restore, pilot light, warm standby and multi-site.