Protegrity Provisioned Cluster on

Upgrading the PPC

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

Before you begin

Before starting an upgrade, ensure the following conditions are met:

Access to the jump box associated with the PPC v1.0.0 cluster is required. This must be the same jump box used during the PPC v1.0.0 installation.
Ensure that the correct cluster is set before performing the upgrade operation, using the following command.
```
kubectl config current-context
```

Note: Before running the bootstrap or resiliency scripts as the root user on RHEL, ensure that /usr/local/bin, and the AWS CLI binary path, if applicable, is included in the $PATH. Alternatively, run the script using a non-root user, such as ec2-user where /usr/local/bin is already part of the default $PATH.

Accessing PPC using a Linux machine

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

Before you begin

Ensure that the following prerequisites are met.

A Linux machine is available and running.
AWS CLI is installed and configured.
Kubernetes command-line tool is installed.

Perform the following steps to access PPC using a separate Linux machine.

Log in to Linux machine with root credentials.
Configure AWS credentials, using the following command.
```
aws configure
```
Verify that AWS credentials are working, using the following command.
```
aws sts get-caller-identity
```
If the Kubernetes command-line tool is not available, then install the Kubernetes command-line tool, using the following command.

Installing Features and Protectors

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

Before you begin

Ensure that PPC is successfully installed before installing the features or protectors.

Installing Features

The following table lists the available features.

Feature	Description
Data Discovery	Installing Data Discovery
Semantic Guardrails	Installing Semantic Guardrails
Protegrity Agent	Installing Protegrity Agent
Anonymization	Installing Anonymization
Synthetic Data	Installing Synthetic Data

Installing Protectors

The following table lists the available protectors.

Protector	Description
Application Protector	Installing Application Protector
Repository Protector	Installing Repository Protector
Application Protector Java Container	Installing Application Protector Java Container
Rest Container	Installing Rest Container
Cloud Protector	Installing Cloud Protector

Restoring the PPC

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

Before you begin

Before starting a restore, ensure the following conditions are met:

An existing backup is available. Backups are taken automatically as part of the default installation using scheduled backup mechanisms. These backups are stored in an AWS S3 bucket configured during the original installation.
Access to the original backup AWS S3 bucket. During restore, the same S3 bucket that was used during the original installation must be specified.

Restoring the SSH keys and PCT from backed up Terraform state file

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

This section describes the procedure to rebuild a usable PPC 1.0 deployment workspace on a jump box from an existing cluster and a backed up Terraform state file.

Before you Begin

Ensure the following requirements are met.

A backup copy of terraform.tfstate from the original PPC 1.0 workspace.
Access to the same AWS account and target EKS cluster.
AWS CLI credentials with required permissions.

Perform the following steps to recover PPC v1.0.0