Object Storage is Vultr's S3-compatible, web-accessible service for storing and retrieving file objects. Objects can be accessed privately or publicly, over the web. Use cases for object storage include:
Object storage is ideal when you need to handle large quantities of file objects without managing or growing the underlying filesystem.
Select the Objects menu at the top of the Vultr customer portal to navigate to the object storage subscription listing, then use the Add Object Storage form to deploy. After deployment, view your access keys on the subscription listing page.
Objects are stored in buckets. Before you can begin uploading objects, you need to create at least one bucket. Buckets are similar to folders on a file system.
Buckets are web-accessible by name. For example, a bucket named
example in the New Jersey location is available at:
This bucket is also available using the alternate URL form:
If you delete a bucket or close a subscription, you'll need to wait up to 48 hours before you can reuse the old bucket name.
Objects transferred to object storage are private by default. You need a secret key to access them. Some tools allow you to change permissions to make objects, files, and buckets public. Be sure to check your tool's documentation and understand how it interacts with object storage.
Please see our pricing page for up-to-date information. Data transfer between Vultr Object Storage and Vultr VPS instances traverse the public internet and incur standard bandwidth charges.
Block storage provides mountable disk volumes for Vultr VPS instances. Object storage offers an internet-accessible endpoint to store and retrieve files via HTTPS.
Do not use object storage as a block device or mounted filesystem. The overhead of HTTP calls severely hinders performance, and we do not support this use. Please use Block Storage for mounted filesystems.
Vultr's object storage is S3-compatible and works with most tools designed for S3.
Yes, the rate limit, also known as a request limit, is 400 requests-per-second per IP address. If you exceed this limit, your requests will receive HTTP error code 429. If your application requires higher request volumes, we recommend deploying a caching proxy in front of your object storage for performance and security.
Yes, object storage is backed by NVMe caching for frequently accessed objects. The cache is not user-controllable.
No, we do not support using a white-labeled domain name for object storage. You must use the name shown for your object storage in the customer portal.
The Cloudflare Bandwidth Alliance program does not include object storage traffic.
The Vultr API offers several endpoints to manage Object Storage.
The table below lists compatibility between Vultr object storage and the S3 protocol. Compatibility may be further limited depending on the S3 tool used to access Vultr object storage.
For download requests, the "Content-Length" header may not match the size of the file, because files are gzip compressed to improve performance. In the rare event that this is causing issues for your automation system, you can disable gzip on requests.
|Bucket ACLs (Get, Put)||Yes|
|Bucket Access Logging||No|
|Bucket Object Versions||Yes|
|Bucket Request Payment||Yes|
|Get Bucket Info (HEAD)||Yes|
|Get Object Info (HEAD)||Yes|
|Object ACLs (Get, Put)||Yes|
|Policy (Buckets, Objects)||Yes|
The Boto3 SDK is compatible with Vultr Object Storage. See the documentation for Python code examples.