AWS CloudTrail to Neon Integration

How Datrise loads AWS CloudTrail into Neon

Datrise syncs AWS CloudTrail's API events, identities, resources, event sources, error codes, and request parameters into Neon as a typed table per source entity. 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 by load date. Neon separates compute from storage, so Datrise batches writes to keep autoscaling compute from cold-starting on every small change.

Ideal for serverless Postgres workloads that scale to zero between syncs.

Endpoints

AWS CloudTrail: AWS account activity and API audit logging.

Neon: Serverless Postgres destination with branching and autoscaling.

How AWS CloudTrail entities map to Neon

AWS CloudTrail entity	Neon 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 Neon?

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 Neon types.

How does the AWS CloudTrail to Neon 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 Neon 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.