Skip to content

docs: aws docs #3449

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
joaquin-borggio-lc merged 5 commits into from
Apr 15, 2026
Merged

docs: aws docs #3449

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
2ba7eb2
wip: aws docs
joaquin-borggio-lc Apr 6, 2026
acad993
update
joaquin-borggio-lc Apr 9, 2026
3558b8a
fix
joaquin-borggio-lc Apr 9, 2026
38c66fa
cleanup
joaquin-borggio-lc Apr 9, 2026
5acde5f
more cleanup
joaquin-borggio-lc Apr 9, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 6 additions & 4 deletions src/langsmith/cicd-pipeline-example.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -335,8 +335,9 @@ For LangSmith API operations (traces, evaluations, datasets):

| Region | Endpoint |
|--------|----------|
| US | `https://api.smith.langchain.com` |
| EU | `https://eu.api.smith.langchain.com` |
| US (GCP) | `https://api.smith.langchain.com` |
| EU (GCP) | `https://eu.api.smith.langchain.com` |
| US (AWS) | `https://aws.api.smith.langchain.com` |

For self-hosted LangSmith instances, use `http(s)://<langsmith-url>/api` where `<langsmith-url>` is your self-hosted instance URL.

Expand All @@ -350,8 +351,9 @@ For LangSmith Deployment operations (deployments, revisions):

| Region | Endpoint |
|--------|----------|
| US | `https://api.host.langchain.com` |
| EU | `https://eu.api.host.langchain.com` |
| US (GCP) | `https://api.host.langchain.com` |
| EU (GCP) | `https://eu.api.host.langchain.com` |
| US (AWS) | `https://aws.api.host.langchain.com` |

For self-hosted LangSmith instances, use `http(s)://<langsmith-url>/api-host` where `<langsmith-url>` is your self-hosted instance URL.

Expand Down
93 changes: 64 additions & 29 deletions src/langsmith/cloud.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,33 +31,37 @@ To deploy your first application to Cloud, follow the [Cloud deployment quicksta
## Cloud architecture and scalability

<Note>
This section is only relevant for the cloud-managed LangSmith services available at [https://smith.langchain.com](https://smith.langchain.com) and [https://eu.smith.langchain.com](https://eu.smith.langchain.com).
This section is only relevant for cloud-managed LangSmith at [https://smith.langchain.com](https://smith.langchain.com), [https://eu.smith.langchain.com](https://eu.smith.langchain.com), and [https://aws.smith.langchain.com](https://aws.smith.langchain.com).

For information on the self-hosted LangSmith solution, please refer to the [self-hosted documentation](/langsmith/self-hosted).
</Note>

LangSmith is deployed on Google Cloud Platform (GCP) and is designed to be highly scalable. Many customers run production workloads on LangSmith for LLM application observability, evaluation, and agent deployment
LangSmith is deployed on Google Cloud Platform (GCP) for the US and EU SaaS regions and on Amazon Web Services (AWS) for the AWS-hosted US SaaS region. The platform is designed to be highly scalable. Many customers run production workloads on LangSmith for LLM application observability, evaluation, and agent deployment.

### Architecture

The US-based LangSmith service is deployed in the `us-central1` (Iowa) region of GCP.
The US-based LangSmith service (default GCP region) is deployed in the `us-central1` (Iowa) region of GCP.

<Note>
The [EU-based LangSmith service](https://eu.smith.langchain.com) is now available (as of mid-July 2024) and is deployed in the `europe-west4` (Netherlands) region of GCP. If you are interested in an enterprise plan in this region, [contact our sales team](https://www.langchain.com/contact-sales).
</Note>

<Note>
As of April 2026, LangSmith SaaS is available on AWS in `us-east-2` (Ohio).
</Note>

#### Regional storage

The resources and services in this table are stored in the location corresponding to the URL where sign-up occurred (either the US or EU). Cloud-managed LangSmith uses [Supabase](https://supabase.com) for authentication/authorization and [ClickHouse Cloud](https://clickhouse.com/cloud) for data warehouse.
The resources and services in this table are stored in the location corresponding to the URL where sign-up occurred (US (GCP), EU (GCP), or US (AWS)). Cloud-managed LangSmith uses [Supabase](https://supabase.com) for authentication/authorization and [ClickHouse Cloud](https://clickhouse.com/cloud) for the data warehouse.

| | US | EU |
| ----------------------------------- | ------------------------------------------------------------------ | ------------------------------------------------------------------------ |
| URL | [https://smith.langchain.com](https://smith.langchain.com) | [https://eu.smith.langchain.com](https://eu.smith.langchain.com) |
| API URL | [https://api.smith.langchain.com](https://api.smith.langchain.com) | [https://eu.api.smith.langchain.com](https://eu.api.smith.langchain.com) |
| GCP | us-central1 (Iowa) | europe-west4 (Netherlands) |
| Supabase | AWS us-east-1 (N. Virginia) | AWS eu-central-1 (Germany) |
| ClickHouse Cloud | us-central1 (Iowa) | europe-west4 (Netherlands) |
| [LangSmith deployment](/langsmith/deployment) | us-central1 (Iowa) | europe-west4 (Netherlands) |
| | US (GCP) | EU (GCP) | US (AWS) |
| ----------------------------------- | ------------------------------------------------------------------ | ------------------------------------------------------------------------ | ------------------------------------------------------------------------ |
| URL | [https://smith.langchain.com](https://smith.langchain.com) | [https://eu.smith.langchain.com](https://eu.smith.langchain.com) | [https://aws.smith.langchain.com](https://aws.smith.langchain.com) |
| API URL | [https://api.smith.langchain.com](https://api.smith.langchain.com) | [https://eu.api.smith.langchain.com](https://eu.api.smith.langchain.com) | [https://aws.api.smith.langchain.com](https://aws.api.smith.langchain.com) |
| Cloud | GCP us-central1 (Iowa) | GCP europe-west4 (Netherlands) | AWS us-east-2 (Ohio) |
| Supabase | AWS us-east-1 (N. Virginia) | AWS eu-central-1 (Germany) | AWS us-east-2 (Ohio) |
| ClickHouse Cloud | us-central1 (Iowa) | europe-west4 (Netherlands) | us-east-2 (Ohio) |
| [LangSmith deployment](/langsmith/deployment) | GCP us-central1 (Iowa); `*.us.langgraph.app` | GCP europe-west4 (Netherlands); `*.eu.langgraph.app` | AWS us-east-2 (Ohio); `*.aws.us.langgraph.app` |

See the [Regions FAQ](/langsmith/regions-faq) for more information.

Expand All @@ -69,6 +73,8 @@ Data listed here is stored exclusively in the US:

#### GCP services

The following applies to the **US and EU** SaaS regions on GCP.

LangSmith is composed of the following services, all deployed on Google Kubernetes Engine (GKE):

* LangSmith Frontend: serves the LangSmith UI.
Expand All @@ -90,6 +96,31 @@ Some additional GCP services we use include:
* Google Cloud CDN for caching static assets.
* Google Cloud Armor for security and rate limits. For more information on rate limits we enforce, please refer to [Rate limits](/langsmith/administration-overview#rate-limits).

#### AWS services

The following applies to the **US (AWS)** SaaS region in `us-east-2` (Ohio). The same logical LangSmith components run on **Amazon EKS** instead of GKE.

LangSmith is composed of the following services, all deployed on Amazon EKS:

* LangSmith Frontend: serves the LangSmith UI.
* LangSmith Backend: serves the LangSmith API.
* LangSmith Platform Backend: handles authentication and other high-volume tasks. (Internal service)
* LangSmith Playground: handles forwarding requests to various LLM providers for the Playground feature.
* LangSmith Queue: handles processing of asynchronous tasks. (Internal service)

LangSmith uses the following AWS storage and data services:

* Amazon S3 for runs inputs and outputs.
* Amazon RDS for PostgreSQL for transactional workloads.
* Amazon ElastiCache for Redis for queuing and caching.
* ClickHouse Cloud over AWS PrivateLink in `us-east-2` for trace ingestion and analytics, consistent with the [regional storage](#regional-storage) table above.

Some additional AWS services we use include:
Copy link
Copy Markdown
Contributor

@katmayb Kathryn May (katmayb) Apr 10, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Some additional AWS services we use include:
Some additional AWS services LangSmith uses include:


* Elastic Load Balancing (Network Load Balancers) and Istio ingress for routing traffic to the LangSmith services. Documented API rate limits are enforced at the Istio ingress gateway. For details, see [Rate limits](/langsmith/administration-overview#rate-limits).
* Amazon CloudFront for caching static assets (including the web UI hostname `aws.smith.langchain.com`).
* AWS WAF on CloudFront for managed rule groups at the edge (for example, AWS Managed Rules common protections and Bot Control).

<div style={{ textAlign: 'center' }}>
<img
className="block dark:hidden"
Expand All @@ -109,36 +140,40 @@ Some additional GCP services we use include:
#### Egress from LangChain SaaS
All traffic leaving LangSmith services will be routed through a NAT gateway. All traffic will appear to originate from the following IP addresses:

| US | EU |
| -------------- | -------------- |
| 34.59.65.97 | 34.13.192.67 |
| 34.67.51.221 | 34.147.105.64 |
| 34.46.212.37 | 34.90.22.166 |
| 34.132.150.88 | 34.147.36.213 |
| 35.188.222.201 | 34.32.137.113 |
| 34.58.194.127 | 34.91.238.184 |
| 34.59.97.173 | 35.204.101.241 |
| 104.198.162.55 | 35.204.48.32 |
| US (GCP) | EU (GCP) | US (AWS) |
| -------------- | -------------- | ------------------------------ |
| 34.59.65.97 | 34.13.192.67 | 18.188.147.158 |
| 34.67.51.221 | 34.147.105.64 | 18.219.86.202 |
| 34.46.212.37 | 34.90.22.166 | 3.21.57.192 |
| 34.132.150.88 | 34.147.36.213 | |
| 35.188.222.201 | 34.32.137.113 | |
| 34.58.194.127 | 34.91.238.184 | |
| 34.59.97.173 | 35.204.101.241 | |
| 104.198.162.55 | 35.204.48.32 | |

It may be helpful to allowlist these IP addresses if connecting to your own AzureOpenAI service or other endpoints that may be required by the Playground or Online Evaluation.

#### Ingress into LangChain SaaS
The langchain endpoints map to the following static IP addresses:
The LangChain endpoints map to the following static IP addresses for traffic that terminates on our **GCP load balancers** (US/EU) or, for **US (AWS)**, on the **Network Load Balancer** in `us-east-2` (API and gateway hostnames):

| US | EU |
| -------------- | -------------- |
| 34.8.121.39 | 34.95.92.214 |
| 34.107.251.234 | 34.13.73.122 |
| US (GCP) | EU (GCP) | US (AWS) |
| -------------- | -------------- | ---------------------------------- |
| 34.8.121.39 | 34.95.92.214 | 3.129.27.169 |
| 34.107.251.234 | 34.13.73.122 | 13.58.107.119 |
| | | 16.59.151.49 |
| | | 16.59.98.147 |
| | | 3.134.146.243 |
| | | 3.150.87.246 |

You may need to allowlist these to enable traffic from your private network to LangSmith SaaS endpoints (`api.smith.langchain.com`, `smith.langchain.com`, `beacon.langchain.com`, `eu.api.smith.langchain.com`, `eu.smith.langchain.com`, `eu.beacon.langchain.com`).
You may need to allowlist these to enable traffic from your private network to LangSmith SaaS endpoints (`api.smith.langchain.com`, `smith.langchain.com`, `beacon.langchain.com`, `eu.api.smith.langchain.com`, `eu.smith.langchain.com`, `eu.beacon.langchain.com`, `aws.api.smith.langchain.com`, `aws.smith.langchain.com`).

### Private Service Connect (Enterprise)

<Callout icon="lock" color="#4F46E5" iconType="regular">
**Enterprise only.** Private Service Connect is available exclusively for Enterprise customers. Contact your account representative or [sales@langchain.dev](mailto:sales@langchain.dev) to enable this feature.
</Callout>

Enterprise customers on GCP can connect to LangSmith via [Private Service Connect (PSC)](https://cloud.google.com/vpc/docs/private-service-connect), providing private connectivity without exposing traffic to the public internet.
Enterprise customers on **GCP** can connect to LangSmith via [Private Service Connect (PSC)](https://cloud.google.com/vpc/docs/private-service-connect), providing private connectivity without exposing traffic to the public internet.

#### Service attachment URIs

Expand Down
4 changes: 4 additions & 0 deletions src/langsmith/create-account-api-key.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,6 +46,10 @@ This is only required if using the EU instance.

`LANGSMITH_ENDPOINT=https://eu.api.smith.langchain.com`

This is only required if using the AWS-hosted US instance.

`LANGSMITH_ENDPOINT=https://aws.api.smith.langchain.com`

This is only required for keys scoped to more than one workspace.

`LANGSMITH_WORKSPACE_ID=<Workspace ID>`
Expand Down
5 changes: 2 additions & 3 deletions src/langsmith/data-export-destinations.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,10 +4,9 @@ description: Configure and manage S3-compatible export destinations for LangSmit
---

<Note>
**For self-hosted and EU region deployments**
**For self-hosted, EU (GCP), and US (AWS) SaaS**

Update the LangSmith URL appropriately for self-hosted installations or organizations in the EU region in the requests below.
For the EU region, use `eu.api.smith.langchain.com`.
Update the LangSmith URL in the requests below for self-hosted installs, EU (GCP) (`eu.api.smith.langchain.com`), or US (AWS) (`aws.api.smith.langchain.com`).
</Note>

A destination is a named configuration that tells LangSmith where to write exported trace data. You [create a destination](/langsmith/data-export#create-a-destination) once, then reference it by ID when [creating export jobs](/langsmith/data-export#create-an-export-job). LangSmith currently supports S3 and any S3-compatible bucket (such as GCS or MinIO) as a destination. Exported data is written in [Parquet](https://parquet.apache.org/docs/overview/) columnar format and contains equivalent fields to the [Run data format](/langsmith/run-data-format).
Expand Down
5 changes: 2 additions & 3 deletions src/langsmith/data-export-monitor.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,10 +14,9 @@ This page covers:
- [Troubleshooting failed exports](#troubleshooting-failed-exports).

<Note>
**For self-hosted and EU region deployments**
**For self-hosted, EU (GCP), and US (AWS) SaaS**

Update the LangSmith URL appropriately for self-hosted installations or organizations in the EU region in the requests below.
For the EU region, use `eu.api.smith.langchain.com`.
Update the LangSmith URL in the requests below for self-hosted installs, EU (GCP) (`eu.api.smith.langchain.com`), or US (AWS) (`aws.api.smith.langchain.com`).
</Note>

## Monitor export status
Expand Down
6 changes: 3 additions & 3 deletions src/langsmith/deploy-hybrid.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,7 @@ The following steps describe how to connect your self-hosted data plane to the m
2. A valid `Ingress` controller is installed on your cluster. For more information about configuring ingress for your deployment, refer to [Create an ingress for installations](/langsmith/self-host-ingress). We highly recommend using the modern [Gateway API](/langsmith/self-host-ingress#option-2%3A-gateway-api) in a production setup.
3. If you plan to have the listener watch multiple namespaces, you **MUST** use the [Gateway API](/langsmith/self-host-ingress#option-2%3A-gateway-api) or an [Istio Gateway](/langsmith/self-host-ingress#option-3%3A-istio-gateway) instead of the [standard ingress](/langsmith/self-host-ingress#option-1%3A-standard-ingress) resource. A standard ingress resource can only route traffic to services in the same namespace, whereas a Gateway or Istio Gateway can route traffic to services across multiple namespaces.
4. You have slack space in your cluster for multiple deployments. `Cluster-Autoscaler` is recommended to automatically provision new nodes.
5. You will need to enable egress to two control plane URLs. The listener polls these endpoints for deployments:
5. You will need to enable egress to two control plane URLs. The listener polls these endpoints for deployments (use the pair that matches your LangSmith region—EU (GCP): `eu.api.host` / `eu.api.smith`; US (AWS): `aws.api.host` / `aws.api.smith`):
- https://api.host.langchain.com
- https://api.smith.langchain.com

Expand Down Expand Up @@ -59,8 +59,8 @@ The following steps describe how to connect your self-hosted data plane to the m
config:
langsmithApiKey: "" # API Key of your Workspace
langsmithWorkspaceId: "" # Workspace ID
hostBackendUrl: "https://api.host.langchain.com" # Only override this if on EU
smithBackendUrl: "https://api.smith.langchain.com" # Only override this if on EU
hostBackendUrl: "https://api.host.langchain.com" # Override for EU (GCP) (`eu.api.host...`) or US (AWS) (`aws.api.host...`)
smithBackendUrl: "https://api.smith.langchain.com" # Override for EU (GCP) (`eu.api.smith...`) or US (AWS) (`aws.api.smith...`)
langgraphListenerId: "" # Listener ID from Step 2f
watchNamespaces: "" # comma-separated list of Kubernetes namespaces that the listener and operator will deploy to
enableLGPDeploymentHealthCheck: true # enable/disable health check step for deployments
Expand Down
Loading
Loading