RDS database

Create and connect to an RDS database instance

Create, configure, and manage RDS instances directly from the DuploCloud Portal.

DuploCloud supports the following RDS databases in AWS:

MySQL PostgreSQL MariaDB Microsoft SQL-Express Microsoft SQL-We	Microsoft SQL-Standard Aurora MySQL Aurora MySQL Serverless Aurora PostgreSQL Aurora PostgreSQL Serverless

*Support for Aurora Serverless V1 database engines has been deprecated. Do not create V1 engines when using Terraform.

When upgrading RDS versions, use the AWS Console and see your Cloud Provider for compatibility requirements. Note that while versions 5.7.40, 5.7.41, and 5.7.42 cannot be upgraded to version 8.0.28, you can upgrade them to version 8.0.32 and higher.

Creating an RDS database

1. In the DuploCloud Portal, navigate to Cloud Services -> Database.

2. Click Add. The Create a RDS page displays.

The Create a RDS page in the DuploCloud Portal

1. Complete the following fields:

RDS Name	Please provide a unique identifier for the RDS instance that is unique across all Tenants.
Create from Snapshot (Optional)	Select this when you want to create RDS instance from existing Snapshot.
RDS Engine	Select Database engine for creating RDS instance.
RDS Engine Version	Select database engine version. If not selected latest version will be used while creating database. Select type as 'Other' if you don't see desired option in dropdown list.
Encryption Key (Optional)	Choose to encrypt the given instance.
RDS Instance Size	Instance size for RDS. Select type as 'Other' if you don't see desired option in dropdown list.
Backup Retention Period in Days	Specify in days for automated backups. Valid values 1-35. (Optional). If not specified, by default Backup Retention Day would be set as 1.
Availability Zone Master/Primary (Optional)	Select an Availability Zone (AZ).
Certificate Authority	Select Certificate authority.
User Name	Specify an alphanumeric string that defines the login ID for the master user.
User Password	Specify a string that defines the password for the master user. Master Password must be at least eight characters long and listed characters are accepted [a-z] [A-Z] [0-9] [- * ! $ % &].
Storage Type (Optional)	Select the Storage Type: e.g., Default, magnetic (standard), gp2, gp3, io1. Default is gp3.
Storage size in GB (Optional)	Storage allocation for RDS instance in GB.
DB Name (Optional)	Specify a name for your Database.
DB Parameter Group (Optional)	Database parameters group name.
DB Subnet Group (Optional)	Choose a DB subnet group.
Store Credentials in Secrets Manager	Enable to store RDS password in AWS Secret Manager.
Enable MultiAZ	Enable Multi Availability Zone.
Enable Logging	Select to enable logging for the RDS instance.
Enable Performance Insights	Enable Performance Insights.

1. Click Create to provision the RDS database.

Creating an Aurora Serverless V2 Cluster database

You can create Aurora Serverless V2 Databases by selecting Aurora-MySql-Serverless-V2 or Aurora-PostgreSql-Serverless-V2 from the RDS Database Engine list box. Select the RDS Engine Version compatible with Aurora Serverless v2. The RDS Instance Size of db.serverless applies to both engines.

Creating Aurora databases

Create Aurora Serverless V2 Cluster Database

You can create Aurora Serverless V2 Databases by selecting Aurora-MySQL-Serverless-V2 or Aurora-PostgreSQL-Serverless-V2 from the RDS Engine list box. Select the RDS Engine Version compatible with Aurora Serverless v2. The db.serverless RDS Instance Size applies to both engines.

Storage Type Selection for Aurora

When creating an Aurora MySQL or Aurora PostgreSQL database, you can select between two storage types:

• Aurora (standard storage type for Aurora databases).

• aurora-iopt1 (optimized for high IOPS performance and low-latency disk operations, ideal for performance-intensive applications).

Creating a publicly available RDS database

1. Create a DB subnet group in AWS consisting only of public subnets from your VPC.

2. In the DuploCloud Portal, navigate to Cloud Services -> Databases

3. Select the RDS tab, and click Add. The Create a RDS page displays.

4. In the DB Subnet Group list box select the public DB subnet group you created in AWS.

5. Complete the remaining fields according to your requirements.

6. Click Create. The publicly available RDS database is created.

To create a public RDS database, you much first create a DB subnet group in AWS consisting only of public subnets from your VPC. Then follow the steps above to create an RDS database, selecting the DB subnet group you created from the DB Subnet Group list box.

The DB subnet group created in AWS must only contain public subnets from your VPC. This configuration is crucial for making the database public.

Connecting to the database

Once you create the database, select it and use the Instances tab to view the endpoint and credentials. Use the Endpoints and credentials to connect to the database from your application running in an EC2 instance. The database is only accessible from inside the EC2 instance in the current Tenant, including the containers running within.

For databases you intend to make publicly available, ensure proper security measures, including broad accessibility, are in place to protect your data.

The Instances tab on the RDS details page

Pass the endpoint, name, and credentials to your application using environment variables for maximum security.

Updating performance insights for an existing RDS

1. In the DuploCloud Portal, navigate to Cloud Services -> Database and select the RDS tab.

2. Click on the RDS name in the NAME column.

3. From the Actions menu, select RDS Settings and then Update Performance Insights. The Update Performance Insights pane displays.

4. Select Enable Performance Insights.

5. In the Performance Insights Retention in Days field, enter a retention period (1–731 days).

6. From the Performance Insights Encryption list box, select an encryption key or select No Encryption.

7. Click Update to apply the changes.

Managing RDS Certificate Authorities

You can manage the Certificate Authority (CA) for an RDS instance when creating a new RDS database or by updating the CA for an existing database.

Choosing a Certificate Authority When Creating an RDS Database

During the RDS creation process, select a Certificate Authority from a dropdown menu.

This option ensures that the RDS instance is set up with the correct certificate authority to encrypt communications using SSL/TLS. The selected CA will validate certificates to ensure secure and trusted connections.

Updating the Certificate Authority for an Existing RDS Database

If you need to update the Certificate Authority used by an existing RDS database, you can do so through the Actions menu in the RDS instance settings:

1. Navigate to Cloud Services → Databases.

2. Select the RDS tab.

3. Select the RDS you want to modify from the NAME column.

4. From the Actions menu, choose RDS Settings.

5. Click Update Certificate Authority.

6. In the Certificate Authority list box, select the new CA to use for the instance.

7. Click Save to apply the new CA.