Skip to main content

How to check or find unattached snapshot in AWS

Checking unattached snapshot is a good technique to save some storage cost; of course, you need to do what’s the best thing after checking unattached snapshots.

If you are confident that the snapshot won’t be needed anymore, then it has to be deleted or else you will be incurring costs for nothing.

Every space on the cloud is not free, any space usage is an added cost to your pocket.But then how do you check for unattached snapshot in AWS?

There are quite a lot of ways you can do, if you love PowerShell it can be done in PowerShell; if you want to do it in Python with Boto3 it can be done as well.

Of course, in PowerShell and Python if this is the preferred method then you need to create some code. It won’t just spit out for you what are the unattached snapshots in your AWS account.


Enough said, the easiest way to search or look for unattached snapshot is just to search using the AWS EC2 console.


Open your browser, login to your EC2 console and search for: vol-ffff

See image below:

vol-ffff will be present as volume-id for those unattached snapshots as part of the search result. Basically, if an snapshot is not attached to any volume, the volume-id will vol-ffff.


There you go no need for PowerShell and Python Boto3 to search for unattached snapshots.

Easy right? If you have to automate the checking for unattached snapshot then just get the list of all the snapshots in your account and compare the volume-id to vol-ffff. Or just simply check all snapshots and look for volume-id that matches the said value.

Any snapshots with that matching value is a snapshot that is not attached to any volumes.

Then you can decide to delete the snapshot, you just need to be very sure that you won’t look for it or it won’t be needed anymore.  Finding unattached snapshot is not so difficult at all.


Cheers. Till next time. Hope it helps. :)


================================
Free Android Apps:

Click  links below to find out more:

Excel Keyboard guide:


Heaven's Dew Fall  Prayer app for Android :



Catholic Rosary Guide  for Android:


Divine Mercy Chaplet Guide (A Powerful prayer) BFF = Be Filled Faith:


Comments

Popular posts from this blog

WMIC get computer name

WMIC get computer model, manufacturer, computer name and  username. WMIC is a command-line tool and that can generate information about computer model, its manufacturer, its username and other informations depending on the parameters provided. Why would you need a command line tool if there’s a GUI to check? If you have 20 or 100 computers, or even more. It’s quite a big task just checking the GUI to check the computer model and username. If you have remote computers, you need to delegate someone in the remote office or location to check. Or you can just write a batch file or script to automate the task. Here’s the code below on how get computer model, manufacturer and the username. Open an elevated command prompt and type:     wmic computersystem get "Model","Manufacturer", "Name", "UserName" Just copy and paste the code above, the word “computersystem” does not need to be change to a computer name. A...

Print error 016-799 - Fuji Film Xerox

016-799 Fuji Xerox or Fuji Film print error code. That shows a description error as “Print instruction Fail detected in decomposer.” The error code and error description are alien languages for users and even system administrators who are not familiar with Fuji Xerox error code. The error code is quite simple and easy to fix, if the job print goes to the printer but print out doesn’t come out. So, basically the print job was received by the printer, but the printer just doesn’t know what type of paper or what size to use or which tray to utilize for the print out. In some instances, this is just a paper mismatch but the error description; if using Windows 10 to print does not exactly points to what is the issue. First thing to check, is the paper size selected by the user to print. Example, if the printer configuration is A3 and A4 sizes only. But then the person printing the file accidentally chooses “A4 Cover” then this error 016-799 will occur. ...

How to check office version from command line

The are quite a few ways to check office version it can be done via registry, PowerShell or VBScript and of course, good old command line can also do it. Checking Windows office version whether it is Office 2010, Office, 2013, Office 2016 or other version is quite important to check compatibility of documents; or just a part of software inventory. For PowerShell this simple snippet can check the office version: $ol = New-Object -ComObject Excel.Application $ol . Version The command line option will tell you where’s the path located; the result will also tell whether office is 32-bit, 64-bit and of course the version of the office as well. Here’s the command that will check the office version and which program directory the file is located which will tell whether it’s 32-bit or 64-bit. Command to search for Excel.exe: DIR C:\ /s excel.exe | find   /i "Directory of"  Above command assumes that program files is on  C: drive. Sample O...