Storage Transfer Service release notes

Storage Transfer Service now supports AWS GovCloud (US) regions, including us-gov-east-1 and us-gov-west-1. You can now transfer data from Amazon S3 buckets located in GovCloud regions using both batch and event-driven transfers.

For more information, see Configure access to a source: Amazon S3 and Event-driven transfers from AWS S3.

The size limit for manifest files used in agent-based transfers has been removed.

For more information, see Transfer specific files or objects using a manifest.

Organization Policy Service custom constraints are now available for Storage Transfer Service. You can use custom constraints to control how Storage Transfer Service is used in your organization. For example, you can restrict transfers to only allow Cloud Storage to Cloud Storage transfers, or restrict transfers to a specific list of approved source buckets.

See Custom organization policy constraints for details.

Storage Transfer Service event-driven transfers are now available for Azure Blob Storage and Data Lake Storage Gen2 sources. Event-driven transfers listen to Azure Event Grid notifications via Azure Storage Queues to automatically transfer new or updated objects from your Azure container to Cloud Storage.

For more information, see Event-driven transfers from Azure Blob Storage or Data Lake Storage Gen2.

You can now transfer data from AWS S3 or Azure Blob Storage to Cloud Storage over a private network connection, using Cross-Cloud Interconnect or Partner Interconnect. Transferring data over a private connection can optimize costs, provide dedicated bandwidth, and help meet compliance needs by keeping data off the public internet.

See Transfer from AWS or Azure over a customer-managed private network for details.

Storage Transfer Service agent-based transfers now support Cloud Storage regional endpoints. When you specify a Cloud Storage regional endpoint for a transfer agent, all data transfer traffic through that agent to or from a Cloud Storage bucket remains within the specified Google Cloud region.

See Regional endpoints for details.

You can now delegate permissions to a user-managed service account for agentless transfers, instead of using the default Google-managed service agent. This allows for more granular permission control by assigning specific bucket permissions to different user-managed service accounts, and restricting which users can use those service accounts for transfer jobs.