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

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

15.1 What RDS Is and Why Companies Use It

By Last updated:

In short: RDS (Relational Database Service) is a managed database: you choose the engine (MySQL, MariaDB, PostgreSQL and others), size and storage, and AWS runs the server for you.

RDS (Relational Database Service) is a managed database: you choose the engine (MySQL, MariaDB, PostgreSQL and others), size and storage, and AWS runs the server for you. You still connect with the normal mysql client and write the same SQL you learnt in Part 5.

Task MySQL on your own EC2 Amazon RDS MySQL
Install and OS patching You AWS
MySQL minor upgrades You AWS (maintenance window you choose)
Backups You write mysqldump + cron Automated daily backups + transaction logs
High availability You build replication Tick Multi-AZ
SSH to the database server Yes No – only the MySQL port
Root/SUPER privilege Yes No – you get a "master user" with most privileges
Schema, users, queries, security groups You Still you 
         Internet
            │  443/80
      ┌─────▼──────┐   3306 (only from app SG)   ┌──────────────────┐
      │ EC2 web/app│ ───────────────────────────►│  RDS MySQL       │
      │ public sub.│                             │  private subnets │
      └────────────┘                             │  Public access:NO│
                                                 └──────────────────┘

Why this matters for security

"Managed" does not mean "secure by default for your data". AWS secures the infrastructure; you secure who can connect, which users exist, what they can do and whether the app is vulnerable to SQL injection. This split is called the shared responsibility model (सामायिक जबाबदारी मॉडेल) and interviewers love asking about it.

Ravindra Bagale's Tip

Many students think that once they use RDS, they don't need to worry about SQL injection – AWS will handle it! No, friends. RDS patches the server, not your PHP code. Prepared statements, a least-privilege user and a private network are your own responsibility.

Practice task

From the table above, list four jobs that move to AWS with RDS and four jobs that stay with you. Explain the shared responsibility model in two sentences.

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.