AMAZON S3 IN. GCS OUT. NO SCRIPTS.
Replicate Amazon S3 files into Google Cloud Storage
When an object lands in your Amazon S3 bucket, DocEvent delivers a copy into your Google Cloud Storage bucket. Event-driven S3-to-GCS replication with no Storage Transfer Service jobs, no scripts and a full audit trail.
From
Amazon S3
To
GCS
Receive endpoints
Cloud storage
Amazon S3
S3 Compatiblepull
GCS Blobpull
Azure Blobpull
Azure Data Lakepull
Azure Filespull
Servers & protocols
FTP Pull
SFTP Pull
HTTP Upload
Email
Apps & trading partners
SharePointpull
AS2trading partner
On-premise
Filerouterlocal filesystem
Agentlocal filesystem
DocEvent
routes · retries · logs
Send endpoints
Cloud storage
Amazon S3s3-compatible
GCSpush
Azure Blobpush
Servers & protocols
FTP / FTPS
SFTP
Webhook
Email
Apps & trading partners
SharePoint
AS2trading partner
On-premise
Filerouterlocal filesystem
Agentlocal filesystem
Get started for free — our basic plan is free forever.
How Amazon S3 to GCS routing works
Source
Amazon S3
Files arrive when objects are uploaded or created in an Amazon S3 bucket.
DocEvent Channel
routes · retries · logs
Destination
Google Cloud Storage
Files are delivered into your Google Cloud Storage bucket.
1
File arrives via Amazon S3
Triggered by S3 object-created events delivered via SNS. Supports all S3-compatible storage.
2
Channel routes it
DocEvent's channel server matches the incoming file to your configured route, queues it for delivery, and ensures no file is ever lost — even during downstream outages.
3
Delivered to GCS
Delivery into a Google Cloud Storage bucket, authenticated with a service-account key. Configurable folder (prefix) inside the bucket, and a built-in connection test that verifies the bucket, credentials and permissions before the first file flows. No Pub/Sub, no Storage Transfer Service, no scripts - each routed file is simply written into your bucket.
Common use cases
Real workflows that teams automate with a Amazon S3 → GCS channel.
- Mirror an S3 bucket into GCS for BigQuery and Vertex AI pipelines
- Hand a Google-Cloud-based partner delivery straight into their bucket
- Migrate from AWS to Google Cloud while both buckets stay live
- Keep a cross-cloud copy of critical objects as they arrive
The two ends don't have to be the same company — invite a customer or trading partner into the channel and they run the Amazon S3 or GCS side under their own account, with their own credentials. Learn how shared channels work.
Technical details
Source:
Amazon S3
Triggered by S3 object-created events delivered via SNS. Supports all S3-compatible storage.
Files arrive when objects are uploaded or created in an Amazon S3 bucket.Destination:
Google Cloud Storage
Delivery into a Google Cloud Storage bucket, authenticated with a service-account key. Configurable folder (prefix) inside the bucket, and a built-in connection test that verifies the bucket, credentials and permissions before the first file flows. No Pub/Sub, no Storage Transfer Service, no scripts - each routed file is simply written into your bucket.
Files are delivered into your Google Cloud Storage bucket.Automatic retries with exponential back-off
Full end-to-end audit log for every file
Zero-code setup via the DocEvent UI
Reliable delivery even during downstream outages