Can I Delete A Snapshot Of The Root Device Of An Ebs Volume Used By A Registered Ami

How-to Delete Unutilized EBS-Based AMIs and Corresponding Snapshots

How-to Guides
April 12

AWS AMIs refer to pre-configured arranged software that has the necessary information to launch an EC2 instance. Nosotros can say that AMI refers to a root device for the instance; when an EC2 instance is launched from that AMI information technology volition accept all the OS, software as well as the applications which were bundled when that AMI was created. If you create an AMI from an existing example, in one case the AMI is created, AWS creates a snapshot of the root storage as well as all the EBS volumes that are attached to the instance. When you deregister the AMI, it is only deleted. Nonetheless, all the snapshots that were attached to the AMI remain and need to exist deleted manually. The diagram below illustrates this concept. If you do not manually delete snapshots later on deregistering an AMI, they will continue to incur costs. This article delves into how to deregister AMIs as well equally delete snapshots. In improver, we provide yous with an automated script that deletes all snapshots that are associated with a corresponding AMI while deregistering the AMI.

Part 1:

Deregister AMIs and delete snapshots using the Amazon Management Console & CLI To deregister an AMI, follow the steps below:

Go to the AWS EC2 console and AMI section. Select the desired AMI. Side by side, select the 'Deregister' option in the 'Actions' tab.
Select the 'Continue' pick to deregister. The AMI is at present deregistered. You can perform the same steps using the AWS CLI, as shown below: (Notation: It is causeless that AWS CLI has already been installed on the local machine.)aws ec2 deregister-paradigm –image-id <ami-id> Every bit mentioned above, the snapshots associated with the deregistered AMI are not automatically deleted, requiring you to delete them manually. This process is outlined below:
You can find the snapshots that are associated with the AMI using the AMI ID in the 'Search' choice, as shown beneath:
To delete the snapshot, select the snapshot and click on the 'Delete' choice from the 'Actions' tab. You can perform the same steps using the AWS CLI, every bit shown below: aws ec2 delete-snapshot –snapshot-id <snapshot-id>

Part ii:

Delete the AMI and snapshots simultaneously using Powershell and a Linux script At times, it tin can be boring to delete an AMI then locate all of its associated snapshots in club to delete them, equally well. Taking that into consideration, a script has been created that tin can delete both an AMI and its associated snapshots, simultaneously. All you lot need to exercise is enter the AMI ID into the script. Two scripts have been created: one by PowerShell Script for Windows machines and the other by and for Linux. Information technology is assumed that the AWS CLI was installed on both machines/instances and that the admission credentials were ready for the AWS business relationship. If yous run these scripts from an EC2 instance, it is recommended to use the AWS IAM Role for better security. PowerShell Script: $amiName = '<The users needs to mention their AMI ID>' $myImage = Become-EC2Image $amiName $count = $myImage[0].BlockDeviceMapping.Count $mySnaps = @() for ($i=0; $i -lt $count; $i++) { $snapId = $myImage[0].BlockDeviceMapping[$i].Ebs | foreach {$_.SnapshotId} $mySnaps += $snapId } Write-Host "Unregistering" $amiName Unregister-EC2Image $amiName foreach ($item in $mySnaps) { Write-Host 'Removing' $item Remove-EC2Snapshot $item } Linux Script: #!bin/sh # chkconfig: 2345 96 14 us_region_name=<Provide Region of AMI>' ami_id='<Provide AMI ID>'' temp_snapshot_id=" my_array=( $(aws ec2 draw-images –epitome-ids $ami_id –region $us_region_name –output text –query 'Images[*].BlockDeviceMappings[*].Ebs.SnapshotId') ) my_array_length=${#my_array[@]} echo "Deregistering AMI: "$ami_id aws ec2 deregister-epitome –image-id $ami_id –region $us_region_name repeat "Removing Snapshot" for (( i=0; i<$my_array_length; i++ )) do temp_snapshot_id=${my_array[$i]} repeat "Deleting Snapshot: "$temp_snapshot_id aws ec2 delete-snapshot –snapshot-id $temp_snapshot_id –region $us_region_name done At that place are two types of AWS AMIs: EBS-backed and instance store-backed. In either case, when an instance is launched the root device is either the EBS volume or ephemeral storage, respectively. It is recommended to utilize snapshots at the awarding configuration level change for regular persistent storage backup. This could exist useful for future instance launches if you want or need to create an AMI. As explained above, when an AMI is deregistered, information technology does not delete its associated snapshots automatically, resulting in you lot having to delete them manually or by using the scripts outlined above. N2WS' Cloud Protection Manager(CPM) offers an automatic snapshot service. CPM is an enterprise-class backup and disaster recovery solution for the EC2 compute deject. It is available as a service model that allows you to register multiple AWS accounts. You can configure policies and schedules to take automated snapshots for backup. Yous can configure policies to remove former snapshots, also. CPM provides automated and regular backup with the features below:

Flexible backup policies and schedules
Consistent database backup, such equally SQL Server, Oracle, MySQL, MongoDB and more than
Instance recovery, fifty-fifty with information located across AWS regions, inside seconds
"Pull" and "Push button" based alerts and notifications
Awarding consequent backup

Disclaimer: This script was given as-is. You can use it for whatever purpose, redistribute it or modify it. Nosotros offer no warranty, expressed or implied, then nosotros simply enquire that you sympathise that information technology may not piece of work. Try N2WS Fill-in & Recovery (CPM) for Gratis! Read Too