RDS supported engines in AWS - Mini Project: Build & Apply

RDS supported engines

📖 Scenario: You are setting up a cloud database service using Amazon RDS. Amazon RDS supports several database engines. You want to create a list of these supported engines and then filter them based on your project needs.

🎯 Goal: Create a list of supported RDS engines, add a filter configuration, select only the engines that are open source, and finally prepare the list for deployment.

📋 What You'll Learn

Create a list variable named rds_engines with exact engine names and their open source status.

Add a configuration variable named open_source_only set to True.

Use a list comprehension to create a new list named filtered_engines containing only open source engines from rds_engines.

Add a final variable named deployment_engines that holds the filtered_engines list.

💡 Why This Matters

🌍 Real World

Cloud architects often need to select database engines supported by cloud services like Amazon RDS. Filtering engines by license type helps in compliance and cost planning.

💼 Career

Understanding how to manage and filter cloud infrastructure options is essential for cloud engineers and architects when designing scalable and compliant systems.

1

Create the initial list of RDS engines

Create a list called rds_engines with these exact dictionaries: {'name': 'MySQL', 'open_source': True}, {'name': 'PostgreSQL', 'open_source': True}, {'name': 'Oracle', 'open_source': False}, {'name': 'SQL Server', 'open_source': False}, {'name': 'MariaDB', 'open_source': True}.

AWS

# Create the list rds_engines with the specified dictionaries
# Your code here

Hint

Use a list of dictionaries with keys 'name' and 'open_source'.

2

Add a configuration variable for filtering

Add a variable called open_source_only and set it to True.

AWS

rds_engines = [
    {'name': 'MySQL', 'open_source': True},
    {'name': 'PostgreSQL', 'open_source': True},
    {'name': 'Oracle', 'open_source': False},
    {'name': 'SQL Server', 'open_source': False},
    {'name': 'MariaDB', 'open_source': True}
]
# Add the open_source_only variable below
# Your code here

Hint

Just assign True to the variable named open_source_only.

3

Filter the list for open source engines

Use a list comprehension to create a list called filtered_engines that includes only the engines from rds_engines where the 'open_source' key is True.

AWS

rds_engines = [
    {'name': 'MySQL', 'open_source': True},
    {'name': 'PostgreSQL', 'open_source': True},
    {'name': 'Oracle', 'open_source': False},
    {'name': 'SQL Server', 'open_source': False},
    {'name': 'MariaDB', 'open_source': True}
]
open_source_only = True
# Create filtered_engines using list comprehension below
# Your code here

Hint

Use a list comprehension with a condition checking engine['open_source'].

4

Prepare the final deployment list

Create a variable called deployment_engines and assign it the value of filtered_engines.

AWS

rds_engines = [
    {'name': 'MySQL', 'open_source': True},
    {'name': 'PostgreSQL', 'open_source': True},
    {'name': 'Oracle', 'open_source': False},
    {'name': 'SQL Server', 'open_source': False},
    {'name': 'MariaDB', 'open_source': True}
]
open_source_only = True
filtered_engines = [engine for engine in rds_engines if engine['open_source'] == True]
# Assign deployment_engines to filtered_engines below
# Your code here

Hint

Just assign filtered_engines to deployment_engines.

Practice

1. Which of the following database engines is supported by AWS RDS?

easy

A. MySQL

B. MongoDB

C. Cassandra

D. Redis

Solution

1. Step 1: Recall AWS RDS supported engines

   AWS RDS supports popular relational database engines like MySQL, PostgreSQL, Oracle, SQL Server, and Aurora.

2. Step 2: Identify which option matches supported engines

   Among the options, only MySQL is a supported RDS engine. MongoDB, Cassandra, and Redis are not supported by RDS but by other AWS services.

3. Final Answer:

   MySQL -> Option A

4. Quick Check:

   RDS supports MySQL = A [OK]

Hint: Remember RDS supports relational engines like MySQL, not NoSQL [OK]

Common Mistakes:

• Confusing NoSQL databases as RDS engines
• Assuming Redis is supported by RDS
• Thinking Cassandra is supported by RDS

2. Which of the following is the correct way to specify the engine when creating an RDS instance using AWS CLI?

easy

A. --engine mongodb

B. --engine mysql

C. --engine redis

D. --engine cassandra

Solution

1. Step 1: Understand AWS CLI engine parameter

   The AWS CLI uses the parameter --engine to specify the database engine when creating an RDS instance.

2. Step 2: Identify valid engine names

   Valid engine names include mysql, postgres, oracle, sqlserver, aurora. MongoDB, Redis, and Cassandra are not valid for RDS engine parameter.

3. Final Answer:

   --engine mysql -> Option B

4. Quick Check:

   Correct engine name for MySQL is mysql [OK]

Hint: Use lowercase engine names like mysql, not unsupported ones [OK]

Common Mistakes:

• Using unsupported engines like mongodb or redis
• Capitalizing engine names incorrectly
• Confusing engine parameter with instance type

3. Given the following AWS CLI command to create an RDS instance:

aws rds create-db-instance --db-instance-identifier mydb --engine postgres --allocated-storage 20 --db-instance-class db.t3.micro --master-username admin --master-user-password secret123

What database engine will this RDS instance use?

medium

A. SQL Server

B. MySQL

C. Oracle

D. PostgreSQL

Solution

1. Step 1: Analyze the --engine parameter in the command

   The command specifies --engine postgres, which corresponds to PostgreSQL.

2. Step 2: Match engine parameter to database engine

   Postgres is the short name for PostgreSQL, a supported RDS engine.

3. Final Answer:

   PostgreSQL -> Option D

4. Quick Check:

   --engine postgres means PostgreSQL [OK]

Hint: Look for --engine value to identify the database engine [OK]

Common Mistakes:

• Confusing postgres with MySQL
• Assuming default engine is MySQL
• Ignoring the --engine parameter

4. You tried to create an RDS instance with the command:

aws rds create-db-instance --db-instance-identifier testdb --engine mongo --allocated-storage 20 --db-instance-class db.t3.micro --master-username admin --master-user-password secret123

But it failed. What is the most likely reason?

medium

A. The master username is missing

B. The allocated storage is too low

C. The engine name 'mongo' is not supported by RDS

D. The instance class db.t3.micro is invalid

Solution

1. Step 1: Check the engine parameter validity

   The engine parameter is set to 'mongo', which is not a supported RDS engine. MongoDB is not supported by RDS.

2. Step 2: Verify other parameters

   Allocated storage of 20 GB and instance class db.t3.micro are valid. Master username is provided.

3. Final Answer:

   The engine name 'mongo' is not supported by RDS -> Option C

4. Quick Check:

   Unsupported engine name causes failure [OK]

Hint: Check engine names carefully; unsupported names cause errors [OK]

Common Mistakes:

• Assuming MongoDB is supported by RDS
• Blaming storage size or instance class incorrectly
• Overlooking the exact error message

5. You want to migrate an on-premises Oracle database to AWS RDS. Which RDS engine should you choose to ensure compatibility and minimal changes?

hard

A. Oracle

B. PostgreSQL

C. Aurora MySQL

D. SQL Server

Solution

1. Step 1: Identify the source database engine

   The source is an on-premises Oracle database, so compatibility is key.

2. Step 2: Choose the matching RDS engine

   AWS RDS supports Oracle as a managed engine, which ensures compatibility and minimal changes during migration.

3. Step 3: Consider other options

   Aurora MySQL, PostgreSQL, and SQL Server are different engines and would require significant changes.

4. Final Answer:

   Oracle -> Option A

5. Quick Check:

   Match source engine to RDS engine for smooth migration [OK]

Hint: Pick the same engine type for easy migration [OK]

Common Mistakes:

• Choosing Aurora MySQL for Oracle migration
• Assuming PostgreSQL is compatible with Oracle
• Ignoring migration compatibility