Deploying PPC on

Configuring PPC for Non-FIPS Deployment on AWS

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

Before you begin

By default, the PCT is configured to deploy a FIPS-enabled cluster using FIPS-compliant Bottlerocket AMIs. To deploy a standard, non-FIPS cluster, the following Terraform configuration files must be modified to use the standard (non-FIPS) Bottlerocket AMI types and SSM parameter paths before running the bootstrap script or the component-based installation.

Perform these steps after downloading and extracting the PCT and before proceeding with either the Script-based installation or the Component-based installation.

Automated script-based installation

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

Note for non-FIPS deployments: If you completed the steps in Configuring PPC for Non-FIPS Deployment on AWS, then the required Terraform configuration files have already been updated with non-FIPS values. The bootstrap script reads these files directly. Do not modify 03_node_group/variables.tf or 05_helm_releases/main.tf files back to FIPS defaults. Reverting those changes will result in a FIPS cluster being deployed instead of a non-FIPS cluster.

Before you begin

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.

The repository provides a bootstrap script that automatically installs or updates the following software on the jump box:

Manual component-based installation

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

Before you begin

Ensure to have the following prerequisites before proceeding with the installation.

Jump box requirement

Ensure that the entire process is performed using the same jump box.

Parameter values

Value	Example
AWS credentials	`AWS_ACCESS_KEY_ID`, `AWS_SECRET_ACCESS_KEY`, `AWS_SESSION_TOKEN`
Cluster name	`my-cluster`
VPC ID	`vpc-0abc123`
Two private subnet IDs	`subnet-aaa`, `subnet-bbb`
Ingress FQDN	`myapp.example.com`
S3 backup bucket name	`my-backup-bucket` (existing) or provision one in Step 3
Image registry endpoint	`registry.example.com`
Registry username and password	Provided by organization

Deploying PPC using component-based installation

To deploy PPC using the component-based installation, perform the following steps