Deploy CENM 1.4 with AWS and PostgreSQL

You can use CENM database and services documentation to complete a reference or test deployment of CENM using AWS and PostgreSQL. The references provided here refer to in depth documentation for databases and services in CENM.

Supported deployment options

The following deployment options are supported in CENM:

  • AWS with external PostgreSQL.
  • Azure with PostgreSQL deployed in cluster.
  • Azure with external PostgreSQL.

Not supported:

  • AWS with PostgreSQL deployed in cluster.

Reference guide

To set up a reference deployment of CENM using AWS and PostgreSQL:

### Set up a PostgreSQL database for each CENM service

You must ensure that each CENM service has it’s own PostgreSQL database. Complete the steps referenced below for each of the following:

To set up each database:

  1. Set up a PostgreSQL database in AWS - follow the instructions in the AWS documentation .
  2. Connect to the database, using the details of the database in AWS.
  3. Create a database user and a schema namespace with restricted permissions . Follow the steps for PostgreSQL .
  4. Create the database schema for each service.
  5. Perform CENM Service configuration - follow the steps for PostgreSQL . See also the database configuration documentation .

Deploy CENM services

  1. Deploy the Auth Service using PostgreSQL on AWS.
  2. Deploy the Identity Manager Service using PostgreSQL on AWS.
  3. Deploy the Network Map Service using PostgreSQL on AWS.
  4. Deploy the Zone Service using PostgreSQL on AWS.
  5. Deploy the Signing Service (it does not use a database).

Was this page helpful?

Thanks for your feedback!

Chat with us

Chat with us on our #docs channel on slack. You can also join a lot of other slack channels there and have access to 1-on-1 communication with members of the R3 team and the online community.

Propose documentation improvements directly

Help us to improve the docs by contributing directly. It's simple - just fork this repository and raise a PR of your own - R3's Technical Writers will review it and apply the relevant suggestions.

We're sorry this page wasn't helpful. Let us know how we can make it better!

Chat with us

Chat with us on our #docs channel on slack. You can also join a lot of other slack channels there and have access to 1-on-1 communication with members of the R3 team and the online community.

Create an issue

Create a new GitHub issue in this repository - submit technical feedback, draw attention to a potential documentation bug, or share ideas for improvement and general feedback.

Propose documentation improvements directly

Help us to improve the docs by contributing directly. It's simple - just fork this repository and raise a PR of your own - R3's Technical Writers will review it and apply the relevant suggestions.