Amazon Redshift
Amazon Redshift
Scan Amazon Redshift, including Redshift Spectrum external tables in S3.
- Category
- Warehouse & Lakehouse
- Source type
- REDSHIFT
- Produces
- table
Redshift holds a warehouse’s own tables and, through Spectrum, external tables read straight out of S3. This source scans both, provisioned clusters and Serverless workgroups alike.
What you need to connect
Host, port and database, and a database user. Sign in with that user’s password, or leave the password empty to sign in with IAM: give the region and the cluster identifier or Serverless workgroup name, plus an access key pair unless the environment already has AWS credentials.
What Classifyre reads
Tables and views in every schema, or only the ones you list, and the external
tables of Spectrum schemas unless you switch them off. External tables report
their format (iceberg, hudi, delta or external) and their S3 location;
the warehouse’s own tables report native.
Shared behaviour · SQL databases
One asset per table or view, never one per row. The asset carries the table's structure — database, schema, table name, object type, its columns and their types, and a row-count estimate — and its content is a sample of real rows, formatted so a detector reads actual values rather than a schema dump.
How many rows, and which ones, is entirely up to the sampling strategy. Large tables are paged through by key rather than by OFFSET, so a scan that stops halfway can resume from where it left off instead of re-reading from the top.
Read-only throughout. The connector issues catalog queries and bounded SELECTs. Nothing is written back, and a read-only account is the right account to give it.
Relationships come out of the engine's own catalog: a view and the tables it reads from are recorded as FLOW — real lineage, with column-level detail parsed out of the view's SQL where the SQL makes that possible. See Lineage.
Metadata on every asset
Asset kind · table
| Field | Type | Always present | What it is |
|---|---|---|---|
| database | string | Yes | Database or catalog name |
| table_name | string | Yes | Table name |
| table_type | string | Yes | Object type (TABLE/VIEW) |
| schema | string | No | Schema name |
| columns | object[] | No | Columns as {name, type} objects |
| row_count | integer | No | Estimated number of rows |
| table_format | string | No | Storage format of the table (iceberg, delta, hudi, paimon, lance, native, external, view) |
| object_type | string | No | Source object type |
| location | string | No | External table location (Spectrum) |
Lineage
Lineage
Views and the tables they read are recorded as lineage, parsed from the view SQL in Redshift’s dialect. Redshift records primary and foreign keys but never enforces them, so no reference edges are drawn from them. See Lineage & Relationships.
Worth knowing
- Spectrum reads bill by bytes scanned in S3, as Athena does; a smaller page size or a narrower scope keeps the cost down.
Configuration
Beyond the fields below, every source also has the settings shared by all of them: the sampling strategy, the augmentation notebook that enriches assets after extraction, the detectors to run, the scan schedule, and the compute limits for its scan jobs.
Required
Without these, the source will not save.
| Field | Type | Required | What it does | Default |
|---|---|---|---|---|
| required | object | Yes | —no extra properties | — |
| database | string | Yes | Database to connect to | — |
| host | string | Yes | Cluster or workgroup endpoint host | — |
| port | integer | Yes | Portmin 1, max 65535 | 5439 |
Secrets
Stored encrypted and never shown again after you save them. See Configuration & Fields.
| Field | Type | Required | What it does | Default |
|---|---|---|---|---|
| masked | object | Yes | —no extra properties | — |
| aws_access_key_id | string | No | AWS access key for IAM sign-in; empty uses the ambient AWS credentials | — |
| aws_secret_access_key | string | No | AWS secret key for IAM sign-in | — |
| aws_session_token | string | No | AWS session token | — |
| password | string | No | Database password; empty signs in with IAM | — |
| username | string | Yes | Database user (password sign-in), or the user to fetch IAM credentials for | — |
Optional
Everything you can tune. Sensible defaults apply when you leave them alone.
| Field | Type | Required | What it does | Default |
|---|---|---|---|---|
| optional | object | No | —no extra properties | — |
| connection | object | No | —no extra properties | — |
| connection.cluster_identifier | string | No | Provisioned cluster id, for IAM sign-in | — |
| connection.connect_timeout_seconds | number | No | Connection timeoutmin 1, max 300 | 30 |
| connection.region | string | No | AWS region, for IAM sign-in | — |
| connection.ssl | boolean | No | Connect over TLS | true |
| connection.workgroup_name | string | No | Serverless workgroup, for IAM sign-in | — |
| extraction | object | No | —no extra properties | — |
| extraction.include_view_lineage | boolean | No | Read view definitions and record what each view selects from | true |
| scope | object | No | —no extra properties | — |
| scope.exclude_schemas | array | No | Skip these schemas (pg_catalog and information_schema are always skipped) | — |
| scope.exclude_schemas[] | string | No | — | — |
| scope.include_external_schemas | boolean | No | Include Redshift Spectrum external schemas (lakehouse tables in S3) | true |
| scope.include_objects | array | No | Only these objects (schema.table, or catalog.schema.table) | — |
| scope.include_objects[] | string | No | — | — |
| scope.include_schemas | array | No | Only these schemas | — |
| scope.include_schemas[] | string | No | — | — |
| scope.include_tables | boolean | No | Include tables | true |
| scope.include_views | boolean | No | Include views | true |
| scope.table_limit | integer | No | Maximum number of tables to scan per runmin 1 | — |