-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
[Feature]: Proxy - Allow users to set DynamoDB URL for Key Management #1307
Comments
looks like we had an issue for dynamoDB: #887 doesn't seem like dynamodb would be supported by the prisma interface - prisma/prisma#1676 (comment) |
An alternative here is using AWS RDS https://aws.amazon.com/rds/free/?loc=ft#Free_Tier Which provides PostgreSQL on AWS |
User said DynamoDB is a hard requirement. We could just use boto3 for this - https://www.honeybadger.io/blog/using-dynamodb-with-python/ Since our db client is already abstracted away - litellm/litellm/proxy/utils.py Line 251 in aa757d1
We could just do this ourselves |
Don't think we should do this ourselves. Seems like there's different edge cases here - e.g. how you set compute cost (aws charges per read/write or by compute, etc.) Considering using this - https://github.com/pynamodb/PynamoDB |
I have an initial working commit - https://github.com/BerriAI/litellm/tree/litellm_dynamo_db_keys Really concerned about the overhead of supporting 2 different db formats (nosql + sql) |
pynamodb doesn't support async 😢 pynamodb/PynamoDB#802 exploring alternatives |
pending work - enable spend tracking for dynamodb |
The Feature
User wants to do key mgmt and budget tracking, but can only use DynamoDB
Motivation, pitch
user request
Twitter / LinkedIn details
No response
The text was updated successfully, but these errors were encountered: