Azure Storage

Connect & Ingest data from / into a Azure Storage Account

Setup

The following credentials keys are accepted:

• account (required) -> This is the Azure account string.

• container (required) -> This is the storage container.

• conn_str (optional) -> This is the Connection String from an Account Access Keys. Looks something like DefaultEndpointsProtocol=https;AccountName=my_account;AccountKey=thisIsAFakeKeyxxxxxxxxxxxxx/MRHCrBw4BLmypbaJyVbvUWn4YZ1Nw==;EndpointSuffix=core.windows.net.

• sas_svc_url (optional) -> This is the Shared Access Signature (SAS) URL.

• client_id (optional) -> Application ID of an Azure service principal. Can also set via env var AZURE_CLIENT_ID

• tenant_id (optional) -> ID of the application's Microsoft Entra tenant. Can also set via env var AZURE_TENANT_ID

• client_certificate_path (optional) -> Path to a PEM or PKCS12 certificate file including private key. If you followed the steps for the Azure CLI, the file isn't password protected. Can also set via env var AZURE_CLIENT_CERTIFICATE_PATH

• client_certificate_password (optional) -> The password you entered when you created the service principal. Can also set via env var AZURE_CLIENT_CERTIFICATE_PASSWORD

Using sling conns

Here are examples of setting a connection named AZURE_STORAGE. We must provide the type=azure property:

$ sling conns set AZURE_STORAGE type=azure account=<account> container=<container> sas_svc_url=<sas_svc_url>
$ sling conns set AZURE_STORAGE type=azure account=<account> container=<container> conn_str="<conn_str>"

Environment Variable

In JSON/YAML format:

export AZURE_STORAGE='{"type": "azure", "account": "<account>", "container": "<container>", "sas_svc_url": "<sas_svc_url>"}'

Sling Env File YAML

See here to learn more about the sling env.yaml file.

connections:
  AZURE_STORAGE:
    type: azure
    account: <account>
    container: <container>
    sas_svc_url: '<sas_svc_url>'

  AZURE_STORAGE_2:
    type: azure
    account: <account>
    container: <container>
    conn_str: '<conn_str>'

If you are facing issues connecting, please reach out to us at [e-mail], on discord or open a Github Issue here.