When connecting using 2 different drivers (e.g. AWS Wrapper and MySQL driver) and 2 different urls (e.g. jdbc:mysql: and jdbc:aws-wrapper:mysql) connect instance picks the first random driver and uses it for all connectors.
This behavior might lead to java.sql.SQLException: No suitable driver found for, because one driver recognizes the URL and the other one not.
The solution is to fix DatabaseDialects static map or support explicit driver class name in the configuration.