This guide explains how to export data from Insider to Amazon S3 and make it available for consumption in Amazon Redshift. Amazon S3 acts as the intermediary data lake between Insider One and Redshift.
Overview
Insider One exports event or user data to a customer-owned Amazon S3 bucket.
Amazon Redshift reads data from Amazon S3 using customer-configured ingestion pipelines (e.g., COPY command).
Data is processed, transformed, or queried in Redshift according to your needs.
This approach enables scalable, decoupled, and flexible data pipelines without direct system-to-system dependencies.
Prerequisites
Insider One
Access to an Insider One account with permissions to configure data exports
Ability to configure Amazon S3 as an export destination
Amazon Web Services (AWS)
An AWS account
Permissions to create and manage S3 buckets
IAM permissions allowing Insider One to write data to the selected bucket
Amazon Redshift
Access to an Amazon Redshift cluster
Permissions to configure data ingestion from Amazon S3 (e.g., IAM roles, cluster permissions)
Step 1: Set Up Amazon S3 Export in Insider One
Insider One supports exporting data directly to Amazon S3. Using the Insider One dashboard, you can:
Select or create an Amazon S3 bucket for export
Configure IAM credentials and bucket policies that allow Insider One to write data
Choose export frequency and data types (for example, events or user attributes)
Validate the integration and monitor exported files in S3
For detailed, up-to-date instructions, refer to Export data to Amazon S3 (Insider One).
Step 2: Consume Insider One Data in Amazon Redshift
Once data is available in Amazon S3, it can be consumed by Amazon Redshift using customer-defined ingestion pipelines. Redshift supports multiple approaches for ingesting data from Amazon S3, including:
Common Ingestion Patterns
Batch ingestion using the COPY command for scheduled, ad-hoc, or backfill workloads
Automated or scheduled loads using Redshift Spectrum or external tables (if applicable)
The choice of ingestion method depends on:
Desired data freshness
Pipeline architecture
Operational preferences of your team
Insider One does not require or enforce a specific Redshift ingestion method.
For implementation details, refer to Amazon Redshift documentation:
Step 3: Automation and Monitoring
To operate a reliable pipeline:
Configure Insider One export schedules to match your desired data refresh cadence
Use Amazon Redshift monitoring and alerting tools to track ingestion health and troubleshoot issues