diff --git a/changelog/22396.txt b/changelog/22396.txt
new file mode 100644
index 000000000..d05cbb7ac
--- /dev/null
+++ b/changelog/22396.txt
@@ -0,0 +1,3 @@
+```release-note:improvement
+website/docs: Fix link formatting in Vault lambda extension docs
+```
diff --git a/website/content/docs/platform/aws/lambda-extension.mdx b/website/content/docs/platform/aws/lambda-extension.mdx
index cd4591895..0187c6122 100644
--- a/website/content/docs/platform/aws/lambda-extension.mdx
+++ b/website/content/docs/platform/aws/lambda-extension.mdx
@@ -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