Cloudera Docs

Setting up DNS overrides

If your private DNS is disabled, you need to set up the DNS manually, adding the specified DNS entries for the respective service component.

In the example below, a private hosted zone named cloudera.com is created for the VPC, and an alias record with Route traffic to the Cluster Connectivity Manager v2 VPC endpoint is created.
  1. Create private hosted zones in Amazon Route 53 with the names below for the VPC endpoint region.
    The following example shows how the endpoints should look like if the Cloudera Control Plane region us-west-1.
    Service component Endpoint
    API us-west-1.cdp.cloudera.com
    CCMV2 v2.us-west-1.ccm.cdp.cloudera.com
    DBUSAPI us-west-1.sigma.altus.cloudera.com
    CONSOLEAUTH us-west-1.cdp.cloudera.com
    MONITORING api.monitoring.us-west-1.cdp.cloudera.com
  2. Create a DNS record in Amazon Route 53 for each of the private hosted zones created in the previous step. You also need to add an alias record and route traffic to the respective endpoint.
    1. For the API endpoint: *.us-west-1.cdp.cloudera.com
    2. For the CCMV2 endpoint: *.v2.us-west-1.ccm.cdp.cloudera.com
    3. For the DBUSAPI endpoint: dbusapi.us-west-1.sigma.altus.cloudera.com
    The following is an example record routing traffic to the endpoint: