CompatibilityDatabaseTypes.md

Database type compatibility

This document is part of the Compatibility Guide and explains plugin compatibility with various database types and deployments. Some plugins require specific metadata from particular database types to function properly.

For example, the limitless plugin is incompatible with Aurora Global Database because it's built on different architectural principles than Limitless Database. Aurora Global Database doesn't use transaction routers and doesn't provide the transaction routers' metadata. This lack of required metadata makes it incompatible with the limitless plugin.

For Aurora Global Database configuration details, see Aurora Global Databases.

Legend: ✅ compatible  |  ❌ incompatible / no added value

Plugin code / Database type	Aurora Global Database (MySQL and PG)	Aurora Cluster (MySQL and PG)	RDS Multi-AZ DB Cluster (3 instances) (MySQL and PG)
custom_endpoint	✅	✅	✅
host_monitoring (EFM v1)	✅	✅	✅
host_monitoring_v2 (EFM v2)	✅	✅	✅
failover	✅	✅	✅
failover_v2	✅	✅	✅
gdb_failover	✅	✅	✅
iam	✅	✅	✅
aws_secrets_manager	✅	✅	✅
federated_auth	✅	✅	✅
okta	✅	✅	✅
stale_dns	✅	✅	✅
read_write_splitting	✅	✅	✅
srw	✅	✅	✅
gdb_rw	✅	✅	✅
aurora_connection_tracker	✅	✅	✅
connect_time	✅	✅	✅
fastest_response_strategy	✅	✅	✅
initial_connection	✅	✅	✅
limitless	❌	✅ (PostgreSQL only)	✅
bg	❌	✅	❌

Plugin code / Database type	RDS Multi-AZ DB Instance (2 instances) (MySQL and PG)	RDS Single-AZ Instance (1 instance) (MySQL and PG)	Community Database (MySQL and PG)
custom_endpoint	❌	❌	❌
host_monitoring (EFM v1)	✅	✅	✅
host_monitoring_v2 (EFM v2)	✅	✅	✅
failover	❌	❌	❌
failover_v2	❌	❌	❌
gdb_failover	❌	❌	❌
iam	✅	✅	❌
aws_secrets_manager	✅	✅	❌
federated_auth	✅	✅	❌
okta	✅	✅	❌
stale_dns	❌	❌	❌
read_write_splitting	❌	❌	❌
srw	✅	❌	✅
gdb_rw	❌	❌	❌
aurora_connection_tracker	❌	❌	❌
connect_time	✅	✅	✅
fastest_response_strategy	❌	❌	❌
initial_connection	❌	❌	❌
limitless	❌	❌	❌
bg	✅	✅	❌

The connect_time, execute_time, and dev plugins are compatible with every database type (see Universally Compatible Plugins).