Object Storage is Vultr's S3-compatible, web-accessible cloud object storage service for storing and retrieving file objects. Objects can be accessed privately or publicly over the web. Use cases for cloud object storage include:
Object storage is ideal when handling large file objects without managing or growing the underlying filesystem.
Select the Objects menu at the top of the 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.
You store objects in buckets. Buckets are similar to folders on a file system. You need to create at least one bucket before you upload objects.
Buckets are web-accessible by name in two different formats. For a bucket named example in the New Jersey location, you can access it through either of these two formats:
https://ewr1.vultrobjects.com/examplehttps://example.ewr1.vultrobjects.com/
If you delete a bucket or close a subscription, you must 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.
The table below lists the compatibility between Object Storage and the S3 protocol. Compatibility may be further limited depending on the S3 tool used to access 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. If this is causing issues for your automation system, you can disable gzip on requests.
| Bucket ACLs (Get, Put) | Yes |
| Bucket Access Logging | No |
| Bucket Inventory | No |
| Bucket Lifecycle | No |
| Bucket Location | Yes |
| Bucket Notification | No |
| Bucket Object Versions | Yes |
| Bucket Replication | No |
| Bucket Request Payment | Yes |
| Bucket Website | No |
| CORS | Yes |
| Copy Object | Yes |
| Create Bucket | Yes |
| Delete Bucket | Yes |
| Delete Object | Yes |
| Get Bucket Info (HEAD) | Yes |
| Get Object | Yes |
| Get Object Info (HEAD) | Yes |
| List Buckets | Yes |
| Multipart Uploads | Yes |
| Object ACLs (Get, Put) | Yes |
| Object Metadata | Yes |
| Object Tagging | Yes |
| POST Object | Yes |
| Policy (Buckets, Objects) | Yes |
| Pre-Signed URLs | Yes |
| Put Object | Yes |
You can transfer objects (files) to Object Storage with standard S3 tools. This is not an exhaustive list, but we do recommend the following tools:
You can perform basic Object Storage management tasks in the Vultr web portal. Some operations are limited. For example, the web portal cannot delete a bucket with more than 50,000 objects. Power users should use one of the other tools below to work with Object Storage such as s3cmd.
Cyberduck is a graphical file manager for Windows and Mac. It supports S3, FTP, and many popular file-sharing services. See our article How to Use Cyberduck with Vultr Object Storage.
S3 Browser is a freeware Windows client for S3-compatible object storage. See our article How to use S3 Browser with Vultr Object Storage.
S3cmd is a command line S3 client for Linux and Mac. See our article How to Use s3cmd with Vultr Object Storage.
UpdraftPlus is a popular WordPress backup plugin. See our article How to Back Up WordPress to Vultr Object Storage with UpdraftPlus.
Rclone is a command-line program to manage files on cloud storage. See our article How to use Rclone with Vultr Object Storage.
The Boto3 SDK is compatible with Object Storage. See the documentation for Python code examples.
Creating Vultr Object Storage With the Vultr Go Client.
How to Use Vultr Object Storage with PHP
Object storage offers an internet-accessible endpoint to store and retrieve files via HTTPS. Block storage provides mountable disk volumes for cloud servers. Block storage is not available for Vultr Bare Metal.
Vultr's object storage is S3-compatible and works with most tools designed for S3.
Do not use object storage as a block device or mounted filesystem. Object Storage provides an S3-compatible REST API. Do not use object storage as a block device or mounted filesystem. The overhead of HTTPS calls severely hinders performance, and we do not support this use. Please use Block Storage for mounted filesystems.
Yes, Object Storage caches frequently accessed objects on NVMe storage. The cache is not user-controllable.
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 for performance and security in front of your object storage.
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.
Files (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.
Yes, the limit is 400 requests per second per IP address. If you exceed this limit, your requests will receive HTTP error code 429.
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.
Object storage cleanup can take up to 48 hours to complete from the time you close the subscription. Please wait for storage cleanup before reusing bucket names.
No, the Cloudflare Bandwidth Alliance program does not include Object Storage traffic.
The Vultr API offers several endpoints to manage Object Storage.