You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
[FOR CHINESE USERS] 请务必使用英文提交 Issue,否则会被关闭。谢谢!:)
Please do not modify this template :) and fill in all the required fields.
1. Is this request related to a challenge you're experiencing? Tell me about your story.
Yes, this request is directly related to the challenge I'm currently experiencing.
I'm deploying and using AWS Bedrock services in an enterprise environment, but due to our company's network security policies, all external AWS service access must go through the company's proxy server. Currently, the system doesn't allow configuring a custom Bedrock endpoint URL, which prevents us from properly connecting to the service.
Specifically, the challenges are:
Company policy requires all outbound traffic to go through corporate proxy
Default AWS Bedrock endpoints are not directly accessible
Need to use specific internal endpoints to ensure compliance and security
I believe other users working with this service in enterprise environments might face similar situations. Adding the bedrock_endpoint_url configuration option would help resolve this issue, making the system more flexible and adaptable.
2. Additional context or comments
No response
3. Can you help us with this feature?
I am interested in contributing to this feature.
The text was updated successfully, but these errors were encountered:
Self Checks
1. Is this request related to a challenge you're experiencing? Tell me about your story.
Yes, this request is directly related to the challenge I'm currently experiencing.
I'm deploying and using AWS Bedrock services in an enterprise environment, but due to our company's network security policies, all external AWS service access must go through the company's proxy server. Currently, the system doesn't allow configuring a custom Bedrock endpoint URL, which prevents us from properly connecting to the service.
Specifically, the challenges are:
I believe other users working with this service in enterprise environments might face similar situations. Adding the
bedrock_endpoint_url
configuration option would help resolve this issue, making the system more flexible and adaptable.2. Additional context or comments
No response
3. Can you help us with this feature?
The text was updated successfully, but these errors were encountered: