<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Installation on</title><link>https://docs.protegrity.com/aiteam-edition/docs/gov_policy/pmg/aws/installation/</link><description>Recent content in Installation on</description><generator>Hugo</generator><language>en</language><atom:link href="https://docs.protegrity.com/aiteam-edition/docs/gov_policy/pmg/aws/installation/index.xml" rel="self" type="application/rss+xml"/><item><title>Prerequisites</title><link>https://docs.protegrity.com/aiteam-edition/docs/gov_policy/pmg/aws/installation/prerequisites/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/aiteam-edition/docs/gov_policy/pmg/aws/installation/prerequisites/</guid><description>&lt;p>The following prerequisites apply to both resource-management paths. Both paths require access to the OCI registry to install the Helm chart.&lt;/p>
&lt;ul>
&lt;li>
&lt;p>Ensure that the target EKS cluster is accessible and has a supported PPC installation.&lt;/p>
&lt;p>For more information, refer to &lt;a href="https://docs.protegrity.com/aiteam-edition/docs/infrastructure/ppc/aws/installation/">PPC installation&lt;/a>.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>Ensure that the jumpbox can connect to the required registries. If not already authenticated, then log in to the required registry.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>For connecting and deploying from the Protegrity Container Registry (PCR), use the following command and the credentials obtained from the My.Protegrity portal during &lt;a href="https://docs.protegrity.com/aiteam-edition/docs/infrastructure/obtainingcreds/">account creation&lt;/a>:&lt;/p></description></item><item><title>Installing Policy Workbench</title><link>https://docs.protegrity.com/aiteam-edition/docs/gov_policy/pmg/aws/installation/install_workbench_aws/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/aiteam-edition/docs/gov_policy/pmg/aws/installation/install_workbench_aws/</guid><description>&lt;!--Before installing Policy Workbench, ensure that the prerequisites are met. For more information about the prerequisites, refer to [Prerequisites](#prerequisites). -->
&lt;p>Policy Workbench is installed on an existing, supported PPC installation running on AWS EKS. Prepare the AWS and Kubernetes resources needs using one of two methods:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Module-managed Workbench resources:&lt;/strong> Use the provided &lt;code>policy-workbench&lt;/code> OpenTofu module to prepare the resources on the existing cluster.The OpenTofu installation procedure depends on whether a root module is available.&lt;br>
For more information about OpenTofu modules and the root module, refer to &lt;a href="https://opentofu.org/docs/language/modules/">Modules&lt;/a> in the OpenTofu documentation.&lt;/li>
&lt;li>&lt;strong>Self-managed Workbench resources:&lt;/strong> Prepare and manage those resources through the existing infrastructure process. &lt;br>
For more information on deploying PPC onto an existing AWS EKS cluster, refer to &lt;a href="https://docs.protegrity.com/aiteam-edition/docs/infrastructure/ppc/aws/installation/deploying_ppc/in_cluster_deployment/">In-cluster deployment&lt;/a>.&lt;/li>
&lt;/ul>
&lt;p>Both methods install Policy Workbench with Helm. The following sections describe the prerequisites and steps for each method.&lt;/p></description></item></channel></rss>