RDS supported engines in AWS - Step-by-Step Execution

Process Flow - RDS supported engines

Start: Choose RDS

↓

Select Engine Type

↓

Configure Instance

↓

Launch Database Instance

↓

Database Ready to Use

This flow shows how you pick an RDS engine type, configure it, and launch a database instance.

Execution Sample

AWS

Choose engine: MySQL
Configure instance size
Launch instance
Connect to database

This sequence shows selecting an engine, setting up, launching, and connecting to an RDS database.

Process Table

Step	Action	Engine Selected	Instance Configured	Result
1	Select engine type	MySQL	No	Engine MySQL selected
2	Configure instance	MySQL	db.t3.medium	Instance configured with db.t3.medium
3	Launch instance	MySQL	db.t3.medium	Instance launched and initializing
4	Instance ready	MySQL	db.t3.medium	Database instance available for connections
5	Connect to database	MySQL	db.t3.medium	Connection successful

💡 Database instance is ready and connected, process complete

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	Final
Engine	None	MySQL	MySQL	MySQL	MySQL	MySQL
InstanceType	None	None	db.t3.medium	db.t3.medium	db.t3.medium	db.t3.medium
InstanceState	None	None	None	Launching	Available	Available
ConnectionStatus	Disconnected	Disconnected	Disconnected	Disconnected	Disconnected	Connected

Key Moments - 3 Insights

Why do we select the engine type before configuring the instance?

Because the engine type determines the database software and features, which affect configuration options. See execution_table step 1 and 2.

What does 'InstanceState' mean in the variable tracker?

'InstanceState' shows the current status of the database instance, like launching or available. It changes from None to Launching to Available as seen in steps 3 and 4.

Why is connection only successful after the instance is available?

Because the database must be fully initialized and ready before accepting connections, shown in execution_table step 4 and 5.

Visual Quiz - 3 Questions

Look at the execution_table, what is the Engine Selected at step 2?

A Oracle

B PostgreSQL

C MySQL

D Aurora

💡 Hint

Check the 'Engine Selected' column at step 2 in the execution_table.

At which step does the InstanceState change to 'Available'?

A Step 2

B Step 4

C Step 3

D Step 5

💡 Hint

Look at the 'InstanceState' variable in variable_tracker after each step.

If you change the engine to PostgreSQL at step 1, what changes in the execution_table?

A Engine Selected changes to PostgreSQL

B InstanceType changes automatically

C ConnectionStatus changes to Connected immediately

D InstanceState skips Launching

💡 Hint

Only the 'Engine Selected' value changes at step 1; other steps remain the same.

Concept Snapshot

RDS supports multiple database engines:
MySQL, PostgreSQL, Oracle, SQL Server, MariaDB, Aurora.
Choose engine first, then configure instance.
Launch instance to create database.
Connect after instance is available.

Full Transcript

This visual execution shows how to select and launch an AWS RDS database instance with a supported engine. First, you pick the engine type like MySQL. Then you configure the instance size. Next, you launch the instance which starts initializing. When the instance state changes to available, the database is ready. Finally, you connect to the database successfully. Variables like Engine, InstanceType, InstanceState, and ConnectionStatus change step-by-step to show progress. Key moments clarify why engine selection comes first, what instance state means, and why connection waits until ready. Quiz questions check understanding of engine choice, instance state timing, and effects of changing engine.