Skip to main content
Object storage provides S3-compatible storage for your data on the Latitude.sh platform. Store and retrieve any amount of data using standard S3 APIs and tools you already know.

​
Creating a bucket

1

Open the create bucket flow

Log in to the Latitude.sh dashboard and navigate to Storage > Object storage in the sidebar. Click Create bucket.
2

Choose a storage class

Select the storage class for your bucket (for example, Standard). The storage class determines the bucket’s performance characteristics and pricing.
3

Choose a location

Pick the region and site where the bucket should live. Bucket data stays in the location you select.
4

Configure the bucket

Enter a Bucket name (see naming rules below). Optionally enable Versioning to keep object history, and Object lock to enforce write-once-read-many retention. Object lock requires versioning and lets you set a retention mode and period.
5

Create the bucket

Click Create bucket to finish.

​
Versioning and object lock

​
Versioning

Versioning preserves every version of an object in your bucket, so deletes and overwrites can be recovered by restoring a prior version. Enable it when you want a safety net against accidental changes or deletions.
Once versioning is enabled on a bucket, it cannot be disabled.

​
Object lock (WORM)

Object lock makes objects immutable for a retention period — write-once-read-many. Until the retention expires, the object cannot be deleted or modified, even by the bucket owner. Use it for regulatory compliance, audit trails, and protection against ransomware or accidental data loss. Two retention modes are available:
  • GOVERNANCE — Objects stay immutable until the retain-until date, but users with specific IAM permissions can override the lock.
  • COMPLIANCE — Objects stay immutable until the retain-until date and the lock cannot be reversed by any user, regardless of permissions.
Object lock must be enabled when the bucket is created — it cannot be added to an existing bucket. Object lock also requires versioning to be enabled.

​
Bucket naming rules

Bucket names must follow these requirements:
  • Be between 3 and 63 characters long
  • Start with a lowercase letter or number
  • Contain only lowercase letters, numbers, dots (.), and hyphens (-)
  • Be globally unique

​
Connecting to Object storage

Use any S3-compatible tool or library to interact with your buckets.

​
Connection details

Find your connection details in the Object storage sidebar:
  • Account ID: Your unique account identifier
  • S3 API endpoint: The endpoint URL for S3 API requests. The format depends on the storage class:
    • Standard: https://<account-id>.s3.latitude.sh
    • High performance: https://objects.<region>.storage.sh (for example, https://objects.nyc.storage.sh)

​
Bucket credentials

Each bucket gets an access key and secret key automatically when it’s created, shown on the bucket detail page immediately after.
The secret key is shown only once — right after the bucket is created. Copy it before you refresh or leave the page. If you lose it, you can create a new access key to regain access to the bucket.
The access key and endpoint remain visible on the bucket detail page after refresh, but the secret key does not.

​
Access keys

Access keys are project-scoped credentials that aren’t tied to a single bucket’s creation. To create one, navigate to the Access keys tab on the Object storage page and click Create access key. This requires a verified team and at least one existing bucket.
1

Choose a storage class and region

The key applies to buckets of the selected storage class in the selected region.
2

Choose an access scope

  • Full access — read and write across all buckets of the selected storage class.
  • Limited — scope the key to specific buckets, each set to Read-only or Read-write.
3

Name and create the key

Give the key a name unique within the project, then create it.
The secret key is shown only once, right after the key is created. Copy it before closing the dialog.
Created keys appear in the Access keys tab with their access key ID, permission, scoped buckets, storage class, and status.

​
Monitoring usage

The Object storage dashboard displays the following metrics:

​
Overview metrics

  • Total Storage: Total amount of data stored across all buckets
  • Total Objects: Number of objects stored across all buckets
  • Class A Operations: Write operations including PUT, POST, DELETE, and LIST requests
  • Class B Operations: Read operations including GET and HEAD requests

​
Storage by bucket

The Metrics tab shows a breakdown of storage usage per bucket, including the number of objects and percentage of total storage each bucket uses.

​
Pricing

See the storage pricing page for details.