-
) as separators, not spaces.https://
designator in each line that matches exactly.b2 get-account-info
command on the command line and use the hostname from the downloadUrl
attribute.-
) as separators, not spaces.create-key
command as follows:<bucketName> <keyName>
represents the name of the bucket and key you created. For example:s3-uswest-000.backblazeb2.com
or f000.backblazeb2.com
).Host
header contains the name of your B2 Bucket. There are two ways to do this, both of which require you to get your region name which will be the 2nd part of your S3 Endpoint. So if your S3 Endpoint is s3.us-west-000.backblazeb2.com
, this means your region will be us-west-000
.<bucket>.s3.<region>.backblazeb2.com
(e.g., testing.s3.uswest-000.backblazeb2.com
)var.b2Bucket
would be 'testing'
and var.b2Region
would be 'uswest-000'
.Item | Description |
---|---|
Bucket name | The name of your Backblaze B2 bucket. When you download items from your bucket, this is the string listed in the URL path or hostname of each object. |
Region | The Backblaze region code of the location where your bucket resides (e.g., uswest-000 ). |
Access key | The Backblaze keyID for the App Key that has at least read permission on the bucket. |
Secret key | The Backblaze applicationKey paired with the access key above. |
AWS protected origin
. When you create the snippet, select within subroutine to specify its placement and choose miss as the subroutine type. Then, populate the VCL field with the following code (be sure to change specific values as noted to ones relevant to your own AWS bucket):Rewrite B2 URL
.url
.20
.'/file/<Bucket Name>' req.url
.Authorization Token
. This must be obtained via the command line.Authorization
header. This is the recommended method.Authorization
.http.Authorization
.20
.DEC0DEC0C0A
, then the Source field would be 'DEC0DEC0C0A'
Authorization
query parameter.Authorization
.url
.20
.