Skip to content

Commit

Permalink
backport of commit 3ab045a (#25048)
Browse files Browse the repository at this point in the history
Co-authored-by: Mark Lewis <[email protected]>
  • Loading branch information
hc-github-team-secure-vault-core and ml4 authored Jan 24, 2024
1 parent 9db1d26 commit 7cfc934
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions website/content/partials/storage-entry-size.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -2,13 +2,13 @@ The maximum size of an object written to a storage backend is determined
by that backend.

The default entry size limit for the integrated storage backend, is 1 MiB. You
can configure the allowable entry size with the `max_entry_size` paramter in
can configure the allowable entry size with the `max_entry_size` parameter in
your the [storage stanza](/vault/docs/configuration/storage/raft#max_entry_size).
Vault automatically chunks any storage entry that is larger than 512 KiB but
smaller than `max_entry_size` into smaller pieces before writing the entry to Raft.

For Vault deployments using the Consul storage backend, the default entry size
limit is 512 KiB. The default size in enforced by Consol rather than Vault. You
limit is 512 KiB. The default size is enforced by Consul rather than Vault. You
can configure the entry size limit with the
[`kv_max_value_size`](/consul/docs/agent/config/config-files#kv_max_value_size)
Consul parameter.
Expand Down

0 comments on commit 7cfc934

Please sign in to comment.