A lightweight server clone of Azure Blob Storage that simulates most of the commands supported by it with minimal dependencies.
Azurite is an open-source Azure Storage API compatible server (emulator). It provides a local environment for testing and development of applications that use Azure Storage services, including Blob, Queue, and Table storage.
Blob Storage
This code snippet demonstrates how to start the Azurite Blob service on port 10000. Blob storage is used for storing large amounts of unstructured data such as text or binary data.
const azurite = require('azurite');
azurite().blob().listen(10000, () => {
console.log('Azurite Blob service is running on port 10000');
});Queue Storage
This code snippet demonstrates how to start the Azurite Queue service on port 10001. Queue storage is used for storing large numbers of messages that can be accessed from anywhere via authenticated calls.
const azurite = require('azurite');
azurite().queue().listen(10001, () => {
console.log('Azurite Queue service is running on port 10001');
});Table Storage
This code snippet demonstrates how to start the Azurite Table service on port 10002. Table storage is used for storing structured NoSQL data.
const azurite = require('azurite');
azurite().table().listen(10002, () => {
console.log('Azurite Table service is running on port 10002');
});LocalStack is a fully functional local AWS cloud stack. It provides a local testing environment for AWS services, including S3, DynamoDB, and SQS. Unlike Azurite, which focuses on Azure Storage services, LocalStack emulates a wide range of AWS services.
MinIO is a high-performance, S3-compatible object storage system. It is designed to be used for large-scale data infrastructure. While Azurite emulates Azure Blob storage, MinIO provides an alternative for S3-compatible object storage.
Fake S3 is a lightweight server that emulates the S3 API. It is useful for testing S3 interactions locally. Unlike Azurite, which emulates Azure Storage services, Fake S3 focuses solely on the S3 API.
A lightweight server clone of Azure Blob Storage that simulates most of the commands supported by it with minimal dependencies.
In order to run Azurite you need Node.js >= 4.0 installed on your system. Azurite works cross-platform on Windows, Linux, and OS X.
After installation you can install Azurite simply with npm which is Node.js package management tool and which is included with every Node.js installation.
$ npm install -g azurite
Then simply start it with the following command:
$ azurite -l path/to/localfolder
This tells Azurite to store all data in a particular directory. If the -l option is ommitted it will use the current working directory.
If you are interested in making a code contribution and would like to learn more about the technologies that we use, check out the list below.
The current status of Azurite's support of the Official Blob Storage REST API Specification is listed in below section Blob Storage - API Implementation Status. Features that are still unimplemented are marked with [TODO]. Completed features are marked with [DONE].
Current bugs that need to be fixed are listed at our issues site on Github and tagged with a red label bug.
Never made an open source contribution before? Wondering how contributions work in Azurite? Here's a quick rundown!
Find an issue that you are interested in addressing or a feature that you would like to add.
Fork the Azurite repository to your local GitHub organization. This means that you will have a copy of the repository under your-GitHub-username/azurite.
Clone the repository to your local machine using git clone https://github.com/github-username/azurite.git.
Create a new branch for your fix using git checkout -b branch-name-here.
Make the appropriate changes for the issue you are trying to address or the feature that you want to add.
Use git add insert-paths-of-changed-files-here to add the file contents of the changed files to the "snapshot" git uses to manage the state of the project, also known as the index.
Use git commit -m "Insert a short message of the changes made here" to store the contents of the index with a descriptive message.
Push the changes to the remote repository using git push origin branch-name-here.
Submit a pull request to the upstream repository. Title the pull request with a short description of the changes made and the issue or bug number associated with your change. For example, you can title an issue like so "Added more log outputting to resolve #4352". In the description of the pull request, explain the changes that you made, any issues you think exist with the pull request you made, and any questions you have for the maintainer. It's OK if your pull request is not perfect (no pull request is), the reviewer will be able to help you fix any problems and improve it!
Wait for the pull request to be reviewed by a maintainer. Make changes to the pull request if the reviewing maintainer recommends them.
Celebrate your success after your pull request is merged!
If you need help, you can ask questions directly at our issues site on Github.
Currently, Azurite only supports the Blob Storage APIs. Support for Azure Queues and Azure Files is planned, but currently not available.
The Standard Emulator Connection String is the same as required by Microsoft's Official Storage Emulator:
BlobEndpoint=http://127.0.0.1:10000/devstoreaccount1;
List Containers [DONE]
Lists all of the containers in a storage account.
Markers are not supported yet.
Account SAS Support [TODO]
See https://docs.microsoft.com/en-us/rest/api/storageservices/constructing-an-account-sas for specification
Blob Service SAS Support [TODO]
See https://docs.microsoft.com/en-us/rest/api/storageservices/constructing-an-account-sas for specification
Set Blob Service Properties [TODO]
Sets the properties of the Blob service, including logging and metrics settings, and the default service version.
Get Blob Service Properties [TODO] Gets the properties of the Blob service, including logging and metrics settings, and the default service version.
Preflight Blob Request [TODO]
Queries the Cross-Origin Resource Sharing (CORS) rules for the Blob service prior to sending the actual request.
Get Blob Service Stats [TODO]
Retrieves statistics related to replication for the Blob service. This operation is only available on the secondary location endpoint when read-access geo-redundant replication is enabled for the storage account.
Create Container [DONE]
Creates a new container in a storage account.
Get Container Properties [DONE]
Returns all user-defined metadata and system properties of a container.
Get Container Metadata [DONE]
Returns only user-defined metadata of a container.
Set Container Metadata [DONE]
Sets user-defined metadata of a container.
Get Container ACL [DONE]
Gets the public access policy and any stored access policies for the container.
Set Container ACL [DONE]
Sets the public access policy and any stored access policies for the container.
Lease Container [TODO]
Establishes and manages a lock on a container for delete operations.
Delete Container [DONE]
Deletes the container and any blobs that it contains.
List Blobs [DONE]
Lists all of the blobs in a container.
Put Blob [DONE]
Creates a new blob or replaces an existing blob within a container.
Get Blob [DONE]
Block Blobs only.
Reads or downloads a blob from the Blob service, including its user-defined metadata and system properties.
Get Blob Properties [DONE]
Returns all system properties and user-defined metadata on the blob.
Set Blob Properties [DONE]
Sets system properties defined for an existing blob.
Get Blob Metadata [DONE]
Retrieves all user-defined metadata of an existing blob or snapshot.
Set Blob Metadata [DONE]
Sets user-defined metadata of an existing blob.
Delete Blob [DONE]
Marks a blob for deletion.
Lease Blob [TODO]
Establishes and manages a lock on write and delete operations. To delete or write to a locked blob, a client must provide the lease ID.
Snapshot Blob [TODO]
Creates a read-only snapshot of a blob.
Copy Blob [TODO]
Copies a source blob to a destination blob in this storage account or in another storage account.
Abort Copy Blob [TODO]
Aborts a pending Copy Blob operation, and leaves a destination blob with zero length and full metadata.
Put Block [DONE]
Block blobs only.
Creates a new block to be committed as part of a block blob.
Put Block List [DONE]
Block blobs only.
Commits a blob by specifying the set of block IDs that comprise the block blob.
Get Block List [DONE]
Block blobs only.
Retrieves the list of blocks that have been uploaded as part of a block blob.
Put Page [DONE]
Page blobs only.
Writes a range of pages into a page blob.
Get Page Ranges [DONE]
Page blobs only.
Returns a list of valid page ranges for a page blob or a snapshot of a page blob.
Append Block [DONE]
Append blobs only
FAQs
An open source Azure Storage API compatible server
The npm package azurite receives a total of 213,521 weekly downloads. As such, azurite popularity was classified as popular.
We found that azurite demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 5 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
PEP 770 proposes adding SBOM support to Python packages to improve transparency and catch hidden non-Python dependencies that security tools often miss.
Security News
Socket CEO Feross Aboukhadijeh discusses open source security challenges, including zero-day attacks and supply chain risks, on the Cyber Security Council podcast.
Security News
Research
Socket researchers uncover how threat actors weaponize Out-of-Band Application Security Testing (OAST) techniques across the npm, PyPI, and RubyGems ecosystems to exfiltrate sensitive data.