-
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
AWS DynamoDb scaler #2482
Closed
Labels
Comments
Are you willing to contribute this? |
Yes, I can have a look at this 👍🏻 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
zroubalik
removed
the
stale
All issues that are marked as stale due to inactivity
label
Mar 16, 2022
Repository owner
moved this from In Review
to Ready To Ship
in Roadmap - KEDA Core
Mar 22, 2022
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Proposal
Scaler based on the result of a DynamoDB table query.
Scaler Source
The single numeric result of a DynamoDb query.
Scaling Mechanics
The scaling mechanics is based on the result of a table query in DynamoDB (similar to what has been done for MongoDB).
Authentication Source
It can reuse the
identityOwner
and theTriggerAuthentication
implemented for the SQS Scaler.Anything else?
The idea is similar to the MongoDB scaler. It is possible to reuse the authentication bit already implemented for Amazon SQS.
DynamoDb paginates results over 1MB, see https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Query.html#Query.Count
The text was updated successfully, but these errors were encountered: