Developers

It is the S3 API. Change the endpoint and keep your code.

No XNS SDK, no client library, no proprietary protocol. Point boto3, the AWS CLI, mc or your own signer at the gateway you run, sign with Signature Version 4, and everything below is reference material for the parts where the details matter.

# the whole integration aws s3 ls --endpoint-url https://relayer.example.com --region us-east-1
Start here

Four routes, depending on what you are doing today

Each one lands on a page that answers the whole question rather than a table of contents. The full reference tree sits one step deeper if you already know what you are looking for.

Sandbox: a live Relayer to test against, no install and nothing stored.

Reference

The S3 API reference, operation by operation

Eight pages covering what the gateway does with each family of requests, written against the running implementation rather than a specification summary.

Operating the gateway itself — certificates, disks, tenants, webhooks, the audit log and the monitoring views — is covered in the Relayer manual. Deployment builds and release notes are on Releases & downloads.

Read the matrix before you write a line of code.

Most storage evaluations end with a surprise in month three. Ours is published up front: every operation, tested and listed, next to the same operation on six other object stores. Check the ones your code actually calls, then decide.


Claims on this page last verified
© Copyright - SCP, Corp | Xa Net Services and Affiliates