<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Protegrity Provisioned Cluster on</title><link>https://docs.protegrity.com/aiteam-edition/1.0.0/docs/infrastructure/ppc/</link><description>Recent content in Protegrity Provisioned Cluster on</description><generator>Hugo</generator><language>en</language><atom:link href="https://docs.protegrity.com/aiteam-edition/1.0.0/docs/infrastructure/ppc/index.xml" rel="self" type="application/rss+xml"/><item><title>Accessing PPC using a Linux machine</title><link>https://docs.protegrity.com/aiteam-edition/1.0.0/docs/infrastructure/ppc/accessing_cluster/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/aiteam-edition/1.0.0/docs/infrastructure/ppc/accessing_cluster/</guid><description>&lt;h2 id="before-you-begin">Before you begin&lt;/h2>
&lt;p>Ensure that the following prerequisites are met.&lt;/p>
&lt;ul>
&lt;li>A Linux machine is available and running.&lt;/li>
&lt;li>AWS CLI is installed and configured.&lt;/li>
&lt;li>Kubernetes command-line tool is installed.&lt;/li>
&lt;/ul>
&lt;p>Perform the following steps to access PPC using a separate Linux machine.&lt;/p>
&lt;ol>
&lt;li>
&lt;p>Log in to Linux machine with &lt;em>root&lt;/em> credentials.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>Configure AWS credentials, using the following command.&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-fallback" data-lang="fallback">&lt;span style="display:flex;">&lt;span>aws configure
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;/li>
&lt;li>
&lt;p>Verify that AWS credentials are working, using the following command.&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-fallback" data-lang="fallback">&lt;span style="display:flex;">&lt;span>aws sts get-caller-identity
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;/li>
&lt;li>
&lt;p>If the Kubernetes command-line tool is not available, then install the Kubernetes command-line tool, using the following command.&lt;/p></description></item><item><title>Installing Features and Protectors</title><link>https://docs.protegrity.com/aiteam-edition/1.0.0/docs/infrastructure/ppc/install_features/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/aiteam-edition/1.0.0/docs/infrastructure/ppc/install_features/</guid><description>&lt;h2 id="before-you-begin">Before you begin&lt;/h2>
&lt;p>Ensure that PPC is successfully installed before installing the features or protectors.&lt;/p>
&lt;h2 id="installing-features">Installing Features&lt;/h2>
&lt;p>The following table lists the available features.&lt;/p>
&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>Feature&lt;/th>
 &lt;th>Description&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td>Data Discovery&lt;/td>
 &lt;td>&lt;a href="https://docs.protegrity.com/aiteam-edition/1.0.0/docs/data_discovery/dd/install/">Installing Data Discovery&lt;/a>&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>Semantic Guardrails&lt;/td>
 &lt;td>&lt;a href="https://docs.protegrity.com/aiteam-edition/1.0.0/docs/ai_security/sgr/sgr_installing/">Installing Semantic Guardrails&lt;/a>&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>Protegrity Agent&lt;/td>
 &lt;td>&lt;a href="https://docs.protegrity.com/aiteam-edition/1.0.0/docs/gov_policy/protegrity_agent/agent_install/">Installing Protegrity Agent&lt;/a>&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>Anonymization&lt;/td>
 &lt;td>&lt;a href="https://docs.protegrity.com/aiteam-edition/1.0.0/docs/data_privacy/anon/install_anon/">Installing Anonymization&lt;/a>&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>Synthetic Data&lt;/td>
 &lt;td>&lt;a href="https://docs.protegrity.com/aiteam-edition/1.0.0/docs/data_privacy/synth_data/install_synth_data/">Installing Synthetic Data&lt;/a>&lt;/td>
 &lt;/tr>
 &lt;/tbody>
&lt;/table>
&lt;h2 id="installing-protectors">Installing Protectors&lt;/h2>
&lt;p>The following table lists the available protectors.&lt;/p>
&lt;table>
 &lt;thead>
 &lt;tr>
 &lt;th>Protector&lt;/th>
 &lt;th>Description&lt;/th>
 &lt;/tr>
 &lt;/thead>
 &lt;tbody>
 &lt;tr>
 &lt;td>Application Protector&lt;/td>
 &lt;td>&lt;a href="https://docs.protegrity.com/aiteam-edition/1.0.0/docs/protectors/app_protectors/ap/">Installing Application Protector&lt;/a>&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>Repository Protector&lt;/td>
 &lt;td>&lt;a href="https://docs.protegrity.com/aiteam-edition/1.0.0/docs/protectors/repository_protectors/">Installing Repository Protector&lt;/a>&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>Application Protector Java Container&lt;/td>
 &lt;td>&lt;a href="https://docs.protegrity.com/aiteam-edition/1.0.0/docs/protectors/app_protectors/ap_java_cont/install_iap_java/">Installing Application Protector Java Container&lt;/a>&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>Rest Container&lt;/td>
 &lt;td>&lt;a href="https://docs.protegrity.com/aiteam-edition/1.0.0/docs/protectors/app_protectors/rest_cont/install_iap_rest/">Installing Rest Container&lt;/a>&lt;/td>
 &lt;/tr>
 &lt;tr>
 &lt;td>Cloud Protector&lt;/td>
 &lt;td>&lt;a href="https://docs.protegrity.com/aiteam-edition/1.0.0/docs/protectors/cloud_protectors/">Installing Cloud Protector&lt;/a>&lt;/td>
 &lt;/tr>
 &lt;/tbody>
&lt;/table></description></item><item><title>Restoring the PPC</title><link>https://docs.protegrity.com/aiteam-edition/1.0.0/docs/infrastructure/ppc/restore/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/aiteam-edition/1.0.0/docs/infrastructure/ppc/restore/</guid><description>&lt;h2 id="before-you-begin">Before you begin&lt;/h2>
&lt;p>Before starting a restore, ensure the following conditions are met:&lt;/p>
&lt;ul>
&lt;li>
&lt;p>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.&lt;/p>
&lt;/li>
&lt;li>
&lt;p>Access to the original backup AWS S3 bucket. During restore, the same S3 bucket that was used during the original installation must be specified.&lt;/p></description></item></channel></rss>