Privacera Manager provides a framework, process, installation components, configuration scripts, and property files for deploying, installing, and managing the deployment of all other Privacera components to target environments. Working within the Privacera Manager framework, you identify Privacera Platform components to be installed, configure those components by editing the properties files, and then invoking Privacera Manager.
The general process for Privacera Manager is very similar for AWS and Azure, but is adjusted for each. The first step is to let Privacera Manager know the Cloud platform it is operating in.
Privacera Manager itself is deployed using Docker with Docker Compose. Once Privacera Manager is in place, it then runs and deploys Privacera Platform components either as Docker containers or within a Kubernetes cluster, so the second step is to select a preferred deployment. The choice will depend on your deployment objectives, target cloud platform and data repository types, and specific Privacera components. After selecting your cloud platform, the second step is to select a deployment:
- Docker/Docker Compose will be the right choice for smaller 'single-node' configurations. A single-node, Docker deployed Privacera Platform uses fewer resources, but may not scale as well.
- A Kubernetes deployed Privacera Platform may use more resources but will scale, taking advantage of Kubernetes' ability to expand and add computation, memory, and storage resources, as needed.
In addition to the 'core' functions: Access Management, Discovery, and Encryption, there are integration options for data repository systems, authentication integration options (AD/LDAP), optional SSO, security options, and audit logging options. Privacera Manager provides individual configuration files to support each of these options.
This document will help you select the method and the correct components for your environment.