luxolus/open-vault
2
0
Fork 0
Code Issues 1 Pull requests Releases Activity

updated 1.3.2 and 1.4.0 upgrade guides to note AWS STS region issue fixed in 1.4.1 (#9137)

Browse source
This commit is contained in:
Dave D'Amico 2020-06-03 13:27:45 -04:00 committed by GitHub
parent 438345c390
commit a60ba90a20
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
3 changed files with 13 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
website/pages/docs/upgrading/upgrade-to-1.3.2.mdx
View file

@ -13,3 +13,5 @@ This page contains the list of deprecations and important or breaking changes
for Vault 1.3.0 compared to 1.3.2. Please read it carefully.
@include 'partials/aws-auth-metadata-issue.mdx'
@include 'partials/aws-sts-issue.mdx'

2
website/pages/docs/upgrading/upgrade-to-1.4.0.mdx
View file

@ -14,5 +14,7 @@ for Vault 1.3.X compared to 1.4.0. Please read it carefully.
@include 'partials/aws-auth-metadata-issue.mdx'
@include 'partials/aws-sts-issue.mdx'
@include 'partials/ldap-upndomain-issue.mdx'

9
website/pages/partials/aws-sts-issue.mdx Normal file
View file

@ -0,0 +1,9 @@
## The AWS STS Region Selection
The AWS Client used in Vault was updated for improved STS performance in
1.3.2 and 1.4.0 [#8161](https://github.com/hashicorp/vault/pull/8161),
however this introduced a side effect of limiting the regions being selected for validation
and a greater possibility of encountering an "invalid security token" error.
Users of the AWS auth engine should upgrade to 1.4.1 release instead,
where this side effect was fixed in [#8679](https://github.com/hashicorp/vault/pull/8679).