Vultr DocsLatest Articles

S3 Compatibility Matrix

Updated on January 7, 2025

Vultr Object Storage is designed to be compatible with the S3 protocol. However, specific features and capabilities may vary depending on the S3 tool used to access Object Storage.

Feature Compatibility List

Below is a detailed list of supported and unsupported features for Vultr Object Storage.

  • 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

Important Notes

Please review the following key points regarding feature compatibility and potential issues when using Vultr Object Storage

  • Feature Compatibility: Refer to the list above for details on supported features and functionality. Ensure the S3 tool you are using is compatible with the required features for your workflow.

  • Content-Length Header Discrepancy: For download requests, the Content-Length header might not match the actual file size. This occurs because files are gzip-compressed to enhance performance. If this discrepancy impacts your automation systems, you can disable gzip compression on requests to ensure the Content-Length matches the file size.

More Resources