.56 cents every month.

Question

Hello everyone,

Every month I get billed .56 cents for Sagemaker. I went to my resources, and there is nothing running. The billing report only indicates "Sagemaker". No endpoints, domains or notebooks running. I'm confused.

Any ideas where I could look for more info? or what could be?

Shahed Kazi (@shajam) · Answer

Use Cost Explorer. Choose SageMaker for the Service drop down and view by API Operations. It will tell you which API calls are costing you.

re:Post Agent · Answer

When you're experiencing unexpected SageMaker charges even after confirming no visible resources are running, there are several hidden components that might still be active. Here's what you should check:

1. **MLflow Tracking Servers**: These can continue running in the background and appear as "RunTrackingServer" charges. These might not be visible in the standard console interface and may require using the AWS CLI or API to list and delete them with commands like `aws sagemaker list-mlflow-tracking-servers`.

2. **EBS volumes and ML storage**: The charge of $0.56 could be related to provisioned ML storage ($0.112 per GB-Mo) that wasn't automatically deleted when you removed other SageMaker resources. Simply deleting a notebook doesn't always remove associated storage volumes.

3. **Canvas workspaces**: There might be "Workspace Instance Session-Hour" charges running that aren't visible in the Console even if you're logged out of Canvas.

4. **Check all regions**: SageMaker resources are region-specific, so verify all AWS regions to ensure you haven't missed any active resources.

5. **VPC resources**: Check for any lingering VPC resources or endpoints associated with SageMaker that might be difficult to delete because they're requester-managed.

To identify the exact source of charges, use AWS Cost Explorer to pinpoint which specific SageMaker resources are causing the costs. If you're still unable to locate the source after checking these areas, contact AWS Support for a detailed breakdown and assistance in identifying and terminating any lingering resources.  
**Sources**  
[Unexpected SageMaker charges appearing on my bill | AWS re:Post](https://repost.aws/questions/QUrRzL1PaFQ3WdS0tZoZM2tA/unexpected-sagemaker-charges-appearing-on-my-bill)  
[Unable to turn off $0.112 per GB-Mo of provisioned ML storage for SageMaker | AWS re:Post](https://repost.aws/questions/QUhaoEzF8gSJSHXpdR0i910A/unable-to-turn-off-0-112-per-gb-mo-of-provisioned-ml-storage-for-sagemaker)  
[Being charged for unused SageMaker: What beyond Instances and Domain can I shut down in SageMaker? | AWS re:Post](https://repost.aws/questions/QUgiBiPI6ARWasijuNHRbfSg/being-charged-for-unused-sagemaker-what-beyond-instances-and-domain-can-i-shut-down-in-sagemaker)  
[Can't delete SageMaker VPC | AWS re:Post](https://repost.aws/questions/QUXhyAfpKZTOKY_y539EZ8Qg/can-t-delete-sagemaker-vpc)  
[SageMaker RunTrackingServer charges | AWS re:Post](https://repost.aws/questions/QU3mYmy8rFQsui44O7c-l3fg/sagemaker-runtrackingserver-charges)

.56 cents every month.

Add your answer

Relevant content