Compatibility snapshot
The Cloud Storage to AWS profile supports core JSON object CRUD and listing, XML request re-signing, lifecycle, and versioning behavior. Google retention policies and notifications are outside the profile. Generation identifiers adapt to S3 version or ETag behavior.ARCHIVE and COLDLINE semantics differ because some S3 objects require restore before read, and compose rejects non-final parts smaller than 5 MiB.
Existing object bodies, versions, and shared links are not copied automatically.
Prerequisites
- an installed Google Cloud-origin Cloud Adapter endpoint;
- a Cloud Storage to S3 service adapter;
- an origin-side Google credential accepted by the endpoint;
- an AWS runtime identity with access to one test bucket;
- a separate read-only AWS verification profile;
- Python 3 with
google-cloud-storageand AWS CLI v2.