-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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.
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
Authentication: support AWS secret manager #4628
Labels
aws
All issues concerning integration with AWS
feature
All issues for new features that have been committed to
help wanted
Looking for support from community
Comments
devopsmash
added
feature-request
All issues for new features that have not been committed to
needs-discussion
labels
Jun 1, 2023
JorTurFer
added
help wanted
Looking for support from community
feature
All issues for new features that have been committed to
aws
All issues concerning integration with AWS
and removed
needs-discussion
feature-request
All issues for new features that have not been committed to
labels
Jun 2, 2023
I would like to work on it, could you please assign this to me @JorTurFer |
Nice!!! ❤️❤️❤️ |
7 tasks
Hi @zroubalik could you please assign this task to me as it been stale for a while now. |
Sure ! |
7 tasks
1 task
github-project-automation
bot
moved this from In Review
to Ready To Ship
in Roadmap - KEDA Core
Jan 12, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
aws
All issues concerning integration with AWS
feature
All issues for new features that have been committed to
help wanted
Looking for support from community
Proposal
add to
TriggerAuthentication
support to "AWS secret manager"Use-Case
We are using AWS MSK with sasl (user & password) for authentication
Why? Because we are allowing our Dev team in Development environment to access the MSK with public IP.
Therefor, the developer can't use AWS IAM role (we are not providing them aws creds) so we have to use sasl (user & password).
Because of this, we want that
TriggerAuthentication
will support also getting the user & password from the AWS secret manager instead of a k8ssecret
that realy easy to get the creds.Is this a feature you are interested in implementing yourself?
No
Anything else?
It seems that you already support Hashicorp Vault secret(s) and Azure Key Vault secret(s).
Support AWS secret manager can be very helpful.
more here: https://keda.sh/docs/2.10/concepts/authentication/
The text was updated successfully, but these errors were encountered: