Issue
You may be unable to connect your storage destination (such as Snowflake) to Segment, preventing direct syncing of event data. This article explains alternative methods to access or export event data from Segment when standard storage destination connections are not possible.
Product
Segment
Environment
Segment Console
Cause
Storage destination connections may fail due to unsupported regions, network restrictions (such as inability to allowlist IPs), or lack of PrivateLink support.
Resolution
If you cannot connect your storage destination to Segment, you can access your event data using these alternative methods:
-
Amazon S3 Export (Recommended for Batch Access):
- Configure the Amazon S3 Destination in Segment to export raw event data as JSON files to an S3 bucket you control.
- Use your own ETL tools or Snowflake’s Snowpipe to ingest data from S3 into your data warehouse.
-
Extensible Webhook Destination (For Real-Time Streaming):
- Set up the Extensible Webhook Destination to stream event data to an endpoint you manage (such as AWS API Gateway).
- Process and route the incoming events to your internal systems as needed.
-
Profile API (Not Recommended for Bulk Extraction):
- The Profile API allows programmatic access to user or account objects, but is subject to strict rate limits and is not suitable for large-scale ETL.
Additional Information
- When using the S3 Destination, it is recommended to use an AWS IAM Role with a customer-generated External ID for secure cross-account access.
- Segment does not provide static source IPs for allowlisting; IAM Role-based access is the best practice.
- For detailed setup instructions, refer to Segment documentation for Amazon S3 Destination and Extensible Webhook Destination.