Skip to content
By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post
About re:Post

Unexpected bill on SageMaker CreateVolumn-Gp3

-1

Hi,

I have cleaned all SageMaker resources via AWS CLI and Console and cannot see any resources in Resource Explorer. But the following resources are still charged everyday. Could you help to resolve this? (1) arn:aws:datazone:us-east-1:242552818661:datazone-notebook/dzd-4obn7qltc00kmf/4uzynge17z1y5j (2) arn:aws:datazone:us-east-1:242552818661:datazone-notebook/dzd-4obn7qltc00kmf/6brokiw2kt7i93

I have done all the following actions and not found any sagemaker resources in my accounts, also attached some snapshots of actions as below.

I think this is a critical AWS SageMaker bug. The orphaned volumes have been not managed, because the charged volumes are not found in the EC2 Console.

  1. No any sagemaker resource in Resource Explorer Enter image description here

  2. Two resources in the region us-east-1 still charged Enter image description here

  3. Unexpected bill Enter image description here

  4. Resource Explorer Enter image description here

  5. DataZone Console in the region us-east-1 Enter image description here

  6. EC2 Console in the region us-east-1 Enter image description here

  7. No any cloudformations in the region us-east-1 Enter image description here

  • Giovanni Melo
    2 months ago

    Please check your CloudFormation, maybe you can see if there is any resources left from Sagemaker.

Topics
Cloud Financial ManagementMachine Learning & AI
Tags
Amazon SageMaker Unified StudioAmazon DataZoneAmazon SageMaker StudioAWS Cost Anomaly DetectionAWS Billing
Language
English
asked 2 months ago80 views
2 Answers
2

As SHAJAM correctly mentioned, the reason you aren't seeing these in the SageMaker console is that they are managed by Amazon DataZone. The ARNs and the "UnifiedStudio" billing line confirm these are DataZone assets.

To stop the charges, you need to:

  • Open the Amazon DataZone Console.
  • Navigate to your Projects and check for any active Environments.
  • Terminate the Environments associated with these notebooks. Simply stopping the notebook is not enough; the EBS volumes (gp3) persist and incur costs until the environment is deleted.
  • If the environments are already gone, check the EC2 Console -> Volumes for any orphaned volumes tagged with "DataZone" and delete them manually.
EXPERT
answered 2 months ago
  • AveryGuo
    2 months ago
    1. No any datazone domains and environments in the Amazon DataZone Console.
    2. No any ebs volumes in the EC2 Console. You can see the snapshots in the questions.
1

I reckon you are filtering with SageMaker when your charges are from DataZone. Maybe, check for EBS volumes in SageMaker which is resulting in the charge.

EXPERT
answered 2 months ago
EXPERT
reviewed 2 months ago
  • AveryGuo
    2 months ago

    I cannot paste snamshot here. You can see the snapshot attached in the questions. I cannot filter out any EBS volumes.

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Relevant content