AWS Redshift

Connect AWS Redshift to Wobby

To connect your Amazon Redshift cluster to Wobby, follow these steps:

• Create a user with read-only access.

• Grant access to the relevant database and schema.

• Allow inbound traffic from Wobby’s static IP.

• Set up the connection in the Wobby interface.

⚠️ Wobby’s agents only run read-only queries on your data. No write or admin privileges are required.

1. Create a Read-Only User in Redshift

You can use your existing admin account to create a technical user for Wobby. Replace placeholders (e.g. <your_strong_password>, analytics_db, public) with your actual values.

-- Create the user
CREATE USER wobby_user WITH PASSWORD '<your_strong_password>';

-- Grant read-only access to the database and schema
GRANT CONNECT ON DATABASE analytics_db TO wobby_user;
GRANT USAGE ON SCHEMA public TO wobby_user;
GRANT SELECT ON ALL TABLES IN SCHEMA public TO wobby_user;
GRANT SELECT ON ALL VIEWS IN SCHEMA public TO wobby_user;

-- Ensure access to future tables/views
ALTER DEFAULT PRIVILEGES IN SCHEMA public GRANT SELECT ON TABLES TO wobby_user;
ALTER DEFAULT PRIVILEGES IN SCHEMA public GRANT SELECT ON VIEWS TO wobby_user;

✅ Use a dedicated database and schema for analytics/reporting if possible. ✅ Only grant access to the data Wobby should analyze.

2. Allow Wobby’s IP Address (If Firewall Enabled)

If your Redshift cluster is behind a firewall or VPC security group, allow inbound traffic from Wobby’s static IP:

34.77.172.158

More detailed info on how to do this:

• In the AWS Console, go to Redshift → Clusters.

• Click your cluster, then look for Network and security settings.

• Find the VPC security groups list, and click the link to your cluster’s security group.

• In the EC2 Security Groups page, go to the Inbound rules tab.

• Click Edit inbound rules.

• Add a new rule:

  • Type: Redshift (or Custom TCP)

  • Port: 5439 (or your configured port)

  • Source: 34.77.172.158 (Wobby’s static IP)

• Save the rule.