Skip to main content

Cross-Plugin Compatibility

This page is part of the Compatibility Guide and explains compatibility between plugins. Combining plugins in one configuration is normal, but some plugins do not work correctly together, either because of a design constraint, a logical conflict, or because the combination is meaningless.

Legend: ✅ compatible · ❌ not compatible · a numbered footnote [^n] links to the reason in Notes · — same plugin

This is a lower-triangular matrix: each plugin pair is shown only once. To keep it compact, a pair appears in just one place — so a blank cell does not mean "unknown." If a cell is blank, find that pair the other way around: look up the other plugin's row and scan across to this plugin's column. Because the plugins are split across more than one table for width, the other orientation of a pair may also be in a different table below. Read a row against the columns; any reason a pair is incompatible is given as a numbered footnote in Notes.

Columns: custom_endpoint, failover, gdb_failover, iam

Plugincustom_endpointfailovergdb_failoveriam
custom_endpoint—
failover✅—
gdb_failover❌ 1❌ 2—
iam✅✅✅—
secrets_manager✅✅✅❌ 3
initial_connection✅✅✅✅
bg❌ 4✅❌ 5✅
kms_encryption✅✅✅✅

Columns: secrets_manager, initial_connection, bg, kms_encryption

Pluginsecrets_managerinitial_connectionbgkms_encryption
secrets_manager—
initial_connection✅—
bg✅✅—
kms_encryption✅✅✅—

Notes​

Footnotes​

  1. Meaningless: a custom endpoint is a single-region Aurora cluster construct, while gdb_failover operates across regions on a global database. ↩

  2. Both drive cluster failover; gdb_failover is the region-aware superset, so running both means two components contend over reconnection and topology. ↩

  3. Two authentication plugins both trying to set the connection credential; only one authentication plugin may be active at a time. ↩

  4. Meaningless: a Blue/Green switchover replaces the whole deployment, so a custom endpoint's hand-picked instance subset does not carry over. ↩

  5. Meaningless: Blue/Green deployments are not supported on Aurora global databases. ↩