Skip to main content

Destinations

A stream writes to exactly one destination in your account. Bucket destinations receive gzip NDJSON objects; table destinations receive rows appended through their catalog. Both use the layout in Delivery format.

Settings are stored as plain configuration; credentials are stored encrypted in Supabase Vault and never shown again.

KindSettingsCredentialsA batch is delivered when
Amazon S3bucket, region, prefix, role_arnnone: Send2Bucket assumes your role with an external IDS3 confirms the object write
Google Cloud Storagebucket, prefixnone: you grant Send2Bucket's service accountThe upload succeeds
S3-compatible storagebucket, endpoint, region, prefix, addressingaccess_key_id, secret_access_keyThe endpoint confirms the object write
DuckLakedata_path, metadata_schema, namespace, tablecatalog_dsn, access_key_id, secret_access_key, region, endpointThe DuckLake transaction commits
Apache Icebergcatalog_uri, warehouse, namespace, tabletoken, access_key_id, secret_access_key, region, endpointThe catalog confirms the append snapshot
Amazon S3 Tablestable_bucket_arn, region, role_arn, namespace, tablenone: Send2Bucket assumes your role with an external IDThe append snapshot commits
Supabase Analytics Bucketsproject_ref, warehouse, region, namespace, tablecatalog_token, access_key_id, secret_access_keyThe catalog confirms the snapshot

Pick the destination your query engine reads best. Querying lists which engine reads which destination.

Access Send2Bucket needs​

Credentials should allow only what delivery needs: writing objects or table data, and reading back what Send2Bucket wrote so it can verify a write after a lost response.

During setup Send2Bucket checks the destination before the stream accepts data. For a bucket it writes a test object under your prefix and reads it back. For a table it creates the table in the namespace you name if it is missing, or checks that an existing table has the expected columns; an incompatible table is left untouched and setup fails with incompatible table: …. A verified destination becomes active; see Destination status.