Skip to main content
Kadoa configures the integration for you through the Support Center.

Before you begin

  • An AWS account with permission to create a bucket and edit its bucket policy.
  • Kadoa’s AWS principal ARN, provided by Support. Your bucket policy grants access without sharing AWS keys.
  • A bucket in any AWS region. Kadoa uses SSE-S3 encryption by default.
If your bucket requires SSE-KMS, contact Support before you request the integration.

Prepare the bucket

1

Create a bucket

Create an S3 bucket in your preferred AWS region.
2

Grant Kadoa access

Add this bucket policy. Replace <KADOA_AWS_PRINCIPAL_ARN>, <YOUR_BUCKET>, and <PREFIX> with your values.Use a prefix with no leading or trailing slash, for example kadoa.

Request the integration

Send these details through the Support Center:

Verify the first delivery

After a workflow run completes, list the delivered files:
  • Confirm one file per selected format exists for that run.
  • Confirm each data file’s row count matches the same run in the dashboard.
  • Run the workflow again. With the default path template, confirm that the new run has a new folder.

What’s next

Load into Snowflake with Snowpipe

Load files from your bucket with a Snowpipe that you manage.

How data integrations work

See delivery timing, formats, file paths, and workflow health files.

Google Cloud Storage

Deliver completed-run data to a Cloud Storage bucket.