CloudCenter 4.8 has reached End of Life (EOL) as of November 14, 2018. See End of Support Notices for additional context.

Configuring HA for PostgreSQL Database on AWS

Prerequisites

Be sure to configure the following dependencies before starting the HA configuration procedure.

  • The required IAM policies – see AWS Configurations (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.

  • The roles and modes for the components used in your environment – see Virtual Appliance Overview > Modes and Roles.

    • CloudCenter 4.8 supports the RDS setup for NON_HA, HA, and NON_HA_SA modes.

    • The HA modes and roles for each component are identified in teal.

  • This procedure assumes that you are using:

    • The CloudCenter 4.8.0 installer with RDS service for CCM Non-HA Standalone or CCM HA.

    • Hardware Requirements of 2 CPU, 4GB memory, 50GB storage

    • If the PostgreSQL RDS master instance fails, the PostgreSQL RDS replica instance will:

      • Become the master in about 5 minutes
        and

      • Be 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.

Process

This procedure may differ based on your AWS version and is intended to provide a point of reference if you choose to configure HA for the PostgreSQL database.

To configure HA for a PostgreSQL database setup on AWS, follow this procedure.

  1. Launch a RDS database Instance and select the PostgreSQL Engine.

    1. Access your AWS RDS console.

    2. Launch a database instance.

    3. Select the PostgreSQL Engine.

    4. Select PostgreSQL with Multi-AZ Deployment, and click on Next Step.

    5. Provide the following values along with the pre-populated value:

      1. DB Instance Identifier – A unique name to identify the AWS database instance account.

      2. Master Username – cliqr (The username for this account – you must use cliqr for this field)

      3. Master Password – The password for this account (8 characters, case insensitive).

      4. Confirm Password – Repeat the master password.

    6. Configure the Advanced Settings:

      1. Change the Backup, Monitoring & Maintenance configuration based on your usage requirements.

      2. Select the VPC Security Group(s) to allow Port 5432 and ensure Database connection.

      3. In the Database Name field, enter cliqrdb.

      4. 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.

  2. Once the instance is up and available, view the cliqrdb instance using the PSQL remote host command. Here is a sample command:

    Sample Command
    psql -h cliqrdb.crogmzfclrjz.eu-west-1.rds.amazonaws.com -U cliqr -d cliqrdb


  3. Launch an instance for CCM, download the installer artifacts, and run the core_installer.

  4. 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:

    1. db_host = the remote host name

    2. db_user = cliqr 

    3. db_pass = the password used to launch the RDS instance

  5. Configure HA for the RDS instance.

    1. Select the RDS instance and choose Create Read Replica from the Instance Actions.

    2. Create the read replica of the master RDS instance by providing the required details.

      1. DB Instance Identifier – The master RDS instance

      2. Destination Region –  Within the same region or a different region

      3. Availability Zone – Any availability zone

    3. Click Create Read Replica to launch the replica.

    4. Once launched, the instances are displayed on the RDS console with the replication role master and replica.

    5. Connect to the replica instance, and verify that the data is synchronized.


Back to CCM (Required)

© 2017-2019 Cisco Systems, Inc. All rights reserved