From: sergiyvamz (@sergiyvamz) <noreply+sergiyvamz@github.com>
To: aws/aws-advanced-jdbc-wrapper <noreply+aws-aws-advanced-jdbc-wrapper@github.com>
Subject: Re: [aws/aws-advanced-jdbc-wrapper] issue #2240: 4.6.0: connections through RDS Proxy are refused after the first ("RDS Proxy currently doesn't support command-line options")
Date: Thu, 19 Nov 2026 23:42:00 +0000
Message-ID: <gh-aws-aws-advanced-jdbc-wrapper-2240-c7025383773@github.com> (raw)
In-Reply-To: <gh-aws-aws-advanced-jdbc-wrapper-2240@github.com>
References: <gh-aws-aws-advanced-jdbc-wrapper-2240@github.com>
Hi @driedelreply,
The fix is now released in [4.7.0](https://github.com/aws/aws-advanced-jdbc-wrapper/releases/tag/4.7.0) (#2252). The wrapper no longer sends connection metadata to RDS Proxy endpoints, so connections through the proxy work as they did in 4.5.0.
4.7.0 also adds the `enableConnectionMetadata` property. If your RDS Proxy is behind a custom DNS name, the wrapper can't recognize it as a proxy, so set `enableConnectionMetadata=false` in that case.
Could you let us know how it works with your RDS Proxy setup? We'll close this issue once you confirm, or in a couple of weeks if we don't hear back.
Thank you!