High Availability & Business Continuity
Section Outline- Overview (Video Only)
- Understanding High Availability Configurations
- RTO & RPO
- Disaster Recovery Models
- Overview of Route53 for Multi-Site Failover
- Advanced Route53 Configurations
- Route53 – Understanding Health Checks
- Route53 – Implementing Health Checks
- Route53 – Understanding Failover Routing Policy
- Implementing Failover Routing Policy
- Understanding Self-Healing Based Architecture
- Multi-AZ vs. Multi-Region Based Design
- Quiz 1: High Availability & Business Continuity
Understanding High Availability Configurations
https://www.udemy.com/aws-certified-solutions-architect-professional/learn/v4/t/lecture/8530100?start=0 Everything fails, all the timeWhat is High Availability?
- Is a characteristic of the system design which makes resource available even in the case of any component failure in a computer system.
- Availability refers to the amount of time the system is in a functioning condition
- General Availability: 100% – Downtime
| Percent Uptime | Max Downtime / Year | Equiv. Downtime / Day |
| 90% | 36.5 days | 2.4 hours |
| 99% | 3.65 days | 14 minutes |
| 99.9 | 8.76 hours | 86 seconds |
| 99.95 (EC2 Uptime SLA) | 4.38 hours | 43 seconds |
Important Points
- Improving availability leads to cost increases. It’s important to balance betweeen the cost factor and the availability.
- SLA of your organization matters. 90% SLA means 2.4 hours of downtime every day.
- You can use Pingdom to get reports on your website’s uptime.