Blixt Documentation v2.11

Create a bucket

  1. Open the Azure Portal.
  2. Create a Storage Account if you don’t have one.
  3. Inside the storage account, go to Containers and click + Container.
  4. Give it a name and click Create.

Credentials and permissions

BlixtFS needs the storage account’s name, set with --azure_storage_account, and one of three credentials. When more than one is set, BlixtFS uses the first in this list.

An account key. In the Azure Portal, open the storage account, go to Security + networking → Access keys, and copy one of the Keys. Set it with --azure_account_key (cloud.azure.account_key).

A shared access signature. On the same page, under Shared access signature, allow the Blob service, the Container and Object resource types, and the Read, Write, Delete, List and Create permissions, then generate the signature. Set it with --azure_sas_token (cloud.azure.sas_token), with or without its leading ?. A signature expires on the date you chose.

An Azure sign-in. With neither of the above, BlixtFS signs in the way the Azure SDK does by default: az login on the machine, a service principal in AZURE_TENANT_ID, AZURE_CLIENT_ID and AZURE_CLIENT_SECRET, or the managed identity of the VM or pod. The identity needs the Storage Blob Data Contributor role on the storage account. Change notifications and region detection always use this sign-in, so set one up if you need them, even with a key or signature.

A connection string in --azure_credentials also works, but it holds the account key in a setting the config server sends to every server. Prefer --azure_account_key, which it never sends.

In the MacOS app, the setup assistant finds an az login sign-in, or takes a key or signature, and tests it before saving it.

Project

A human-friendly alias for the Azure project, set with AZURE_PROJECT, --azure_project or cloud.azure.project. The subscription itself is a separate setting, AZURE_SUBSCRIPTION_ID (--azure_subscription_id, or cloud.azure.subscription_id), which takes the subscription GUID.

Storage account

The Azure storage account holding the containers BlixtFS serves. Set it with AZURE_STORAGE_ACCOUNT, --azure_storage_account or cloud.azure.storage_account. It is the same Storage account name you copy from the Access keys page.