ATX AnalyticsTable signs in to Amazon Redshift with AWS IAM — temporary credentials, nothing to rotate — pulls the rows your report needs into a DuckDB database in the project, and lets you build and schedule the report from there. The cluster is asked once per refresh; everything else happens on your machine.
The Amazon Redshift connection form in ATX AnalyticsTable 1.7, filled in with the example values below. Secrets go into the encrypted vault, never into the project.
IAM policy for the identity the app runs as: { "Version": "2012-10-17", "Statement": [{ "Effect": "Allow", "Action": "redshift:GetClusterCredentialsWithIAM", "Resource": "arn:aws:redshift:eu-central-1:123456789012:dbname:risk/dev" }] } — Serverless: redshift-serverless:GetCredentials on the workgroup instead.
Grants for the IAM database user (after its first sign-in creates it): GRANT USAGE ON SCHEMA public TO "IAMR:atx-reporting"; GRANT SELECT ON ALL TABLES IN SCHEMA public TO "IAMR:atx-reporting";
Reporting query — e-mails hashed in Redshift: SELECT DATE_TRUNC('week', e.event_time)::date AS week, e.channel, SHA2(LOWER(e.customer_email), 256) AS customer_key, COUNT(*) AS events FROM public.events e WHERE e.event_time >= DATEADD(day, -28, GETDATE()) GROUP BY 1, 2, 3 ORDER BY 1;
Then reshape locally — a Run SQL step on the project's DuckDB: -- "input" is the table the previous pipeline step produced (the import above). -- This runs on your machine, in the project's DuckDB, not on the database. SELECT region, SUM(revenue) AS revenue, COUNT(DISTINCT customer_key) AS customers FROM input GROUP BY region ORDER BY revenue DESC; — Column names follow the query above; on the local engine the pipeline's current table is registered as input before the script runs.
Redshift dynamic data masking and row-level security apply to the database user. Redshift cannot carry a per-user identity: credentials are minted for the connection's AWS identity, so give each team its own connection and role, and do per-person masking in the project's data-access policy.
A refresh needs a route to port 5439 on the cluster. The imported copy and every report over it work offline on your machine; the licence validates offline and no ATX service is involved.
redshift:GetClusterCredentialsWithIAM (or GetClusterCredentials) for a provisioned cluster, redshift-serverless:GetCredentials for Serverless.
Yes, through a VPN or a VPC endpoint. Set Certificate host name or a CA file so you can use verify-full on the custom host.
Results are fetched page by page. Importing once and working on the local copy is faster for you and lighter on the cluster.
This site needs JavaScript for the full experience. Every page above is reachable without it.