Unexpected SageMaker Charges on My Account

I understand your concern about unexpected SageMaker charges on your account. There appears to be a discrepancy between your Cost Explorer query showing zero usage and the actual charges on your bill.

When unexpected SageMaker charges appear, there are several hidden components that might be running even if you don't actively use the service. Here are some areas to check:

1. MLflow Tracking Servers: These can run in the background and appear as "RunTrackingServer" charges on your bill. They might not be visible in the standard console interface.

2. EBS volumes and ML storage: SageMaker might have provisioned ML storage ($0.112 per GB-Mo) that wasn't automatically deleted.

3. Inference endpoints: These continue to run and incur charges even if you're not actively using them.

4. Canvas workspaces: There might be "Workspace Instance Session-Hour" charges running that aren't visible in the Console.

5. Check all regions: SageMaker resources are region-specific, so verify all AWS regions for any active resources.

6. Hidden resources: Components like HyperPod clusters, Pipelines, EMR clusters, RStudio resources, and TensorBoard applications might be running.

7. VPC resources: Check for lingering VPC resources associated with SageMaker.

To identify the exact source of charges:

• Use AWS Cost Explorer with more detailed filters - try filtering by SageMaker in the Service dropdown and view by API Operations to see which specific operations are costing you
• Check all AWS regions for any SageMaker resources
• Look for resources that might not be visible in the standard console views

If you're still unable to locate the source of the charges after checking these areas, I recommend contacting AWS Support directly by creating a billing support case. They can provide a detailed breakdown of the charges and assist in identifying and terminating any lingering resources.

Also, note that there might be a discrepancy in your query dates (2025) which could be affecting your results. Make sure you're querying the correct time period that corresponds to your actual charges.
Sources
Unexpected SageMaker charges appearing on my bill | AWS re:Post
Unexpected SageMaker costs | AWS re:Post
.56 cents every month. | AWS re:Post
Being charged for unused SageMaker: What beyond Instances and Domain can I shut down in SageMaker? | AWS re:Post

Can you double-check your Budgets and confirm it only includes the SageMaker service. Also, is this budget set for a specific account - if you have a main/root account, it's possible the charges are from another account.

We are unable to verify any usage history in SageMaker AI or on our SageMaker environment.

After discussing internally, we suspect that resources created by a former single user may have been left running. However, since that user has already left the organization and their account has been deleted, we are unable to confirm this.

We would like to request guidance on how to stop these resources, including any necessary procedures or steps.

Hi AWS Support Team,

I hope you are doing well. This is a second follow-up to my earlier message. When you have time, I would appreciate your response.

Additionally, I believe the invisible costs are critical for AWS services — this issue could have serious implications. I would appreciate it if you could address it as soon as possible.

Best regards, Daicih_Y