Skip to content

How to find elusive but expensive snapshots?

0

Bill shows an increasing amount of charges related to EBS - snapshot data stored 9,027.345 GB-Mo last month and rising.

The suggestion by support is, of course, to delete snapshots I no longer need. Trouble is: I can't find any snapshots. Zero. Zilch. Nada. If I can't find them, I can't delete them. I can't manage their lifecycle. I can't find out where they are coming from and put a stop to it. I looked under EC2 dashboard under snapshots. There's nothing there. I tried the CLI. Still nothing there.

The big winner is Amazon, since they get to charge me for invisible and possibly fictitious snapshots.

asked a year ago257 views
2 Answers
2

Hello.

Specifically, in which region are the charges occurring?
Is it possible that I'm checking the wrong region?
I created a shell script to check if there are any remaining snapshots in the AWS account region.
Please run the shell script below to check if it remains in your AWS account.

#!/bin/bash

regions=$(aws ec2 describe-regions --query 'Regions[].RegionName' --output text)

for region in $regions
do
        echo "Checking snapshots in region: $region"
        snapshots=$(aws ec2 describe-snapshots --owner-ids self --region $region --query 'Snapshots[*].[SnapshotId,VolumeSize]' --output text)
        if [ -z "$snapshots" ]
        then
                echo "No snapshots found in $region"
        else
                echo "$snapshots"
        fi
done
EXPERT
answered a year ago
EXPERT
reviewed a year ago
EXPERT
reviewed a year ago
0

Hii...Nathan

i just wanted to share a suggestion from what I know. I hope it helps you in some way

Use AWS Config and CloudTrail logs to identify the source of the snapshots

  1. Enable AWS Config and CloudTrail in your account, if not already enabled.
  2. Go to the AWS Config dashboard and search for EBS snapshot creation events.
  3. Filter the events by date and time to match the increasing charges.
  4. Identify the snapshot IDs and the resources EC2 instances, volumes associated with them.
  5. Use the CloudTrail logs to track the API calls made to create these snapshots.
  6. Analyze the logs to determine the source of the snapshots automated scripts, user actions.
  7. Once you identify the source, take corrective action to stop the unnecessary snapshot creation.

This approach will help you detect and prevent the creation of unwanted snapshots, reducing your EBS charges.

EXPERT
answered a year ago
  • I am trying and not getting much closer. In AWSConfig, I went through every resource it could find. None of them were snapshots. Not in the AWS Config, but in the cloudtrail, I found CreateSnapshot events, happening twice a day for at least the last month. ALL of them appear to be failing because of "Client.InvalidVolume.NotFound" The volume associated with all of them is a volume that doesn't exist. There is no snapshot ID associated, apparently because they all fail. The username is AWS_Events_Invoke_Action_On_EBS_Volume_[BIG NUMBER]
    I discovered this is a "Role" I created a long time ago. I can edit or delete it - will that do the job? And how will I ever find the gazillion snapshots it created? Or maybe it didn't ever succeed and there are none, yet I am being charged for the failed snapshots? I still don't what script or setting or config is causing this to happen twice a day.

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.