I have tried Data Wrangler in Sagemaker last month and close the service. A few weeks later I have noticed the credit was charge $1 every hour and just realized that the Data Wranger auto-save the flow every minute. So, I deleted the unsaved flow and shut down all the services and instances according to advice on these two links :
Then, I left the Sagemaker untouched for the whole month of May, and just got back to the console yesterday. This is what I found out for May's bill:
Amazon SageMaker RunInstance $531.74
Detail | Usage | Total |
---|
$0.00 for Host:ml.m5.xlarge per hour under monthly free tier | 125.000 Hrs | $0.00 |
$0.00 for Notebk:ml.t2.medium per hour under monthly free tier | 107.056 Hrs | $0.00 |
$0.00 per Data Wrangler Interactive ml.m5.4xlarge hour under monthly free tier | 25.000 Hrs | $0.00 |
$0.23 per Hosting ml.m5.xlarge hour in US East (N. Virginia) | 88.997 Hrs | $20.47 |
$0.922 per Data Wrangler Interactive ml.m5.4xlarge hour in US East (N. Virginia) | 554.521 Hrs | $511.27 |
So, with another attempt, I installed an extension to automatically shut down idle kernels and set the limit to 10 min from advice here:
https://aws.amazon.com/blogs/machine-learning/save-costs-by-automatically-shutting-down-idle-resources-within-amazon-sagemaker-studio/
Checked the cost in usage report, it turns out that the service was shut down after installing the extension but then it revoked itself after 5 hours later (during my sleep time). There's still cost from Studio although with less charge than previous one.
Service | Operation | UsageType | StartTime | EndTime | UsageValue |
---|
AmazonSageMaker | RunInstance | USE1-Studio_DW:KernelGateway-ml.m5.4xlarge | 5/24/2022 23:00 | 5/25/2022 0:00 | 1 |
AmazonSageMaker | RunInstance | USE1-Studio_DW:KernelGateway-ml.m5.4xlarge | 5/25/2022 0:00 | 5/25/2022 1:00 | 1 |
AmazonSageMaker | RunInstance | USE1-Studio_DW:KernelGateway-ml.m5.4xlarge | 5/25/2022 1:00 | 5/25/2022 2:00 | 1 |
AmazonSageMaker | RunInstance | USE1-Studio_DW:KernelGateway-ml.m5.4xlarge | 5/25/2022 2:00 | 5/25/2022 3:00 | 0.76484417 |
AmazonSageMaker | RunInstance | USE1-Studio_DW:KernelGateway-ml.m5.4xlarge | 5/25/2022 8:00 | 5/25/2022 9:00 | 0.36636722 |
AmazonSageMaker | RunInstance | USE1-Studio_DW:KernelGateway-ml.m5.4xlarge | 5/25/2022 9:00 | 5/25/2022 10:00 | 0.38959556 |
During this time, I'm sure that there're no running instances, running apps, kernel sessions or terminal sessions. I even deleted the user profile. Last thing I haven't tried is to set up scheduled shutdown coz I think the services should not cause difficulty to our life that much. Any advice for any effective action to completely shutdown the Sagemaker instance? Thanks.