Skip to main content

Preflight checks for Amazon Redshift

TL;DR

Before running the Amazon Redshift crawler, run preflight checks to verify connectivity, schema access, and miner permissions. Each check maps to a specific error message and fix.

Connect

Before running the Amazon Redshift crawler, you can run preflight checks to perform the necessary technical validations. The following preflight checks will be completed:

Database and schema​

✅ Check successful

❌ Check failed for $missingObjectName

Fix: the Atlan user is missing USAGE on that database or schema - grant it per Set up Amazon Redshift.

Tables count​

✅ Check successful. Table count: <count>

❌ Source returned error/UI default failure message

Query text (provisioned only)​

Two system tables are checked together—the miner extract SQL joins them, so a missing grant on either makes the whole extract fail. Both this check and Session (provisioned only) must pass.

✅ Check successful

❌ Check failed! Please grant select permission on pg_catalog.svl_statementtext

Fix: run the miner permission grants (GRANT SELECT ON pg_catalog.svl_statementtext plus ALTER USER atlan_user SYSLOG ACCESS UNRESTRICTED).

Session (provisioned only)​

✅ Check successful

❌ Check failed! Please grant select permission on pg_catalog.stl_connection_log

Fix: run the miner permission grants (GRANT SELECT ON pg_catalog.stl_connection_log plus ALTER USER atlan_user SYSLOG ACCESS UNRESTRICTED).

S3​

✅ Check successful if the bucket, region, and prefix combination is valid and the S3 credential passed is accessible.

❌ Check failed with error code <AWS error code> - <AWS SDK ERR message>

For example: Miner S3 credentials: failed with error code: NoSuchBucket

Fix: verify the bucket name, region, prefix, and the S3 credential's read access - see Mine Amazon Redshift.

See also​