All Integrations
AWS S3
x

Connect AWS S3 to Pigment and centralize planning data

Load the CSV extracts your data teams already store in AWS S3 into Pigment, and export planning data back to your buckets through Pigment’s API. Built for IT and Transformation teams fitting planning into an existing AWS stack, and for FP&A, Supply Chain, and RevOps teams who want current actuals without handling files.

AWS S3

AWS S3

Connect AWS S3 to Pigment to load CSV files from your buckets into planning models and export Pigment data back to S3.

Category

File Storage Systems

Integration method

Native Connector
API

Best for

Actuals loading · Data lake planning · Plan data export

See documentation

What can you do with AWS S3 and Pigment?

  • Refresh actuals from the latest extract. An FP&A analyst points the import at a dated path, and Pigment loads the most recent matching file each time the import runs, so plans start from the same extracts the data team maintains.
  • Keep Dimension Lists current. Load cost center, product, or entity files from S3 into Pigment Lists so models use the same structure as your source systems.
  • Stage approved plans to your warehouse. Your IT team runs an AWS Lambda function that calls the Pigment export API, writes plan data to S3, and stages it for Snowflake.
  • Import without separate AWS logins. An admin sets up the connection once, and model builders in approved Applications import from the bucket without their own AWS credentials.

How the AWS S3 integration works

An AWS admin creates a dedicated IAM user with read access to the bucket and generates its access keys. In Pigment, you add the connection under Settings > Integrations with the bucket name, region, and keys. Model builders then choose Integration in the Import data interface and load a fixed file or the most recent dated file into a Block.

Exports run through a different path. You create an AWS Lambda function with a Python script that calls the Pigment REST API and saves the result to S3. You can schedule it with Amazon EventBridge Scheduler. From there, S3 can act as the staging step for Snowflake.

Key capabilities

  • Match how your extracts are named. Pigment reads ISO-8601 dates in file or folder names, so data teams don't rename exports for planning.
  • Limit what Pigment can read. Pigment connects through a dedicated IAM user with read access only to the bucket you share.
  • Decide which Applications use each bucket. Each connection covers one bucket, and its Application access setting controls which Pigment Applications can import from it.
  • Keep your encryption policy intact. Pigment reads buckets encrypted with SSE-S3 or SSE-KMS, including customer-managed keys once you grant the Pigment user kms:Decrypt.
  • Export on your own schedule. Trigger the Lambda export with Amazon EventBridge Scheduler and choose which Views, Lists, Metrics, or Tables land in S3.

Frequently Asked Questions

Which file formats and import modes does the AWS S3 integration support?

The integration loads CSV files in two modes. Fixed file mode loads one exact path, such as folder1/folder2/file.csv. Most recent file mode uses a date placeholder in the file or folder name and loads the newest matching file.

Can AWS S3 imports run on a schedule?

Yes. You can schedule an S3 import configuration to run automatically, with up to four schedules per configuration and notifications if an import fails. With most recent file mode, each scheduled run picks up the newest dated file in the folder.

Can Pigment export data back to AWS S3?

Yes, through the Pigment REST API rather than the native connector. An AWS Lambda function calls the export API and saves data from Views, Lists, Metrics, or Tables to an S3 bucket, and you can schedule it with Amazon EventBridge Scheduler. See the export guide for setup steps.

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.

Three colleagues focused on an iMac screen in a bright office with plants and modern artwork.

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