The Bedrock provider currently always routes requests to AWS's native Bedrock endpoints, with no way to point at a different host. Some organizations run an internal proxy or gateway in front of Bedrock's invoke API for network control, auditing, or centralized access management, and need requests to go through that proxy instead of directly to AWS. The underlying AI SDK (@ai-sdk/amazon-bedrock v4+, already in use by Port) natively supports a baseURL override alongside its existing credential options, so adding an optional baseUrl config field to Port's Bedrock provider would unblock proxy-fronted Bedrock deployments without changing the default AWS-direct behavior.