Ordnary

Docs Ordnary Web Services Basics

Access keys

The S3 access key for your account: where to find it, how to use it with your tools, and how to rotate it.

3 min readBeginner

One key for the account

Ordnary R2 uses an Ordnary-issued access key pair, an access key ID and a secret access key, with the S3 API. The key belongs to your account, not to a bucket: it reaches every bucket you own. You find it under S3 API access on the Buckets page, together with the S3 endpoint.

Generate the key

  1. 1

    Open Buckets

    In the console, go to Ordnary R2 and then Buckets. The S3 API access section is below the bucket list.

  2. 2

    Generate

    Choose Generate access key. The console shows the endpoint, the access key ID and the secret access key.

  3. 3

    Save the secret now

    The secret is not shown again. Put it in your secret manager or your deployment's environment straight away.

Use it

AWS_ACCESS_KEY_ID=<access-key-id>

The access key ID from the console.

AWS_SECRET_ACCESS_KEY=<secret-access-key>

The secret, shown once.

AWS_ENDPOINT_URL_S3=https://s3.ordnary.com

Read by the AWS CLI and most SDKs, so you do not have to pass the endpoint on every command.

Most tools and SDKs read these variables, so the key never ends up in your code. Use auto as the region when a tool insists on one. See the S3 API for the details.

Rotate

Generating a new key replaces the current one for the whole account; clients still using the old key stop working the moment the new one exists. Plan a rotation: update every deployment with the new secret right after generating it. There is no grace period with two valid keys.

Do

  • Keep the secret in a secret manager or environment variables.
  • Rotate at once if you suspect a leak; the old key dies immediately.
  • Use the console's upload and browser for one-off work, so the key stays in deployments only.

Don't

  • Put the secret in client-side code or a public repository.
  • Share one key across teams that each need to be cut off separately. Today there is one key per account; use separate accounts for separate trust boundaries.
Was this page helpful?
Updated 25 October 2026 Suggest an edit

Choose which cookies Ordnary may use. You can change this at any time via Cookie settings at the bottom of every page.