Associating Cloudera Manager peer to use in Iceberg replication policy

Communication between the source and target clusters during an Iceberg replication policy run is accomplished through a Cloudera Manager peer. By default, during the Iceberg replication policy creation process, the Cloudera Manager peer is created automatically if the source and target environment names are unique within the first eight characters. However, if that is not the case, you must manually associate the Cloudera Manager peer using Cloudera Manager API explorer.

You must obtain the following details to associate a Cloudera Manager peer:

The IP address of the Cloudera Manager host. You can find this on the source Iceberg Replication Data Hub.
The name and workload password of a Cloudera Manager user with the Administrator role. You can find these credentials on the Cloudera Management Console > User Management page.

Go to the of the target Iceberg Replication Data Hub.
On the left pane, click Support > API Explorer.
Go to the CmPeersResource > POST /cm/peers API.

Click Try it out, and enter the following payload details:

{
  "name": "[***PEER NAME TO BE USED DURING POLICY CREATION ***]",
  "type": "REPLICATION",
  "url": "[*** IP ADDRESS OF SOURCE ICEBERG REPLICATION DATA HUB. For example, https://10.85.219.54:7183 ***]",
  "username": "[*** WORKLOAD USER with ADMINISTRATOR ROLE ***]",
  "password": "[*** PASSWORD FOR THE AFOREMENTIONED WORKLOAD USER ***]"
}

Click Execute.

Verify that the API returns the 200 response code.

Example

Response code : 200
{
  "name": "Cldr1",
  "type": "REPLICATION",
  "url": "https://10.85.219.54:7183",
  "clouderaManagerCreatedUser": true
}

If the provided credentials are incorrect, the API returns a 400 response code.

Example

Response code : 400 
{
  "message": "Provided credential is not able to connect to Cloudera Manager at https://10.85.219.54:7183."
}

Continue configuring IAM role access for Iceberg replication.