> ## Documentation Index > Fetch the complete documentation index at: https://docs.bunny.net/llms.txt > Use this file to discover all available pages before exploring further. # Backblaze > Speed up Backblaze B2 file delivery with bunny.net CDN for global caching and reduced bandwidth costs. Bunny CDN caches files from your Backblaze B2 bucket and delivers them from a global edge network, speeding up delivery and saving on bandwidth costs. This guide uses S3-compatible authentication to securely connect a private B2 bucket. If you don't have a Backblaze B2 account yet, you can [create one for free](https://www.backblaze.com/b2/sign-up.html). Prefer to keep your files on bunny.net? [Bunny Storage](/storage) is globally replicated object storage with tight CDN integration, and it offers an [S3-compatible API](/storage/s3) (currently in beta). Log in to Backblaze and click **Create a Bucket**. Set the bucket to **Private** mode to keep your content secure while it's served to users. Encryption and Object Lock can be left at their defaults. Creating a Backblaze B2 bucket

To authenticate securely, Bunny CDN connects to your bucket using S3 authentication. Select **App Keys** in the Backblaze dashboard. The App Keys page

Click **Add a New Application Key**. Adding a new application key

Select the private bucket you created and ensure **Allow List All Bucket Names** is checked, then click **Create New Key**. Configuring the application key

On the confirmation page, save the **keyID** and **applicationKey** somewhere safe. You'll need them in a later step. The created application key details

Click **Browse Files** and upload a test file if you don't have one. Click the **(i)** info tooltip next to the file. Browsing files and opening the info tooltip

Find the **S3 URL** and save it, excluding the file name. For example, for a bucket named `bunnytestbucket`: ``` https://bunnytestbucket.s3.eu-central-003.backblazeb2.com ``` The S3 URL in the file details

Log in to your [bunny.net dashboard](https://dash.bunny.net) and open **Add Pull Zone**. Give it a name (this becomes your CDN hostname) and paste the S3 URL from the previous step into the **Origin URL** field. The Host Header is generated automatically and doesn't need changing. For details, see [How to create your first Pull Zone](/cdn/quickstart). Adding a Pull Zone with the B2 S3 URL as origin

Adding a Pull Zone with the B2 S3 URL as origin

To use an existing Pull Zone instead, set the same Origin URL in its settings. Reconfiguring an existing Pull Zone

Open the **S3 Authentication** section of your Pull Zone's **Security** settings and click **Enable AWS S3 Authentication**. Fill in the details using the keys from step 2: * **AWS Key**: your B2 `keyID` * **AWS Secret**: your B2 `applicationKey` * **AWS Region Name**: the region from your origin URL (for example, `eu-central`) Configuring AWS S3 authentication on the Pull Zone

Configuring AWS S3 authentication on the Pull Zone

Click **Save Configuration**. With everything configured, request a file through your Pull Zone hostname, for example: ``` https://bunnytestwordpress.b-cdn.net/code-to-share.js ``` If the file is served, your private B2 bucket is protected by S3 authentication and accelerated by Bunny CDN. Replace your existing URLs with the Bunny CDN URLs in your application to start serving cached content.