Register a cluster in DPS Platform

You must register Ambari-managed clusters with DPS Platform. You must register clusters with DPS before you can view or manage data on the clusters, or before you can enable the clusters for use with any DPS service.

	Caution
	After you register a cluster in DPS Platform, do not change the cluster name in Ambari. A cluster name change in Ambari does not currently propagate to DPS Platform. Therefore, jobs associated with that cluster name will fail, and datasets associated with that cluster name are not discoverable in the DPS services.

You must be logged in using the DataPlane Admin (DPS Admin) role with valid LDAP credentials, to perform this task.
If your clusters are configured for Knox Gateway and using a self-signed SSL certificate, you must have uploaded your certificate to DPS prior to starting this task (or you can disable certificate validation on registration). Refer to “Upload a certificate to DPS” for more information.
Clusters must have been created using Apache Ambari.
Clusters that are not managed by Ambari cannot be accessed by DPS Platform or associated services.
All clusters must meet the requirements identified in DPS Getting Started.

In the DPS Platform navigation pane, click the (Clusters) icon.
Click Add Cluster.
(Optional) Check Ambari and Cluster Services Behind Knox Gateway only if you are using Knox Gateway to proxy Ambari and DPS services.
(Optional) Check Validate the SSL certificate and only allow trusted connections only if your cluster is SSL-enabled.
DPS validates the existing SSL certificate.
If you plan to validate the SSL certificate but the certificate is self-signed, be sure to upload the certificate to DPS. Refer to “Upload a certificate to DPS” for more information.

Enter the URL of the Ambari host that manages the cluster.

If the cluster is behind a Knox Gateway, use the following format:
```
https://knox_host_fqdn:knox_port/gateway_name/dp-proxy/ambari
```
By default, the gateway_name is gateway.
If the cluster is not using Knox Gateway, use the following format:
```
https://ambari_host_fqdn:ambari_port/
```
You can use HTTP or HTTPS. HTTPS is used if Wire Encryption is enabled for Ambari.

You can also enter the IP address instead of the FQDN, but the FQDN is recommended.

The host name must either be in a DNS server or configured in the etc/hosts file.

	Important
DPS Platform host must be able to resolve and reach the Ambari URL, whether you are using the FQDN or the IP address. That is, you should be able to use curl or wget to access the Ambari URL from the DPS Platform host. If this requirement is not met, cluster registration fails. If host names are resolved from /etc/hosts, you should explicitly register the cluster host names on the DPS container before the cluster is registered with DPS.

Important

DPS Platform host must be able to resolve and reach the Ambari URL, whether you are using the FQDN or the IP address. That is, you should be able to use curl or wget to access the Ambari URL from the DPS Platform host. If this requirement is not met, cluster registration fails.

If host names are resolved from /etc/hosts, you should explicitly register the cluster host names on the DPS container before the cluster is registered with DPS.

Click Go.
The cluster name, IP address, and enabled HDP services display, similar to the following:
If the cluster is designated a data lake, add the following cluster details:
- Cluster Location
- Data Center
- Tags (optional)
- Description (optional)

You can now enable the registered cluster for the DPS App you want to use it with.