PingOne Advanced Services

AWS PrivateLink network

If you have your own AWS infrastructure and already established network connectivity and routing to and from it, the AWS PrivateLink network might be the right option for you. It does not require you to provide IP addresses for development or connectivity because IP space is hosted within your AWS Virtual Private Cloud (VPC).

This network option might also be appropriate if you need TCP connectivity and can be used in conjunction with a Simple VPN network.

Unlike the Simple VPN network, it is not a multipurpose connection. Instead, consider which services will be exposed for each environment and ensure they can be accessed using the appropriate protocol, such as HTTPS (API endpoints for PingAccess, PingFederate, and PingDirectory) and LDAPS.

Set up AWS PrivateLink for each of your PingOne Advanced Services environments.

  • Then, set up AWS PrivateLink endpoints in your AWS account that point to the exposed services.

  • Finally, set up a private hosted zone that contains the required hostnames in DNS records for the exposed services.

AWS PrivateLink network diagram
Diagram of an AWS PrivateLink network.

To learn more, see What is AWS PrivateLink? in the Amazon Virtual Private Cloud User Guide.

To learn more about additional items you might need to consider, see Setup considerations.