Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documented adding secretKey parameter to access aws secret manager #1508

Open
wants to merge 4 commits into
base: main
Choose a base branch
from
Open

Documented adding secretKey parameter to access aws secret manager #1508

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
2c33b1b
Documented adding secretKey parameter to access aws secret manager
mpechner-akasa Dec 5, 2024
74e17fe
Merge branch 'main' into aws-secretsmanager-additions
mpechner-akasa Jan 13, 2025
a700f03
Added a note to the description for the secretKey parameter and entry…
mpechner-akasa Jan 17, 2025
ca43554
Merge branch 'main' into aws-secretsmanager-additions
mpechner-akasa Jan 17, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions content/docs/2.17/authentication-providers/aws-secret-manager.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
```
6 changes: 4 additions & 2 deletions content/docs/2.17/concepts/authentication.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
JorTurFer marked this conversation as resolved.
Show resolved Hide resolved
gcpSecretManager: # Optional.
secrets: # Required.
- parameter: {param-name-used-for-auth} # Required.
Expand Down Expand Up @@ -377,7 +378,7 @@ The `credentials` section specifies AWS credentials, including the `accessKey` a

The `region` parameter is optional and represents the AWS region where the secret resides, defaulting to the default region if not specified.

The `secrets` list within `awsSecretManager` defines the mapping between the AWS Secret Manager secret and the authentication parameter used in your application, including the parameter name, AWS Secret Manager secret name, and an optional version parameter, defaulting to the latest version if unspecified.
The `secrets` list within `awsSecretManager` defines the mapping between the AWS Secret Manager secret and the authentication parameter used in your application, including the parameter name, AWS Secret Manager secret name, an optional secret key parameter, and an optional version parameter, defaulting to the latest version if unspecified.

```yaml
awsSecretManager:
Expand All @@ -399,6 +400,7 @@ awsSecretManager:
- parameter: {param-name-used-for-auth} # Required.
name: {aws-secret-name} # Required.
version: {aws-secret-version} # Optional.
secretKey: {aws-secret-key} # Optional.
```

#### AWS Pod Identity Webhook for AWS
Expand All @@ -425,4 +427,4 @@ You can tell KEDA to use EKS Pod Identity Webhook via `podIdentity.provider`.
```yaml
podIdentity:
provider: aws-eks # Optional. Default: none
```
```
Loading