Difference between revisions of "AWS RDS Single-AZ"
Jump to navigation
Jump to search
| (3 intermediate revisions by 2 users not shown) | |||
| Line 3: | Line 3: | ||
1) Instance failure: | 1) Instance failure: | ||
* [[RTO]] is typically under 30 minutes. [[RPO]] = 0 | * [[RTO]] is typically under 30 minutes. [[RPO]] = 0 | ||
| + | |||
| + | 2) [[Amazon Elastic Block Store (EBS)|EBS]] volume failures | ||
| + | * From 10 minutes to hours | ||
| + | |||
| + | == Related == | ||
| + | * [[AWS RDS Instance Types]] | ||
== See also == | == See also == | ||
Latest revision as of 12:42, 15 February 2023
https://aws.amazon.com/blogs/database/amazon-rds-under-the-hood-single-az-instance-recovery/
1) Instance failure:
2) EBS volume failures
- From 10 minutes to hours
Related[edit]
See also[edit]
- AWS SLA,
Single-AZ, Multi-AZ - Amazon databases: AWS RDS, storage,
aws rds, Amazon RDS Proxy, RDS FAQs, PostgreSQL, MySQL, SQL Server, AWS Outposts, Amazon Aurora, Amazon Aurora Serverless , Amazon DocumentDB, Amazon DynamoDB, Amazon Redshift, Amazon QLDB, Amazon RDS Performance Insights, DataFileRead, DMS, Amazon Neptune, Amazon MemoryDB for Redis, Amazon RDS query editor for Aurora Serverless, Amazon Redshift query editor, AWS RDS Snapshots, AWS RDS Instance Types,rds_superuser, Authentication, autoscaling
Advertising:
