Region issue when running aws-dataprocessing-mcp-server on Bedrock AgentCore Runtime

[gians14ga]

Region issue when running aws-dataprocessing-mcp-server on Bedrock AgentCore Runtime (eu-west-1)

Hi,

I am running mcp/aws-dataprocessing-mcp-server:latest as a container inside Amazon Bedrock AgentCore Runtime in eu-west-1.

The entire infrastructure is deployed in eu-west-1, including:

• Bedrock AgentCore Runtime
• Glue Data Catalog
• Athena workgroups
• S3 buckets

However, when the MCP server makes calls to Glue or Athena, the requests are sent to us-east-1 by default.

This results in:

• Glue databases not being found
• Athena not seeing the expected catalog
• General region mismatch issues

From what I understand:

• The container is executed in eu-west-1
• No explicit region is passed via environment variables by AgentCore Runtime
• The MCP server might be creating boto3 clients without explicitly setting region_name

What I already tried:

1. I built a custom image starting from mcp/aws-dataprocessing-mcp-server:latest, adding:

   ENV AWS_REGION=eu-west-1
   ENV AWS_DEFAULT_REGION=eu-west-1

Then I pushed this custom image to ECR in eu-west-1 and used it in AgentCore Runtime.
2. I also explicitly configured the following environment variables in the Bedrock AgentCore Runtime configuration:

• AWS_REGION=eu-west-1
• AWS_DEFAULT_REGION=eu-west-1

Despite this, the MCP server still appears to make calls against us-east-1.

Questions:

1. Does the aws-dataprocessing-mcp-server explicitly hardcode us-east-1 anywhere?
2. Does Bedrock AgentCore Runtime inject AWS_REGION or AWS_DEFAULT_REGION automatically?
3. What is the recommended way to configure the region when running this MCP server inside AgentCore Runtime?

Thanks in advance for any clarification.

[aniruddhaadak80]

The fact that both AWS_REGION and AWS_DEFAULT_REGION are set but calls still appear to land in us-east-1 makes this sound less like an environment issue and more like a client construction path that is either hardcoding a default or bypassing the expected session config.nnIf the maintainers can point to where the Glue and Athena clients are instantiated, that will probably answer most of the mystery. Right now the strongest clue is that your runtime region and your service region are aligned, but the SDK behavior is not.