Update aws-privatelink-beta.md

Author: forstisabella

src/connections/storage/aws-privatelink-beta.md

@@ -6,21 +6,7 @@ hidden: true
 [Amazon Web Services' PrivateLink](https://aws.amazon.com/privatelink/){:target="_blank”} is an AWS service that provides private connectivity between VPCs without exposing traffic to the public Internet. Keeping traffic in the Amazon network reduces the data security risk associated with exposing your Warehouse traffic to the Internet.
 
 > info ""
-> Segment's PrivateLink integration is currently in public beta and is governed by Segment’s [First Access and Beta Preview Terms](https://www.twilio.com/en-us/legal/tos){:target="_blank”}. Only warehouses located in region `us-east-1` are eligible for PrivateLink. 
-
-During the AWS PrivateLink Private Beta, Segment supports the following integrations: 
-- Databricks
-  - [Databricks storage destination](/docs/connections/storage/catalog/databricks/)
-  - [Databricks Reverse ETL source](/docs/connections/reverse-etl/reverse-etl-source-setup-guides/databricks-setup/)
-  - [Databricks Profiles Sync destination](/docs/unify/profiles-sync/profiles-sync-setup/databricks-profiles-sync/)
-- RDS Postgres
-  - [RDS Postgres storage destination](/docs/connections/storage/catalog/postgres/)
-  - [RDS Postgres Reverse ETL source](/docs/connections/reverse-etl/reverse-etl-source-setup-guides/postgres-setup/)
-  - [RDS Postgres Profiles Sync destination](/docs/unify/profiles-sync/profiles-sync-setup/#step-1-select-a-warehouse)
-- Redshift
-  - [Redshift storage destination](/docs/connections/storage/catalog/redshift/)
-  - [Redshift Reverse ETL source](/docs/connections/reverse-etl/reverse-etl-source-setup-guides/redshift-setup/)
-  - [Redshift Profiles Sync destination](/docs/unify/profiles-sync/profiles-sync-setup/#step-1-select-a-warehouse)
+> Segment's PrivateLink integration is currently in public beta and is governed by Segment’s [First Access and Beta Preview Terms](https://www.twilio.com/en-us/legal/tos){:target="_blank”}. Only warehouses located in region `us-east-1` are eligible for PrivateLink. You might incur additional networking costs while using AWS PrivateLink. 
 
 ## Getting started
 
@@ -33,19 +19,26 @@ You can set up AWS PrivateLink for [Databricks](#databricks), [RDS Postgres](#rd
 
 #### Prerequisites
 
-Before you begin, [reach out to Segment]() and indicate your interest in configuring AWS PrivateLink for Databricks. Segment's engineering team will create a VPC endpoint on your behalf and share the VPC endpoint ID with you. You need information about this VPC endpoint to [Create VPC Endpoints](https://docs.databricks.com/en/security/network/classic/privatelink.html#step-3-register-privatelink-objects){:target="_blank”} in your Databricks instance.
-
-To configure AWS PrivateLink for Databricks:
+Before you can configure AWS PrivateLink for Databricks:
 - Your Databricks account must be on the [Enterprise pricing tier](https://www.databricks.com/product/pricing/platform-addons){:target="_blank”} and use the [E2 version](https://docs.databricks.com/en/archive/aws/end-of-life-legacy-workspaces.html#e2-architecture){:target="_blank”} of the platform. 
 - Your Databricks workspace must use a [Customer-managed VPC](https://docs.databricks.com/en/security/network/classic/customer-managed-vpc.html){:target="_blank”} and [Secure cluster connectivity](https://docs.databricks.com/en/security/network/classic/secure-cluster-connectivity.html){:target="_blank”}
-- You must have the AWS permissions required to [set up a new Databricks workspace](https://docs.databricks.com/en/admin/workspace/create-workspace.html#before-you-begin){:target="_blank”} and [create a VPC](https://docs.aws.amazon.com/vpc/latest/privatelink/getting-started.html#create-vpc-subnets){:target="_blank”} 
+- You must have the AWS permissions required to [set up a new Databricks workspace](https://docs.databricks.com/en/admin/workspace/create-workspace.html#before-you-begin){:target="_blank”} and [create a VPC](https://docs.aws.amazon.com/vpc/latest/privatelink/getting-started.html#create-vpc-subnets){:target="_blank”}
+- You must have a technical parter in your organization to support the PrivateLink integration.
+-  
 
-> warning "The `us-west-1` region does not support PrivateLink"
+> warning "Only warehouses in the `us-east-1` region support Segment's PrivateLink integration"
 > Create a Databricks warehouse in a new region to use PrivateLink.
 
 ### Getting started
 
-To configure PrivateLink for Databricks, follow the instructions in Databricks' [Enable private connectivity using AWS PrivateLink](https://docs.databricks.com/en/security/network/classic/privatelink.html){:target="_blank”} documentation. You must create both [front-end and back-end](https://docs.databricks.com/en/security/network/classic/privatelink.html#private-connectivity-overview){:target="_blank”} connections to integration PrivateLink for Segment.
+To configure PrivateLink for Databricks, follow the instructions in Databricks' [Enable private connectivity using AWS PrivateLink](https://docs.databricks.com/en/security/network/classic/privatelink.html){:target="_blank”} documentation. You must create a [back-end](https://docs.databricks.com/en/security/network/classic/privatelink.html#private-connectivity-overview){:target="_blank”} connection to integrate with Segment's front-end connection. 
+
+After you've configured a back-end connection for Databricks, request access to Segment's PrivateLink integration by taking the following steps:
+1. Open your [Databricks storage destination](/docs/connections/storage/catalog/databricks/), [Databricks Reverse ETL source](/docs/connections/reverse-etl/reverse-etl-source-setup-guides/databricks-setup/), or [Databricks Profiles Sync destination](/docs/unify/profiles-sync/profiles-sync-setup/databricks-profiles-sync/).
+2. Navigate to **Settings > Connection**. 
+3. Click the **Request PrivateLink** button and fill out the 
+
+<!--- todo: get context about what happens when users click the link--->
 
 ### RDS Postgres 
 
@@ -56,6 +49,14 @@ To configure PrivateLink for Databricks, follow the instructions in Databricks'
 
 ### Redshift
 
+#### Prerequisites
+- **You're using the RA3 node type**: <br>Segment's PrivateLink integration requires you to use one of the following RA3 instances types: 
+  - ra3.16xlarge
+  - ra3.4xlarge
+  - ra3.xlplus  
+- **You've enabled cluster relocation**: Cluster relocation migrates your cluster behind a proxy and keeps the cluster endpoint unchanged, even if your cluster needs to be migrated to a new Availability Zone duew to lack of resources. A consistent cluster endpoint makes it possible for Segment's Edge account and VPC to remain connected to your cluster.
+- **Your warehouse is using port range 5431-5455 and 8191-8215**: 
+
 1. [Reach out to Segment]() and let the engineering team know you're interested in configuring AWS PrivateLink for Redshift. Segment's engineering team will then share information with you about Segment’s Edge account and VPC.
 2. After you receive information from Segment about the Edge account and VPC, [grant cluster access to Segment's Edge account and VPC](https://docs.aws.amazon.com/redshift/latest/gsg/rs-gsg-connect-to-cluster.html){:target="_blank”}.
 3. Segment creates a Redshift managed VPC endpoint within a Redshift subnet on your behalf, which creates an internal PrivateLink Endpoint URL. Segment will provide you with this URL, which you need to configure your Warehouse in the Segment app.