Azure Blob Storage and S3-compatible providers join Sippy

Sippy can now incrementally migrate data from Azure Blob Storage and any S3-compatible object storage provider to Cloudflare R2, in addition to Amazon S3 and Google Cloud Storage. Sippy copies objects to R2 as your application requests them, so you can start serving data from R2 without first moving your entire dataset or paying migration-specific egress fees.

Enable Sippy

Run the following command and follow the prompts to select and configure your source storage provider:

<span class="line"><span class="nb-shiki-1t8gfj">npx</span><span class="nb-shiki-mdbnqw"> wrangler</span><span class="nb-shiki-mdbnqw"> r2</span><span class="nb-shiki-mdbnqw"> bucket</span><span class="nb-shiki-mdbnqw"> sippy</span><span class="nb-shiki-mdbnqw"> enable</span><span class="nb-shiki-1itgoe"> <</span><span class="nb-shiki-mdbnqw">BUCKET_NAM</span><span class="nb-shiki-140thh">E</span><span class="nb-shiki-1itgoe">></span></span>

For Azure Blob Storage, provide your storage account name, container name, and either an account key or a shared access signature (SAS) token with read and list permissions. For an S3-compatible provider, provide the S3 API endpoint URL and read-only Access Key ID and Secret Access Key.

After you enable Sippy, requests for objects that are not yet in R2 are served from your source bucket and copied to R2. Subsequent requests for those objects are served from R2.

For setup instructions and credential requirements, refer to the Sippy documentation.