Skip to content

Encryption Deployment Specification

These are the minimal specifications for running Privacera Encryption in production.

Hardware#

Hardware Minimum Configuration
Number of CPUs 32
RAM 32 GB
Network bandwidth 10 Gbps

Software and Server Configuration#

These are specifications and configurations for Privacera Encryption software components.

Tomcat and Privacera Encryption Settings#

For details about copying configuration files in Privacera Manager, see Privacera Encryption Gateway (PEG) and Cryptography with Ranger KMS.

In addition to properties already defined, the following properties are set in the following variables file:

  • ~/privacera/privacera-manager/config/custom-vars/vars.peg.yml
spring.task.execution.pool.max-size=1024
server.tomcat.connection-timeout=20s
server.tomcat.max-connections=1200
server.tomcat.min-spare-threads=200
server.tomcat.accept-count=1000
privacera.peg.connectionpool=500

After setting these properties, you must update Privacera Manager. See Privacera Manager Command Line.

Operational Specifications#

These specifications relate to the operational use of Privacera Encryption.

Batch together the elements in PEG REST API requests in the datalist JSON array of the /protect or /unprotect request. For details on these requests, see Example PEG API Requests on Privacera Platform.

  • Minimum batch size: 2,000 elements per request.
  • Maximum recommended batch size: 15,000.
  • Maximum number of requestsi sent to the PEG service must not exceed 1,800 at any given time.

Note

Network latency can impact performance, so your network architecture should be optimized.


Last update: September 23, 2021