aws / aws/amazon-sagemaker-feedback
Unable to open Sagemaker Classic through the new studio
- Dominant language
- No language data
- Stars
- 10
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
### Product Version
- [X] Amazon SageMaker Studio Classic
- [ ] Amazon SageMaker Studio
- [ ] Issue is not related to SageMaker Studio
### Issue Description
With the new sagemaker studio experience, I'm unable to open the classic sagemaker studio classic. The new jupyter lab opens without issues but the classic sagemaker does not open. Runs into a sagemaker auth token error which does not resolve no matter how many times you try.
### Expected Behavior
Sagemaker classic should open without issues
### Observed Behavior
Does not open and always presents an expired auth token error.
### Product Category
JupyterLab
### Feedback Category
Configuration and Setup
### Other Details
_No response_
Contributor guide
Research direction
No repository files, tests, or entry points are identified. Start by opening SageMaker Studio's new experience, launching JupyterLab, and attempting to open Studio Classic while observing the expired auth token error. Done means Studio Classic opens successfully without the authentication failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, jupyter
- Domain
- authentication, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100