NO_PROXY support for AWS Bedrock Chat Model

Questions
,
1

Describe the problem/error/question

The AWS Bedrock Chat Model Node currently has a documented limitation stating it doesn’t support the NO_PROXY environment variable. This is problematic for enterprise environments where:

  1. A proxy is required to access the internet

  2. Internal AWS services (like Bedrock endpoints within the same VPC/region) should bypass the proxy for better performance and security

  3. The NO_PROXY variable is the standard way to exclude certain domains/IPs from proxy routing

Feature Request: Add support for the NO_PROXY environment variable to the AWS Bedrock Chat Model Node, allowing internal AWS service endpoints to bypass the configured proxy while still routing external traffic through it.

Use Case:
We’re running n8n on AWS EKS in a shared enterprise network where:

  • All internet traffic must go through a corporate proxy

  • AWS Bedrock endpoints are accessible directly within our VPC

  • Using the proxy for Bedrock requests adds unnecessary latency and potential failure points

What is the error message (if any)?

Connection timeout or proxy-related errors when the Bedrock endpoint should be accessible directly without proxy.

Please share your workflow

N/A - This is a feature request for proxy configuration support rather than a specific workflow issue.

Information on your n8n setup

  • n8n version: [Your version]

  • Database: [Your database, e.g., PostgreSQL]

  • n8n EXECUTIONS_PROCESS setting: [e.g., main]

  • Running n8n via: Docker on AWS EKS

  • Operating system: Linux (EKS/Kubernetes)