Chapters0/41 ▾
- 1.Cloud Concepts: Benefits & Economics0/4
- 2.Cloud Concepts: Well-Architected & Migration0/5
- 3.Security: Shared Responsibility & Compliance0/4
- 4.Security: IAM & Access Management0/4
- 5.Security: Services & Resources0/4
- 6.Technology: Deployment & Global Infrastructure0/4
- 7.Technology: Compute & Networking0/4
- 8.Technology: Databases & Storage0/4
- 9.Technology: AI, Analytics & Other Services0/4
- AI and machine learning services: pre-trained services and SageMaker AI
- Analytics services: Glue, Athena, Redshift, EMR, OpenSearch, Kinesis and Amazon Quick
- Messaging and workflows: SQS, SNS, EventBridge, Step Functions, Amazon Connect and SES
- Developer tools, cloud desktops, AWS Amplify and AWS IoT Core
- 10.Billing, Pricing & Support0/4
- EC2 purchasing options: On-Demand, Spot, Savings Plans, Reserved Instances and dedicated hardware
- Data transfer costs, consolidated billing and cost allocation tags
- Cost management tools: Pricing Calculator, Cost Explorer, Budgets, Cost and Usage Reports and Compute Optimizer
- AWS Support plans, Trusted Advisor, AWS Health and where to get help
Chapter 8 · Lesson 1 of 4
Relational databases: Amazon RDS, Aurora and databases on EC2
1 min read
The first decision is managed or self-managed. With Amazon RDS, AWS handles operating system and database patching, automated backups, high availability options and the hardware. The customer still owns how the application uses the database, such as tuning slow queries.
Hosting the database yourself on Amazon EC2 makes sense only when you need control that RDS does not give, for example an engine RDS does not offer or vendor agents installed on the operating system. You then take on patching, backups and scaling yourself.
| Feature | Purpose |
|---|---|
| Multi-AZ DB instance deployment | A standby in another Availability Zone takes over automatically if the primary fails; it does not serve reads |
| Read replicas | Asynchronously updated copies that answer read-only queries and take load off the primary |
| Snapshot | A point-in-time copy that must be restored by hand before use |
Amazon Aurora is a fully managed relational engine in the RDS family, compatible with MySQL and PostgreSQL, whose storage grows automatically and keeps copies across three Availability Zones.
It is a common target when leaving a commercial engine. Example: if reporting queries slow the store at noon but writes are fine, add read replicas; if the worry is surviving an Availability Zone outage, choose Multi-AZ.
Check yourself
1. A company's Amazon RDS database must keep running after an Availability Zone outage, with automatic failover. Read performance is not a concern. Which feature addresses this need?
2. A company wants to leave a commercial database for a fully managed relational engine that is compatible with PostgreSQL and whose storage grows automatically. Which service fits?
Facts checked 2026-11-15 · Sources: AWS Certified Cloud Practitioner (CLF-C02) exam guide, Domain 3, Amazon S3 User Guide: Understanding and managing Amazon S3 storage classes, Amazon RDS User Guide: Multi-AZ deployments and read replicas
AWS Cloud Practitioner cheat sheet: every key fact on one page →