SQL errors after enabling Multi AZ plugin

[trixpan]

Describe the bug

a number of errors will show up on logs (on RDS side or via finest logging) when enabling Multi AZ flavour on RDS.

The issue seems to be related to a mix between sparse documentation on what exactly is needed on the RDS side (i.e. what grant to provide to a non super admin user) for the plugin to work

Expected Behavior

The documentation actually explains how to use the required extensions and they work

What plugins are used? What other connection properties were set?

wrapperDialect=rds-multi-az-pg-cluster&wrapperPlugins=auroraConnectionTracker,failover2,efm2,iam&sslmode=verify-ca&sslrootcert=/etc/ca/cacerts.pem}

Current Behavior

2025-08-13 11:09:14,102 WARNING [software.amazon.jdbc.hostlistprovider.monitoring.ClusterTopologyMonitorImpl] (AWS JDBC Driver mactmi-1) The topology query returned an invalid topology - no writer instance detected.

Reproduction Steps

Create RDS, enable delegated extensions;

create DB1, create non-admin-username to access DB1

as superadmin:

CREATE EXTENSION IF NOT EXISTS rds_tools;
GRANT EXECUTE ON ALL FUNCTIONS IN SCHEMA rds_tools TO non-admin-username;

Possible Solution

No response

Additional Information/Context

No response

The AWS Advanced JDBC Driver version used

2.6.1

JDK version used

java -version openjdk version "17.0.16" 2025-07-15 LTS OpenJDK Runtime Environment (Red_Hat-17.0.16.0.8-1) (build 17.0.16+8-LTS) OpenJDK 64-Bit Server VM (Red_Hat-17.0.16.0.8-1) (build 17.0.16+8-LTS, mixed mode, sharing)

Operating System and version

RHEL

[trixpan]

downgrading to 2.6.0 and adding clusterId=<value> to connection props seems to suppress the error.

not related to clusterId or the version. The error messages vanish about 14 minutes after the initial connection.

The required access to non super admins still an issue the documentation could be more detailed.