[PR #12838] feat: bedrock_endpoint_url #27761

Closed
opened 2026-02-21 20:42:09 -05:00 by yindo · 0 comments
Owner

Original Pull Request: https://github.com/langgenius/dify/pull/12838

State: closed
Merged: Yes


add bedrock_endpoint_url for users who need a proxy

Summary

Added bedrock_endpoint_url configuration option to allow users to customize the AWS Bedrock endpoint URL. This change is primarily intended for:

  1. Users who need to access Bedrock services through a proxy
  2. Users utilizing private VPC endpoints
  3. Users who need to connect to Bedrock services in different regions

Motivation and Context

In certain enterprise environments, network security policies require accessing AWS Bedrock services through specific proxies or private endpoints. Adding this configuration option enhances system flexibility, enabling service usage across more scenarios.

Dependencies

  • No new dependencies added
  • Compatible with existing AWS Bedrock client configuration

Fixes #12926

Screenshots

| Before | After |
|image|image|

Checklist

Important

Please review the checklist below before submitting your pull request.

  • This change requires a documentation update, included: Dify Document
  • I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!)
  • I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change.
  • I've updated the documentation accordingly.
  • I ran dev/reformat(backend) and cd web && npx lint-staged(frontend) to appease the lint gods
**Original Pull Request:** https://github.com/langgenius/dify/pull/12838 **State:** closed **Merged:** Yes --- add bedrock_endpoint_url for users who need a proxy # Summary Added `bedrock_endpoint_url` configuration option to allow users to customize the AWS Bedrock endpoint URL. This change is primarily intended for: 1. Users who need to access Bedrock services through a proxy 2. Users utilizing private VPC endpoints 3. Users who need to connect to Bedrock services in different regions ### Motivation and Context In certain enterprise environments, network security policies require accessing AWS Bedrock services through specific proxies or private endpoints. Adding this configuration option enhances system flexibility, enabling service usage across more scenarios. ### Dependencies - No new dependencies added - Compatible with existing AWS Bedrock client configuration Fixes #12926 # Screenshots | Before | After | |<img width="639" alt="image" src="https://github.com/user-attachments/assets/fd435089-b730-46dd-9918-1fab6ae23af6" />|<img width="638" alt="image" src="https://github.com/user-attachments/assets/d7cc3376-28e1-4023-b9b0-95a8c36087ae" />| # Checklist > [!IMPORTANT] > Please review the checklist below before submitting your pull request. - [ ] This change requires a documentation update, included: [Dify Document](https://github.com/langgenius/dify-docs) - [x] I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!) - [x] I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change. - [x] I've updated the documentation accordingly. - [x] I ran `dev/reformat`(backend) and `cd web && npx lint-staged`(frontend) to appease the lint gods
yindo added the pull-request label 2026-02-21 20:42:09 -05:00
yindo closed this issue 2026-02-21 20:42:09 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#27761