feat/create new sagemaker vpc #185
Draft
Conversation
This file contains 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
…agemaker-separate-vpc Merge upstream changes.
chore/bring branch up to date with main
Merge changes from feat/sagemaker-llms - switch off llama 70b
…be called from Theia
incorporate latest changes to main sagemaker branch (incl. autoscaling)
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.
Create new SageMaker VPC. Run SageMaker endpoints inside VPC. Move relevant endpoints inside new SageMaker VPC (e.g. sagemaker-runtime, sagemaker-api, sns). Create peering connection with datasets and main VPC to utilise their endpoints.