This is the multi-page printable view of this section. Click here to print.

Return to the regular view of this page.

Login to PPC

Steps to access the PPC UI

1 - Prerequisites

Use Route 53 configuration on AWS to resolve the PPC FQDN specified during the installation to the internal load balancer.

  • Ensure that the instance is using the AWS-provided DNS server, such as, VPC CIDR + 2.
  • Verify that enableDnsHostnames and enableDnsSupport are set to true in the VPC settings.
  • Verify the Security Group of the load balancer. Ensure that Inbound traffic is allowed on the required ports, such as, 80 and 443, from the client instance’s IP or Security Group.
  • Keep the following information ready:
    • VPC ID: The ID of the VPC for the client instances and the Load Balancer. For example, vpc-0123456789.
    • Internal ELB DNS Name: The DNS name of the load balancer. For example, internal-abcdefghi123456-123456789.us-east-1.amazonaws.com.
    • Target FQDN: The FQDN for PPC. For example, mysite.aws.com.

  1. Find the AWS Load Balancer address.

    kubectl get gateway -A

    The output appears similar to the following:

    NAMESPACE     NAME       CLASS   ADDRESS                                                                           PROGRAMMED   AGE
api-gateway   pty-main   envoy   internal-abcdefghi123456-123456789.us-east-1.elb.amazonaws.com   True

  2. Map the PPC FQDN to the load balancer using Route 53.

For more information about configuring Route 53, refer to the AWS documentation.

2 - Log in to PPC

Access the PPC using the FQDN provided during the installation process.

Enter the username and password for the admin user to log in and view the Insight Dashboard.

If Protegrity Agent is installed, then the Protegrity Agent dashboard appears. Click Insight to open the Insight Dashboard. For more information about Protegrity Agent, refer to Using Protegrity Agent.