Unstructured-IO · Paul-Cornell · Nov 6, 2025 · Nov 6, 2025
diff --git a/docs.json b/docs.json
@@ -322,6 +322,7 @@
             "group": "AWS",
             "pages": [
               "enterprise/aws/overview",
+              "enterprise/aws/dedicated-instance-privatelink",
               "enterprise/aws/onboard"
             ]
           },

diff --git a/enterprise/aws/dedicated-instance-privatelink.mdx b/enterprise/aws/dedicated-instance-privatelink.mdx
@@ -0,0 +1,56 @@
+---
+title: Unstructured Enterprise dedicated instance on Amazon Web Services (AWS) with PrivateLink - onboarding
+sidebarTitle: Dedicated instance + PrivateLink onboarding
+---
+
+<Note>
+    The following information applies only to dedicated instance deployments with PrivateLink for [Unstructured Enterprise](/enterprise/overview) on AWS. 
+
+    For dedicated instance deployments of Unstructured Enterprise to AWS _without_ PrivateLink, contact your Unstructured sales representative, 
+    or email Unstructured Sales at [sales@unstructured.io](mailto:sales@unstructured.io).
+
+    For in-VPC deployments of Unstructured Enterprise to AWS instead, see the [AWS in-VPC onboarding](/enterprise/aws/onboard) checklist.
+</Note>
+
+After your organization has signed the Enterprise agreement with Unstructured, a member of the Unstructured technical enablement team will reach out to you to begin the 
+deployment onboarding process. While you wait, you can get started by following the onboarding process:
+
+1. Provide your Unstructured sales representative or technical enablement contact with the AWS Region name 
+   where you want the dedicated instance deployment to be created. Unstructured will begin creating the dedicated instance deployment in that AWS Region.
+
+   <Note>
+       If you do not know who your Unstructured sales representative or technical enablement contact is, 
+       email Unstructured Sales at [sales@unstructured.io](mailto:sales@unstructured.io), and a member of the Unstructured sales or technical enablement teams 
+       will get back to you as soon as possible.
+   </Note>
+
+   Unstructured supports only the following AWS Regions for dedicated instance deployments:
+
+   | Name | Code |
+   | --- | --- |
+   | `us-east-1` | US East (N. Virginia) |
+   | `us-east-2` | US East(Ohio) |
+   | `us-west-2` | US West(Oregon) |
+   | `eu-west-1` | Europoe (Ireland) |
+   | `eu-north-1` | Europe (Stockholm) |
+   | `eu-central-1` | Europe (Frankfurt) |
+   | `ap-southeast-2` | Asia Pacific (Sydney) |
+   | `ap-south-1` | Asia Pacific (Mumbai) |
+   | `ap-northeast-2` |Asia Pacific (Seoul) |
+
+2. In your AWS account, create an endpoint service powered by AWS PrivateLink. Be sure when creating the endpoint service to use the same AWS Region name that you provided to Unstructured. 
+   [Learn how](https://docs.aws.amazon.com/vpc/latest/privatelink/create-endpoint-service.html). (In AWS terminology, this makes you the _service provider_ and 
+   Unstructured the _service consumer_.)
+3. As the service provider, you must provide your Unstructured sales representative or technical enablement contact (as the service consumer) with the name of your endpoint service 
+   (for example, `com.amazonaws.vpce.us-east-1.vpce-svc-0e123abc123198abc`) and the supported Availability Zones for that endpoint service, for the AWS Region 
+   name that you provided to Unstructured earlier. [Learn how](https://docs.aws.amazon.com/vpc/latest/privatelink/create-endpoint-service.html#share-endpoint-service).
+4. As the service consumer, Unstructured will create a related endpoint service in its own AWS account in the same AWS Region as your AWS account. Unstructured will then send you an endpoint connection request to 
+   complete the connection between its endpoint service (as the service consumer) and your endpoint service (as the service provider). 
+   You must accept Unstructured's endpoint connection request as soon as possible, to avoid delays in the deployment process. 
+   [Learn how](https://docs.aws.amazon.com/vpc/latest/privatelink/configure-endpoint-service.html#accept-reject-connection-requests).
+
+## Questions? Need help?
+
+If you have questions or need help as you go, contact your Unstructured sales representative or technical enablement contact. If you do not know who they are, 
+email Unstructured Sales at [sales@unstructured.io](mailto:sales@unstructured.io), and a member of the Unstructured sales or technical enablement teams 
+will get back to you as soon as possible.
diff --git a/enterprise/aws/onboard.mdx b/enterprise/aws/onboard.mdx
@@ -1,13 +1,16 @@
 ---
 title: Unstructured Enterprise in-VPC on Amazon Web Services (AWS) - onboarding checklist
-sidebarTitle: Onboarding
+sidebarTitle: In-VPC onboarding
 ---
 
 <Note>
     The following information applies only to in-VPC deployments of [Unstructured Enterprise](/enterprise/overview). 
 
     For dedicated instance deployments of Unstructured Enterprise, contact your Unstructured sales representative, 
     or email Unstructured Sales at [sales@unstructured.io](mailto:sales@unstructured.io).
+
+    For dedicated instance deployments of Unstructured Enterprise that also use PrivateLink, see 
+    the [onboarding process for AWS PrivateLink](/enterprise/aws/dedicated-instance-privatelink).
 </Note>
 
 After your organization has signed the Enterprise agreement with Unstructured, a member of the Unstructured technical enablement team will reach out to you to begin the 

diff --git a/enterprise/aws/overview.mdx b/enterprise/aws/overview.mdx
@@ -1,15 +1,8 @@
 ---
-title: Unstructured Enterprise in-VPC on Amazon Web Services (AWS) - overview
+title: Unstructured Enterprise on Amazon Web Services (AWS) - overview
 sidebarTitle: Overview
 ---
 
-<Note>
-    The following information applies only to in-VPC deployments of [Unstructured Enterprise](/enterprise/overview). 
-
-    For dedicated instance deployments of Unstructured Enterprise, contact your Unstructured sales representative, 
-    or email Unstructured Sales at [sales@unstructured.io](mailto:sales@unstructured.io).
-</Note>
-
 ## Getting started
 
 To get started with an Enterpise deployment, your organization must first sign an Enterprise agreement with Unstructured. 
@@ -18,8 +11,10 @@ This agreement outlines the terms and conditions for your organization to use Un
 To begin the Enterprise agreement process, contact your Unstructured sales representative, or email Unstructured Sales at [sales@unstructured.io](mailto:sales@unstructured.io).
 
 After your organization has signed the Enterprise agreement, a member of the Unstructured technical enablement team will reach out to you to begin the 
-deployment onboarding process. To streamline this process, you are encouraged to begin setting up your target environment as soon as possible. To do this, 
-see the [onboarding checkist](/enterprise/aws/onboard).
+deployment onboarding process. While you wait, you can get started by following the onboarding checkist for your deployment type, if it applies to you:
+
+- For dedicated instance deployments with AWS PrivateLink, follow the [onboarding checkist for AWS PrivateLink](/enterprise/aws/dedicated-instance-privatelink). 
+- For in-VPC deployents, follow the [onboarding checkist for in-VPC on AWS](/enterprise/aws/onboard).
 
 ## Questions? Need help?
 

diff --git a/enterprise/overview.mdx b/enterprise/overview.mdx
@@ -45,7 +45,8 @@ After your organization has signed the Enterprise agreement, a member of the Uns
 deployment onboarding process.
 
 - For a dedicated instance deployment, a member of the Unstructured technical enablement team will reach out to you with the unique URL to log in to 
-  the Unstructured UI, along with any next steps that you need to take.
+  the Unstructured UI, along with any next steps that you need to take. For dedicated instance deployments to AWS that also use PrivateLink, see 
+  the [onboarding process for AWS PrivateLink](/enterprise/aws/dedicated-instance-privatelink).
 - For an in-VPC deployment, your organization will work with a member of the Unstructured technical enablement team to deploy Unstructured 
   into your own cloud instrastructure. You are encouraged to begin setting up your target environment as soon as possible. To do this, 
   see the onboarding requirements for your [AWS](/enterprise/aws/onboard), [Azure](/enterprise/azure/onboard), or