Key points

• RDS provides managed relational database engines for transactional sources and targets.
• Connection limits, locks, indexes, transactions, and source-load effects matter when pipelines read or write the database.

Best-known use cases

• Host relational operational data used as a pipeline source or target.
• Preserve transactions and constraints for structured application records.

What candidates often confuse it with

• RDS is for relational transactions; Redshift is the analytical warehouse and DynamoDB is the modeled key-access alternative.

Key takeaway

Choose RDS when the workload requires a supported relational engine and transactional constraints.

Relevant exam tasks

• D1.1 — Task 1.1: Perform data ingestion
• 1.1.9 — Implement throttling and overcoming rate limits (for example, DynamoDB, Amazon RDS, Kinesis).
• D2.1 — Task 2.1: Choose a data store
• 2.1.1 — Implement the appropriate storage services for specific cost and performance requirements (for example, Amazon Redshift, Amazon EMR, AWS Lake Formation, Amazon RDS, Amazon DynamoDB, Amazon Kinesis Data Streams, Amazon Managed Streaming for Apache Kafka [Amazon MSK]).
• 2.1.2 — Configure the appropriate storage services for specific access patterns and requirements (for example, Amazon Redshift, Amazon EMR, Lake Formation, Amazon RDS, DynamoDB).
• 2.1.6 — Manage locks to prevent access to data (for example, Amazon Redshift, Amazon RDS).

Learn more

• DEA-C01 in-scope services
• DEA-C01 Domain 1: Data Ingestion and Transformation
• DEA-C01 Domain 2: Data Store Management