DigitalOcean Managed Database Guide

Use this page when your source or target is hosted in a DigitalOcean managed database.

This guide focuses on the provider-specific parts of the setup:

• trusted-source network allowlisting
• managed MySQL and managed PostgreSQL connection details
• DigitalOcean-specific constraints around CDC-related settings

For the core workflow split, use:

• MySQL Server Configuration
• PostgreSQL Server Configuration
• MySQL CDC Source Configuration
• PostgreSQL CDC Source Configuration

Base setup

1. Open the DigitalOcean console and select the managed database cluster.
2. Note the host, port, database name, username, and password.
3. Add the DBConvert Streams deployment IP address or range to Trusted Sources.
4. Confirm the workflow: Load only, or MySQL/PostgreSQL CDC source.

Network access

DigitalOcean managed databases rely on trusted-source allowlisting. Before you create a stream:

• add the DBConvert Streams deployment IP or range
• wait for the rule to propagate
• test the connection from the Data Explorer sidebar (right-click → Test connection) or from the connection editor

Managed MySQL notes

DigitalOcean managed MySQL typically exposes binlog behavior as a managed service capability rather than a fully user-tuned MySQL instance.

Use this page conservatively:

• verify binlog-related settings if the provider exposes them
• do not assume every low-level MySQL replication setting is customer-configurable
• follow MySQL CDC Source Configuration for the DBConvert Streams-side CDC requirements

Helpful checks:

SHOW VARIABLES LIKE 'binlog_format';
SHOW VARIABLES LIKE 'binlog_row_image';
SHOW BINARY LOG STATUS;

Managed PostgreSQL notes

DigitalOcean managed PostgreSQL may expose logical-replication capability, but managed limits still apply.

Use this page conservatively:

• verify logical replication prerequisites if the provider exposes them
• do not assume unrestricted access to every PostgreSQL replication setting
• follow PostgreSQL CDC Source Configuration for the DBConvert Streams-side CDC requirements

Helpful checks:

SHOW wal_level;

SELECT name, setting
FROM pg_settings
WHERE name IN (
  'wal_level',
  'max_replication_slots',
  'max_wal_senders'
);

Validation checklist

1. Test the managed database connection from the Data Explorer sidebar (right-click → Test connection) or from the connection editor. If it fails, confirm the deployment IP is listed in Trusted Sources.
2. Open it in Data Explorer to confirm visible objects.
3. For MySQL CDC, run SHOW GRANTS and verify the user has replication-related privileges. If SUPER or REPLICATION SLAVE is missing, contact DigitalOcean support or use Load mode instead.
4. For PostgreSQL CDC, run SHOW wal_level and confirm it returns logical. If DigitalOcean does not expose this setting, CDC may not be available on this managed tier.

Related docs

• MySQL Server Configuration
• PostgreSQL Server Configuration
• MySQL CDC Source Configuration
• PostgreSQL CDC Source Configuration