/
Client-side S3 access

Client-side S3 access

Relevant Issue: https://sagebionetworks.jira.com/browse/PLFM-4253


StorageLocationSettings are immutable and thus can be cached client side. The information in these will therefore not be repeated in the new implementations of UploadDestination and FileHandle.

keyPrefixUUID is a new UUID generated by the backend every time a ExternalObjectStoreUploadDestination is requested.

The key in ExternalObjectStorageFileHandle, once uploaded will be keyPrefixUUID/fileName.

New API

The clients are responsible for creating FileHandles after upload has completed since Synapse does not have access to the new storage location

With the changes to the hierarchy of FileHandle, the POST /externalFileHandle service will be made generic to allow all implementations of ExternalFileHandleInterface

ActionURIMethodRequest BodyResponse Body
Creates any instance of an ExternalFileHandleInterface/externalFileHandlePOSTExternalFileHandleInterfaceExternalFileHandleInterface

Related content

Cloud Object Storage Requirements for Synapse
Cloud Object Storage Requirements for Synapse
More like this
Synapse S3 Storage Maintenance
Synapse S3 Storage Maintenance
More like this
External File Management
External File Management
More like this
Data Migration
Data Migration
More like this
Custom Storage Locations
Custom Storage Locations
More like this
Direct (STS Token) S3 access in Synapse
Direct (STS Token) S3 access in Synapse
More like this