Prerequisites

Ensure that the following prerequisites are met before installing Data Discovery with PPC:

• PPC Cluster Team Edition must be installed and accessible. For more information on installing PPC, refer Installing PPC for instructions.

• Access to a Kubernetes cluster with sufficient permissions to manage the following resources:

  • Namespace
  • Deployment
  • Service
  • ConfigMap
  • Secret
  • HorizontalPodAutoscaler
  • Gateway API resources (HTTPRoute, ReferenceGrant, SecurityPolicy)
  • Karpenter resources (NodePool, EC2NodeClass)

• Authorization to provision AWS m5.large instances.

• Ensure that the jumpbox can connect to the required repositories. If not already authenticated, then log in to the required repository.

• For connecting and deploying from the Protegrity Container Registry (PCR), use the following command and the credentials obtained from the My.Protegrity portal during account creation:

helm registry login registry.protegrity.com:9443

• For connecting and deploying to the local repository, use your local credentials and local repository endpoint as required.
• AWS credentials with permission to read SSM parameters in the target region (required only when overriding the AMI ID).

Option A (Recommended): Run the following AWS CLI command to retrieve the AMI ID dynamically

aws ssm get-parameter \
  --name /aws/service/bottlerocket/aws-k8s-1.34/x86_64/latest/image_id \
  --region <region> \
  --query "Parameter.Value" \
  --output text

Alternatively, refer to these example AMI IDs.

Option B: The following table provides the list of AMI IDs