| title | Quickstart: Azure Blob storage library - JavaScript | |||||
|---|---|---|---|---|---|---|
| description | In this quickstart, you learn how to use the Azure Blob Storage for JavaScript to create a container and a blob in Blob (object) storage. Next, you learn how to download the blob to your local computer, and how to list all of the blobs in a container. | |||||
| author | stevenmatthew | |||||
| ms.author | shaas | |||||
| ms.date | 09/13/2024 | |||||
| ms.service | azure-blob-storage | |||||
| ms.topic | quickstart | |||||
| ms.devlang | javascript | |||||
| zone_pivot_groups | azure-blob-storage-quickstart-options | |||||
| ms.custom |
|
::: zone pivot="blob-storage-quickstart-scratch"
Note
The Build from scratch option walks you step by step through the process of creating a new project, installing packages, writing the code, and running a basic console app. This approach is recommended if you want to understand all the details involved in creating an app that connects to Azure Blob Storage. If you prefer to automate deployment tasks and start with a completed project, choose Start with a template.
::: zone-end
::: zone pivot="blob-storage-quickstart-template"
Note
The Start with a template option uses the Azure Developer CLI to automate deployment tasks and starts you off with a completed project. This approach is recommended if you want to explore the code as quickly as possible without going through the setup tasks. If you prefer step by step instructions to build the app, choose Build from scratch.
::: zone-end
Get started with the Azure Blob Storage client library for Node.js to manage blobs and containers.
::: zone pivot="blob-storage-quickstart-scratch"
In this article, you follow steps to install the package and try out example code for basic tasks.
::: zone-end
::: zone pivot="blob-storage-quickstart-template"
In this article, you use the Azure Developer CLI to deploy Azure resources and run a completed console app with just a few commands.
::: zone-end
API reference | Library source code | Package (npm) | Samples
::: zone pivot="blob-storage-quickstart-scratch"
- Azure account with an active subscription - create an account for free
- Azure Storage account - Create a storage account
- Node.js LTS
::: zone-end
::: zone pivot="blob-storage-quickstart-template"
- Azure subscription - create one for free
- Node.js LTS
- Azure Developer CLI
::: zone-end
::: zone pivot="blob-storage-quickstart-scratch"
This section walks you through preparing a project to work with the Azure Blob Storage client library for Node.js.
Create a JavaScript application named blob-quickstart.
-
In a console window (such as cmd, PowerShell, or Bash), create a new directory for the project:
mkdir blob-quickstart -
Switch to the newly created blob-quickstart directory:
cd blob-quickstart -
Create a package.json file:
npm init -y -
Open the project in Visual Studio Code:
code .
From the project directory, install the following packages using the npm install command.
-
Install the Azure Storage npm package:
npm install @azure/storage-blob -
Install the Azure Identity npm package for a passwordless connection:
npm install @azure/identity -
Install other dependencies used in this quickstart:
npm install uuid dotenv
From the project directory:
-
Create a new file named
index.js -
Copy the following code into the file:
:::code language="javascript" source="~/azure_storage-snippets/blobs/quickstarts/JavaScript/V12/nodejs/boilerplate.js":::
::: zone-end
::: zone pivot="blob-storage-quickstart-template"
With Azure Developer CLI installed, you can create a storage account and run the sample code with just a few commands. You can run the project in your local development environment, or in a DevContainer.
From an empty directory, follow these steps to initialize the azd template, create Azure resources, and get started with the code:
-
Clone the quickstart repository assets from GitHub and initialize the template locally:
azd init --template blob-storage-quickstart-nodejsYou'll be prompted for the following information:
- Environment name: This value is used as a prefix for all Azure resources created by Azure Developer CLI. The name must be unique across all Azure subscriptions and must be between 3 and 24 characters long. The name can contain numbers and lowercase letters only.
-
Sign in to Azure:
azd auth login -
Provision and deploy the resources to Azure:
azd upYou'll be prompted for the following information:
- Subscription: The Azure subscription that your resources are deployed to.
- Location: The Azure region where your resources are deployed.
The deployment might take a few minutes to complete. The output from the
azd upcommand includes the name of the newly created storage account, which you'll need later to run the code.
At this point, the resources are deployed to Azure and the code is almost ready to run. Follow these steps to install packages, update the name of the storage account in the code, and run the sample console app:
- Install packages: Navigate to the local
blob-quickstartdirectory. Install packages for the Azure Blob Storage and Azure Identity client libraries, along with other packages used in the quickstart, using the following command:npm install @azure/storage-blob @azure/identity uuid dotenv - Update the storage account name: In the local
blob-quickstartdirectory, edit the file named index.js. Find the<storage-account-name>placeholder and replace it with the actual name of the storage account created by theazd upcommand. Save the changes. - Run the project: Execute the following command to run the app:
node index.js - Observe the output: This app creates a container and uploads a text string as a blob to the container. The example then lists the blobs in the container and downloads the blob and displays the blob contents. The app then deletes the container and all its blobs.
To learn more about how the sample code works, see Code examples.
When you're finished testing the code, see the Clean up resources section to delete the resources created by the azd up command.
::: zone-end
Azure Blob storage is optimized for storing massive amounts of unstructured data. Unstructured data is data that doesn't adhere to a particular data model or definition, such as text or binary data. Blob storage offers three types of resources:
- The storage account
- A container in the storage account
- A blob in the container
The following diagram shows the relationship between these resources.
Use the following JavaScript classes to interact with these resources:
- BlobServiceClient: The
BlobServiceClientclass allows you to manipulate Azure Storage resources and blob containers. - ContainerClient: The
ContainerClientclass allows you to manipulate Azure Storage containers and their blobs. - BlobClient: The
BlobClientclass allows you to manipulate Azure Storage blobs.
These example code snippets show you how to do the following tasks with the Azure Blob Storage client library for JavaScript:
- Authenticate to Azure and authorize access to blob data
- Create a container
- Upload blobs to a container
- List the blobs in a container
- Download blobs
- Delete a container
::: zone pivot="blob-storage-quickstart-scratch"
Sample code is also available on GitHub.
::: zone-end
::: zone pivot="blob-storage-quickstart-template"
Note
The Azure Developer CLI template includes a file with sample code already in place. The following examples provide detail for each part of the sample code. The template implements the recommended passwordless authentication method, as described in the Authenticate to Azure section. The connection string method is shown as an alternative, but isn't used in the template and isn't recommended for production code.
::: zone-end
[!INCLUDE storage-quickstart-passwordless-auth-intro]
DefaultAzureCredential supports multiple authentication methods and determines which method should be used at runtime. This approach enables your app to use different authentication methods in different environments (local vs. production) without implementing environment-specific code.
The order and locations in which DefaultAzureCredential looks for credentials can be found in the Azure Identity library overview.
For example, your app can authenticate using your Azure CLI sign-in credentials with when developing locally. Your app can then use a managed identity once it's deployed to Azure. No code changes are required for this transition.
[!INCLUDE assign-roles]
You can authorize access to data in your storage account using the following steps:
-
Make sure you're authenticated with the same Microsoft Entra account you assigned the role to on your storage account. You can authenticate via the Azure CLI, Visual Studio Code, or Azure PowerShell.
Sign-in to Azure through the Azure CLI using the following command:
az loginInstall the Azure CLI to work with
DefaultAzureCredentialthrough Visual Studio Code.On the main menu of Visual Studio Code, navigate to Terminal > New Terminal.
Sign-in to Azure through the Azure CLI using the following command:
az loginSign-in to Azure using PowerShell via the following command:
Connect-AzAccount -
To use
DefaultAzureCredential, make sure that the @azure\identity package is installed, and the class is imported::::code language="javascript" source="~/azure_storage-snippets/blobs/quickstarts/JavaScript/V12/nodejs/index.js" id="snippet_StorageAcctInfo_without_secrets":::
-
Add this code inside the
tryblock. When the code runs on your local workstation,DefaultAzureCredentialuses the developer credentials of the prioritized tool you're logged into to authenticate to Azure. Examples of these tools include Azure CLI or Visual Studio Code.:::code language="javascript" source="~/azure_storage-snippets/blobs/quickstarts/JavaScript/V12/nodejs/index.js" id="snippet_StorageAcctInfo_create_client":::
-
Make sure to update the storage account name,
AZURE_STORAGE_ACCOUNT_NAME, in the.envfile or your environment's variables. The storage account name can be found on the overview page of the Azure portal.:::image type="content" source="./media/storage-quickstart-blobs-python/storage-account-name.png" alt-text="A screenshot showing how to find the storage account name.":::
[!NOTE] When deployed to Azure, this same code can be used to authorize requests to Azure Storage from an application running in Azure. However, you'll need to enable managed identity on your app in Azure. Then configure your storage account to allow that managed identity to connect. For detailed instructions on configuring this connection between Azure services, see the Auth from Azure-hosted apps tutorial.
A connection string includes the storage account access key and uses it to authorize requests. Always be careful to never expose the keys in an unsecure location.
Note
To authorize data access with the storage account access key, you'll need permissions for the following Azure RBAC action: Microsoft.Storage/storageAccounts/listkeys/action. The least privileged built-in role with permissions for this action is Reader and Data Access, but any role which includes this action will work.
[!INCLUDE retrieve credentials]
After you copy the connection string, write it to a new environment variable on the local machine running the application. To set the environment variable, open a console window, and follow the instructions for your operating system. Replace <yourconnectionstring> with your actual connection string.
Windows:
setx AZURE_STORAGE_CONNECTION_STRING "<yourconnectionstring>"After you add the environment variable in Windows, you must start a new instance of the command window.
Linux:
export AZURE_STORAGE_CONNECTION_STRING="<yourconnectionstring>".env file:
AZURE_STORAGE_CONNECTION_STRING="<yourconnectionstring>"The following code retrieves the connection string for the storage account from the environment variable created earlier, and uses the connection string to construct a service client object.
::: zone pivot="blob-storage-quickstart-scratch"
Add this code inside the try block:
::: zone-end
:::code language="javascript" source="~/azure_storage-snippets/blobs/quickstarts/JavaScript/V12/nodejs/index.js" id="snippet_StorageAcctInfo__with_secrets":::
Important
The account access key should be used with caution. If your account access key is lost or accidentally placed in an insecure location, your service may become vulnerable. Anyone who has the access key is able to authorize requests against the storage account, and effectively has access to all the data. DefaultAzureCredential provides enhanced security features and benefits and is the recommended approach for managing authorization to Azure services.
Create a new container in the storage account. The following code example takes a BlobServiceClient object and calls the getContainerClient method to get a reference to a container. Then, the code calls the create method to actually create the container in your storage account.
::: zone pivot="blob-storage-quickstart-scratch"
Add this code to the end of the try block:
::: zone-end
:::code language="javascript" source="~/azure_storage-snippets/blobs/quickstarts/JavaScript/V12/nodejs/index.js" id="snippet_CreateContainer":::
To learn more about creating a container, and to explore more code samples, see Create a blob container with JavaScript.
Important
Container names must be lowercase. For more information about naming containers and blobs, see Naming and Referencing Containers, Blobs, and Metadata.
Upload a blob to the container. The following code gets a reference to a BlockBlobClient object by calling the getBlockBlobClient method on the ContainerClient from the Create a container section.
The code uploads the text string data to the blob by calling the upload method.
::: zone pivot="blob-storage-quickstart-scratch"
Add this code to the end of the try block:
::: zone-end
:::code language="javascript" source="~/azure_storage-snippets/blobs/quickstarts/JavaScript/V12/nodejs/index.js" id="snippet_UploadBlobs":::
To learn more about uploading blobs, and to explore more code samples, see Upload a blob with JavaScript.
List the blobs in the container. The following code calls the listBlobsFlat method. In this case, only one blob is in the container, so the listing operation returns just that one blob.
::: zone pivot="blob-storage-quickstart-scratch"
Add this code to the end of the try block:
::: zone-end
:::code language="javascript" source="~/azure_storage-snippets/blobs/quickstarts/JavaScript/V12/nodejs/index.js" id="snippet_ListBlobs":::
To learn more about listing blobs, and to explore more code samples, see List blobs with JavaScript.
Download the blob and display the contents. The following code calls the download method to download the blob.
::: zone pivot="blob-storage-quickstart-scratch"
Add this code to the end of the try block:
::: zone-end
:::code language="javascript" source="~/azure_storage-snippets/blobs/quickstarts/JavaScript/V12/nodejs/index.js" id="snippet_DownloadBlobs":::
The following code converts a stream back into a string to display the contents.
::: zone pivot="blob-storage-quickstart-scratch"
Add this code after the main function:
::: zone-end
:::code language="javascript" source="~/azure_storage-snippets/blobs/quickstarts/JavaScript/V12/nodejs/index.js" id="snippet_ConvertStreamToText":::
To learn more about downloading blobs, and to explore more code samples, see Download a blob with JavaScript.
Delete the container and all blobs within the container. The following code cleans up the resources created by the app by removing the entire container using the delete method.
::: zone pivot="blob-storage-quickstart-scratch"
Add this code to the end of the try block:
::: zone-end
:::code language="javascript" source="~/azure_storage-snippets//blobs/quickstarts/JavaScript/V12/nodejs/index.js" id="snippet_DeleteContainer":::
To learn more about deleting a container, and to explore more code samples, see Delete and restore a blob container with JavaScript.
::: zone pivot="blob-storage-quickstart-scratch"
From a Visual Studio Code terminal, run the app.
node index.jsThe output of the app is similar to the following example:
Azure Blob storage - JavaScript quickstart sample
Creating container...
quickstart4a0780c0-fb72-11e9-b7b9-b387d3c488da
Uploading to Azure Storage as blob:
quickstart4a3128d0-fb72-11e9-b7b9-b387d3c488da.txt
Listing blobs...
quickstart4a3128d0-fb72-11e9-b7b9-b387d3c488da.txt
Downloaded blob content...
Hello, World!
Deleting container...
Done
Step through the code in your debugger and check your Azure portal throughout the process. Check to see that the container is being created. You can open the blob inside the container and view the contents.
::: zone-end
::: zone pivot="blob-storage-quickstart-scratch"
- When you're done with this quickstart, delete the
blob-quickstartdirectory. - If you're done using your Azure Storage resource, use the Azure CLI to remove the Storage resource.
::: zone-end
::: zone pivot="blob-storage-quickstart-template"
When you're done with the quickstart, you can clean up the resources you created by running the following command:
azd downYou'll be prompted to confirm the deletion of the resources. Enter y to confirm.
::: zone-end
[!div class="nextstepaction"] Azure Storage samples and developer guides for JavaScript and TypeScript
