aws / aws/amazon-sagemaker-feedback
Canvas Started Itself After Being Turned Off Multiple Times
- 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 turned Canvas off at least four times, only to check my account and see it turned itself back on. And my alerts for capping spending did not trigger. I've said this multiple times, but it's like there is a deliberate attempts to run up charges.
### Expected Behavior
_No response_
### Observed Behavior
_No response_
### Product Category
_No response_
### Feedback Category
_No response_
### Other Details
_No response_
Contributor guide
Research direction
The report contains no source files, tests, or implementation entry points. Start by reproducing the Canvas enablement behavior in Amazon SageMaker Studio and checking the related spending-alert configuration. Done would require a confirmed cause and a defined change, but this feedback issue does not specify either.
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
- 15/100