Replicate to InfluxDB 3 Cloud

Use EDR to replicate data from InfluxDB 3 Enterprise to InfluxDB 3 Cloud. This guide covers only what’s different when Cloud is the destination—auth and endpoint. For shared configuration (token store, historic_fill, scope, bandwidth scheduling), see Configuration file reference.

Direct mode: write straight to InfluxDB 3 Cloud

When the destination does not run an EDR agent, EDR replicates directly to a plain InfluxDB v3 write endpoint:

downstream:
  name: "cloud-influx"
  address: "https://cloud.influxdata.com"
  auth_token: "cloud-api-token"
  mode: direct

In direct mode:

• There is no /connect handshake.
• Health checks use the destination’s GET /health.
• No topology is propagated to the destination.
• Auth failures and schema conflicts are handled identically to agent-to-agent mode.
• The pt wire encoding is not available—direct mode always uses lp (Line Protocol).

Replace cloud-api-token with a token-store entry containing an InfluxDB 3 Cloud API token with write access to the target database. See Manage tokens.

Compatibility

EDR’s agent-to-agent compatibility matrix (protocol version negotiation, storage-format preflight) applies to hops between two influxdb3-edr agents. A direct-mode connection to InfluxDB 3 Cloud doesn’t negotiate an agent protocol version—the InfluxDB 3 write API itself governs compatibility. See Compatibility for the full agent-to-agent and agent-to-InfluxDB compatibility matrices.

Next

• Size WAL retention on the source Enterprise instance to cover your expected outage windows.
• Monitor EDR to watch replication health and lag to Cloud.