UnifiedStudio:VolumeUsage.gp3 - charges incurred

The usage type USE1-UnifiedStudio:VolumeUsage.gp3 in your report indicates that you have General Purpose SSD (gp3) EBS volumes active in the US East (N. Virginia) region. Even if you deleted your EC2 instances, the associated storage volumes often persist unless specifically told to "Delete on termination“. It is important to know that volumes used by managed services (like Amazon RDS) do NOT appear in the EC2 Console. Only "EC2 Volumes" are manually managed and visible in the EC2 "Volumes" list. e.g. "RDS Storage" is managed within the Amazon RDS Console. If you have a "stopped" database, you are still charged for the allocated gp3 storage !

1. Check the Correct Region

In your screenshot, the usage e.g. US East (N. Virginia).

• Open the Amazon EC2 Console.
• Check the top-right corner of the AWS navigation bar. Ensure the region is set to US East (N. Virginia) us-east-1 but please also check the other regions. If you are looking in „Mumbai“ you won't see these volumes.

So, example here is us-east-1 mean for Volumes in all other regions you need to switch inside the Web Console into the other region:

2. Locate and Delete the Volumes

Once you are in the N. Virginia region:

• In the left-hand sidebar, scroll down to the Elastic Block Store section.
• Click on Volumes.
• Look for any volumes with the State "available" (this means they are not attached to anything but are still costing you money) or "in-use."
• Select the volume(s), click Actions, and select Delete volume.

3. Don't Forget Snapshots

Sometimes, users delete the volume but leave a Snapshot (a backup) behind. While your specific usage type points to a live volume, snapshots also incur costs.

• In the same sidebar, click Snapshots.
• Filter by "Owned by me."
• Delete any snapshots you no longer need.

4. Use Tag Editor for a "Global" Search

If you still can't find them, use the AWS Resource Groups & Tag Editor:

• Search for Resource Groups & Tag Editor in the AWS search bar.
• Click Tag Editor on the left.
• Select All Regions and Resource Type AWS::EC2::Volume and AWS::RDS::DBInstance, check also for AWS::SageMaker::NotebookInstance if you used Machine Learning tools and AWS::EMR::Clusterif you may used it.
• Click Search resources. This will show you exactly which region the hidden volumes are hiding in.
• https://docs.aws.amazon.com/tag-editor/latest/userguide/find-resources-to-tag.html

One additional tip regarding gp3 volumes: Since you are using gp3 volumes, keep in mind that you are charged not only for the storage (GB-Month) but potentially also for provisioned performance. Unlike older gp2 volumes, gp3 allows you to scale IOPS and Throughput independently of storage size. If you decide to keep a volume but want to minimize costs, ensure that IOPS and Throughput are set to their baseline values (3,000 IOPS and 125 MB/s), as anything above these thresholds incurs additional hourly charges. Of course, once you delete the volume entirely, these charges will stop automatically.

If the steps described above do not lead to the desired result, I would go one layer deeper inside the affected AWS account. In “Billing and Cost Management”, under “Bills”, scroll down a bit, select the “Charges by service” tab, and then check e.g. under “Elastic Compute Cloud” (or other services which use EBS volumes like RDS etc.) whether EBS charges were incurred, as shown in the following example:

In my example, I selected the region "EU (Frankfurt)" and "Elastic Compute Cloud" because I do not currently have a suitable example for SageMaker Studio like in your case:

Ultimately, the Billing console, with a delay of around 12 hours, shows the real truth: which resources caused which costs in which AWS account and in which AWS region. That helps narrow things down. Even if this approach might not feel particularly elegant, it very often gets me to the right answer in similar cases.

What I would also do in this case is use the "AWS Resource Explorer" to search for things like RDS snapshots, EBS volumes, and similar resources.

1. select the as Property "Resource type"

2. Resource Type = Euqals

3. In this Example rds:snapshot

or alternatively ec2:volumein the following example

-> https://docs.aws.amazon.com/resource-explorer/latest/userguide/welcome.html

However, in your specific case, based on your screenshots and the persistent charges for UnifiedStudio:VolumeUsage.gp3, here are the likely reasons you are still seeing costs and how to resolve them:

In your bill, you should find line items for SageMaker Studio-specific resources.

Also, please check the SageMaker Console. Select Studio and look for any User Profiles. Even if no apps are running, SageMaker Studio creates an Amazon EFS or EBS volume for the user's home directory that persists (and incurs costs) until the User Profile itself is deleted.

Based on your screenshot, there also appears to be a region mismatch during manual checks. Your billing report shows usage in US East (N. Virginia). So, in your Tag Editor screenshot, you are searching for resources, but if you are manually looking through the EC2 or RDS consoles while your console is set to Mumbai, those North Virginia resources will remain invisible. You need to switch your AWS Console region to us-east-1 (N. Virginia) and then check the Volumes and Snapshots sections under EC2.

Regarding Resource Explorer indexing: You mentioned the Tag Editor/Resource Search showed "No resources". For Resource Explorer to work globally, you must first create an aggregator index in one region and enable indexing for all regions. If this is not set up, the search will return nothing even if resources exist.

• Go to AWS Resource Explorer, click Settings, and ensure that "Multi-region search" is enabled and that the index has finished crawling your account

check also:

• https://docs.aws.amazon.com/sagemaker/latest/dg/studio-tasks-manage-storage.html