Redshift

Sync your Pylon support data into your Redshift warehouse.

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

Trusted by 1,500+ B2B customers globally

Why teams use it

Analyze support data alongside the rest of your business

Pipe Pylon's ticket and customer data directly into Redshift so it lives next to your other warehouse data for unified reporting and analysis.

Choose the Redshift setup that fits your stack

Connect whether you run Redshift Standard or Redshift Serverless. Pylon supports both, with a setup path tailored to each.

Keep your data secure with scoped, temporary access

Pylon uses IAM role credentials to access your Redshift resources only temporarily, backed by minimum-required permissions and an external ID for an extra layer of security.

Get up and running with a guided sync

Create, test, and enable a sync from the Pylon dashboard, so you can confirm the connection works before turning it on.

How to install

Step 1

Create an IAM policy

In AWS, create a new IAM policy granting the minimum Redshift permissions plus S3 read access on the Pylon staging buckets (named exactly pylon-staging-*). Use the standard or serverless permission set depending on your Redshift type.

Step 2

Create an IAM role for Pylon

Create an IAM role with an "Another AWS account" trusted entity, enter Pylon's service account ID 825765419603, and supply an external ID for added security. Attach the policy from Step 1, and ensure both the role and Redshift have STS assume-role permissions in the trust policy.

Step 3

Grant permissions on your Redshift cluster

Associate the new IAM role with your cluster (Actions → Permissions → Manage IAM Roles for standard, or Workgroup → Security and encryption → Manage IAM roles for serverless), then run the provided SQL to create the DB user and grant the required database and schema permissions.

Step 4

Install the Redshift app in Pylon

Install the Redshift App from the Pylon Apps Directory and click Create to start a new sync. For serverless, provide the workgroup name; for standard, provide the cluster ID and DB user (not ARNs).

Step 5

Test, save, and enable the sync

Test your connection, save the settings, then toggle the sync on so it's connected and enabled. If you hit internal server or AWS permission errors, recheck your IAM and permissions setup.

Frequently asked questions

Does Pylon support both Redshift Standard and Redshift Serverless?

Yes. Pylon supports both, though the setup differs, so follow the instructions for the type you run.

How does Pylon access my Redshift data?

Pylon uses IAM role credentials to temporarily access your Redshift resources for sync purposes, scoped to the minimum permissions required.

Why does Pylon need S3 permissions?

Pylon uses an S3 staging approach for Redshift syncs, so the IAM policy must grant read access on the staging buckets, which must be named exactly pylon-staging-*. These buckets are not stored in your AWS account.

What do I need to provide when creating the sync?

For serverless, just the workgroup name (not an ARN). For standard, the cluster ID (not an ARN) and the DB user you created during cluster setup.

Other integrations

Pylon connects with the tools your team lives in — Slack, email, CRMs, ticketing systems,and more. Meet your customers where they are and streamline every support workflow.