Quibank app: now on the App Store — free, works offline. Get the app ↗

Chapters0/41 ▾
  1. 1.Cloud Concepts: Benefits & Economics0/4
    1. The six advantages of cloud computing
    2. Elasticity, scalability, agility, high availability and global reach
    3. Cloud economics: fixed versus variable cost and total cost of ownership
    4. Licensing, rightsizing and automation
  2. 2.Cloud Concepts: Well-Architected & Migration0/5
    1. The six pillars of the Well-Architected Framework
    2. Pillar trade-offs and the AWS Well-Architected Tool
    3. The AWS Cloud Adoption Framework: outcomes, perspectives and phases
    4. Migration strategies: the 7 Rs
    5. AWS migration services and tools
  3. 3.Security: Shared Responsibility & Compliance0/4
    1. Security of the cloud and security in the cloud
    2. How responsibility shifts with the service you choose
    3. Compliance reports, programs and where data lives
    4. Encryption, keys and audit records
  4. 4.Security: IAM & Access Management0/4
    1. The root user and sign-in credentials
    2. IAM users, user groups and roles
    3. Policies, deny rules and least privilege
    4. Federation, IAM Identity Center, Amazon Cognito and secrets
  5. 5.Security: Services & Resources0/4
    1. Blocking web attacks and DDoS: AWS WAF, AWS Shield and AWS Firewall Manager
    2. Detecting threats, flaws and sensitive data: GuardDuty, Inspector and Macie
    3. Collecting, investigating and advising: Security Hub, Detective and Trusted Advisor
    4. AWS Marketplace and where to find security help
  6. 6.Technology: Deployment & Global Infrastructure0/4
    1. Ways to access AWS: console, CLI, SDKs and APIs
    2. Deployment tools and cloud deployment models
    3. Regions, Availability Zones and high availability
    4. Multiple Regions, data residency and edge services
  7. 7.Technology: Compute & Networking0/4
    1. Amazon EC2 instance types, auto scaling and load balancers
    2. Containers, serverless compute, Lightsail and AWS Batch
    3. Inside a VPC: subnets, gateways, security groups and network ACLs
    4. Route 53 and connecting networks to AWS
  8. 8.Technology: Databases & Storage0/4
    1. Relational databases: Amazon RDS, Aurora and databases on EC2
    2. NoSQL, in-memory and graph databases, plus database migration
    3. Amazon S3 object storage, storage classes and lifecycle policies
    4. Block and file storage, Storage Gateway, AWS Backup and disaster recovery
  9. 9.Technology: AI, Analytics & Other Services0/4
    1. AI and machine learning services: pre-trained services and SageMaker AI
    2. Analytics services: Glue, Athena, Redshift, EMR, OpenSearch, Kinesis and Amazon Quick
    3. Messaging and workflows: SQS, SNS, EventBridge, Step Functions, Amazon Connect and SES
    4. Developer tools, cloud desktops, AWS Amplify and AWS IoT Core
  10. 10.Billing, Pricing & Support0/4
    1. EC2 purchasing options: On-Demand, Spot, Savings Plans, Reserved Instances and dedicated hardware
    2. Data transfer costs, consolidated billing and cost allocation tags
    3. Cost management tools: Pricing Calculator, Cost Explorer, Budgets, Cost and Usage Reports and Compute Optimizer
    4. AWS Support plans, Trusted Advisor, AWS Health and where to get help
Saved in this browser. Move it to another device →
← Technology: Databases & Storage

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.

FeaturePurpose
Multi-AZ DB instance deploymentA standby in another Availability Zone takes over automatically if the primary fails; it does not serve reads
Read replicasAsynchronously updated copies that answer read-only queries and take load off the primary
SnapshotA 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 →