Deregister an Amazon EC2 AMI

When you deregister an AMI, Amazon EC2 permanently deletes it. After you deregister an AMI, you can't use it to launch new instances. You might consider deregistering an AMI when you have finished using it.

To protect against accidental or malicious deregistering of an AMI, you can turn on deregistration protection. If you accidentally deregister an EBS-backed AMI, you can use the Recycle Bin to restore it only if you restore it within the allowed time period before it is permanently deleted.

Deregistering an AMI has no effect on any instances that were launched from the AMI. You can continue to use these instances. Deregistering an AMI also has no effect on any snapshots that were created during the AMI creation process. You'll continue to incur usage costs for these instances and storage costs for the snapshots. Therefore, to avoid incurring unnecessary costs, we recommend that you terminate any instances and delete any snapshots that you do not need. For more information, see Avoid costs from unused resources.

Contents

• Considerations
• Deregister an AMI
• Avoid costs from unused resources
• Protect an Amazon EC2 AMI from deregistration

Considerations

• You can't deregister an AMI that is not owned by your account.

• You can't use Amazon EC2 to deregister an AMI that is managed by the AWS Backup service. Instead, use AWS Backup to delete the corresponding recovery points in the backup vault. For more information, see Deleting backups in the AWS Backup Developer Guide.

Deregister an AMI

Use any of the following methods to deregister an EBS-backed AMI or instance store-backed AMI.

Tip

To avoid incurring unnecessary costs, you should delete any resources that you do not need. For example, for EBS-backed AMIs, if you do not need the snapshots associated with the deregistered AMI, you should delete them. For more information, see Avoid costs from unused resources.

Console

To deregister an AMI

1. Open the Amazon EC2 console at https://console.aws.amazon.com/ec2/.

2. In the navigation pane, choose AMIs.

3. From the filter bar, choose Owned by me to list your available AMIs, or choose Disabled images to list your disabled AMIs.

4. Select the AMI to deregister.

5. Choose Actions, Deregister AMI.

6. When you are prompted for confirmation, choose Deregister AMI.

   It might take a few minutes before the console removes the AMI from the list. Choose Refresh to refresh the status.

AWS CLI

To deregister an AMI

Use the deregister-image command and specify the ID of the AMI to deregister.

aws ec2 deregister-image --image-id ami-0123456789example

PowerShell

To deregister an AMI

Use the Unregister-EC2Image cmdlet and specify the ID of the AMI to deregister.

Unregister-EC2Image -ImageId ami-0123456789example

Avoid costs from unused resources

When you deregister an AMI, you don't delete the resources that are associated with the AMI. These resources include the snapshots for EBS-backed AMIs and the files in Amazon S3 for instance store-backed AMIs. When you deregister an AMI, you also don't terminate or stop any instances launched from the AMI.

You will continue to incur costs for storing the snapshots and files, and you will incur costs for any running instances.

To avoid incurring these types of unnecessary costs, we recommend deleting any resources that you don't need.

EBS-backed AMIs

Use any of the following methods to delete the resources associated with your EBS-backed AMI.

Console

To delete resources associated with your EBS-backed AMI

1. Deregister the AMI.

   Note the AMI ID—this can help you find the snapshots to delete in the next step.

2. Delete snapshots that you don't need.

   The ID of the associated AMI is displayed in the Description column on the Snapshots screen.

3. Terminate instances that you don't need.

AWS CLI

To delete resources associated with your EBS-backed AMI

1. Deregister the AMI by using the deregister-image command.

   aws ec2 deregister-image --image-id ami-0123456789example

2. Delete snapshots that you don't need by using the delete-snapshot command.

   aws ec2 delete-snapshot --snapshot-id snap-0123456789example

3. Terminate instances that you don't need by using the terminate-instances command.

   aws ec2 terminate-instances --instance-ids i-0123456789example

PowerShell

To delete resources associated with your EBS-backed AMI

1. Deregister the AMI by using the Unregister-EC2Image cmdlet.

   Unregister-EC2Image -ImageId ami-0123456789example

2. Delete snapshots that you don't need by using the Remove-EC2Snapshot cmdlet.

   Remove-EC2Snapshot -SnapshotId snap-0123456789example

3. Terminate instances that you don't need by using the Remove-EC2Instance cmdlet.

   Remove-EC2Instance -InstanceId i-0123456789example

The following diagram illustrates the flow for you to delete resources associated with an EBS-backed AMI.

Instance store-backed AMI

Use the following method to delete the resources associated with your instance store-backed AMI.

To delete resources associated with your instance store-backed AMI

1. Deregister the AMI by using the deregister-image command.

   aws ec2 deregister-image --image-id ami-0123456789example

2. Delete the bundle in Amazon S3 by using the ec2-delete-bundle (AMI tools) command.

   ec2-delete-bundle -b amzn-s3-demo-bucket/myami -a your_access_key_id -s your_secret_access_key -p image

3. Terminate instances that you don't need by using the terminate-instances command.

   aws ec2 terminate-instances --instance-ids i-0123456789example

4. If you are finished with the Amazon S3 bucket that you uploaded the bundle to, you can delete the bucket. To delete an Amazon S3 bucket, open the Amazon S3 console, select the bucket, choose Actions, and then choose Delete.

The following diagram illustrates the flow for you to delete resources associated with your instance store-backed AMI.