DatriseAI-first ETL

AWS CloudTrail to Yellowfin Integration

AI-first ETL from AWS CloudTrail into Yellowfin. Governed entities, incremental sync, typed landing tables.

How Datrise loads AWS CloudTrail into Yellowfin

Datrise syncs AWS CloudTrail's API events, identities, resources, event sources, error codes, and request parameters into Yellowfin as warehouse tables Yellowfin builds views on. Flexible or custom fields land in flattened columns, and timestamps such as created, updated, and status changes are typed as date/time dimensions.

Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts. Yellowfin views reference columns by name, so Datrise lands stable, well-typed columns to keep reports valid.

Ideal for dashboards with automated data storytelling.

Endpoints

AWS CloudTrail: AWS account activity and API audit logging.

Yellowfin: BI suite with dashboards, automated insights, and data storytelling.

How AWS CloudTrail entities map to Yellowfin

AWS CloudTrail entityYellowfin objectNotes
API eventsaws_cloudtrail_api_eventsdate/time dimensions events
identitiesaws_cloudtrail_identitiesid PK · linked to aws_cloudtrail_api_events
resourcesaws_cloudtrail_resourcesid PK · linked to aws_cloudtrail_api_events
event sourcesaws_cloudtrail_event_sourcesdate/time dimensions events

FAQ

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

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

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

It runs incrementally — Datrise uses incremental refresh of the connected tables.

Related pipelines

Early access

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