6.67 Management console AWS

In this lab we create our first RDS database from the AWS Management Console. Open the RDS service and click Create database. AWS offers two creation methods: Easy create with best-practice defaults, and Standard create which exposes every option. We use Standard to see all settings. RDS supports several engines: Amazon Aurora, MySQL, MariaDB, PostgreSQL, Oracle, and Microsoft SQL Server. For this lab we pick MySQL Community 8.0.

Configuration steps

  • Template: Free tier, to stay within the AWS free usage program.
  • Credentials: choose a master user (e.g. christian) and a password.
  • Instance class: db.t2.micro — the only free-tier eligible option.
  • Storage: gp2 SSD, 20 GB, no auto-scaling for this lab.
  • Multi-AZ: disabled (not available on free tier).
  • Network: default VPC, Publicly accessible: Yes (only for the lab), default security group.
  • Database port: 3306 for MySQL.
  • Authentication: password authentication (could be combined with IAM or Kerberos).
  • Backups: enabled, 7-day retention by default.

Click Create database. Provisioning takes several minutes. Meanwhile, install MySQL Workbench on your laptop (free, multi-platform) to test the connection. Once RDS shows the database as Available, copy the endpoint and port displayed in the console, open Workbench, add a new connection with hostname = endpoint, port = 3306, user = christian, password = your password, and test the connection.

If everything is configured correctly, the connection succeeds and you can run SQL queries from Workbench. A simple SHOW DATABASES; lists the default schemas (information_schema, mysql, performance_schema, etc.). From the RDS console you can now stop, reboot, take snapshots and restore to a point in time on this MySQL instance. You have a managed MySQL database up and running on AWS in under 15 minutes.

Summary

This lesson covers the fundamental steps to create and configure an AWS RDS (Relational Database Service) database instance using the AWS Management Console. You will learn how to navigate the RDS interface, select database engines like MySQL, configure instance types and storage options, set up authentication credentials, and manage connectivity and security settings. The lesson focuses on using the free tier offering to understand core RDS configuration principles within AWS's free tier constraints.

Key points

  • Access the RDS service from the AWS Management Console to create a new database instance with guided or advanced creation methods
  • Choose from multiple database engines (MySQL, MariaDB, PostgreSQL, Oracle, SQL Server) and select supported versions, with MySQL 8.0.17 shown as a stable option
  • Select your deployment model (production, development, test, or free tier) which determines available instance types and features
  • Configure essential parameters including database credentials (username and password), instance type (t2 micro in free tier), and storage type (SSD GP2 by default)
  • Enable public accessibility to allow database access from outside your VPC (required for lab demonstrations but not recommended for production)
  • Configure database connectivity through VPC, security groups, and port settings (default port 3306 for MySQL) to control network access

FAQ

What are the main database engine options available in AWS RDS?

AWS RDS supports multiple database engines including MySQL, MariaDB, PostgreSQL, Oracle, and Microsoft SQL Server. Amazon also offers Aurora, which is Amazon's proprietary high-performance database engine. The choice depends on your application requirements and compatibility needs.

How does the AWS free tier affect RDS instance configuration?

The AWS free tier limits your RDS instance to the t2.micro instance type and includes 20 GB of storage with General Purpose (GP2) SSD. Multi-AZ deployment and other advanced features are not available in the free tier, so you must select compatible options during configuration.

Why should public accessibility be carefully managed for an RDS database?

Enabling public accessibility allows anyone on the internet to attempt connecting to your database, which poses significant security risks. It should only be enabled for development and learning purposes. For production, databases should be accessible only from resources within your VPC or through restricted security group rules.