AWS Security ChangesHomeSearch

AWS athena: Clarify NonProxyHost and proxy scope behavior in ODBC driver v2.4.0.0

Service: athena · 2026-09-29 · Documentation medium

File: athena/latest/ug/odbc-v2-driver-proxy-options.md · Type: network

Summary

Documents that NonProxyHost is now passed to the AWS SDK client configuration (with no effect on Windows in 2.4.0.0, routing all traffic through ProxyHost), that ProxyHost is applied to SDK-created identity provider clients even when UseProxyForIdP=0, and that proxy/CA settings for SDK-created clients are process-wide and may leak from the most recently initialized connection to concurrent connections.

Security assessment

This is network egress/proxy configuration detail: on Windows the bypass list is ignored so all traffic is forced through ProxyHost, and proxy/CA settings are process-wide, meaning one DSN's proxy or CA settings can silently apply to SDK HTTP clients created by other concurrent connections - a genuine traffic-routing/trust-anchor concern worth documenting even though no defect or CVE is cited.

Evidence

+In driver version 2.4.0.0, this parameter has no effect on Windows. The Windows HTTP client does not apply a proxy bypass list, so the driver routes all traffic through the proxy that you specify in `ProxyHost`.

Diff

diff --git a/athena/latest/ug/odbc-v2-driver-proxy-options.md b/athena/latest/ug/odbc-v2-driver-proxy-options.md
index ddd6600e9..68bbf9fca 100644
--- a//athena/latest/ug/odbc-v2-driver-proxy-options.md
+++ b//athena/latest/ug/odbc-v2-driver-proxy-options.md
@@ -47 +47,5 @@ Use this optional parameter to specify a host that the driver connects to withou
-The `NonProxyHost` connection parameter is passed to the `CURLOPT_NOPROXY` curl option. For information about the `CURLOPT_NOPROXY` format, see [CURLOPT_NOPROXY](https://curl.se/libcurl/c/CURLOPT_NOPROXY.html) in the curl documentation.
+The driver passes this value to the AWS SDK client configuration and applies it to HTTP clients that the SDK creates internally. On Linux and macOS, the SDK forwards the value to the `CURLOPT_NOPROXY` curl option. For information about the `CURLOPT_NOPROXY` format, see [CURLOPT_NOPROXY](https://curl.se/libcurl/c/CURLOPT_NOPROXY.html) in the curl documentation.
+
+###### Windows behavior
+
+In driver version 2.4.0.0, this parameter has no effect on Windows. The Windows HTTP client does not apply a proxy bypass list, so the driver routes all traffic through the proxy that you specify in `ProxyHost`.
@@ -51 +55 @@ The `NonProxyHost` connection parameter is passed to the `CURLOPT_NOPROXY` curl
-NonProxyHost | Optional | `none` | `NonProxyHost=.amazonaws.com,localhost,.example.net,.example.com;`  
+NonProxyHost | Optional | `none`. See Windows behavior. | `NonProxyHost=.amazonaws.com,localhost,.example.net,.example.com;`  
@@ -55 +59,5 @@ NonProxyHost | Optional | `none` | `NonProxyHost=.amazonaws.com,localhost,.examp
-Enables user traffic through the specified proxy.
+Enables the specified proxy for AWS SDK service clients and HTTP clients that the AWS SDK creates internally. In driver version 2.4.0.0, the driver also applies this proxy to both driver-owned and SDK-created identity provider HTTP clients, even when `UseProxyForIdP` is set to `0`.
+
+###### Process-wide settings for concurrent connections
+
+Proxy and CA settings applied to SDK-created clients are process-wide. If you use different DSNs for multiple connections at the same time, the settings from your most recently initialized connection apply to subsequently created SDK-internal HTTP clients.