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

backport of commit a58d650e58d377caaf2f06a5693bad8faac51395 (#22417) 

Co-authored-by: Markus Cisler <bl1nk@users.noreply.github.com>
This commit is contained in:
hc-github-team-secure-vault-core 2023-08-17 17:11:56 -04:00 committed by GitHub
parent 0f495abea9
commit 63ccd41bad
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
changelog/22396.txt Normal file
View File

@ -0,0 +1,3 @@
```release-note:improvement
website/docs: Fix link formatting in Vault lambda extension docs
```

2
website/content/docs/platform/aws/lambda-extension.mdx
View File

@ -53,7 +53,7 @@ to read secrets, which can both be used side-by-side:
- An instance of Vault accessible from AWS Lambda
- An authenticated `vault` client
- A secret in Vault that you want your Lambda to access, and a policy giving read access to it
- Your Lambda function must use one of the [supported runtimes][https://docs.aws.amazon.com/lambda/latest/dg/runtimes-extensions-api.html] for extensions
- Your Lambda function must use one of the [supported runtimes](https://docs.aws.amazon.com/lambda/latest/dg/runtimes-extensions-api.html) for extensions
#### Step 1. configure Vault