AWS CloudTrail to PlanetScale Integration

How Datrise loads AWS CloudTrail into PlanetScale

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

Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE, so re-runs update only what changed. Vitess sharding by tenant or entity key for very large tables. PlanetScale disallows foreign-key constraints by default, so Datrise models relationships by stable id columns rather than enforced FKs.

Ideal for horizontally scalable MySQL apps on Vitess.

Endpoints

AWS CloudTrail: AWS account activity and API audit logging.

PlanetScale: Serverless MySQL platform with safe schema workflows.

How AWS CloudTrail entities map to PlanetScale

AWS CloudTrail entity	PlanetScale object	Notes
API events	`aws_cloudtrail_api_events`	DATETIME 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`	DATETIME events

FAQ

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

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

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

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

Related pipelines

Early access

Connect AWS CloudTrail to PlanetScale 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.