Skip to content
DestinationCDPs & data

AWS Firehose

Point a delivery stream from your AWS account and each resolved event lands as one JSON line — ready for S3, Redshift or OpenSearch on your side. The credential is yours, minimum write scope on the stream, kept in the secrets vault.

Data delivered

Data delivered

  • The full resolved event, as JSONL
  • Per-record delivery results (partial failures never go unnoticed)
  • Configurable region and stream

What it is for

What you can do with it

  • Build your own data lake from CDP events
  • Feed the warehouse without building and operating a pipeline

Why integrate

The business reason, not just the tech

A data lake without an engineering project

Every resolved event becomes a JSONL line in YOUR Firehose — then S3, Redshift or OpenSearch on infrastructure AWS already operates. The pipeline that would cost weeks becomes one credential.

Own the data, literally

The stream lives in your AWS account. If you ever leave the platform, the history is in your bucket, your format, your keys.

Failures never slip by

Delivery checks results PER RECORD: if AWS accepts half a batch, the other half retries — nothing vanishes silently.

How to connect

Step by step

  1. Step 1

    Create a delivery stream in your account’s Firehose.

  2. Step 2

    Create an IAM user with PutRecord-only permission on the stream and copy the keys.

  3. Step 3

    Create the destination with stream, region and keys.

Frequently asked questions

Is the credential exposed?

No — it goes to the managed secrets vault, like every destination token. And the recommended scope is minimal: write-only to that stream.

Start measuring what actually becomes revenue

Create a free account, connect your first source and see your first lead timeline today. No card required.