​
Overview

Follow the steps to configure Native Networking within an identity with AWS PrivateLink or GCP Private Service Connect.

​
Prerequisites

  • Review the identity reference page.
  • Create a resource with one of the following:
    • For AWS, a resource is created with PrivateLink configured (see example).
    • For GCP, a resource is created with Private Service Connect configured (see example).
  • Control Plane support has created an endpoint using your resource’s service name (AWS) or service attachment (GCP).

​
Create using the UI Console

  1. Create or edit an identity.
  2. Navigate to the Native Networking tab on the left hand side.
  3. Select Add Native Networking
  4. In the Fully Qualified Domain Name (FQDN) field, enter a unique name.
  5. In the Name field, enter another unique name that does not match the FQDN.
Your workload can reference either the FQDN or the Name as an environment variable to connect using the identity. If the internal resource is configured with TLS, the FQDN must be used.
  1. Add a port number.
You can configure multiple Native Networking connections to different resources by specifying different port numbers for each resource. Each new database that is created in the cloud will require a new PrivateLink/Private Service Connect endpoint.
  1. Select your Cloud Provider.
    • If using AWS choose AWS PrivateLink and paste your service name.
    • If using GCP choose GCP Service Connect and paste your service attachment.
  2. Select Add to finish configuring Native Networking.

​
Next Steps