Configuring an AWS Database
To setup the CloudCenter database to be an RDS instance, you must configure an AWS database as identified in this section.
Be sure to configure the following dependencies before starting the HA configuration procedure.
The required IAM policies – see IAM Role for additional context.(this page) > IAM and STS for additional context. Verify that the IAM policy and role has been used and has worked prior to starting this procedure. See
The roles and modes for the components used in your environment – see.
This procedure assumes that you are using:
Hardware Requirements as specified
If the PostgreSQL RDS master instance fails, the PostgreSQL RDS replica instance remains in read-only mode
After this switch, you must configure the CCM server by invoking the config wizard and provide the new master details. See Configure CCM Wizard Properties > DB > IP or Hostname row in the table.
Read replicas are used to ensure a healthy replica set of the database at all times – in case the RDS crashes at any point.
Manual CCM wizard changes are required when you have read replicas, but are not required for Multi-AZ.
You can define additional deployment parameters by name (vpcId and dbSubnetGroup) for the RDS service and pass the values for the VPC ID and DB Subnet Group at deployment time. The CloudCenter platform uses these values while provisioning the RDS instance. See Services > PaaS Support for additional context.
Process to Create cliqrdb
Here you create cliqrdb as part of the setup and provide the hostname in the CCM.
This procedure may differ based on your AWS version and is intended to provide a point of reference.
Launch a RDS database Instance and select the PostgreSQL Engine.
Access your AWS RDS console.
Launch a database instance.
Select the PostgreSQL Engine.
Select PostgreSQL with Multi-AZ Deployment, and click on Next Step.
Provide the following values along with the pre-populated values:
DB Instance Identifier – A unique name to identify the AWS database instance account.
Master Username – cliqr (The username for this account – you must use cliqr for this field)
Master Password – The password for this account (8 characters, case insensitive).
Confirm Password – Repeat the master password.
Configure the Advanced Settings for the cliqrdb configuration:
Change the Backup, Monitoring & Maintenance configuration based on your usage requirements.
Select the VPC Security Group(s) to allow Port 5432 and ensure Database connection.
In the Database Name field, enter cliqrdb.
Click Launch DB Instance.
You have now launched the database instance. The RDS instance takes some time to come up as it involves creating, modifying > backing-up process on the backend.
Once the instance is up and available, view the cliqrdb instance using the PSQL remote host command. Here is a sample command:
Launch an instance for CCM, download the installer artifacts, and run the core_installer.
To install DB in remote host, change the ccm-response.xml for CCM and provide the RDS canonical name for the following items and run the appliance installer:
db_host = the remote host name
db_user = cliqr
db_pass = the password used to launch the RDS instance
Configure the RDS instance.
HA – Multi-AZ Option
For High Availability, launch the RDS instance using the Multi-AZ option – When you provision a Multi-AZ DB instance, Amazon RDS automatically creates a primary DB instance and synchronously replicates the data to a standby instance in a different Availability Zone (AZ).
In case of an infrastructure failure, Amazon RDS performs an automatic failover to the standby database instance. Since the endpoint for the CloudCenter database instance remains the same after a failover, the database operation resumes without the need for manual administrative intervention.
You can also Create read replica for the instances launched with/without the Multi-AZ option as seen in the following image.
Process to Create and Connect to the Replica DB Instance
Create the read replica of the master RDS instance by providing the required details.
DB Instance Identifier – The master RDS instance
Destination Region – Within the same region or a different region
Availability Zone – Any availability zone
Click Create Read Replica to launch the replica.
Once launched, the instances are displayed on the RDS console with the replication role master and replica.
Connect to the replica instance, and verify that the data is synchronized.
Approaches to Configure an AWS capacitydb
To configure an AWS capacitydb for the CloudCenter platform, you have the following options:
Create a separate Database
Create capacitydb as part of the cliqrdb database.
Configure a Combined Database
Use cliqrdb for capacity management as well
Approach 1: Create a Separate Database for capacitydb
To create a separate database for capacitydb after the RDS instance is up and running with the cliqrdb and before you access the CCM server.
Access the RDS instance by remotely logging into the cliqrdb database.
Create another database called capacitydb.
Restart the Management server so it can access the capacitydb.
Approach 2: Create a Combined Database
Edit the file /etc/sysconfig/capacity-manager.conf file and add the following entry to use the same cliqrdb to generate the capacity-manager database's related tables without explicitly creating a separate capacitydb – perform this step after the RDS instance is up and running with the cliqrdb and before you access the CCM server.
Back to Database (Required)