-
Notifications
You must be signed in to change notification settings - Fork 923
Add reference / best practice for AWS + Azure infrastructure #1403
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.
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
base: main
Are you sure you want to change the base?
Conversation
|
Mintlify preview ID generated: preview-selfho-1763054841-914688a |
57baa47 to
cedd495
Compare
|
Mintlify preview ID generated: preview-selfho-1763055531-4b07c43 |
src/langsmith/aws-self-hosted.mdx
Outdated
| - <Icon icon="globe" /> **Ingress & networking**: Requests enter via [Amazon Application Load Balancer (ALB)](https://aws.amazon.com/elasticloadbalancing/application-load-balancer/) within your [VPC](https://aws.amazon.com/vpc/), secured using [AWS WAF](https://aws.amazon.com/waf/) and [IAM](https://aws.amazon.com/iam/)-based authentication. | ||
| - <Icon icon="cube" /> **Frontend & backend services:** Containers run on [Amazon EKS](https://aws.amazon.com/eks/), orchestrated behind the ALB. Nginx routes requests to the LangSmith frontend, backend, and queue workers. | ||
| - <Icon icon="database" /> **Storage & databases:** | ||
| - [Amazon RDS for PostgreSQL](https://aws.amazon.com/rds/postgresql/): metadata, projects, users. | ||
| - [Amazon ElastiCache (Redis)](https://aws.amazon.com/elasticache/redis/): caching and job queues. | ||
| - ClickHouse + [Amazon EBS](https://aws.amazon.com/ebs/): analytics and trace storage. | ||
| - [Amazon S3](https://aws.amazon.com/s3/): object storage for trace artifacts and telemetry. | ||
| - <Icon icon="sparkles" /> **LLM integration:** Optionally proxy requests to [Amazon Bedrock](https://aws.amazon.com/bedrock/) or [Amazon SageMaker](https://aws.amazon.com/sagemaker/) for LLM inference. | ||
| - <Icon icon="chart-line" /> **Monitoring & observability:** Integrated with [Amazon CloudWatch](https://aws.amazon.com/cloudwatch/) and [LangSmith Beacon](/langsmith/self-host-egress) (for self-hosted telemetry opt-in). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rahul-langchain I noticed you had a section like this in the Azure google doc. I've essentially copied that into AWS but adapted — can you check whether this is all correct?
|
Mintlify preview ID generated: preview-selfho-1763139517-b0f2587 |
|
Mintlify preview ID generated: preview-selfho-1763435197-a35c7ce |
src/langsmith/aws-self-hosted.mdx
Outdated
| - <Icon icon="sparkles" /> **LLM integration:** Optionally proxy requests to [Amazon Bedrock](https://aws.amazon.com/bedrock/) or [Amazon SageMaker](https://aws.amazon.com/sagemaker/) for LLM inference. | ||
| - <Icon icon="chart-line" /> **Monitoring & observability:** Integrate with [Amazon CloudWatch](https://aws.amazon.com/cloudwatch/) | ||
|
|
||
| - [LangSmith Observability and Evaluation](/langsmith/self-hosted#self-host-langsmith-observability-and-evaluation): Deploy the UI and API services (frontend, backend, platform backend, playground, queue workers, and ACE). Use external AWS managed services for RDS PostgreSQL, ElastiCache, and S3. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should consider linking out, or having briefer mentions of the self-hosted types — while it is in other places in the docs, users can land on a page from search and then they have no context.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Comment applies to Azure + AWS pages. In my opinion you could actually keep the page description and add a small addendum:
This page provides AWS-specific architecture patterns, service recommendations, and best practices for deploying and operating LangSmith on AWS. For more details on LangSmith self-hosted models, refer to the self-hosted overview page.
src/langsmith/aws-self-hosted.mdx
Outdated
|
|
||
| When running LangSmith on [Amazon Web Services (AWS)](https://aws.amazon.com/), you can set up in either [self-hosted](/langsmith/self-hosted) or [hybrid](/langsmith/hybrid) mode. In both cases, your workloads run on AWS infrastructure within your account, allowing you to use AWS managed services while maintaining control over your data and compute resources. | ||
|
|
||
| This page provides AWS-specific architecture patterns, service recommendations, and best practices for deploying and operating LangSmith on AWS. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See comment below re this paragraph
|
Mintlify preview ID generated: preview-selfho-1763473632-8f0ba30 |
|
Mintlify preview ID generated: preview-selfho-1763518232-00a0eab |
Fixes DOC-442
Adds reference / best practice pages on AWS + Azure infrastructure setup for self-hosted and hybrid in LangSmith.
Decided on a different placement from initial discussion, for the following reasons:
These pages belong under "Self-hosted cloud architecture" rather than "Setup guides" because they provide reference architecture and best practices, not step-by-step installation instructions.
Structure allows for:
Preview
AWS reference
Azure reference