langchain-ai/docs
1
0
Fork 0
mirror of https://github.com/langchain-ai/docs.git synced 2026-07-22 04:15:25 -04:00
Code Issues 490 Packages Projects Releases Wiki Activity

[PR #4044] [MERGED] docs: note Bedrock IAM trusted entity not applicable for self-hosted [closes DOC-1128] #4050

New Issue
Closed
opened 2026-06-05 18:54:00 -04:00 by yindo · 0 comments
yindo commented 2026-06-05 18:54:00 -04:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/langchain-ai/docs/pull/4044
Author: @open-swe[bot]
Created: 5/18/2026
Status: ✅ Merged
Merged: 5/20/2026
Merged by: @katmayb

Base: main ← Head: open-swe/doc-1128-bedrock-iam-note

📝 Commits (3)

  • 46001a0 docs: note IAM trusted entity not applicable for self-hosted [DOC-1128]
  • 87c6dbc Apply suggestion from @katmayb
  • 65df481 Apply suggestion from @katmayb

📊 Changes

1 file changed (+4 additions, -0 deletions)

View changed files

📝 src/langsmith/playground-model-providers.mdx (+4 -0)

📄 Description

Description

Add an inline note in the AWS Bedrock "IAM trusted entity (recommended)" section of the Playground model providers docs clarifying that this auth method is hidden in the Playground UI on self-hosted LangSmith, and pointing users to Access Keys (or the Bedrock API Key) instead. Only this section is affected.

Release Note

none

Test Plan

  • Verify the new note renders inside the "IAM trusted entity (recommended)" subsection on the Playground model providers page.

Opened collaboratively by Kathryn May and open-swe.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/langchain-ai/docs/pull/4044 **Author:** [@open-swe[bot]](https://github.com/apps/open-swe) **Created:** 5/18/2026 **Status:** ✅ Merged **Merged:** 5/20/2026 **Merged by:** [@katmayb](https://github.com/katmayb) **Base:** `main` ← **Head:** `open-swe/doc-1128-bedrock-iam-note` --- ### 📝 Commits (3) - [`46001a0`](https://github.com/langchain-ai/docs/commit/46001a0fe1ccff5fd58063c9a6518f2c1e9da0bf) docs: note IAM trusted entity not applicable for self-hosted [DOC-1128] - [`87c6dbc`](https://github.com/langchain-ai/docs/commit/87c6dbca0a2c55e8beab6e1c5652c8cb0d81bc9d) Apply suggestion from @katmayb - [`65df481`](https://github.com/langchain-ai/docs/commit/65df481d38900df3de084342d3fc93d8e85e3980) Apply suggestion from @katmayb ### 📊 Changes **1 file changed** (+4 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `src/langsmith/playground-model-providers.mdx` (+4 -0) </details> ### 📄 Description ## Description Add an inline note in the AWS Bedrock "IAM trusted entity (recommended)" section of the Playground model providers docs clarifying that this auth method is hidden in the Playground UI on self-hosted LangSmith, and pointing users to Access Keys (or the Bedrock API Key) instead. Only this section is affected. ## Release Note none ## Test Plan - [ ] Verify the new note renders inside the "IAM trusted entity (recommended)" subsection on the Playground model providers page. _Opened collaboratively by Kathryn May and open-swe._ --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-06-05 18:54:00 -04:00
yindo closed this issue 2026-06-05 18:54:00 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
deepagents
docs-infra
external
external
help wanted
integration
internal
internal
javascript
js/ts
langchain
langgraph
langsmith
needs-title
pull-request
Mirrored from GitHub Pull Request
 python
reference
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langchain-ai/docs#4050
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?