| At line 2 changed 3 lines |
| Backblaze supports external integration through an HTTP-based REST API.\\ |
| __Restriction:__ REST API does not support resume on upload and mdtm(File modification time) changes. You can use the __S3 connection endpoint__ as a workaround.\\ |
| \\ |
| Backblaze supports external integration through an HTTP-based REST API ([Documentation Link| https://www.backblaze.com/apidocs/introduction-to-api-documentation]).\\ |
| ---- |
| At line 5 added 19 lines |
| See the [B2 Native API Documentation|https://www.backblaze.com/apidocs/introduction-to-the-b2-native-api]\\ |
| ---- |
| __⚠️ General restrictions__: Backblaze Storage is not a traditional file system but an object storage service. What appears to be a __folder__ is actually just a prefix in the object’s name. As a result, renaming folders is not supported. To __move__ a folder, you must copy all the objects to the new location and then delete them from the original one.\\ |
| B2 REST API does not support resumes on upload and MDTM(File modification time) changes. You can use the __S3 connection endpoint__ as a workaround. [2. Access Through S3 REST API Link|https://www.crushftp.com/crush11wiki/Wiki.jsp?page=BackBlaze(b2)%20integration#section-BackBlaze_28b2_29+integration-2.AccessThroughS3RESTAPI]\\ |
| ---- |
| __⚠️ Proxy Configuration:__ If your server accesses the internet through a proxy, make sure to whitelist the following domains for Backblaze Authentication and Drive access: __api.backblazeb2.com__\\ |
| ---- |
| Create __App Keys__ on Backblaze:\\ |
| __1.)__ Go to the __Backblaze__ website: [Link|https://www.backblaze.com/]\\ |
| __2.)__ Log in to your __Backblaze B2 Cloud Storage account__.\\ |
| __3.)__ Navigate to the Buckets section (under __B2 Cloud Storage__).\\ |
| __4.)__ Click on __App Keys__ in the left-hand menu.\\ |
| __5.)__ Click __Add a New Application Key__.\\ |
| __6.)__ Configure the key:\\ |
| • Name your key.\\ |
| • Set permissions (read/write).\\ |
| • (Optional) Restrict the key to a specific bucket or folder.\\ |
| __7.)__ Click __Create New Key__.\\ |
| __8.)__ Copy and securely store the __Key ID__ and __Application Key__. ⚠️ The Application Key is shown only once after creation.\\ |
| At line 7 removed one line |
| Create App keys on [https://www.backblaze.com/]\\ |
| At line 10 changed one line |
| Use the "KeyId" as username and the application Key as password.\\ |
| Use the __KeyId__ as __User name__ and the __Application Key__ as __Password__. Also, make sure to provide the corresponding __Bucket Name__ for access.\\ |
| At line 13 changed one line |
|
| \\ |
| At line 21 changed one line |
| !3. Access through S3 API\\ |
| ---- |
| !2. Access through S3 REST API\\ |
| At line 23 changed one line |
| Open the bucket settings and use the s3 endpoint URL for S3 connection.\\ |
| See the [BackBlaze S3-Compatible API Documentation| https://www.backblaze.com/docs/cloud-storage-s3-compatible-api]\\ |
| At line 43 added 16 lines |
| Create __App Keys__ on Backblaze with __S3 Permissions__:\\ |
| __1.)__ Go to [BlackBlaze Link|https://www.backblaze.com/] and sign in to your __Backblaze B2 Cloud Storage__ account.\\ |
| __2.)__ In the left-hand menu, go to __Buckets__, then click on __App Keys__.\\ |
| __3.)__ Click __Add a New Application Key__.\\ |
| __4.)__ In the key creation form:\\ |
| • Name your key.\\ |
| • Under Type of Access, select the appropriate permissions (e.g., read-only or read/write).\\ |
| • ⚠️ Important: Enable the option for S3 Compatible API access by checking the “Allow access to S3-compatible API” checkbox.\\ |
| • Optionally, restrict access to a specific bucket.\\ |
| __5.__ Click __Create New Key__.\\ |
| __6.__ Copy and securely store both the __Key ID__ and __Application Key__. ⚠️ The Application Key is shown only once after creation.\\ |
| \\ |
| [attachments|b2_application_key_s3_allow.png]\\ |
| \\ |
| Open the bucket settings and use the __S3 Endpoint URL__ for S3 connection.\\ |
| \\ |
| At line 27 changed 2 lines |
| Use the "KeyId" as username and the application Key as password.\\ |
| The URL pattern looks like this: |
| Use the __KeyId__ as __User name__ and the __Application Key__ as __Password__. Also, make sure to provide the corresponding __Bucket Name__ for access.\\ |
| The __URL Pattern__ looks like this (use the __S3 Endpoint URL__):\\ |
| At line 67 added 3 lines |
| ---- |
| __⚠️ Proxy Configuration:__ If your server accesses the internet through a proxy, make sure to whitelist the following domains for Backblaze Authentication and Drive access: __s3.us-west-000.backblazeb2.com__\\ |
| ---- |
| At line 34 changed one line |
| __SHA256 enabled on signing (Signing Version 4)__ and Include SHA256 to request headers (Signing Version 4 related)__ flags must be checked.\\ |
| __SHA256 enabled on signing (Signing Version 4)__ and __Include SHA256 to request headers (Signing Version 4 related)__ flags must be checked.\\ |
| At line 75 added 2 lines |
| More info about s3 VFS configuration: [S3 integration]\\ |
| \\ |
