S3 COMPATIBLE (PULL) IN. GCS OUT. NO SCRIPTS.
Move files from S3-compatible buckets into Google Cloud Storage
DocEvent polls an S3 or S3-compatible bucket on a schedule - Amazon S3, Cloudflare R2, MinIO, Backblaze B2 or Wasabi - and delivers every new file into your Google Cloud Storage bucket. Cross-cloud transfer with no notifications, no scripts and a full audit trail.
From
S3 Compatible (pull)
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 S3 Compatible (pull) to GCS routing works
Source
S3 Compatible
DocEvent checks your S3 or S3-compatible bucket on a schedule and collects new files — Cloudflare R2, MinIO, Backblaze B2, Wasabi and more.
DocEvent Channel
routes · retries · logs
Destination
Google Cloud Storage
Files are delivered into your Google Cloud Storage bucket.
1
File arrives via S3 Compatible (pull)
Scheduled polling of any bucket that speaks the S3 API — Amazon S3, Cloudflare R2, MinIO, Backblaze B2, Wasabi, Supabase Storage and friends (custom endpoint URL and path-style addressing supported). Collects from a prefix with filename pattern filtering, then each collected file is deleted or moved to an archive prefix. No bucket notifications or event plumbing needed.
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 S3 Compatible (pull) → GCS channel.
- Sync Amazon S3, Cloudflare R2, MinIO, B2 or Wasabi into GCS on a schedule
- Collect a partner's drop bucket into your own GCS bucket
- Migrate to Google Cloud while both stores stay live
- Bridge providers with no event notifications or transfer tooling
The two ends don't have to be the same company — invite a customer or trading partner into the channel and they run the S3 Compatible (pull) or GCS side under their own account, with their own credentials. Learn how shared channels work.
Technical details
Source:
S3 Compatible
Scheduled polling of any bucket that speaks the S3 API — Amazon S3, Cloudflare R2, MinIO, Backblaze B2, Wasabi, Supabase Storage and friends (custom endpoint URL and path-style addressing supported). Collects from a prefix with filename pattern filtering, then each collected file is deleted or moved to an archive prefix. No bucket notifications or event plumbing needed.
DocEvent checks your S3 or S3-compatible bucket on a schedule and collects new files — Cloudflare R2, MinIO, Backblaze B2, Wasabi and more.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
Related channel integrations
Other destinations from S3 Compatible (pull)
- S3 Compatible (pull) → Amazon S3
- S3 Compatible (pull) → Azure Blob
- S3 Compatible (pull) → FTP
- S3 Compatible (pull) → SFTP
- S3 Compatible (pull) → HTTP Webhook
- S3 Compatible (pull) → SES Email
- S3 Compatible (pull) → AS2
- S3 Compatible (pull) → SharePoint
- S3 Compatible (pull) → Filerouter (on-premise)
- S3 Compatible (pull) → DocEvent Agent (on-prem)