Skip to main content

​
Overview

Follow these 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, create a resource with PrivateLink configured (see example).
    • For GCP, create a resource with Private Service Connect configured (see example).
  • Contact Control Plane support to associate the resource’s service name (AWS) or service attachment (GCP) to the org.

​
Create using the UI Console

  1. Create or edit an identity.
  2. Under the Native Networking submenu, click on AWS PrivateLink or GCP Service Connect.
  3. Click on Add AWS Resource or Add GCP Resource.
  4. In the FQDN (Fully Qualified Domain Name) field, enter the hostname of the cloud resource.
  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 to connect using the attached identity. If the resource is configured with TLS, the FQDN must be used.
You can configure multiple Native Networking connections to different resources by specifying different port numbers for each resource. If the same port is required, a new PrivateLink or Private Service Connect endpoint must be configured.
  1. Optional: If you have a connected cloud account, select the account that contains the endpoint service.
  2. Enter the endpoint service name (Service name for AWS or Service attachment name for GCP). If you selected a cloud account, you can also click ... to browse for it.
  3. Add at least one port number.
  4. Click Add to finish configuring Native Networking.
  5. Click Update to save.

​
Next Steps