From 2ed4242ab18fee1f2e0e2e3216c3ba1f54e27feb Mon Sep 17 00:00:00 2001 From: hc-github-team-secure-vault-core <82990506+hc-github-team-secure-vault-core@users.noreply.github.com> Date: Thu, 8 Jun 2023 11:06:11 -0400 Subject: [PATCH] backport of commit bbcd3f1c1bb787e15c6008e684b81b83be7245f0 (#21079) Co-authored-by: Conor McCullough <103977699+conor-mccullough@users.noreply.github.com> --- .../enterprise/automated-integrated-storage-snapshots.mdx | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/website/content/docs/enterprise/automated-integrated-storage-snapshots.mdx b/website/content/docs/enterprise/automated-integrated-storage-snapshots.mdx index 2dee6c4be..5bebd9653 100644 --- a/website/content/docs/enterprise/automated-integrated-storage-snapshots.mdx +++ b/website/content/docs/enterprise/automated-integrated-storage-snapshots.mdx @@ -35,6 +35,14 @@ and GCP can be used without specifying credentials, by ensuring that the VMs on which Vault is running have been granted permission to access the specified object store. + + +Currently, Vault does not allow the use of AWS IAM Roles for EKS Service +Accounts to authenticate to Amazon S3 buckets for the Automated Integrated +Storage Snapshots. + + + # vs Snapshot Agents Nomad and Consul Enterprise offer the same functionality in a slightly different way.