-
Notifications
You must be signed in to change notification settings - Fork 4
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
🧱 MVP: Build SageMaker in Development #1970
Comments
I followed the aforementioned setup guide and there were AWS components mentioned, EFS, S3, etc. These are handled by the module and do not need to be declared in the code. Initially I wanted to setup the solution using SSO. However, if this solution is adopted it will liaise with control panel to manipulate user permissions. As such the I've also updated Yikang's Google doc to include an explainer on what an AWS SageMaker Domain is, this can be pulled into more formal documentation later. |
Enabled user ability to spawn spaces with the following in
|
RStudio is now out of scope of the MVP as "RStudio on Amazon SageMaker is a paid product and requires that each user is appropriately licensed." (source) |
Setup a Share manually ( |
Further details regarding price are included in the #data-platform-sagemaker Slack channel. |
linked the my for integration part to this ticket |
Completed and branch merged. |
User Story
As a member of the team taking part in the SageMaker spike.
I want to build a MVP of the SageMaker product.
So that we can properly assess the product.
Value / Purpose
Informs the spike on this piece of work.
Useful Contacts
Gary + Yikang
Hypothesis
If we build the simplest version of SageMaker possible...
Then... we can better understand the project.
Proposal
Build the simplest, probably most open version of SageMaker in the analytical-platform-development AWS account. Do this in the
data-platform
repository.Out of Scope
Definition of Done
Follow this setup guide.Semi-irrelevant as some of the setup is covered by the terraform module.The text was updated successfully, but these errors were encountered: