> ## Documentation Index
> Fetch the complete documentation index at: https://controlplanecorporation-kyle-cron-and-quotas.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Native Networking Setup

> Configure Native Networking within an identity using AWS PrivateLink or GCP Private Service Connect to securely access cloud resources.

## Overview

Follow these steps to configure Native Networking within an [identity](/reference/identity) with [AWS PrivateLink](https://docs.aws.amazon.com/vpc/latest/privatelink/what-is-privatelink.html) or [GCP Private Service Connect](https://cloud.google.com/vpc/docs/private-service-connect).

### Prerequisites

* Review the [identity](/reference/identity) reference page.
* Create a resource with one of the following:
  * For AWS, create a resource with PrivateLink configured [(see example)](/guides/native-networking/aws-privatelink/privatelink-rds-terraform).
  * For GCP, create a resource with Private Service Connect configured [(see example)](/guides/native-networking/private-service-connect/cloud-sql).
* 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](/guides/create-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.

<Tip>
  Your workload can reference either the FQDN or the Name to connect using the attached [identity](/reference/identity). If the resource is configured with TLS, the FQDN must be used.
</Tip>

<Note>
  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.
</Note>

6. Optional: If you have a connected [cloud account](/reference/cloudaccount), select the account that contains the endpoint service.
7. 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.
8. Add at least one port number.
9. Click `Add` to finish configuring Native Networking.
10. Click `Update` to save.

## Next Steps

* Finish creating or updating your [identity](/guides/create-identity).
* The identity can be associated with one or more [workloads' identity](/reference/workload#identity) setting.