Find your Redshift credentials in the AWS console, whitelist the connector's IP on your security group, enable SSL, and pull data with Apps Script JDBC or a no-code add-on — with named-error fixes, Redshift Serverless support, and two-way write-back.
Amazon Redshift is the warehouse for many AWS-native data teams, and the people who need that data day-to-day — finance analysts, ops leads, growth — usually don't live in a SQL IDE. They live in Google Sheets. This guide walks through every realistic path from Redshift to Sheets in 2026: the AWS-native UNLOAD-to-S3 flow, Apps Script with the Postgres JDBC driver, BigQuery federation via Omni, and the full Brooked setup including two-way write-back and the AI agent.
Evaluating more than one warehouse? The same Brooked setup covers Snowflake and Databricks, and you can weigh price and two-way sync against the usual pick in Brooked vs Coefficient.
Quick comparison: 4 ways to get Redshift data into Sheets
| Method | Cost | Setup | Auto-refresh | Two-way sync | Code | Best for |
|---|---|---|---|---|---|---|
| AWS UNLOAD to S3 → CSV | Free + S3 storage | 20 min | Schedule via EventBridge | No | SQL + IAM setup | One-time bulk extracts |
| Apps Script + Postgres JDBC | Free | 1–2 hours | Time-driven trigger | DIY | Required | One-developer custom workflows |
| BigQuery federation (Omni) | BigQuery + Omni pricing | 1 hour | Query-time | No | SQL | Teams already on BigQuery wanting cross-warehouse queries |
| Brooked add-on | Free tier · Pro $29/user | Under 10 min | 15 min / hourly / daily | Yes | None | Teams who want live Redshift data in Sheets without owning a pipeline |
Step 0 — Find your Redshift credentials in AWS
Whatever method you pick, you need the same five things from AWS. This is the most common 30-minute time sink for first-time connectors, and no top SERP result tells you exactly where to find each value.
- Endpoint / Host — AWS console → Redshift → Clusters → click your cluster → Properties tab → Endpoint. Format: cluster-name.region-id.redshift.amazonaws.com. Strip the :5439/database suffix if it's appended.
- Port — 5439 by default for provisioned clusters and Redshift Serverless. Confirm in the same Properties tab.
- Database name — Redshift creates a default 'dev' database. Your team's data is usually in a different DB — check Clusters → your cluster → Databases.
- Username — the database user, not your AWS console user. Find existing users via Query editor v2 → Databases → Users, or create a new one with CREATE USER sheets_reader PASSWORD 'value'.
- Password — set when the user was created. If lost, reset with ALTER USER sheets_reader PASSWORD 'value' from a privileged session.
Redshift Serverless is different. Endpoint format is workgroup-name.account-id.region.redshift-serverless.amazonaws.com, and IAM database authentication is the default. Most Sheets connectors expect username/password — create a password-auth user explicitly: CREATE USER sheets_reader WITH PASSWORD 'YourPassword', then GRANT SELECT ON ALL TABLES IN SCHEMA public TO sheets_reader.
Step 0.5 — Allow inbound traffic from the connector
This is the single most common silent failure. If your cluster is in a private VPC (most production setups are), no connector tool can reach it without an inbound rule on the cluster's security group. AWS console → EC2 → Security Groups → find the SG attached to your cluster → Inbound rules → Add rule: Type Redshift, Protocol TCP, Port 5439, Source the connector's IP range.
Brooked publishes its outbound IP ranges in the help docs; pin those in the Source field rather than 0.0.0.0/0. If your cluster has no public endpoint and lives entirely in a private VPC, no Sheets-side connector can reach it directly — you'll need a VPN, AWS Direct Connect, or a bastion host with an SSH tunnel. If the cluster is publicly accessible (Publicly accessible Yes in cluster properties), the IP rule alone is enough.
For Apps Script users: Google does not publish a stable IP range, so you cannot pin to a specific source. The honest options are to open the security group to all IPs (bad for production), put a proxy in front (e.g. a Lambda using the Redshift Data API), or move to a connector that uses fixed IPs you can whitelist.
Method 1 — UNLOAD to S3 → CSV → Sheets
The AWS-native path. From Redshift: UNLOAD ('SELECT … FROM …') TO 's3://your-bucket/dump_' CREDENTIALS '…' CSV HEADER; Then either download the CSV manually or wire up a Lambda + EventBridge to deliver it to a Google Drive folder for IMPORTRANGE pickup. This is the AWS official answer.
Pros: Free (only S3 storage), handles arbitrarily large dumps, native AWS. Cons: Snapshot only. Wiring up the S3 → Sheets bridge is non-trivial. IAM permissions, role assumption, and credential rotation are real ongoing work.
Method 2 — Apps Script + Postgres JDBC
Redshift speaks the Postgres wire protocol. Apps Script's Jdbc service can connect with a Postgres-style JDBC URL (jdbc:postgresql:// cluster-endpoint:5439/db). Write a function, run it, schedule with time-driven triggers.
Pros: Free, customizable, no third party. Cons: Apps Script's 6-minute execution limit. Apps Script's IP ranges aren't well-documented and change, so security group inbound rules are a moving target.
Method 3 — BigQuery federation via Omni
Google's BigQuery Omni can federate queries to Redshift directly. From BigQuery you can write a query that runs against Redshift. Then Sheets' native BigQuery connector pulls the result. This is useful if you're already a heavy BigQuery shop and Redshift is one of multiple warehouses you query.
Pros: Cross-warehouse queries from a single SQL surface. Cons: Omni pricing is on top of BigQuery pricing. Heavyweight for "I just want Redshift data in a sheet".
Method 4 — A Google Sheets add-on (Brooked)
Brooked connects to Redshift directly, runs queries on demand, holds the connection across refreshes, and ships two-way write-back plus the AI agent. Setup is under 10 minutes including security group configuration.
Step 1 — Install Brooked
Install from the Workspace Marketplace. Free tier covers 100 imports/month with AI Analyst.
Step 2 — Connect Redshift
In the Brooked sidebar, click Add data source → Amazon Redshift. Paste your cluster endpoint (or Serverless workgroup endpoint), port 5439, database, username, and password. SSL is on by default. Click Test connection.
Almost always you'll need to allow Brooked's egress IPs through your VPC security group. Brooked's sidebar surfaces the exact IPs to allow-list during this step.
Step 3 — Run a query, pick a destination, schedule refresh
Click New import, write your SQL (or browse the schema and pick a table to auto-generate a SELECT), pick a destination range, click Import. Toggle Auto-refresh in settings and pick a cadence (15 min / hourly / daily / weekly).
Step 4 — Two-way write-back (optional)
For writing data from the sheet back to Redshift, click 'Convert to two-way sync' on any import. Map columns, pick a primary key, pick write mode (INSERT, UPDATE, UPSERT compiled to DELETE+INSERT, or DELETE). Every write is captured in an audit log.
Using the AI agent with Redshift
Open the Chat tab. Ask: "What's our daily active user trend over the last 8 weeks?" The agent introspects your schema, writes the SQL, runs it on your cluster, and lands the result in the sheet. For follow-up analysis the SQL layer can't easily do — cohort retention, statistical tests, projections — the agent drops into a Python sandbox with pandas pre-loaded.
Brooked AI — RedshiftWhat about Microsoft Excel?
Brooked is Sheets-native. For Excel, AWS publishes the Amazon Redshift ODBC driver — install locally, configure a DSN, use Excel's Data → Get Data → From ODBC. This is the AWS official Excel path. It works but every analyst needs the driver installed. Coefficient also supports Redshift for Excel on its Premium tier. Most teams that try live-Excel with Redshift settle on Brooked + .xlsx export for the snapshot use case.
The verdict — which method when
I need a one-time bulk dump
→ UNLOAD to S3 → CSV → Sheets. AWS native, free, handles arbitrarily large result sets without Apps Script timeouts.
I want a single query refreshed daily
→ Apps Script + JDBC. Free, customizable, can be scheduled. Fine if you don't mind maintaining the script.
I want live Redshift data across many queries with no script
→ Brooked. Visual SQL editor, scheduled refresh, two-way write-back, AI agent — all without owning code.
I want to ask Redshift questions in plain English
→ Brooked. The agent introspects your schema, writes the SQL, runs it on your cluster, and lands results in the sheet.
Troubleshooting common issues
Frequently asked questions
Does Amazon Redshift have a native Google Sheets connector?
No first-party connector. AWS offers UNLOAD-to-S3 as the official bulk-export path; everything else is third-party (Brooked, Coefficient, Apps Script + JDBC, etc.) or BI tools (QuickSight, Tableau, Power BI).
Can I query Redshift live from Google Sheets?
Yes — with a connector add-on that holds the connection and runs queries on demand. Brooked, Coefficient (Premium tier), or Apps Script all support this. Native Sheets doesn't.
What's the difference between Redshift provisioned and Redshift Serverless?
Provisioned has clusters you scale manually; Serverless has workgroups that scale automatically and bill by usage. From a Sheets connector perspective they're identical — you point at an endpoint either way. Brooked supports both.
Can Brooked write data back to Redshift?
Yes. INSERT, UPDATE, UPSERT (via DELETE + INSERT on Redshift), and DELETE are supported on every tier. Most other Sheets connectors are read-only.
How does Brooked handle a Redshift cluster behind a VPC?
By default, Brooked connects via your VPC's public-facing endpoint with allow-listed IPs. For clusters in private subnets, Brooked supports PrivateLink for enterprise customers — short setup call to configure.
What about Redshift Spectrum (querying S3)?
Spectrum is exposed via the same SQL interface — Brooked queries through Redshift's normal interface, so anything Redshift can query (including Spectrum external tables) is available through Brooked.
Can I schedule Redshift refreshes into Google Sheets automatically?
Yes, on the Pro plan. Set any Redshift query or table to refresh every 15 minutes, hourly, daily, or weekly — the sheet updates on its own with no manual re-run. Most teams put dashboards on an hourly schedule and finance models on a daily one.
Why does my Redshift connection time out from Google Sheets?
Usually the connector's IP isn't allow-listed on your Redshift security group, or the cluster sits in a private subnet with no public endpoint. Add Brooked's IPs to the inbound rules, confirm the cluster is publicly accessible (or use PrivateLink for private subnets), and check that port 5439 is open. The Troubleshooting section above maps each error string to its fix.
Connect Redshift to Sheets in under 10 minutes.
Free tier covers 100 imports per month with AI Analyst — works with provisioned clusters and Redshift Serverless. See the full Redshift integration details.
Install Brooked free →
