- Newest
- Most votes
- Most comments
Hello.
I tested it on my AWS account.
I created a VPC endpoint for EC2 and bedrock-runtime in the Singapore region to access us-west-2.
As a result, we were able to run the us-west-2 model and confirm the response.
I was able to confirm the response with the guardrails in place.
As of June 2025, testing has shown that it is not possible to access Bedrock in another region from a VPC endpoint in another region.
aws bedrock-runtime invoke-model --model-id amazon.titan-text-express-v1 --body '{"inputText": "Describe the purpose of a \"hello world\" program in one line.", "textGenerationConfig": {"maxTokenCount": 512, "temperature": 0.5, "topP": 0.9}}' --cli-binary-format raw-in-base64-out invoke-model-output-text.txt --region us-west-2 --endpoint-url https://vpce-1234567890-1234567.bedrock-runtime.ap-southeast-1.vpce.amazonaws.com
aws bedrock-runtime invoke-model --model-id amazon.titan-text-express-v1 --body '{"inputText": "Describe the purpose of a \"hello world\" program in one line.", "textGenerationConfig": {"maxTokenCount": 512, "temperature": 0.5, "topP": 0.9}}' --cli-binary-format raw-in-base64-out invoke-model-output-text.txt --region us-west-2 --guardrail-identifier iftck9dvp3w5 --guardrail-version 1 --endpoint-url https://vpce-1234567890-1234567.bedrock-runtime.ap-southeast-1.vpce.amazonaws.com
An error occurred (InvalidSignatureException) when calling the InvokeModel operation: Credential should be scoped to a valid region.
It seems that VPC endpoints recently became capable of cross-region access, and when I checked with the AWS CLI, it appeared that they could be used with Bedrock as well.
https://aws.amazon.com/jp/blogs/networking-and-content-delivery/introducing-cross-region-connectivity-for-aws-privatelink/
Therefore, if you want to access Bedrock in another region via a VPC endpoint, you need to connect to a VPC in the same region as Bedrock using VPC peering or similar, as described in the following document, and then connect to the VPC endpoint.
https://repost.aws/knowledge-center/vpc-endpoints-cross-region-aws-services

I followed the instructions from the blog you shared and was able to use a VPC endpoint to connect with a VPC endpoint service in a different region. However, it still doesn't work when trying to access Bedrock across regions via VPCe. I also noticed from the blog that:
"Considerations Providers
That mean I can't use "com.amazonaws.us-west-2.bedrock-runtime" at this time. Is that correct?
Apologies if I’ve misunderstood anything—I'm still fairly new to setting up VPC endpoints.
Sorry. I tried setting it up again with my AWS account and testing it, but I was unable to connect. Therefore, you cannot access Bedrock in another region from a VPC endpoint in another region. Therefore, if you want to access Bedrock in another region via a VPC endpoint, you need to connect to a VPC in the same region as Bedrock using VPC peering or similar, as described in the following document, and then connect to the VPC endpoint. https://repost.aws/knowledge-center/vpc-endpoints-cross-region-aws-services