Connecting to Azure Blob Storage Using a SAS Token

In addition to a string or GDAL VSI filename, HTTP headers and query parameters to be forwarded to remote endpoints can be specified within the filename option. As shown below, a JSON object can be substituted, with the ‘headers’ and ‘query’ fields as JSON objects of key/value string pairs.

{
    "filename":
    {
        "path":"path to remote file [required]",
        "headers":
        {
            "some_header_key": "HTTP header value"
        },
        "query":
        {
            "some_query_key": "HTTP query value"
        }
    }
}

Connecting to Azure Blob Storage Using a SAS Token#

To specify a filename when accessing an Azure Blob container with a SAS token, use one of the following formats:

Using the Arbiter Azure Driver#

First, export the necessary environment variables:

export AZURE_STORAGE_ACCOUNT=<your_storage_account>
export AZURE_SAS_TOKEN=<your_sas_token>

Then, set the filename as follows:

{
    "filename": {
        "path": "az://<PATH_TO_EPT>/ept.json"
    }
}

Note: PATH_TO_EPT is simply the path to the container; there is no need to specify blob.core.windows.net or the Azure storage account.

Contents