- Newest
- Most votes
- Most comments
I see a warning about this here:
When you shutdown the Studio notebook instances, any additional resources, such as SageMaker endpoints, Amazon EMR clusters, and Amazon S3 buckets created from Studio are not deleted. Delete those resources to stop accrual of charges.
Why can't we see these and shut them down from Studio? I was being charged unknowingly until I got a bill.
You can either use CLI or AWS Config advance queries. With CLI you can use list-notebook-instances which Returns a list of the SageMaker notebook instances in the requester’s account in an Amazon Web Services Region. Reference : https://awscli.amazonaws.com/v2/documentation/api/latest/reference/sagemaker/list-notebook-instances.html
Same here, I can't identify where to stop whatever is consuming the hosting of one instance ml.g5.2xlarge hourly. This should be a lot easier to do in AWS, we're talking about wasted resources that are difficult for the user to stop.
Relevant content
- Accepted Answerasked 6 years ago
- Accepted Answerasked a year ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a month ago