From 50cc886e46b41ef8066c10ee4692b38e47e7ff65 Mon Sep 17 00:00:00 2001 From: kevin-loehfelm <37027455+kevin-loehfelm@users.noreply.github.com> Date: Tue, 19 Nov 2024 10:14:08 -0500 Subject: [PATCH] Update typo in AWS Secrets Engine documentation (#28930) Co-authored-by: Kuba Wieczorek --- website/content/docs/secrets/aws.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/content/docs/secrets/aws.mdx b/website/content/docs/secrets/aws.mdx index 84598c6a7aa78..6e0b74957d061 100644 --- a/website/content/docs/secrets/aws.mdx +++ b/website/content/docs/secrets/aws.mdx @@ -14,7 +14,7 @@ involve clicking in the web UI. Additionally, the process is codified and mapped to internal auth methods (such as LDAP). The AWS IAM credentials are time-based and are automatically revoked when the Vault lease expires. -Vault supports three different types of credentials to retrieve from AWS: +Vault supports four different types of credentials to retrieve from AWS: 1. `iam_user`: Vault will create an IAM user for each lease, attach the managed and inline IAM policies as specified in the role to the user, and if a