The AWS Advanced JDBC Wrapper uses plugins to execute JDBC methods. You can think of a plugin as an extensible code module that adds additional logic around JDBC method calls. Plugins are designed with the intention of being compatible with each other; however, there are logical constraints related to database type or database features that can make plugins inefficient in certain configurations.
For example, RDS Single-AZ Instance deployments do not support failover, so the failover and failover2 plugins are marked as incompatible. If either of these plugins is included in the driver configuration, there will be no added value. However, these unnecessary plugins will function without errors and will simply consume additional resources.
The following matrices help verify plugin compatibility with other plugins and with various database types. Some plugins are sensitive to the database URL provided in the connection string, and this is also presented below.
We encourage users to verify their configurations and ensure that their configuration contains no incompatible components.
The following plugins operate independently of connection management and are compatible with all plugins, database types, and endpoint types:
| Plugin | Description |
|---|---|
| kmsEncryption | Transparent column-level encryption using AWS KMS. |
| remoteQueryCache | Caches read-only query results in a remote Valkey cache using SQL query hints. |
| driverMetaData | Overrides driver metadata information reported to the database. |
| dev | Developer utility plugin for debugging and diagnostics. |
| executionTime | Logs the time taken to execute any JDBC method. |
| logQuery | Tracks and logs the SQL statements to be executed. |
| dataCache | Caches results locally from SQL queries matching a configured trigger condition. |