a3dfde5cec
* conversion stage 1 * correct image paths * add sidebar title to frontmatter * docs/concepts and docs/internals * configuration docs and multi-level nav corrections * commands docs, index file corrections, small item nav correction * secrets converted * auth * add enterprise and agent docs * add extra dividers * secret section, wip * correct sidebar nav title in front matter for apu section, start working on api items * auth and backend, a couple directory structure fixes * remove old docs * intro side nav converted * reset sidebar styles, add hashi-global-styles * basic styling for nav sidebar * folder collapse functionality * patch up border length on last list item * wip restructure for content component * taking middleman hacking to the extreme, but its working * small css fix * add new mega nav * fix a small mistake from the rebase * fix a content resolution issue with middleman * title a couple missing docs pages * update deps, remove temporary markup * community page * footer to layout, community page css adjustments * wip downloads page * deps updated, downloads page ready * fix community page * homepage progress * add components, adjust spacing * docs and api landing pages * a bunch of fixes, add docs and api landing pages * update deps, add deploy scripts * add readme note * update deploy command * overview page, index title * Update doc fields Note this still requires the link fields to be populated -- this is solely related to copy on the description fields * Update api_basic_categories.yml Updated API category descriptions. Like the document descriptions you'll still need to update the link headers to the proper target pages. * Add bottom hero, adjust CSS, responsive friendly * Add mega nav title * homepage adjustments, asset boosts * small fixes * docs page styling fixes * meganav title * some category link corrections * Update API categories page updated to reflect the second level headings for api categories * Update docs_detailed_categories.yml Updated to represent the existing docs structure * Update docs_detailed_categories.yml * docs page data fix, extra operator page remove * api data fix * fix makefile * update deps, add product subnav to docs and api landing pages * Rearrange non-hands-on guides to _docs_ Since there is no place for these on learn.hashicorp, we'll put them under _docs_. * WIP Redirects for guides to docs * content and component updates * font weight hotfix, redirects * fix guides and intro sidenavs * fix some redirects * small style tweaks * Redirects to learn and internally to docs * Remove redirect to `/vault` * Remove `.html` from destination on redirects * fix incorrect index redirect * final touchups * address feedback from michell for makefile and product downloads
70 lines
2.3 KiB
Markdown
70 lines
2.3 KiB
Markdown
---
|
||
layout: "docs"
|
||
page_title: "Azure - Storage Backends - Configuration"
|
||
sidebar_title: "Azure"
|
||
sidebar_current: "docs-configuration-storage-azure"
|
||
description: |-
|
||
The Azure storage backend is used to persist Vault's data in an Azure Storage
|
||
Container. The storage container must already exist and the provided account
|
||
credentials must have read and write permissions to the storage container.
|
||
---
|
||
|
||
# Azure Storage Backend
|
||
|
||
The Azure storage backend is used to persist Vault's data in an
|
||
[Azure Storage Container][azure-storage]. The storage container must already
|
||
exist and the provided account credentials must have read and write permissions
|
||
to the storage container.
|
||
|
||
- **No High Availability** – the Azure storage backend does not support high
|
||
availability.
|
||
|
||
- **Community Supported** – the Azure storage backend is supported by the
|
||
community. While it has undergone review by HashiCorp employees, they may not
|
||
be as knowledgeable about the technology. If you encounter problems with them,
|
||
you may be referred to the original author.
|
||
|
||
```hcl
|
||
storage "azure" {
|
||
accountName = "my-storage-account"
|
||
accountKey = "abcd1234"
|
||
container = "container-efgh5678"
|
||
environment = "AzurePublicCloud"
|
||
}
|
||
```
|
||
|
||
The current implementation is limited to a maximum of 4 megabytes per blob.
|
||
|
||
## `azure` Parameters
|
||
|
||
- `accountName` `(string: <required>)` – Specifies the Azure Storage account
|
||
name.
|
||
|
||
- `accountKey` `(string: <required>)` – Specifies the Azure Storage account key.
|
||
|
||
- `container` `(string: <required>)` – Specifies the Azure Storage Blob
|
||
container name.
|
||
|
||
- `environment` `(string: "AzurePublicCloud")` - Specifies the cloud
|
||
environment the storage account belongs to by way of the case-insensitive
|
||
name defined in the [Azure Go SDK][azure-environment].
|
||
|
||
- `max_parallel` `(string: "128")` – Specifies The maximum number of concurrent
|
||
requests to Azure.
|
||
|
||
## `azure` Examples
|
||
|
||
This example shows configuring the Azure storage backend with a custom number of
|
||
maximum parallel connections.
|
||
|
||
```hcl
|
||
storage "azure" {
|
||
accountName = "my-storage-account"
|
||
accountKey = "abcd1234"
|
||
container = "container-efgh5678"
|
||
max_parallel = 512
|
||
}
|
||
```
|
||
|
||
[azure-storage]: https://azure.microsoft.com/en-us/services/storage/
|
||
[azure-environment]: https://godoc.org/github.com/Azure/go-autorest/autorest/azure#pkg-variables |