mirror of
https://github.com/hashicorp/vault.git
synced 2026-06-08 16:24:51 -04:00
known issue for sts configuration (#29993)
This commit is contained in:
parent
2dfc88f157
commit
8d0743c16d
1 changed files with 27 additions and 0 deletions
27
website/content/partials/known-issues/aws-fallback-sts.mdx
Normal file
27
website/content/partials/known-issues/aws-fallback-sts.mdx
Normal file
|
|
@ -0,0 +1,27 @@
|
|||
### STS configuration can fail if STS endpoints are unspecified
|
||||
|
||||
#### Affected Versions
|
||||
|
||||
- 1.19.0
|
||||
|
||||
#### Issue
|
||||
|
||||
When configuring an sts endpoint in the AWS Secrets engine, when no sts_endpoint is set, the engine will return
|
||||
an error stating that the number of endpoints and regions do not match:
|
||||
|
||||
```
|
||||
{"errors":["number of regions does not match number of endpoints"]}
|
||||
```
|
||||
|
||||
#### Workaround
|
||||
|
||||
Explicitly set the default endpoint and region when configuring sts:
|
||||
|
||||
```
|
||||
{
|
||||
...
|
||||
sts_region = "us-east-1"
|
||||
sts_endpoint = "https://sts.amazonaws.com"
|
||||
...
|
||||
}
|
||||
```
|
||||
Loading…
Reference in a new issue