Infrastructure on

Preparing for Protegrity AI Team Edition

Mon, 01 Jan 0001 00:00:00 +0000

Ensure that the following prerequisites are met. If a feature is not required, skip the requirements in that section.

Infrastructure

Prerequisites for Protegrity Provisioned Cluster (PPC)

For more information, refer to Prerequisites.

Governance and Policy

Prerequisites for Protegrity Policy Manager

For more information, refer to Prerequisites.

Prerequisites for Protegrity Agent

For more information, refer to Prerequisites.

Prerequisites for Data Discovery

For more information, refer to Prerequisites.

AI Security

Prerequisites for Semantic Guardrails

For more information, refer to Prerequisites.

Configuring Authentication for Protegrity AI Team Edition

Mon, 01 Jan 0001 00:00:00 +0000

Log into My.Protegrity and obtain the necessary credentials and certificates. This portal hosts all products and features included in your Protegrity contract.

Deploy Using PCR

Use the steps provided here for deploying PPC and the features directly from the PCR.

Troubleshooting

Mon, 01 Jan 0001 00:00:00 +0000

Accessing the PPC CLI

Permission denied (publickey): Ensure you’re using the correct private key that matches the authorized_keys in the pod
Connection refused: Verify the load balancer IP and hosts file configuration
Key format issues: Ensure your private key is in the correct format (OpenSSH format for Linux/macOS, .ppk for PuTTY)

Failure of init-resiliency script

Issue: When running the init_resiliency.sh script on a fresh RHEL 10.1 system as the root user, some required tools, such as, AWS CLI, kubectl, or Helm are not detected during setup. The following error apears:

Replacing the default Certificate Authority (CA) with a Custom CA in PPC

Mon, 01 Jan 0001 00:00:00 +0000

In a PPC deployment, Envoy and other internal components rely on a CA to establish trusted TLS communication.

By default, PPC uses an internally generated CA. PPC supports replacing the default CA with a custom CA that can be preserved and reused across cluster restore or migration.

Prerequisites

Before you begin, ensure that:

You have access to the PPC Kubernetes cluster (kubectl configured).
Openssl is installed.
Cert-manager is installed.
The eclipse-issuer ClusterIssuer exists.
You have permission to create secrets in the cert-manager namespace.

Perform the following steps: