Overview
Replicate Preview enables efficient data delivery into Amazon Simple Storage Service (S3), allowing organizations to use scalable object storage as a target for analytics, archival, and downstream processing workloads. Users can quickly configure replication pipelines by selecting source datasets and defining target bucket locations, enabling reliable data movement with minimal operational overhead. The platform simplifies cloud-based ingestion workflows while ensuring consistent and scalable data delivery.
Note
Amazon S3 is currently supported as both a source and target endpoint in Replicate Preview, limited to Snapshot (full load) replication mode, with Change Data Capture (CDC) and streaming replication not yet supported.
Connection Considerations
If you do not have a connection configured, refer to Connecting to Amazon S3 for more information.
When configuring and using a connection to Amazon S3, consider the following:
Configuration | Details |
|---|---|
Authentication Configuration | Ensure that the correct AWS authentication method is configured, including Access Key ID and Secret Access Key when applicable. Invalid or expired credentials are a common cause of connection failures. |
Bucket and Path Configuration | Verify that the target S3 bucket exists and that the configured folder or object path is valid. Incorrect bucket names or invalid paths may prevent replication jobs from writing data successfully. |
AWS Region Alignment | Ensure that the correct AWS region is specified for the target bucket. Region mismatches may result in connection or endpoint resolution errors. |
Network and Security Configuration | Confirm that firewall rules, VPC endpoint policies, proxy configurations, or organizational security controls do not block access between Replicate Preview and the Amazon S3 environment. |
SSL/TLS Connectivity | Amazon S3 connections use secure HTTPS/TLS communication. Ensure that SSL inspection or restrictive network policies do not interfere with secure connectivity. |
Object Naming Conventions | Review folder and file naming conventions used during replication. Avoid unsupported or inconsistent naming patterns that may impact downstream processing or integration workflows. |
Large File and Dataset Considerations | Large Snapshot replications may generate substantial object volumes or file sizes. Consider storage organization, partitioning strategy, and downstream consumption requirements when designing replication outputs. |
File Format and Output Structure | Understand the expected output format and folder hierarchy generated during replication. Ensure that downstream analytics or ingestion platforms are compatible with the generated structure. |
Cross-Account and Organizational Policies | In AWS environments using cross-account buckets or organizational SCP policies, ensure that replication traffic and bucket access are explicitly permitted. |