connection · literal
read-only IAM credential
no VPC · no JDBC · no password
Connection Console
There is no connection string. Access is Amazon Redshift Serverless through the Redshift Data API (HTTPS, IAM auth) — an asynchronous, paged, IAM-authenticated HTTPS API. Hit Connect & run to watch the real handshake stages fire in order, then get live rows from the catalogued row_counts query.
Connection target
- engine
- Amazon Redshift Serverless
- api
- Redshift Data API (HTTPS, IAM auth)
- region
- us-west-1
- workgroup
- default-workgroup
- database
- dev
- readOnly
- true · cannot INSERT/UPDATE/DELETE
Environment
AWS_ACCESS_KEY_ID=••••••AWS_SECRET_ACCESS_KEY=••••••REGION=us-west-1WORKGROUP=default-workgroupDATABASE=devDB_USER=••••••
The browser never holds IAM creds
A browser cannot safely carry AWS credentials, so nothing here connects directly. Every statement is executed by the server-side Data API proxy.
Execution path
POST /api/redshift/querymode: offline-snapshot
today; boto3 Data API tomorrow.redshift-data-api — us-west-1/default-workgroup/dev
$ asdcheck connect --data-api --read-only
$ execute_statement --sql "Backbone row counts (all sports)"
Idle. Press Connect & run to open the handshake.
Operator notes
- No VPC, no JDBC/ODBC driver, no password, no connection string.
- The issued credential cannot INSERT, UPDATE, or DELETE.
- Data API is asynchronous + paged: execute_statement → poll describe_statement → get_statement_result, following NextToken to exhaustion (a single get_statement_result silently returns only the first page).
- Expect ~1.5–2s latency per statement regardless of result size — batch questions into one query.
- Timestamps are `timestamp without time zone`, UTC by convention (..._utc). Do not let a driver localize them.
Pulled with AWS_PROFILE=asd against Redshift Serverless (us-west-1 / default-workgroup / dev).