How-to guideSourcesManaged setup
Managed Amazon Redshift Setup
Prepare a Redshift deployment, scoped database grants, and the agreed IAM or database credential for managed Vendo access.
Last reviewed July 13, 2026
Redshift setup is Vendo-led because the correct authentication and network path depend on your provisioned or Serverless deployment.
Before you start
- Identify the cluster or Serverless workgroup, region, and database.
- Select the schemas and objects Vendo needs.
- Decide whether your environment requires Data API access, a database principal, or another approved method.
- Identify the AWS and database administrators who own the grants.
Grant least privilege
For a read connection, the database principal generally needs schema usage and SELECT on the approved tables or views. IAM permissions, network rules, and credential retrieval depend on the agreed connection method.
Do not copy a wildcard IAM policy or open a security group before Vendo confirms the method and source identity.
Connect with Vendo
- Share the non-secret region, deployment type, database, and schema names.
- Agree on the connection and authentication method.
- Apply the reviewed IAM, network, and database grants.
- Transfer credentials through the approved secret channel.
- Ask Vendo to test metadata discovery and one bounded query.
Verify
- Confirm only the approved schemas and tables are visible.
- Run the same small query in Redshift and Vendo.
- Compare results and inspect Redshift query history.
- Test expected behavior while a cluster is paused or a Serverless workgroup scales.
- Record credential rotation and access-review owners.
Troubleshooting
| Symptom | Check |
|---|---|
| Connection fails | Agreed protocol, endpoint/Data API, region, network, and credentials |
| Permission denied | Schema usage, table/view grants, and IAM permissions |
| Objects are missing | Database/search path and approved schema list |
| Query times out | Cluster state, workload queue, scan size, and statement limits |
Related
Last updated on