Use the S3 tools you already have
STRG implements the commonly used Amazon S3 API surface with regional endpoints and AWS Signature Version 4 authentication.
Use the endpoint for the region that contains your bucket. STRG accepts HTTPS connections and Signature Version 4 requests; Signature Version 2 requests are rejected.
Regional endpoints
https://s3.us-east-1.strg.com US-Easthttps://s3.eu-central-1.strg.com EU-CentralBucket addressing styles
STRG supports both path-style and virtual-host-style addressing over HTTPS.
https://s3.<region>.strg.com/<bucket-name> Path stylehttps://<bucket-without-dots>.s3.<region>.strg.com Virtual host styleVirtual-host-style addressing requires a bucket name without dots. For bucket names containing dots, use path-style addressing. Replace <region> with the region that contains your bucket.
Buckets
CreateBucketSupportedListBucketsSupportedDeleteBucketSupportedGetBucketLocationSupportedObjects
PutObjectSupportedGetObjectSupportedHeadObjectSupportedCopyObjectSupportedDeleteObjectSupportedListObjectsV2SupportedLarge objects
CreateMultipartUploadSupportedUploadPartSupportedCompleteMultipartUploadSupportedAbortMultipartUploadSupportedListPartsSupportedSecurity & access
AWS Signature Version 4SupportedHTTPS endpointsSupportedBucket-level private and public-read ACLsSupportedProvider-managed encryption and SSE-CSupportedAWS Signature Version 2Not supportedSSE-KMSNot supportedIAM rolesNot supportedObject taggingNot supportedStatic website configurationNot supportedChange the endpoint, not your tooling
aws s3 ls --endpoint-url https://s3.us-east-1.strg.com --region us-east-1
Use your STRG access key as the AWS access key ID and your STRG application key as the secret access key. Existing AWS SDKs and S3 clients can use the same regional endpoint configuration.
Validate your integration
S3 implementations differ at the edges. Before migrating production data, test authentication, permissions, error handling, multipart behavior and any third-party integration you rely on.