Container for the parameters to the TerminateInstances operation. Shuts down the specified instances. This operation is idempotent; if you terminate an instance more than once, each call succeeds.
If you specify multiple instances and the request fails (for example, because of a single incorrect instance ID), none of the instances are terminated.
If you terminate multiple instances across multiple Availability Zones, and one or more of the specified instances are enabled for termination protection, the request fails with the following results:
The specified instances that are in the same Availability Zone as the protected instance are not terminated.
The specified instances that are in different Availability Zones, where no other specified instances are protected, are successfully terminated.
For example, say you have the following instances:
Instance A:
us-east-1a; Not protectedInstance B:
us-east-1a; Not protectedInstance C:
us-east-1b; ProtectedInstance D:
us-east-1b; not protected
If you attempt to terminate all of these instances in the same request, the request reports failure with the following results:
Instance A and Instance B are successfully terminated because none of the specified instances in
us-east-1aare enabled for termination protection.Instance C and Instance D fail to terminate because at least one of the specified instances in
us-east-1b(Instance C) is enabled for termination protection.
Terminated instances remain visible after termination (for approximately one hour).
By default, Amazon EC2 deletes all EBS volumes that were attached when the instance launched. Volumes attached after instance launch continue running.
You can stop, start, and terminate EBS-backed instances. You can only terminate instance
store-backed instances. What happens to an instance differs if you stop it or terminate
it. For example, when you stop an instance, the root device and any other devices
attached to the instance persist. When you terminate an instance, any attached EBS
volumes with the DeleteOnTermination block device mapping parameter set to
true are automatically deleted. For more information about the differences
between stopping and terminating instances, see Instance
lifecycle in the Amazon EC2 User Guide.
For more information about troubleshooting, see Troubleshooting terminating your instance in the Amazon EC2 User Guide.
Inheritance Hierarchy
Amazon.Runtime.AmazonWebServiceRequest
Amazon.EC2.AmazonEC2Request
Amazon.EC2.Model.TerminateInstancesRequest
Namespace: Amazon.EC2.Model
Assembly: AWSSDK.EC2.dll
Version: 3.x.y.z
Syntax
public class TerminateInstancesRequest : AmazonEC2Request IAmazonWebServiceRequest
The TerminateInstancesRequest type exposes the following members
Constructors
| Name | Description | |
|---|---|---|
|
TerminateInstancesRequest() |
Empty constructor used to set properties independently even when a simple constructor is available |
|
|
TerminateInstancesRequest(List<String>) |
Instantiates TerminateInstancesRequest with the parameterized properties |
Properties
| Name | Type | Description | |
|---|---|---|---|
|
|
InstanceIds | System.Collections.Generic.List<System.String> |
Gets and sets the property InstanceIds. The IDs of the instances. Constraints: Up to 1000 instance IDs. We recommend breaking up this request into smaller batches. |
Examples
This example terminates the specified EC2 instance.
To terminate an EC2 instance
var client = new AmazonEC2Client();
var response = client.TerminateInstances(new TerminateInstancesRequest
{
InstanceIds = new List<string> {
"i-1234567890abcdef0"
}
});
List<InstanceStateChange> terminatingInstances = response.TerminatingInstances;
Version Information
.NET Core App:
Supported in: 3.1
.NET Standard:
Supported in: 2.0
.NET Framework:
Supported in: 4.5, 4.0, 3.5