DatriseAI-first ETL

AWS CloudTrail to GoodData Integration

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

How Datrise loads AWS CloudTrail into GoodData

Datrise syncs AWS CloudTrail's API events, identities, resources, event sources, error codes, and request parameters into GoodData as warehouse tables GoodData maps into its logical data model. Flexible or custom fields land in flattened columns, and timestamps such as created, updated, and status changes are typed as date dimensions.

Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts. GoodData's LDM maps datasets by keys, so Datrise lands stable primary and foreign id columns to keep the model valid.

Ideal for embedded, multi-tenant analytics.

Endpoints

AWS CloudTrail: AWS account activity and API audit logging.

GoodData: Composable analytics platform with headless BI and embedded dashboards.

How AWS CloudTrail entities map to GoodData

AWS CloudTrail entityGoodData objectNotes
API eventsaws_cloudtrail_api_eventsdate 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 dimensions events

FAQ

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

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

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

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

Related pipelines

Early access

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