AWS CloudTrail to Supabase Integration

How Datrise loads AWS CloudTrail into Supabase

Datrise syncs AWS CloudTrail's API events, identities, resources, event sources, error codes, and request parameters into Supabase as a typed table per source entity in your Supabase Postgres. Flexible or custom fields land in jsonb columns, and timestamps such as created, updated, and status changes are typed as timestamptz.

Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON CONFLICT DO UPDATE, so re-runs update only what changed. Optional declarative partitioning for high-volume tables. Datrise lands into a dedicated schema and leaves row-level security to you, so synced tables don't inherit public access by accident.

Ideal for app builders who want CRM data alongside their Supabase product data.

Endpoints

AWS CloudTrail: AWS account activity and API audit logging.

Supabase: Postgres platform with auth, storage, and realtime APIs.

How AWS CloudTrail entities map to Supabase

AWS CloudTrail entity	Supabase object	Notes
API events	`aws_cloudtrail_api_events`	timestamptz events
identities	`aws_cloudtrail_identities`	id PK · linked to aws_cloudtrail_api_events
resources	`aws_cloudtrail_resources`	id PK · linked to aws_cloudtrail_api_events
event sources	`aws_cloudtrail_event_sources`	timestamptz events

FAQ

How does Datrise handle AWS CloudTrail's custom fields in Supabase?

Flexible values are stored as jsonb columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Supabase types.

How does the AWS CloudTrail to Supabase sync stay up to date?

It runs incrementally — Datrise uses a watermark on updated-at, applied with INSERT … ON CONFLICT DO UPDATE.

Related pipelines

Early access

Connect AWS CloudTrail to Supabase the easy way

Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.