Ravindra BagaleCourses & study guides मराठी Track your progress

15. Amazon RDS for MySQL: Create, Connect, Back Up and Keep It Private

By Last updated:

Chala mitrano, Part 5 madhe aapan MySQL swatah EC2 var install kela – install, mysql_secure_installation, users, GRANT, backups sagla aaplya haatat. Companies madhe production database sathi bahutek vela Amazon RDS vapartat: AWS server chalavto, patching karto, automatic backups gheto, aani aapan fakt database vaparto. Aaj aapan RDS MySQL banvu, tyala EC2 varun connect karu, app sathi vegla user banvu, backups aani restore baghu. Aani ek niyam aadhich doktyat bhara – RDS kadhi public nako. He khup important aahe, lakshat theva.

What you will learn in this chapter

  • What RDS manages for you and what is still your job
  • Planning the network: VPC, DB subnet group and security groups
  • Creating an RDS MySQL instance step by step (console and CLI)
  • Connecting from EC2 and creating a least-privilege application user
  • Automated backups, snapshots and point-in-time restore
  • Hardening RDS: never public, encryption, TLS, deletion protection and monitoring

Concepts in this chapter

  1. 15.1What RDS Is and Why Companies Use It
  2. 15.2Planning the Network: Subnet Group and Security Groups
  3. 15.3Creating an RDS MySQL Instance Step by Step
  4. 15.4Connecting from EC2 and Creating the Application User
  5. 15.5Automated Backups, Snapshots and Restore
  6. 15.6Hardening RDS: Never Public, Encrypted, Monitored

The chapter recap is at the end of the last concept page.

Chapter 15: Amazon RDS for MySQL — practice tasks

Open chapter lessons · Full guided lab: rds private security group backups (not repeated here)

15.1 Review an RDS setup checklist (paper)

EasyBanking

Why: Public databases are a top breach cause.

What: Mark each setting Safe or Fix.

Data file: rds-settings.csv

SettingValue
Publicly accessibleYes
Backup retention0 days
Storage encryptionOn

About this file: Made-up RDS settings. Each row is one setting. Columns: Setting = name; Value = current value.

How:

  1. Read each row.
  2. Decide Safe/Fix.

Expected output: Public access Fix; backups 0 days Fix; encryption on Safe.

Hint

Database should never be public.

Answer / how to check
  1. Two Fix items.

15.2 Force TLS to MySQL

MediumIT

Why: Database traffic can be sniffed if not encrypted.

What: Require SSL for a user in Docker MySQL.

How:

  1. ALTER USER 'report'@'%' REQUIRE SSL;
  2. mysql -h127.0.0.1 -ureport -p --ssl-mode=DISABLED
  3. Then with --ssl-mode=REQUIRED.

Expected output: First fails (access denied), second works.

Hint

MySQL 8 auto-creates certs.

Answer / how to check
  1. Session status shows a Cipher in use.

15.3 Restore test of a backup

MediumLogistics

Why: A backup you never restored is not a backup.

What: Restore ship.sql into a new database.

How:

  1. CREATE DATABASE restore_test;
  2. docker exec -i db mysql -uroot -plabpass restore_test < ship.sql
  3. SELECT COUNT(*) FROM restore_test.ship;

Expected output: Same row count as lab.ship.

Hint

ship.sql from ch11 task 1.

Answer / how to check
  1. Counts match.

Extended teaching notes

Why this lesson matters

Use this lesson to strengthen systems you own: understand the risk, practise safely in a lab, then write and apply the fix.

Apply the fix across stacks

Same class of bug, same idea in every language.

Java / Spring Boot

Parameterise queries, encode output, CSRF tokens, limited Actuator, dependency scanning.

ASP.NET Core

EF Core / parameterised SQL, Razor encoding, HTTPS, Data Protection.

Node.js / Express

helmet, parameterised SQL, npm audit, avoid eval and shell concat.

Python / Django / Flask / FastAPI

ORM, autoescape, pip-audit, Bandit; never shell=True with user input.

PHP / Laravel

PDO/Eloquent, Blade escaping, composer audit.

Go / Ruby

database/sql placeholders / ActiveRecord; html/template / ERB escaping; govulncheck / Brakeman.

nginx / Apache / Tomcat

Hide versions, TLS, security headers, least-open ports.

MySQL / PostgreSQL / MongoDB / Redis

Private networks, auth on, least-privilege users, no 0.0.0.0/0.

AWS / Azure / GCP

Roles not long-lived keys, private data stores, cloud audit logs on.

Mini case study

Suppose we are on a purple-team exercise for an Indian mid-size company (sample data). Red notes a technique from this lesson against a lab clone. Blue must show the control that stops it, the log that would have fired, and the ticket that hardens production. That is the standard this course trains you for.

Defender's worksheet (do this today)

  1. Write the lesson title, date and the exact lab target you are allowed to use.
  2. List three owned systems (VMs, apps, or cloud accounts) where this lesson applies.
  3. Run one safe check from the lesson on a lab system only. Paste the command and output.
  4. Write a two-sentence fix you would give a teammate.
  5. Name one related public advisory (CERT-In, CISA, NVD, or a vendor bulletin) with its date.

Indian workplace (sample data)

Suppose we are a junior analyst at Infosys, TCS, Wipro or a fintech SOC in Bengaluru/Pune. Turn this lesson into one checklist item with an owner, a due date and a place to store evidence (ticket + screenshot).

Global practice

Compare your notes with OWASP, CIS Benchmarks, NIST CSF/IR guidance or a cloud Well-Architected security question. Write five lines on what overlaps.

Everyday analogy

Explain the risk and the fix to a family member without jargon. If they can repeat the warning, you understand it well enough to teach juniors.

Key terms

  • Control: a safeguard (patch, config, process, detection).
  • Finding: a weakness backed by evidence.
  • Remediation: the fix plus how you verified it.
  • Scope: systems you have written permission to touch.
  • Least privilege: only the access the task needs.
  • Defence in depth: several layers so one failure does not end the story.

Common mistakes

  • Skipping written permission "just for a quick scan".
  • Practising on hostel, office or public targets without authorisation.
  • Collecting tool output without writing the fix.
  • Copying attack steps onto production to "verify". Defenders verify with versions, configs and patches.
  • Publishing screenshots that contain secrets, cookies or internal hostnames.

Recap

  • Evidence, fix, owner, date.
  • Own lab only.
  • Fix > spectacle.