Running a database on your own server means installing it, patching it, taking backups and recovering when the disk fails. Amazon RDS (Relational Database Service) does most of that for you, which is why it is the default choice for databases in many AWS projects.
What RDS manages
- Installing and patching the database engine (MySQL, PostgreSQL, MariaDB, SQL Server, Oracle, or Amazon Aurora).
- Automated daily backups and point-in-time restore.
- Monitoring, with metrics in CloudWatch.
- Optional standby copies and read replicas.
You still design tables, write queries and manage users inside the database.
Key settings when you create one
- Instance class: the CPU and memory size. Start small; you can resize later.
- Storage: general-purpose SSD is fine for most apps; enable storage autoscaling.
- Public access: keep it off. The database should sit in private subnets.
- Security group: allow the database port (3306 for MySQL) only from your application’s security group.
- Backups: set a retention period, such as 7 days.
Multi-AZ vs read replicas
- Multi-AZ keeps a standby copy in another Availability Zone and fails over automatically. It is for availability, not extra speed.
- Read replicas are extra copies that serve read queries. They are for performance when reads are heavy.
Interviewers often ask for exactly this difference.
Connecting from your app
RDS gives you an endpoint hostname. Your app on EC2 or in a container connects to it like any MySQL server. Store the password in AWS Secrets Manager or an environment variable, never in your code.
Cost tips for learners
Use a free-tier eligible instance, turn off Multi-AZ while practising, and stop or delete test databases when you finish.
Related: AWS VPC basics, AWS EC2 for beginners and MySQL basics.
Hands-on labs like this are part of our AWS and DevOps course in Bangalore.
Book a free demo class at our BTM Layout centre, and ask a counsellor for batch details.
