aws / aws/amazon-sagemaker-feedback

Interval failure

Open
#217 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

I'm hitting non descriptive internal failure errors when trying to start spaces, both jupyter lab and code editor. No logs on cloud watch available for the spaces that fail to start.

### Expected Behavior

No failure or at least descriptive error or logs

### Observed Behavior

_No response_

### Product Category

_No response_

### Feedback Category

_No response_

### Other Details

_No response_

Contributor guide

Open the contributing guide

Research direction

No repository files, tests, or implementation entry points are identified. Start by reproducing the startup failure for both JupyterLab and the code editor in Amazon SageMaker Studio, then check whether CloudWatch contains corresponding space logs; done requires a descriptive failure or available logs instead of an internal error.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
cloud
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.