Object Storage

Nirvana Object Storage gives each of your projects S3-compatible buckets in a region. It speaks the S3 API, so any S3 client works: the AWS CLI, boto3, rclone, and the AWS SDKs for other languages.

You manage buckets and access keys through the Nirvana API, the CLI and the Terraform provider. You read and write objects with an S3 client, pointed at your region’s endpoint.

How It Fits Together

• A bucket belongs to a project and a region. Its name is how S3 clients address it. See Buckets.
• An access key also belongs to a project and a region, and works for every bucket of that project in that region. See Access Keys.
• Every region has one S3 endpoint. Point your client at it, with a key from the same project and region as the bucket.

Region Endpoints

Region	Location	S3 endpoint
us-sva-2	San Jose, CA, USA	https://s3.sva2.nirvanacloud.io
us-wdc-1	Washington, D.C., USA	https://s3.wdc1.nirvanacloud.io

Buckets and access keys belong to one region, and a key works only with that region’s endpoint.

Each bucket also reports its own endpoint and signing_region in the API. Use those values when you configure a client, as shown in the Quickstart.

URL Styles

Both S3 URL styles work:

• Path style: https://s3.sva2.nirvanacloud.io/<bucket>/<key>
• Virtual-hosted style: https://<bucket>.s3.sva2.nirvanacloud.io/<key>

us-wdc-1 uses the same two styles with s3.wdc1.nirvanacloud.io.

We recommend path style. It also works for bucket names that contain dots, which don’t match the endpoint’s TLS certificate in virtual-hosted style.

Pricing

Storage costs $0.01 per GB-month, and egress is free. See Billing and Limits.

Next Steps

• Quickstart: create a bucket and a key, then upload your first object.
• Buckets: naming rules, tags and deletion.
• Access Keys: scope and rotation.
• Billing and Limits: pricing and the storage quota.
• Public Objects: the URL of a publicly readable object.