Skip to main content

Prerequisites

  • A OneBucket account — request one.
  • Live configuration: credentials, an endpoint, and a deployed policy connecting them together. First time here? Do the one-time setup first.
  • From OneBucket console: your S3 endpoint and an access key / secret key pair.
Use the global endpoint https://s3.onebucket.io — geoproximity DNS routes each request to the cluster closest to you, and your policy is active on every cluster. To pin a specific cluster, use its endpoint from your console, e.g. https://s3.<cluster>.onebucket.io.

Use it as S3

OneBucket speaks the S3 API with AWS SigV4 auth, so any S3 client or SDK works — just change the endpoint.
Because it’s standard S3, the same endpoint and keys work with SDKs in any language, s3cmd, rclone, and most S3-compatible tools.

Connect Claude

Prefer to work in natural language? Add OneBucket as an MCP connector and let Claude list, read, and manage your objects for you.

OneBucket Connector for Claude

Add core.onebucket.io as a custom connector, sign in, and ask Claude to work with your buckets.

Manage keys and tokens (CLI)

The onebucket CLI handles authentication and tokens — your data operations go through the S3 client above.

Next steps

  • Automate with AIconnect Claude for natural-language access to your data.
  • Span backends — copy, migrate, and locate objects across clouds, on-prem, and edge from the same client.
  • Cut egress — prefetch hot objects into the edge cache so repeat reads are served locally.