aws / aws/amazon-sagemaker-feedback

Unable to change the instance from ml.t3.medium to any higher version

Open
#102 0 comments 2 reactions 0 assignees View on GitHub
bug
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 created my space in SageMaker Studio Code Editor in the same way as all my work colleagues did, starting initially with ml.t3.medium, but I'm the only one who cannot update the instance to ml.t3.large or higher.

### Expected Behavior

When choosing ml.t3.large on the list of instances (on the personal Code Editor page) and clicking "Run space" the button "Open CodeEditor" should appear after a short time (usually a few minutes).

### Observed Behavior

After clicking "Run space" the status changes to "Updating" and the button "Open CodeEditor" never appears (the status "Updating" doesn't change to "Running" after more than one hour). When I refresh the page or go back to the list of all Code Editor spaces, the status goes back to "Stopped".

### Product Category

Code-Editor

### Feedback Category

Error Handling and Debugging

### Other Details

_No response_

Contributor guide

Open the contributing guide

Research direction

The report provides no repository file, test, or code entry point. Start by reproducing the SageMaker Studio Code Editor space update from ml.t3.medium to ml.t3.large, then compare the Updating-to-Stopped behavior with the expected Running state and Open CodeEditor button. Done would require identifying a documented cause or confirmed product fix.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
cloud
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.