The Backblaze S3 Compatible API does not support unauthenticated ListObject calls on Public Buckets.Īs with the B2 Native API, the capabilities of an application key give you access to the S3 Compatible API. Key used for deleting files in the S3 Compatible API.
As a general rule, both the writeFiles and deleteFiles permissions should be associated with the WriteFiles permission is necessary when deleting by name and the deleteFiles permission is required when deleting a
The Delete Object and Delete Objects call may require that the App Key have both the writeFiles and deleteFiles capabilities. The listAllBucketNames permission can be enabled upon creation in the web UI or using If an Application Key is restricted to a bucket, the listAllBucketNames permission is required for compatibility
The automatically created Master Application Key is not supported in the Backblaze S3 Compatible API - onlyĪpplication Keys that are manually created in the Backblaze Web UI or via the Backblaze B2 Native API can be used to authenticate the Backblaze S3 Compatible For more information about App Keys, please see our documentation here. Please refer to the Buckets and Files page for namingįor the purposes of terminology, the Application Key and Application Key ID are the equivalent of the Secret Access The Backblaze S3 Compatible API features slightly different restrictions on file and Bucket names than the AWS S3ĪPI. The call will succeed only when specified ACL matches the ACL of The Put Object ACL call only supports the same canned ACL values mentioned The S3 Compatible API supports the Put Bucket ACL call to change between "private" and “public-read” only.Īttempting to put a different value will return an error. If aīucket is public, the ACL returned for the Bucket and any files within the bucket will be “public-read”. If a Bucket is private, the ACL returned for the Bucket and any files within the bucket will be “private”. For example, a Get Object ACLĬall returns the ACL for the Bucket the object is contained in. However, object-level ACLs are not supported. Get Object ACL and Getīucket ACL calls will work as expected. The Backblaze S3 Compatible API features limited support for ACLs (Access Control Lists). Note that this may vary slightlyįrom AWS S3 API documentation - this difference is expected based on the AWS S3 API. The Backblaze S3 Compatible API returns calls in the same way the AWS S3 API does. To learn more about S3 authentication, see this article. The Backblaze S3 Compatible API only supports v4 signatures for authentication and does not support v2 signatures at S3 Compatible API for Backblaze B2 and the Amazon S3 API.įollow our tutorial to get started with the Backblaze S3 Compatible API using Python: Backblaze B2 Quick Start: Using Python With the Backblaze S3 Compatible API Authentication This documentation will serve as a resource for developers and end-users to distinguish the differences between the If you aren’t currently a Backblaze B2 user you can start an account today and get your first 10GBs of storage free. Integrate B2 and see dramatic savings on your cloud storage bill. The Backblaze S3 Compatible API easily integrates with your existing data management tools and S3 gateways.īackblaze B2 Cloud Storage is ¼ the price of AWS S3 so you can quickly
0 kommentar(er)
