Connect AWS Redshift to Pigment and plan with up-to-date data
Bring financial and operational data from AWS Redshift into Pigment through a native connector, so forecasts and planning models start from the latest warehouse data. Finance, Sales, Supply Chain, and Operations teams plan from the same figures the data team maintains. IT controls which tables Pigment can read and which Applications can use the connection.

AWS Redshift
Connect AWS Redshift to Pigment to plan from the latest actuals in your data warehouse.
Category
Integration method
Best for
Actuals refresh · Rolling forecasts · Variance analysis
What can you do with AWS Redshift and Pigment?
- Update forecasts before the next review. Planning teams schedule actuals imports from AWS Redshift, so forecasts in Pigment start from the latest actuals.
- Analyze performance against plans. Bring actuals into Pigment Metrics alongside budgets and forecasts to find variances in financial and operational performance without building spreadsheet extracts.
- Keep Dimension Lists in sync. Model builders update Dimension Lists, such as products, regions, or cost centers, from AWS Redshift so new items appear in Pigment without manual entry.
- Build demand plans from shared data. Supply Chain and Operations teams bring demand and operational data stored in AWS Redshift into Pigment as inputs for demand forecasts and resource plans.
How the AWS Redshift integration works
IT sets up a Redshift database user with SELECT access to the needed tables and an IAM user with Redshift and Redshift Data API permissions. A Pigment Workspace Admin adds the connection with the IAM user's access key and secret key, then picks which Applications can use it.
In an Application, you open a Transaction List, Dimension List, or Metric, choose the integration as the import source, and enter a SQL query.
Key capabilities
- Choose exactly the data you plan with. Write a SQL query that selects the fields and filters you need from any table the database user can read.
- Scope warehouse access. Pigment reads through a database user with
SELECTaccess only to the tables IT chooses, so planning teams get what they need without access to the rest of the warehouse. - Restrict access to approved Applications. Workspace Admins choose which Applications can use the AWS Redshift connection.
- Set imports to run on their own. Schedule an import with up to 4 schedules per import configuration, and get notified in-app, by email, or in Slack if a run fails.
- Control who configures and runs imports. The Configure Imports and Run Imports permissions separate who can create import configurations from who can run existing ones.
Frequently Asked Questions
What data can I import, and is there a size limit?
You can import the result of any SQL query on tables the database user can read, into a Transaction List, Dimension List, or Metric. Each query result can be up to 100MB, a limit set by the Amazon Redshift Data API. For larger datasets, you can load files through the AWS S3 integration instead.
Will FP&A have to ask IT for every data refresh?
No. Once IT creates the AWS users and a Workspace Admin sets up the connection, scheduled imports refresh your data without anyone stepping in. Members with the Run Imports permission can also rerun a saved import whenever they need newer numbers.
Can Pigment send data back to AWS Redshift?
Not through the Redshift connector, which only imports data. To send plan data to Redshift, export it to an S3 bucket through the Pigment REST API, then load it into Redshift from there.
Related integrations
See Pigment in action
The fastest way to understand Pigment is to see it in action. Sign up today and explore how agentic AI can transform the way you plan.

From 8 days to 4 min
Update P&L actuals & financial forecasting
80%
Time cut on data aggregation
12 hours
Saved per month on executive reporting
6 days faster
For scenarios creation and analysis