[PR #1416] [CLOSED] docs: correct the Bedrock connection options against the AWS and Lite… #1380

New issue

Closed

opened 2026-10-18 14:19:16 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-18 14:19:16 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/open-webui/docs/pull/1416
Author: @JGoutin
Created: 9/18/2026
Status: ❌ Closed

Base: main ← Head: bedrock

📝 Commits (1)

c8e7619 docs: correct the Bedrock connection options against the AWS and LiteLLM docs

📊 Changes

3 files changed (+102 additions, -84 deletions)

View changed files

📝 docs/getting-started/quick-start/connect-a-provider/starting-with-openai-compatible.mdx (+102 -84)
➖ static/images/tutorials/amazon-bedrock/amazon-bedrock-proxy-api.png (+0 -0)
➖ static/images/tutorials/amazon-bedrock/amazon-bedrock-proxy-connection.png (+0 -0)

📄 Description

AWS deprecated and archived the Bedrock Access Gateway on 2026-09-04, pointing users at Bedrock's native OpenAI-compatible APIs instead. Also update other gateways' information.

Summary

Reduce BAG to a deprecation note plus the settings an existing deployment needs.
Add the native Bedrock endpoints as the first option, covering both bedrock-runtime (AWS's recommendation for new applications) and bedrock-mantle, and note that only bedrock-mantle serves /models.
Update the comparison table around Open WebUI capabilities and Gateways capabilities.
Give each live option an explicit trade-offs block.

Checklist

I have reviewed the relevant documentation and matched the existing style.
This PR meets Open WebUI's contribution standards: it is accurate, relevant to users, narrowly scoped, maintainable, and not promotional content, advertising, lead generation, SEO placement, or a request to list a product, service, provider, integration, gateway, tool, or company primarily for visibility.
I understand that PRs that do not meet these standards may be closed without review and will not be merged. Repeated, low-quality, off-topic, promotional, or intentionally misleading submissions may result in the contributor being blocked from future participation in Open WebUI repositories.

_{🔄 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/open-webui/docs/pull/1416 **Author:** [@JGoutin](https://github.com/JGoutin) **Created:** 9/18/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `bedrock` --- ### 📝 Commits (1) - [`c8e7619`](https://github.com/open-webui/docs/commit/c8e76195241c946a3c6fbcb0020371f113ab5bca) docs: correct the Bedrock connection options against the AWS and LiteLLM docs ### 📊 Changes **3 files changed** (+102 additions, -84 deletions) <details> <summary>View changed files</summary> 📝 `docs/getting-started/quick-start/connect-a-provider/starting-with-openai-compatible.mdx` (+102 -84) ➖ `static/images/tutorials/amazon-bedrock/amazon-bedrock-proxy-api.png` (+0 -0) ➖ `static/images/tutorials/amazon-bedrock/amazon-bedrock-proxy-connection.png` (+0 -0) </details> ### 📄 Description AWS deprecated and archived the Bedrock Access Gateway on 2026-09-04, pointing users at Bedrock's native OpenAI-compatible APIs instead. Also update other gateways' information. ## Summary - Reduce BAG to a deprecation note plus the settings an existing deployment needs. - Add the native Bedrock endpoints as the first option, covering both bedrock-runtime (AWS's recommendation for new applications) and bedrock-mantle, and note that only bedrock-mantle serves /models. - Update the comparison table around Open WebUI capabilities and Gateways capabilities. - Give each live option an explicit trade-offs block. ## Checklist - [x] I have reviewed the relevant documentation and matched the existing style. - [x] This PR meets Open WebUI's contribution standards: it is accurate, relevant to users, narrowly scoped, maintainable, and not promotional content, advertising, lead generation, SEO placement, or a request to list a product, service, provider, integration, gateway, tool, or company primarily for visibility. - [x] I understand that PRs that do not meet these standards may be closed without review and will not be merged. Repeated, low-quality, off-topic, promotional, or intentionally misleading submissions may result in the contributor being blocked from future participation in Open WebUI repositories. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi

2026-10-18 14:19:16 +00:00