Feat/use jumpstart streamlined for new llm options #192
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.
Using Sagemaker Jumpstart containers and model weights stored in an AWS account in the eu-west-2 region, we redeploy the existing two small LLMs. This process then trivially allows for new LLMs to be added. Note that through jumpstart we also optimize the instance size and ensure the correct environment variables for the model, which can otherwise be difficult. It should be possible to also store these containers and model weights in our own account, I need to check how to do that, but I do wonder if it adds value since this way it never goes to the public internet in any case as it stays within the AWS region.