From 4835df609de3f2650851353cefc27c0baf0beb6f Mon Sep 17 00:00:00 2001 From: Dan Gorst Date: Thu, 24 Nov 2016 15:36:46 +0000 Subject: [PATCH] Minor documentation tweak (#2127) Should be arn, not policy - latter will error as that assume an inline policy json document --- website/source/docs/secrets/aws/index.html.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/source/docs/secrets/aws/index.html.md b/website/source/docs/secrets/aws/index.html.md index 1d238bb8ac..db09c4b769 100644 --- a/website/source/docs/secrets/aws/index.html.md +++ b/website/source/docs/secrets/aws/index.html.md @@ -305,7 +305,7 @@ Finally, let's create a "deploy" policy using the arn of our role to assume: ```text $ vault write aws/roles/deploy \ - policy=arn:aws:iam::ACCOUNT-ID-WITHOUT-HYPHENS:role/RoleNameToAssume + arn=arn:aws:iam::ACCOUNT-ID-WITHOUT-HYPHENS:role/RoleNameToAssume ``` To generate a new set of STS assumed role credentials, we again read from