- Plugins and Integrations: other versions:
- Introduction to plugins
- Plugin Management
- API Extension Plugins
- Analysis Plugins
- Discovery Plugins
- Ingest Plugins
- Mapper Plugins
- Snapshot/Restore Repository Plugins
- Store Plugins
- Integrations
- Help for plugin authors
IMPORTANT: No additional bug fixes or documentation updates
will be released for this version. For the latest information, see the
current release documentation.
Azure Repository
editAzure Repository
editTo enable Azure repositories, you have first to define your azure storage settings as secure settings, before starting up the node:
bin/elasticsearch-keystore add azure.client.default.account bin/elasticsearch-keystore add azure.client.default.key
Note that you can also define more than one account:
bin/elasticsearch-keystore add azure.client.default.account bin/elasticsearch-keystore add azure.client.default.key bin/elasticsearch-keystore add azure.client.secondary.account bin/elasticsearch-keystore add azure.client.secondary.sas_token
For more information about these settings, see Client settings.
Supported Azure Storage Account types
The Azure Repository plugin works with all Standard storage accounts
-
Standard Locally Redundant Storage -
Standard_LRS
-
Standard Zone-Redundant Storage -
Standard_ZRS
-
Standard Geo-Redundant Storage -
Standard_GRS
-
Standard Read Access Geo-Redundant Storage -
Standard_RAGRS
Premium Locally Redundant Storage (Premium_LRS
) is not supported as it is only usable as VM disk storage, not as general storage.
Was this helpful?
Thank you for your feedback.