Connecting over S3

Myota Cyberstorage for Objects speaks the S3 API. Point any S3-compatible tool at your endpoint, sign requests with Signature Version 4, and use your access keys.

Endpoint

Use this endpoint for S3 requests:

https://s3.demo.myota.io

The address shown is a demo endpoint. Your real endpoint is the one for your Myota tenant; the region and the path-style and Signature V4 settings used throughout this guide are the real defaults.

Region and locations

For S3 requests, use the region value us-east-1 wherever a region is required. This is the endpoint’s region, used for request signing.

Where your objects physically spread is a separate matter, and it is not a fixed list you choose from in your S3 configuration. The spread is set by the shard repositories configured for your tenant, which can span one or more storage providers. See Security and resilience.

Request signing

Sign requests with AWS Signature Version 4. Most S3 tools and SDKs do this for you once you set the endpoint, region, and access keys.

Addressing style

If a tool cannot resolve virtual-hosted-style bucket URLs, switch it to path-style addressing. The examples in CLI and SDKs show where to set this.