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.
| Kind | Settings | Credentials | A batch is delivered when |
|---|---|---|---|
| Amazon S3 | bucket, region, prefix, role_arn | none: Send2Bucket assumes your role with an external ID | S3 confirms the object write |
| Google Cloud Storage | bucket, prefix | none: you grant Send2Bucket's service account | The upload succeeds |
| S3-compatible storage | bucket, endpoint, region, prefix, addressing | access_key_id, secret_access_key | The endpoint confirms the object write |
| DuckLake | data_path, metadata_schema, namespace, table | catalog_dsn, access_key_id, secret_access_key, region, endpoint | The DuckLake transaction commits |
| Apache Iceberg | catalog_uri, warehouse, namespace, table | token, access_key_id, secret_access_key, region, endpoint | The catalog confirms the append snapshot |
| Amazon S3 Tables | table_bucket_arn, region, role_arn, namespace, table | none: Send2Bucket assumes your role with an external ID | The append snapshot commits |
| Supabase Analytics Buckets | project_ref, warehouse, region, namespace, table | catalog_token, access_key_id, secret_access_key | The 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.