aws / aws/amazon-sagemaker-feedback
Can't launch instance without timeout but timeout not configurable
- Dominant language
- No language data
- Stars
- 10
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
### Product Version
- [ ] Amazon SageMaker Studio Classic
- [X] Amazon SageMaker Studio
- [ ] Issue is not related to SageMaker Studio
### Issue Description
I need to increase my jupyterlab instance size beyond 4GB RAM, but lack of timeout is preventing me from launching different instance types.
There are no options available in the lifecycle dropdown
I see a place to define them at the domain level
Contributor guide
Research direction
No repository files, tests, or entry points are identified in the issue. Start by reviewing the Amazon SageMaker Studio launch flow and the timeout settings shown at the domain level. Done means users can configure a timeout and launch larger JupyterLab instance types without the current timeout limitation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 20/100