Stay organized with collections
Save and categorize content based on your preferences.
Storage Transfer Service can listen to event notifications in AWS or Google Cloud
to automatically transfer data that has been added or updated in the source
location. Event-driven transfers are supported from AWS S3 or Cloud Storage,
and always use a Cloud Storage bucket as the destination.
Event-driven transfers listen to Amazon S3 Event Notifications
sent to Amazon SQS for AWS S3 sources. Cloud Storage sources send
notifications to a Pub/Sub subscription.
Benefits of event-driven transfers
Because event-driven transfers listen for changes to the source bucket, updates
are copied to the destination in near-real time. Storage Transfer Service doesn't need
to execute a list operation against the source, saving time and money.
Use cases include:
Event-driven analytics: Replicate data from AWS to Cloud Storage to
perform analytics and processing.
Event-driven transfers with Storage Transfer Service differ from
typical Cloud Storage replication by creating
a copy of your data in a different bucket.
This provides benefits such as:
Keeping development and production data in separate namespaces.
Sharing data without providing access to the original bucket.
Backing up to a different continent, or to an area not covered by
dual-region and multi-region storage.
DR/HA setup: Replicate objects from source to backup destination in order
of minutes:
Cross-cloud backup: Create a copy of AWS S3 backup on Cloud Storage.
Cross-region or cross-project backup: Create a copy of Cloud Storage
bucket in a different region or project.
Live migration: Event-driven transfer can power low-downtime migration, on
the order of minutes of downtime, as a follow up step to one-time batch
migration.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-07 UTC."],[],[],null,["# Event-driven transfers\n\nStorage Transfer Service can listen to event notifications in AWS or Google Cloud\nto automatically transfer data that has been added or updated in the source\nlocation. Event-driven transfers are supported from AWS S3 or Cloud Storage,\nand always use a Cloud Storage bucket as the destination.\n\nEvent-driven transfers listen to [Amazon S3 Event Notifications](https://docs.aws.amazon.com/AmazonS3/latest/userguide/NotificationHowTo.html)\nsent to Amazon SQS for AWS S3 sources. Cloud Storage sources send\nnotifications to a Pub/Sub subscription.\n\nBenefits of event-driven transfers\n----------------------------------\n\nBecause event-driven transfers listen for changes to the source bucket, updates\nare copied to the destination in near-real time. Storage Transfer Service doesn't need\nto execute a list operation against the source, saving time and money.\n\nUse cases include:\n\n- **Event-driven analytics**: Replicate data from AWS to Cloud Storage to\n perform analytics and processing.\n\n- **Cloud Storage replication**: Enable automatic, asynchronous object\n replication between Cloud Storage buckets.\n\n Event-driven transfers with Storage Transfer Service differ from\n [typical Cloud Storage replication](/storage/docs/availability-durability#cross-region-redundancy) by creating\n a copy of your data in a different bucket.\n\n This provides benefits such as:\n - Keeping development and production data in separate namespaces.\n - Sharing data without providing access to the original bucket.\n - Backing up to a different continent, or to an area not covered by dual-region and multi-region storage.\n- **DR/HA setup**: Replicate objects from source to backup destination in order\n of minutes:\n\n - Cross-cloud backup: Create a copy of AWS S3 backup on Cloud Storage.\n - Cross-region or cross-project backup: Create a copy of Cloud Storage bucket in a different region or project.\n- **Live migration**: Event-driven transfer can power low-downtime migration, on\n the order of minutes of downtime, as a follow up step to one-time batch\n migration.\n\nLearn how\n---------\n\n- [Set up event-driven transfers from Cloud Storage](/storage-transfer/docs/event-driven-google).\n- [Set up event-driven transfers from AWS S3](/storage-transfer/docs/event-driven-aws)."]]