Lambda function#1
Draft
stefan-novak-brt wants to merge 2 commits into
Draft
Conversation
Collaborator
Author
|
When |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Here's an initial work of deploying a
RetrievalQAinside of a Lambda function. The approach here is to load the sample dataset into a Chroma database and persist it during the image build phase. When the Lambda runs, it'll be able to open the database on-the-fly.Steps to run:
ggml-alpaca-7b-q4.binto themodels/directory.make imageOnce the Docker image can be built, we can add a Terraform config to deploy the Lambda function to AWS. We can hook up the Lambda to the AWS API Gateway so that a web app can call it via a REST API.