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: Mon, 16 Nov 2026 16:21:55 +0000
Message-ID: <gh-aws-aws-advanced-jdbc-wrapper-2240-c6922173529@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,
Thanks for the detailed report. We confirmed it on `main`: since 4.6.0, `AuroraPgDialect` always adds `-c aurora.connection_str=...` to `options`, and RDS Proxy refuses connections that carry command-line options.
Until a fix is available, you can stay on 4.6.0 by setting the dialect explicitly:
```
wrapperDialect=rds-pg
```
When `wrapperDialect` is set, the wrapper uses that dialect as-is and doesn't switch it to Aurora PostgreSQL after connecting. The RDS PostgreSQL dialect doesn't add the `options` value. Your setup only uses the `iam` plugin through the proxy, and the proxy hides the cluster topology anyway, so you shouldn't lose any functionality. Staying on 4.5.0 also works, as you mentioned.
Both of your suggested fixes make sense. One is to skip the option for RDS Proxy hosts. The other is a property that turns the connection metadata off, which would also cover a proxy behind a custom DNS name. We'll update this issue when a fix lands.
Could you let us know whether the `wrapperDialect=rds-pg` workaround works for you?
Thank you!