Lab Information
The Nautilus Development Team is working on a new application feature that requires a reliable and scalable database solution. To facilitate development and testing, they need a new private RDS instance. This instance will be used to store critical application data and must be provisioned using the AWS free tier to minimize costs during the initial development phase. The team has chosen MySQL as the database engine due to its compatibility with their existing systems. The DevOps team has been tasked with setting up this RDS instance, ensuring that it is correctly configured and available for use by the development team.
As a member of the Nautilus DevOps Team, your task is to perform the following:
Provision a Private RDS Instance: Create a new private RDS instance named nautilus-rds using a sandbox template, further it must be a db.t3.micro type instance.
Engine Configuration: Use the MySQL engine with version 8.4.x.
Enable Storage Autoscaling: Enable storage autoscaling and set the threshold value to 50GB. Keep the rest of the configurations as default.
Instance Availability: Ensure the instance is in the available state before submitting this task.
Lab Solutions
🧭 STEP-BY-STEP SOLUTION (AWS Console)
🔹 Step 1: Open RDS Console
Go to AWS Console → RDS
Click Create database
🔹 Step 2: Choose Database Creation Method
Select Full Configuration
(Do not choose Easy create)
🔹 Step 3: Engine Configuration
Engine type: MySQL
Engine version: MySQL 8.4.x
(Choose the latest 8.4 option available)
✔ This satisfies the engine requirement.
🔹 Step 4: Templates
Select Sandbox
(I choose dev/test)
🔹 Step 5: DB Instance Settings
DB instance identifier:
nautilus-rds
Credentials:
Username: keep default (e.g., admin)
Password: auto-generate or set manually (either is fine for the lab)
🔹 Step 6: Instance Configuration
DB instance class:
db.t3.micro
✔ Free-tier eligible and required by lab.
🔹 Step 7: Storage Configuration
Keep default storage type
✅ Enable storage autoscaling
Maximum storage threshold:
50 GB
⚠️ This value is mandatory — do not skip it.
🔹 Step 8: Connectivity (PRIVATE is critical)
VPC: Default or existing (keep default)
Public access:
❌ No (must be private)
Subnet group: Default
Security group: Default (or existing)
✔ This ensures the RDS is private, as required.
🔹 Step 9: Additional Configuration
Leave all other settings as default
No backups / monitoring changes needed unless already enabled by template
🔹 Step 10: Create Database
Click Create database
⏳ WAIT FOR AVAILABILITY (VERY IMPORTANT)
Go to RDS → Databases
Select nautilus-rds
Wait until Status = Available
⏱ This may take 5–10 minutes
🚫 Do NOT submit while status is:
Creating
Modifying
Backing-up