Configuring existing Amazon S3 applications to work with Swarm consists of changing the region end-point and changing the authentication credentials.
...
Region end-point – Use the Swarm storage domain name in place of the Amazon S3 region end-point host name.
Access Key – In the Content UI, create an S3 authentication token in the correct domain and bucket, and use that token ID as your Access Key ID. For creating tokens in Content UI, see Setting Tokens.
Secret Key – From the same token, use its secret key value in your S3 applications.
Update your configuration for best results:
To avoid certificate validation failure, enable Enable "path style" access to avoid certificate validation failure; otherwise, the client/SDK may attempt to access as
mybucket.mydomain.example.com/object.For best performance, use Use Version 2 signatures with the AWS .NET SDK for best performance. See https://docs.aws.amazon.com/general/latest/gr/signature-version-2.html.
For multipart uploads, increase Increase the part size to 100 MB or more for multipart uploads, if configurable.
| Child pages (Children Display) |
|---|