aws / aws/amazon-sagemaker-feedback

SageMaker Studio bug report

Open
#160 0 comments 0 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

SageMaker Studio have some wrong. I can't scale up the storage and also can't delete this space. The error message as below:
"VolumeModificationRateExceeded: We encountered an internal error when trying to update your volume size. We apologize for the inconvenience. Wait at least 6 hours before trying to update the volume size again."

The error image as below:

![Image](https://github.com/user-attachments/assets/acfe9812-9b2f-49fe-9a4b-01437bfd54e3)

![Image](https://github.com/user-attachments/assets/ed84167a-a15f-48ea-96f3-e37444d40eb7)

### Expected Behavior

_No response_

### Observed Behavior

_No response_

### Product Category

_No response_

### Feedback Category

_No response_

### Other Details

_No response_

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the SageMaker Studio storage scaling and space deletion failures described in the issue, using the attached error screenshots and the VolumeModificationRateExceeded message as references. Confirm the behavior across both operations and document what happens after the stated six-hour wait; done means storage can be scaled and the space can be deleted without these errors.

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
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.