Hey there! I am Karthick from TechieDrone. Hope you are all doing good ? Today I am going to show you the step by step tutorial to launch AWS RDS instances. While seeing this article, many of you might come up with the question, why AWS RDS? AWS’ relational database services has come up with in-build optimization with simple and clean user-interface to modify the RDS’ setting like master-master replica, master-slave replica, etc., Additionally it provides us point-in-recovery option which helps us to restore backups from specific date excluding to daily automated snapshots ?
Relational Database Service
Sign into your AWS account and choose RDS from services
You will see Launch DB instance button under Amazon RDS > Instances tab. Click on it to launch DB instances.
#1 Select engine
First step is to choose preferred DB engine type. It is completely based on your application / needs. Amazon web services provides six different types of DB engines (Amazon Aurora, MySQL, MariaDB, PostgreSQL, Oracle and Microsoft SQL server) under relational database services. If you’re about to choose Amazon Aurora / Oracle / Microsoft SQL server, then you should choose the edition preferences wisely based on your needs. Here in this example I have chosen MySQL as the database engine type.
Sometimes AWS provide us few recommendations based on the environment usage. Make sure to choose what you need. In my case, I have opted for MySQL engine type and it shows few other recommendations. I am sure that MySQL engine type suits me better. So I have opted in for MySQL.
#2 Specify DB details
You should provide details like DB engine version, DB instance class, Multi-AZ deployment (we’ll see this in later topic), Storage type, Allocated storage, IOPS, DB instance identifier (unique identifier to identify the DB instance), Master username, Master password, etc. In this example I have chosen db.t2.micro as DB instance class and opted No for Multi-AZ deployment. You can also compare the DB instance specifications here.
It is to be noted that DB instance identifier is a unique one which helps us to identify the DB instance. It will generate an endpoint which we will use to login the database / mention it in applications.
#3 Configure advanced settings
Advanced settings covers the topic like VPC details, Security groups, AZ, DB name, DB port, DB parameter group, option group, IAM DB authentication, Encryption, Backup retention period, Monitoring, Log exports, Maintenance window, etc.,
In this example, I am using default VPC created by AWS. If you wish to use your own customized virtual private cloud environment, then create new one as required and use it. In addition I have opted No for public accessibility (restricting pubic access will deny access outside the VPC network) and I have chosen default security group (create new one if needed)
Provide database name, port number to access, DB parameter & option group (we’ll discuss this in later topic) and I have disabled IAM DB authentication module (we’ll discuss this in later topic).
Coming to backup policies, by default AWS suggest us to use 7 days backup retention period (extend it if necessary). If you do consider about backup window, then select preference window as required and choose enhanced monitoring if needed. In this example, I have opted for no preference for backup window. Opt in for log exports / maintenance based on real time requirements.
Once the DB instances is launched, click view instance details to review the DB instance specifications.
It is to be noted that AWS Free Tier includes 750 hours of db.t2.micro instances each month for one year. To stay within the Free Tier, use only db.t2.micro instances. For more info, check AWS Official page. FYI, Amazon Aurora doesn’t supports AWS free tier programme.