How to Configure Windsurf Redshift Permissions

Published
Length
3 min read

Luis Felipe Dias

All posts

You set up windsurf redshift permissions by creating a scoped database role for your agent. Next, you pass those login keys to your local shell or server settings. Note that on June 2, 2026, Cognition renamed Windsurf to Devin Desktop. The app keeps the same IDE and features under the new name. Teams often connect the agent to data warehouses using their own admin keys. Overly broad roles let the agent change schemas, drop tables, or pull sensitive rows. How windsurf redshift permissions work

Your coding agents run with your access.

Claude Code reaches prod with a developer's credentials, and approval prompts get clicked through. hoop.dev checks every query, masks sensitive data, and holds risky changes for a human.

You set up windsurf redshift permissions by creating a scoped database role for your agent. Next, you pass those login keys to your local shell or server settings. Note that on June 2, 2026, Cognition renamed Windsurf to Devin Desktop. The app keeps the same IDE and features under the new name. Teams often connect the agent to data warehouses using their own admin keys. Overly broad roles let the agent change schemas, drop tables, or pull sensitive rows.

How windsurf redshift permissions work in practice

The agent reaches external data warehouses in two main ways. First, the agent can run terminal commands on its own with user permission. It uses a dedicated terminal that loads your local shell setup. On macOS it uses zsh, and on Linux it uses bash. Because it loads your shell setup, your aliases and shell variables are ready. If you store database keys in your shell profile, the agent can use them. It can run command line database tools using those exact login details.

Second, the legacy Cascade agent connects to Model Context Protocol servers. You set up these servers in a local JSON settings file. A database server reads your warehouse keys and runs SQL queries for the agent. In both paths, Redshift only checks the database user or role you provide. You must create a specific database role inside your warehouse first. Grant that role read access only to the schemas your project needs. Then give the agent a database user tied to that narrow role. Never share your personal admin login with the local coding agent.

What native database roles solve and what they miss

Native warehouse roles control which schemas and tables a user can read or write. They stop an agent from touching billing tables if you block those schemas. They also block table drops when you grant read-only rights to the role. This setup decides who can log in and which objects they can touch.

Still, static database roles leave a big gap during daily work. A role cannot check what an individual SQL statement does in flight. If the agent needs a customer table to debug code, it gets the whole table. A native role will return raw emails, phone numbers, card numbers, and national IDs. Also, shared keys sit in plain text inside local shell files or settings files. Every query from the agent looks the same in your warehouse logs. You cannot see if a human or an agent ran a heavy query. And if you allow write queries for testing, the agent runs them right away. Native roles lack step-by-step approval checks for risky commands.

Redshift Security + AI Agent Permissions: architecture patterns and best practices

Continue reading? Get the full guide.

Free. No spam. Unsubscribe anytime.

Scoping agent queries at the statement level

Safe agent setups separate login rights from query controls. Begin by stripping write permissions from the database role the agent uses. Give the role access to safe views instead of raw production tables. Keep live keys out of local shell profiles whenever you can. Review every terminal command before you let the agent run it. For shared data warehouses, add controls that check queries in flight and rewrite sensitive fields.

Govern statements and responses across databases and APIs

Good config and scoped roles are needed setup. They do not check single queries in flight or mask sensitive fields in returned rows. Across Postgres, MySQL, SQL Server, MongoDB, ClickHouse, Kubernetes APIs, SSH, and internal HTTP endpoints, hoop.dev sits inline in the protocol beside each supported service as an open-source proxy, a sidecar for your database or API. For every query or command an AI agent or engineer runs against production, hoop.dev decides to pass, mask, block, or hold it for human approval.

First, hoop.dev guardrails block banned queries before they run or hold risky ones for review, and hoop.dev data masking rewrites matched sensitive values in responses in memory. Furthermore, hoop.dev holds SOC 2 Type II and is open source on GitHub.

Frequently asked questions

Did Windsurf change its name to Devin Desktop?

Yes, Cognition announced that Windsurf became Devin Desktop on June 2, 2026. The app keeps the same IDE, agent features, and local terminal setup.

How does the agent read my local Redshift login keys?

The agent runs commands in a dedicated terminal that loads your shell setup. Any database keys stored in your shell variables are open to the agent.

Why are read-only roles not enough for AI coding agents?

Read-only roles still let the agent pull entire tables with sensitive customer data. They do not rewrite emails or card numbers in query results.

The query runs. The emails stay hidden.