Documented adding secretKey parameter to access aws secret manager

Doc for issue: kedacore/keda#5940 PR: kedacore/keda#6381 Signed-off-by: michael pechner <[email protected]>
mpechner-akasa · Dec 5, 2024 · 2c33b1b · 2c33b1b
1 parent f12f165
commit 2c33b1b
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 1 deletion.
diff --git a/content/docs/2.17/authentication-providers/aws-secret-manager.md b/content/docs/2.17/authentication-providers/aws-secret-manager.md
@@ -37,4 +37,5 @@ awsSecretManager:
   - parameter: {param-name-used-for-auth}          # Required.
     name: {aws-secret-name}                        # Required.
     version: {aws-secret-version}                  # Optional.
+    secretKey: {aws-secret-key}                    # Optionqal
 ```
diff --git a/content/docs/2.17/concepts/authentication.md b/content/docs/2.17/concepts/authentication.md
@@ -157,6 +157,7 @@ spec:
     - parameter: {param-name-used-for-auth}                               # Required.
       name: {aws-secret-name}                                             # Required.
       version: {aws-secret-version}                                       # Optional.
+      secretKey: {aws-secret-key}                                         # Optional.
   gcpSecretManager:                                                       # Optional.
     secrets:                                                              # Required.
       - parameter: {param-name-used-for-auth}                             # Required.
@@ -425,4 +426,4 @@ You can tell KEDA to use EKS Pod Identity Webhook via `podIdentity.provider`.
 ```yaml
 podIdentity:
   provider: aws-eks # Optional. Default: none
-```
+```