From 8d0743c16d75a582bb8e0c5f4afb73b7ff52c57b Mon Sep 17 00:00:00 2001
From: kpcraig <3031348+kpcraig@users.noreply.github.com>
Date: Mon, 24 Mar 2025 17:41:01 -0400
Subject: [PATCH] known issue for sts configuration (#29993)

---
 .../known-issues/aws-fallback-sts.mdx         | 27 +++++++++++++++++++
 1 file changed, 27 insertions(+)
 create mode 100644 website/content/partials/known-issues/aws-fallback-sts.mdx

diff --git a/website/content/partials/known-issues/aws-fallback-sts.mdx b/website/content/partials/known-issues/aws-fallback-sts.mdx
new file mode 100644
index 0000000000..607f2e6c5b
--- /dev/null
+++ b/website/content/partials/known-issues/aws-fallback-sts.mdx
@@ -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"
+...
+}
+```