Installing and configuring databases

Configure external databases using FIPS-compliant JDBC drivers and Bouncy Castle FIPS Keystore (BCFKS) formats to establish secure TLS connections across cluster components.

Configure the database to meet FIPS requirements by following the guidelines provided by your database vendor.
Enable TLS/SSL client support on your database, to maintain FIPS compliance for all Java Database Connectivity (JDBC) connections. For details, refer to your databse vendor documentation.
Set up the JDBC Driver with TLS/SSL and Bouncy Castle FIPS Keystore (BCFKS) to comply with FIPS standards. For additional details, see Configuring SSL/TLS from the various CDH Services to their respective PostgreSQL Databases.
Complete all the database configurations to ensure that they are fully prepared for integration with Cloudera Runtime and Cloudera Manager components. For instaructions, see Install and Configure PostgreSQL for Cloudera.

note
On FIPS-enabled clusters running Cloudera Runtime 7.1.9 SP1 or higher versions or higher versions, if Cloudera Data Explorer (Hue) uses PostgreSQL as the backend database, you must manually install the psycopg2 package (version 2.9.5 or higher) from source on all Hue hosts. The standard psycopg2-binary package includes its own libssl library, that is not FIPS-compliant. For instructions, see Installing the psycopg2 Python package for PostgreSQL database on a FIPS cluster (RHEL 8).
Start the Cloudera Manager instance and run the following command to start the server:
```
sudo systemctl start cloudera-scm-server
```

Configure the Spark Cluster