AWS Builder Center is the official home for builders on AWS. Share and read what others are working on, follow people who inspire you, explore training and workshops, and find tools to support what you're building.
Unable to turn off $0.112 per GB-Mo of provisioned ML storage for SageMaker
Hello, I am relatively new to Amazon AWS. Two months ago, I created a Notebook in Sagemaker, then deleted it. However, I am still charged $0.112 per GB-Mo of provisioned ML storage. How do I turn this off?
Thanks!
- Newest
- Most votes
- Most comments
Do you still have a running endpoint? If so, there will be bills from the endpoint. Also, you can enable cost utilisation report, that will show you the exact resource that is resulting in the cost.
https://docs.aws.amazon.com/AmazonS3/latest/userguide/aws-usage-report.html
It appears you're experiencing a common issue with SageMaker where resources may not have been fully cleaned up after deleting a notebook, leading to ongoing charges. Here are some steps you can take to address this:
-
Check your SageMaker resources: Even though you deleted the notebook, there might be other associated resources still active, such as endpoints, models, or storage volumes.
-
Review the SageMaker console: Look for any lingering resources in the SageMaker section of the AWS console, particularly in the region where you created the notebook.
-
Check for EBS volumes: The charge you're seeing ($0.112 per GB-Mo) is consistent with EBS storage pricing. There may be an EBS volume that was created for your SageMaker notebook but wasn't automatically deleted.
-
Use AWS Cost Explorer: This tool can help you identify exactly which SageMaker resources are still incurring charges.
-
Clean up ML storage: Look for any ML storage volumes in the SageMaker section of the console and delete them if they're no longer needed.
-
Check for inference endpoints: Ensure that any endpoints created for model deployment have been properly shut down.
If you're unable to locate the source of the charges after following these steps, it's advisable to contact AWS Support. They can provide a detailed breakdown of the charges and assist you in identifying and terminating any lingering resources.
For future use, consider implementing best practices such as using CloudWatch Billing Alarms to monitor your estimated AWS charges and receive notifications when they exceed a threshold. Also, familiarize yourself with the proper shutdown procedures for SageMaker resources to avoid unexpected charges.
Remember, simply deleting a notebook instance doesn't always remove all associated resources automatically. It's important to ensure all components are properly cleaned up to avoid ongoing charges.
Sources
AWS Sagemaker Charging when it is not is usage | AWS re:Post
How to know what is it that I am getting charged for. | AWS re:Post
Billling issue : sagemaker runinstance : How to terminate | AWS re:Post
MLCOST-16: Stop resources when not in use - Machine Learning Lens
Being charged for unused SageMaker: What beyond Instances and Domain can I shut down in SageMaker? | AWS re:Post
Check your Amazon s3 bucket instances and delete them. At times deleting a notebook in SageMaker does not automatically delete the s3 bucket attached to it. Hope this works for you.
answered a year ago
Relevant content
asked a year ago
asked 3 years ago
Hello, I checked running endpoints on Sagemaker but have nothing activated. I tried to enable cost utilization report, but to do that, I need to create a bucket, and that costs money. I am afraid of installing/creating something, then being unable to delete it, like this previous storage from a notebook. Is there a "terminate all" button somewhere in the program? Thank you so much!