Add domain names for Privacera service URLs

Note

If you have Nginx ingress enabled in your environment, then the configuration described below would not be required. For more information on Nginx ingress, see Externalize Access to Privacera Services - Nginx Ingress.

You can expose Privacera services such as Portal, Ranger, AuditServer, DataServer and PEG to be accessed externally and configure a domain name to point to them. You can use DNS service to host DNS records needed for them.

Configuration

Create a vars.service_hostname.yml file.

vi config/custom-vars/vars.service_hostname.yml

Depending on the services you want to expose, add the properties in the file. Replace <PLEASE_CHANGE> with a hostname.

PORTAL_HOST_NAME:"<PLEASE_CHANGE>"DATASERVER_HOST_NAME:"<PLEASE_CHANGE>"RANGER_HOST_NAME:"<PLEASE_CHANGE>"PEG_HOST_NAME:"<PLEASE_CHANGE>"AUDITSERVER_HOST_NAME:"<PLEASE_CHANGE>"

Create CNAME records to point them to the service load balancer URLs. If you are installing Privacera and its services for the first time, you must complete the installation and then return to this step to create CNAME records.
1. Run the following command to get the service URL. Replace <name_space> with your Kubernetes namespace.
```
kubectl get svc -n <name_space>
```
2. To create CNAME records using the service URLs, do the following:
  - For AWS, refer to Creating records by using the Amazon Route 53 console.
  - For Azure, refer to Create the CNAME record.
  - For GCP, refer to Adding a CNAME record.

Run the update.

cd ~/privacera/privacera-manager
./privacera-manager.sh update

Privacera Platform

Table of ContentsTable of Contents

Add domain names for Privacera service URLs

Note

Configuration