<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Login to PPC on</title><link>https://docs.protegrity.com/aiteam-edition/docs/infrastructure/ppc/aws/usage/access_ui/</link><description>Recent content in Login to PPC on</description><generator>Hugo</generator><language>en</language><atom:link href="https://docs.protegrity.com/aiteam-edition/docs/infrastructure/ppc/aws/usage/access_ui/index.xml" rel="self" type="application/rss+xml"/><item><title>Prerequisites</title><link>https://docs.protegrity.com/aiteam-edition/docs/infrastructure/ppc/aws/usage/access_ui/prereq/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/aiteam-edition/docs/infrastructure/ppc/aws/usage/access_ui/prereq/</guid><description>&lt;p>Use Route 53 configuration on AWS to resolve the PPC FQDN specified during the installation to the internal load balancer.&lt;/p>
&lt;ul>
&lt;li>Ensure that the instance is using the AWS-provided DNS server, such as, VPC CIDR + 2.&lt;/li>
&lt;li>Verify that &lt;code>enableDnsHostnames&lt;/code> and &lt;code>enableDnsSupport&lt;/code> are set to true in the VPC settings.&lt;/li>
&lt;li>Verify the &lt;strong>Security Group&lt;/strong> of the load balancer. Ensure that Inbound traffic is allowed on the required ports, such as 80 and 443, from the client instance&amp;rsquo;s IP or Security Group.&lt;/li>
&lt;li>Keep the following information ready:
&lt;ul>
&lt;li>&lt;strong>VPC ID&lt;/strong>: The ID of the VPC for the client instances and the Load Balancer. For example, vpc-0123456789.&lt;/li>
&lt;li>&lt;strong>Internal ELB DNS Name&lt;/strong>: The DNS name of the load balancer. For example, internal-abcdefghi123456-123456789.us-east-1.amazonaws.com.&lt;/li>
&lt;li>&lt;strong>Target FQDN&lt;/strong>: The FQDN for PPC. For example, mysite.aws.com.&lt;/li>
&lt;/ul>
&lt;/li>
&lt;/ul>
&lt;ol>
&lt;li>Find the AWS Load Balancer address.&lt;/li>
&lt;/ol>
&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-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span> kubectl get gateway -A
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>The output appears similar to the following:&lt;/p></description></item><item><title>Log in to PPC</title><link>https://docs.protegrity.com/aiteam-edition/docs/infrastructure/ppc/aws/usage/access_ui/access/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/aiteam-edition/docs/infrastructure/ppc/aws/usage/access_ui/access/</guid><description>&lt;p>Access the PPC using the FQDN provided during the installation process.&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>https://&amp;lt;cluster-FQDN&amp;gt;
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>Enter the following parameters to log in and view the homepage.&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Username&lt;/strong>: Application username&lt;/li>
&lt;li>&lt;strong>Password&lt;/strong>: Application password&lt;/li>
&lt;/ul>
&lt;p>For more information about the default credentials, refer to the &lt;em>Release Notes&lt;/em>.&lt;/p>
&lt;blockquote>
&lt;p>&lt;strong>Note:&lt;/strong> When logging in for the first time, ensure to use the application username and password. &lt;/br>
If the password is changed using the CLI Manager, then use the updated credentials to log in to the Web UI.&lt;/p></description></item><item><title>Overview of the UI</title><link>https://docs.protegrity.com/aiteam-edition/docs/infrastructure/ppc/aws/usage/access_ui/ui/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/aiteam-edition/docs/infrastructure/ppc/aws/usage/access_ui/ui/</guid><description>&lt;h2 id="overview-of-the-ui">Overview of the UI&lt;/h2>
&lt;p>After logging in, the UI is organized into the following main areas:&lt;/p>
&lt;ul>
&lt;li>&lt;strong>Top banner&lt;/strong>: Displays the Protegrity logo, the &lt;strong>Home&lt;/strong> button that returns you to the homepage, and the user menu badge at the upper-right corner. The badge shows the initials of the logged-in user. It provides access to your profile, appearance settings, and the sign out option.&lt;/li>
&lt;li>&lt;strong>Navigation pane&lt;/strong>: Appears on the left and groups the product capabilities into the following sections:
&lt;ul>
&lt;li>&lt;strong>Discover&lt;/strong>: Provides access to &lt;strong>Sources&lt;/strong> and &lt;strong>Classifications&lt;/strong>.&lt;/li>
&lt;li>&lt;strong>Policy&lt;/strong>: Provides access to &lt;strong>Data&lt;/strong>, &lt;strong>AI&lt;/strong>, and &lt;strong>Policy Library&lt;/strong>.&lt;/li>
&lt;li>&lt;strong>Insight&lt;/strong>: Opens the dashboards used to monitor protection and policy coverage.&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>&lt;strong>Content area&lt;/strong>: Displays the page that corresponds to the item selected in the navigation pane.&lt;/li>
&lt;/ul>
&lt;h2 id="working-with-the-home-page">Working with the Home Page&lt;/h2>
&lt;p>The home page welcomes the logged-in user and presents &lt;em>The Path to Protection&lt;/em>. It is a guided workflow that helps you discover sensitive data, create policy, and continuously improve protection through Insight.&lt;/p></description></item></channel></rss>