aws / aws/amazon-sagemaker-feedback
Unable to create a MLFlow tracking server
- 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
amed the server. It was supposed to automatically redirect me to the final server's page, but it did not act at all and I waited for a long time. Then, after checking the result and thinking it might be an issue with IAM permissions, I had our DevOps grant me the necessary IAM permissions. Yet, when I attempted the operation again, the result was the same, and I could not create the final server. Therefore, I am now unsure which part of the process is malfunctioning. The expected behavior is that it should automatically redirect me to the final server after a while, but the behavior I observed is that it did not redirect me to the server, hence I cannot access this resource endpoint and am unable to proceed with the subsequent experiments.
### Expected Behavior
The expected behavior is that it should automatically redirect me to the final server after a while
### Observed Behavior
the behavior I observed is that it did not redirect me to the server, hence I cannot access this resource endpoint and am unable to proceed with the subsequent experiments.
### Product Category
_No response_
### Feedback Category
_No response_
### Other Details
_No response_
Contributor guide
Research direction
Start by reproducing MLFlow tracking server creation in Amazon SageMaker Studio and record whether the operation completes or redirects to the server page. Compare the observed behavior with the expected redirect and investigate the resource endpoint and IAM permissions; done means the server is created and accessible for subsequent experiments.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, machine-learning
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100