AWS services or capabilities described in AWS Documentation may vary by region/location. Click Getting Started with Amazon AWS to see specific differences applicable to the China (Beijing) Region.
Deregisters the specified AMI. A deregistered AMI can't be used to launch new instances.
If a deregistered EBS-backed AMI matches a Recycle Bin retention rule, it moves to the Recycle Bin for the specified retention period. It can be restored before its retention period expires, after which it is permanently deleted. If the deregistered AMI doesn't match a retention rule, it is permanently deleted immediately. For more information, see Recover deleted Amazon EBS snapshots and EBS-backed AMIs with Recycle Bin in the Amazon EBS User Guide.
When deregistering an EBS-backed AMI, you can optionally delete its associated snapshots at the same time. However, if a snapshot is associated with multiple AMIs, it won't be deleted even if specified for deletion, although the AMI will still be deregistered.
Deregistering an AMI does not delete the following:
Instances already launched from the AMI. You'll continue to incur usage costs for the instances until you terminate them.
For EBS-backed AMIs: Snapshots that are associated with multiple AMIs. You'll continue to incur snapshot storage costs.
For instance store-backed AMIs: The files uploaded to Amazon S3 during AMI creation. You'll continue to incur S3 storage costs.
For more information, see Deregister an Amazon EC2 AMI in the Amazon EC2 User Guide.
For .NET Core this operation is only available in asynchronous form. Please refer to DeregisterImageAsync.
Namespace: Amazon.EC2
Assembly: AWSSDK.EC2.dll
Version: 3.x.y.z
public virtual DeregisterImageResponse DeregisterImage( DeregisterImageRequest request )
Container for the necessary parameters to execute the DeregisterImage service method.
.NET Framework:
Supported in: 4.5 and newer, 3.5