Amazon QuickSight - Lineage

This article outlines lineage coverage, configuration requirements, supported components, transformation support, supported use cases, partial or limited coverage, unsupported scenarios, and the current functional status of lineage extraction in Amazon QuickSight.

The Amazon QuickSight connector provides end-to-end lineage across source databases and S3 files through QuickSight Datasets and Analyses to Dashboards, Sheets, and Visuals. The connector supports direct relational sources and Custom SQL datasets, with table-level, report-level, and column-level lineage relationships.

Lineage Configuration Requirements

Successful lineage extraction depends on valid Amazon QuickSight API access, complete metadata, correctly configured source connections, and the availability of required lineage configuration properties. The following requirements apply to QuickSight lineage extraction.

Configuration Requirements Table

Configuration	Required Detail
Amazon QuickSight API Access	Valid Amazon QuickSight API credentials and Region must be available for metadata extraction.
QuickSight Metadata	Dashboard, Analysis, and Dataset metadata must be crawled before lineage is built.
Reference Database Connections	Reference database connections should be crawled so that source tables and columns can be resolved during lineage extraction.
SQL Dialects	supportingDialects must be configured for Custom SQL parsing.
Connection Priority	connectionsPriorityForLineage must be configured when the same table or schema exists across multiple source connections.
S3 Metadata	S3 datasets should include manifest or file-location/folder metadata to provide the most complete lineage coverage.
Dataset and Analysis References	dataSetId and analysisId references in QuickSight metadata must match the corresponding crawled catalog objects.

Missing metadata, unavailable source connections, incomplete S3 file or folder metadata, invalid API credentials, or unmatched Dataset and Analysis references may result in incomplete lineage generation.

Lineage Components

The following table identifies the QuickSight components and lineage features supported by the connector.

Component / Feature	Supported
Dashboards	✅
Analyses	✅
Datasets	✅
Sheets	✅
Visuals / Child Reports	✅
CUSTOM_SQL Sources	✅
RELATIONAL_TABLE Sources	✅
S3_SOURCE	✅ / ⚠️
Table → Report Lineage	✅
Report → Report Lineage	✅
Column-level Lineage	✅
Multi-Dataset Analysis	✅
Cross-Dataset Join Semantics	⚠️
Calculated / Derived Visual Fields	⚠️
Dynamic SQL / Parameter-driven Queries	❌ / ⚠️

The ⚠️ icon indicates partially supported functionality where lineage coverage depends on metadata availability, transformation complexity, or the specific QuickSight configuration.

Column Creation Support

This section outlines lineage support for columns created through direct source mappings, aliases, derived fields, expressions, and cross-dataset transformations.

Column Creation from Lineage

Transformation Type	Supported
Direct Relational Column → Report Column	✅
Qualified Column Name Matching (table.column → column)	✅
Custom SQL Alias Mapping	✅
Derived / Calculated Fields	⚠️
Visual-level Custom Expressions / Parameters	❌
Cross-Dataset Derived / Join Columns	⚠️ / ❌

The ⚠️ icon indicates partial lineage coverage. The resulting lineage depends on the availability of transformation metadata and the complexity of the calculated, derived, or cross-dataset expression.

Supported Use Cases

The Amazon QuickSight connector supports lineage extraction across QuickSight dashboards, analyses, datasets, reporting hierarchies, relational sources, Custom SQL sources, and supported S3 sources.

Supported Lineage Scenarios

Supported Scenario	Details
Source Table → Dataset → Analysis → Dashboard Lineage	End-to-end lineage from source tables through QuickSight datasets and analyses to dashboards.
Dashboard → Sheet → Visual Hierarchy	Lineage and reporting hierarchy across dashboards, sheets, and visuals.
Custom SQL Dataset Lineage	Lineage extraction from Custom SQL datasets using dialect-aware SQL parsing.
Direct Relational-table Dataset Lineage	Lineage from relational source tables to QuickSight datasets.
S3-source Lineage	Lineage from S3 sources when manifest, file-location, or folder metadata is available.
Multi-dataset Analyses	Lineage across analyses that reference multiple datasets.
Source-column → Report-column Matching	Automatic lineage based on matching source-column and report-column names.
Qualified Column Name Matching	Lineage resolution for qualified column names such as table.column.
Custom SQL Alias → Destination Column Mapping	Lineage between Custom SQL aliases and destination report columns.
Table-to-report Lineage	Lineage between source tables and QuickSight reports.
Report-to-report Lineage	Lineage relationships between related QuickSight reports.

Lineage extraction depends on QuickSight metadata, source connection availability, SQL parsing support, and the completeness of the crawled catalog objects.

Partial or Limited Coverage

Certain QuickSight scenarios provide partial lineage coverage because the required source metadata may be incomplete, transformations may not be fully represented in dataset metadata, or runtime behavior may prevent complete static lineage resolution.

Scenarios

Scenario	Limitation Description	Recommendation / Workaround
S3-source Lineage	Lineage quality depends on the availability and completeness of manifest, file-location, or folder metadata.	Ensure relevant S3 manifest and file-location/folder metadata is available before lineage extraction.
Derived / Calculated Fields	Derived or calculated fields may be represented only when the required information is available in dataset metadata. Complex transformations are not always decomposed into individual lineage relationships.	Validate lineage manually for complex calculated or derived fields where required.
Cross-Dataset Joins	Lineage can represent the participating datasets, but detailed join-expression semantics have limited coverage.	Validate detailed join relationships manually where join-expression-level lineage is required.
Missing Dataset References	Missing dataset references can prevent the affected lineage paths from being resolved.	Ensure referenced datasets are crawled and available in the catalog.
Blank Table or Schema Metadata	Blank table or schema metadata can cause affected lineage paths to be skipped.	Ensure complete table and schema metadata is available from the source connection.
Cross-account / Cross-region Sources	Source resolution depends on correctly configured reference connections and connection priorities.	Configure the required reference connections and connectionsPriorityForLineage values.

Incomplete source metadata, unresolved dataset references, complex calculated fields, cross-dataset joins, and incorrectly configured reference connections may reduce lineage completeness and column-level accuracy.

Unsupported Scenarios

The connector does not support complete lineage extraction for runtime-generated queries, visual-level expressions, parameter propagation, and transformation scenarios that cannot be statically resolved from available QuickSight metadata.

Unsupported Lineage

Not Supported	Description	Recommendation / Workaround
Dynamic / Runtime-generated SQL	Lineage cannot be fully generated when SQL is created dynamically at runtime and cannot be statically parsed.	Use statically available SQL definitions where possible and validate affected lineage manually.
Visual-level Custom Expression Parsing	Custom expressions defined at the visual level are not parsed for lineage extraction.	Validate visual-level dependencies manually where required.
Parameter / Variable Propagation	Parameters and variables are not propagated through lineage relationships.	Validate parameter-dependent data flows separately where required.
Complex Calculated Fields	Complete expression-level lineage is not available for complex calculated fields when the required transformation details are not represented in the source metadata or SQL parser.	Validate calculated-field lineage manually where required.
Detailed Aggregate Semantics	Aggregate operations such as SUM, AVG, and COUNT are not represented as transformation expressions when the source SQL parser does not expose the required semantics.	Validate aggregate transformation logic separately where detailed expression-level lineage is required.

Unsupported scenarios do not generate complete lineage and may result in missing or disconnected lineage relationships within lineage visualization.

Current Functional Status

This section outlines the current lineage capabilities and coverage of the Amazon QuickSight connector.

Status Area	Details
Overall Coverage	Production-ready coverage across core QuickSight Dashboards, Analyses, Datasets, relational-table sources, Custom SQL sources, and column-level lineage.
Lineage Depth	Table-level, report-level, and column-level lineage across supported QuickSight components and source connections.
Supported Inputs	Dashboards, Analyses, Datasets, Sheets, Visuals / Child Reports, relational-table sources, Custom SQL sources, and supported S3 sources.
Functional Scope	End-to-end lineage from source databases and S3 files through QuickSight Datasets and Analyses to Dashboards, Sheets, and Visuals.
Transformation Support	Direct relational column mappings, qualified column name matching, and Custom SQL alias mapping are supported. Derived and calculated fields have partial coverage.
Limitation Areas	S3 metadata dependencies, cross-dataset join semantics, derived/calculated fields, dynamic SQL, parameter-driven queries, visual-level custom expressions, and incomplete source metadata.
Resulting Output	Reliable lineage for core QuickSight workloads, with metadata-dependent and partial coverage for advanced transformation, S3, dynamic SQL, parameter, and cross-dataset scenarios.

The Amazon QuickSight connector provides production-ready lineage coverage across core QuickSight Dashboards, Analyses, Datasets, relational-table sources, Custom SQL sources, and column-level relationships. S3 lineage depends on the availability of manifest or file-location/folder metadata. Advanced scenarios involving dynamic SQL, parameters, visual-level expressions, complex calculated fields, cross-dataset join semantics, and incomplete source metadata have partial or unsupported coverage and may require manual validation.

---

Copyright © 2026, OvalEdge LLC, Peachtree Corners, GA, USA.