id
stringlengths 14
16
| text
stringlengths 1
2.43k
| source
stringlengths 99
229
|
|---|---|---|
24fdbf2f4809-1 | },
{
"BlockIndex": 1002,
"BlockToken": "AAABATGQIgwr0WwIuqIMjCA/Sy7e/YoQFZsHejzGNvjKauzNgzeI13YHBfQB"
},
{
"BlockIndex": 1007,
"BlockToken": "AAABAZ9CTuQtUvp/dXqRWw4d07eOgTZ3jvn6hiW30W9duM8MiMw6yQayzF2c"
},
{
"BlockIndex": 1012,
"BlockToken": "AAABAQdzxhw0rVV6PNmsfo/YRIxo9JPR85XxPf1BLjg0Hec6pygYr6laE1p0"
},
{
"BlockIndex": 1030,
"BlockToken": "AAABAaYvPax6mv+iGWLdTUjQtFWouQ7Dqz6nSD9L+CbXnvpkswA6iDID523d"
},
{
"BlockIndex": 1031,
"BlockToken": "AAABATgWZC0XcFwUKvTJbUXMiSPg59KVxJGL+BWBClkw6spzCxJVqDVaTskJ"
}, | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-accessing-snapshot.md |
24fdbf2f4809-2 | },
...
],
"ExpiryTime": 1576287332.806,
"VolumeSize": 32212254720,
"BlockSize": 524288
}
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-accessing-snapshot.md |
df0b355e1dc4-0 | The following [list\-changed\-blocks](https://docs.aws.amazon.com/cli/latest/reference/ebs/list-changed-blocks.html) example command returns the block indexes and block tokens of blocks that are different between snapshots `snap-1234567890` and `snap-0987654321`\. The `--starting-block-index` parameter limits the results to block indexes greater than `0`, and the `--max-results` parameter limits the results to the first `500` blocks\.\.
```
aws ebs list-changed-blocks --first-snapshot-id snap-1234567890 --second-snapshot-id snap-0987654321 --starting-block-index 0 --max-results 500
```
The following example response for the previous command shows that block indexes 0, 6000, 6001, 6002, and 6003 are different between the two snapshots\. Additionally, block indexes 6001, 6002, and 6003 exist only in the first snapshot ID specified, and not in the second snapshot ID because there is no second block token listed in the response\.
Use the `get-snapshot-block` command and specify the block index and block token of the block for which you want to get data\. The block tokens are valid until the expiry time listed\.
```
{
"ChangedBlocks": [
{
"BlockIndex": 0, | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-accessing-snapshot.md |
df0b355e1dc4-1 | ```
{
"ChangedBlocks": [
{
"BlockIndex": 0,
"FirstBlockToken": "AAABAVahm9SO60Dyi0ORySzn2ZjGjW/KN3uygGlS0QOYWesbzBbDnX2dGpmC",
"SecondBlockToken": "AAABAf8o0o6UFi1rDbSZGIRaCEdDyBu9TlvtCQxxoKV8qrUPQP7vcM6iWGSr"
},
{
"BlockIndex": 6000,
"FirstBlockToken": "AAABAbYSiZvJ0/R9tz8suI8dSzecLjN4kkazK8inFXVintPkdaVFLfCMQsKe",
"SecondBlockToken": "AAABAZnqTdzFmKRpsaMAsDxviVqEI/3jJzI2crq2eFDCgHmyNf777elD9oVR"
},
{
"BlockIndex": 6001,
"FirstBlockToken": "AAABASBpSJ2UAD3PLxJnCt6zun4/T4sU25Bnb8jB5Q6FRXHFqAIAqE04hJoR"
},
{
"BlockIndex": 6002, | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-accessing-snapshot.md |
df0b355e1dc4-2 | },
{
"BlockIndex": 6002,
"FirstBlockToken": "AAABASqX4/NWjvNceoyMUljcRd0DnwbSwNnes1UkoP62CrQXvn47BY5435aw"
},
{
"BlockIndex": 6003,
"FirstBlockToken": "AAABASmJ0O5JxAOce25rF4P1sdRtyIDsX12tFEDunnePYUKOf4PBROuICb2A"
},
...
],
"ExpiryTime": 1576308931.973,
"VolumeSize": 32212254720,
"BlockSize": 524288,
"NextToken": "AAADARqElNng/sV98CYk/bJDCXeLJmLJHnNSkHvLzVaO0zsPH/QM3Bi3zF//O6Mdi/BbJarBnp8h"
}
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-accessing-snapshot.md |
313882661cc2-0 | The following [get\-snapshot\-block](https://docs.aws.amazon.com/cli/latest/reference/ebs/get-snapshot-block.html) example command returns the data in the block index `6001` with block token `AAABASBpSJ2UAD3PLxJnCt6zun4/T4sU25Bnb8jB5Q6FRXHFqAIAqE04hJoR`, in snapshot `snap-1234567890`\. The binary data is output to the `data` file in the `C:\Temp` directory on a Windows computer\. If you run the command on a Linux or Unix computer, replace the output path with `/tmp/data` to output the data to the `data` file in the `/tmp` directory\.
```
aws ebs get-snapshot-block --snapshot-id snap-1234567890 --block-index 6001 --block-token AAABASBpSJ2UAD3PLxJnCt6zun4/T4sU25Bnb8jB5Q6FRXHFqAIAqE04hJoR C:/Temp/data
```
The following example response for the previous command shows the size of the data returned, the checksum to validate the data, and the algorithm of the checksum\. The binary data is automatically saved to the directory and file you specified in the request command\.
```
{
"DataLength": "524288", | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-accessing-snapshot.md |
313882661cc2-1 | ```
{
"DataLength": "524288",
"Checksum": "cf0Y6/Fn0oFa4VyjQPOa/iD0zhTflPTKzxGv2OKowXc=",
"ChecksumAlgorithm": "SHA256"
}
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-accessing-snapshot.md |
d2c61efaa43c-0 | The following [start\-snapshot](https://docs.aws.amazon.com/cli/latest/reference/ebs/start-snapshot.html) example command starts an `8` GiB snapshot, using snapshot `snap-123EXAMPLE1234567` as the parent snapshot\. The new snapshot will be an incremental snapshot of the parent snapshot\. The snapshot moves to an error state if there are no put or complete requests made for the snapshot within the specified `60` minute timeout period\. The `550e8400-e29b-41d4-a716-446655440000` client token ensures idempotency for the request\. If the client token is omitted, the AWS SDK automatically generates one for you\. For more information about idempotency, see [Idempotency for StartSnapshot API](ebs-direct-api-idempotency.md)\.
```
aws ebs start-snapshot --volume-size 8 --parent-snapshot snap-123EXAMPLE1234567 --timeout 60 --client-token 550e8400-e29b-41d4-a716-446655440000
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-accessing-snapshot.md |
d2c61efaa43c-1 | ```
The following example response for the previous command shows the snapshot ID, AWS account ID, status, volume size in GiB, and size of the blocks in the snapshot\. The snapshot is started in a `pending` state\. Specify the snapshot ID in subsequent `put-snapshot-block` commands to write data to the snapshot, then use the `complete-snapshot` command to complete the snapshot and change its status to `completed`\.
```
{
"SnapshotId": "snap-0aaEXAMPLEe306d62",
"OwnerId": "111122223333",
"Status": "pending",
"VolumeSize": 8,
"BlockSize": 524288
}
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-accessing-snapshot.md |
3a8488c9e4e2-0 | The following [put\-snapshot](https://docs.aws.amazon.com/cli/latest/reference/ebs/put-snapshot.html) example command writes `524288` Bytes of data to block index `1000` on snapshot `snap-0aaEXAMPLEe306d62`\. The Base64 encoded `QOD3gmEQOXATfJx2Aa34W4FU2nZGyXfqtsUuktOw8DM=` checksum was generated using the `SHA256` algorithm\. The data that is transmitted is in the `/tmp/data` file\.
```
aws ebs put-snapshot-block --snapshot-id snap-0aaEXAMPLEe306d62 --block-index 1 --data-length 524288 --block-data /tmp/data --checksum QOD3gmEQOXATfJx2Aa34W4FU2nZGyXfqtsUuktOw8DM= --checksum-algorithm SHA256
```
The following example response for the previous command confirms the data length, checksum, and checksum algorithm for the data received by the service\.
```
{
"DataLength": "524288",
"Checksum": "QOD3gmEQOXATfJx2Aa34W4FU2nZGyXfqtsUuktOw8DM=",
"ChecksumAlgorithm": "SHA256"
}
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-accessing-snapshot.md |
a44491fce9d0-0 | The following [complete\-snapshot](https://docs.aws.amazon.com/cli/latest/reference/ebs/complete-snapshot.html) example command completes snapshot `snap-0aaEXAMPLEe306d62`\. The command specifies that `5` blocks were written to the snapshot\. The `6D3nmwi5f2F0wlh7xX8QprrJBFzDX8aacdOcA3KCM3c=` checksum represents the checksum for the complete set of data written to a snapshot\. For more information about checksums, see [Using checksums](#ebsapis-using-checksums) earlier in this guide\.
```
aws ebs complete-snapshot --snapshot-id snap-0aaEXAMPLEe306d62 --changed-blocks-count 5 --checksum 6D3nmwi5f2F0wlh7xX8QprrJBFzDX8aacdOcA3KCM3c= --checksum-algorithm SHA256 --checksum-aggregation-method LINEAR
```
The following is an example response for the previous command\.
```
{
"Status": "pending"
}
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-accessing-snapshot.md |
6d68104d263c-0 | You can run API requests concurrently\. Assuming PutSnapshotBlock latency is 100ms, then a thread can process 10 requests in one second\. Furthermore, assuming your client application creates multiple threads and connections \(for example, 100 connections\), it can make 1000 \(10 \* 100\) requests per second in total\. This will correspond to a throughput of around 500 MB per second\.
The following list contains few things to look for in your application:
+ Is each thread using a separate connection? If the connections are limited on the application then multiple threads will wait for the connection to be available and you will notice lower throughput\.
+ Is there any wait time in the application between two put requests? This will reduce the effective throughput of a thread\.
+ The bandwidth limit on the instance – If bandwidth on the instance is shared by other applications, it could limit the available throughput for PutSnapshotBlock requests\.
Be sure to take note of other workloads that might be running in the account to avoid bottlenecks\. You should also build retry mechanisms into your EBS direct APIs workflows to handle throttling, timeouts, and service unavailability\.
Review the EBS direct APIs service quotas to determine the maximum API requests that you can run per second\. For more information, see [Amazon Elastic Block Store Endpoints and Quotas](https://docs.aws.amazon.com/general/latest/gr/ebs-service.html#w542aab9d130b7c15) in the *AWS General Reference*\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-accessing-snapshot.md |
7a30e4d098c6-0 | **Can a snapshot be accessed using the EBS direct APIs if it has a pending status?**
No\. The snapshot can be accessed only if it has a completed status\.
**Are the block indexes returned by the EBS direct APIs in numerical order?**
Yes\. The block indexes returned are unique, and in numerical order\.
**Can I submit a request with a MaxResults parameter value of under 100?**
No\. The minimum MaxResult parameter value you can use is 100\. If you submit a request with a MaxResult parameter value of under 100, and there are more than 100 blocks in the snapshot, then the API will return at least 100 results\.
**Can I run API requests concurrently?**
You can run API requests concurrently\. Be sure to take note of other workloads that might be running in the account to avoid bottlenecks\. You should also build retry mechanisms into your EBS direct APIs workflows to handle throttling, timeouts, and service unavailability\. For more information, see [Optimizing performance](#ebsapi-performance)\.
Review the EBS direct APIs service quotas to determine the API requests that you can run per second\. For more information, see [Amazon Elastic Block Store Endpoints and Quotas](https://docs.aws.amazon.com/general/latest/gr/ebs-service.html#w542aab9d130b7c15) in the *AWS General Reference*\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-accessing-snapshot.md |
7a30e4d098c6-1 | **When running the ListChangedBlocks action, is it possible to get an empty response even though there are blocks in the snapshot?**
Yes\. If the changed blocks are scarce in the snapshot, the response may be empty but the API will return a next page token value\. Use the next page token value to continue to the next page of results\. You can confirm that you have reached the last page of results when the API returns a next page token value of null\.
**If the NextToken parameter is specified together with a StartingBlockIndex parameter, which of the two is used?**
The NextToken is used, and the StartingBlockIndex is ignored\.
**How long are the block tokens and next tokens valid?**
Block tokens are valid for seven days, and next tokens are valid for 60 minutes\.
**Are encrypted snapshots supported?**
Yes\. Encrypted snapshots can be accessed using the EBS direct APIs\.
To access an encrypted snapshot, the user must have access to the key used to encrypt the snapshot, and the AWS KMS decrypt action\. See the [Permissions for IAM users](#ebsapi-permissions) section earlier in this guide for the AWS KMS policy to assign to a user\.
**Are public snapshots supported?**
Public snapshots are not supported\.
**Does list snapshot block return all block indexes and block tokens in a snapshot, or only those that have data written to them?** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-accessing-snapshot.md |
7a30e4d098c6-2 | **Does list snapshot block return all block indexes and block tokens in a snapshot, or only those that have data written to them?**
It returns only block indexes and tokens that have data written to them\.
**Can I get a history of the API calls made by the EBS direct APIs on my account for security analysis and operational troubleshooting purposes?**
Yes\. To receive a history of EBS direct APIs API calls made on your account, turn on AWS CloudTrail in the AWS Management Console\. For more information, see [Logging API Calls for the EBS direct APIs with AWS CloudTrail](logging-ebs-apis-using-cloudtrail.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-accessing-snapshot.md |
ef64c2e8c339-0 | Enhanced networking uses single root I/O virtualization \(SR\-IOV\) to provide high\-performance networking capabilities on [supported instance types](#supported_instances)\. SR\-IOV is a method of device virtualization that provides higher I/O performance and lower CPU utilization when compared to traditional virtualized network interfaces\. Enhanced networking provides higher bandwidth, higher packet per second \(PPS\) performance, and consistently lower inter\-instance latencies\. There is no additional charge for using enhanced networking\.
**Topics**
+ [Enhanced networking types](#supported_instances)
+ [Enabling enhanced networking on your instance](#enabling_enhanced_networking)
+ [Enhanced networking: ENA](enhanced-networking-ena.md)
+ [Enhanced networking: Intel 82599 VF](sriov-networking.md)
+ [Troubleshooting ENA](troubleshooting-ena.md) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/enhanced-networking.md |
393d2a3a40d5-0 | Depending on your instance type, enhanced networking can be enabled using one of the following mechanisms:
**Elastic Network Adapter \(ENA\)**
The Elastic Network Adapter \(ENA\) supports network speeds of up to 100 Gbps for supported instance types\.
The [current generation](instance-types.md#current-gen-instances) instances support ENA for enhanced networking, except for M4 instances smaller than `m4.16xlarge`\.
**Intel 82599 Virtual Function \(VF\) interface**
The Intel 82599 Virtual Function interface supports network speeds of up to 10 Gbps for supported instance types\.
The following instance types use the Intel 82599 VF interface for enhanced networking: C3, C4, D2, I2, M4 \(excluding m4\.16xlarge\), and R3\.
For information about the supported network speed for each instance type, see [Amazon EC2 Instance Types](https://aws.amazon.com/ec2/instance-types)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/enhanced-networking.md |
a9bcac8b14ec-0 | If your instance type supports the Elastic Network Adapter for enhanced networking, follow the procedures in [Enabling enhanced networking with the Elastic Network Adapter \(ENA\) on Linux instances](enhanced-networking-ena.md)\.
If your instance type supports the Intel 82599 VF interface for enhanced networking, follow the procedures in [Enabling enhanced networking with the Intel 82599 VF interface on Linux instances](sriov-networking.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/enhanced-networking.md |
69c1b29b4910-0 | An *EC2 Fleet* contains the configuration information to launch a fleet—or group—of instances\. In a single API call, a fleet can launch multiple instance types across multiple Availability Zones, using the On\-Demand Instance, Reserved Instance, and Spot Instance purchasing options together\. Using EC2 Fleet, you can:
+ Define separate On\-Demand and Spot capacity targets and the maximum amount you’re willing to pay per hour
+ Specify the instance types that work best for your applications
+ Specify how Amazon EC2 should distribute your fleet capacity within each purchasing option
You can also set a maximum amount per hour that you’re willing to pay for your fleet, and EC2 Fleet launches instances until it reaches the maximum amount\. When the maximum amount you're willing to pay is reached, the fleet stops launching instances even if it hasn’t met the target capacity\.
The EC2 Fleet attempts to launch the number of instances that are required to meet the target capacity specified in your request\. If you specified a total maximum price per hour, it fulfills the capacity until it reaches the maximum amount that you’re willing to pay\. The fleet can also attempt to maintain its target Spot capacity if your Spot Instances are interrupted\. For more information, see [How Spot Instances work](how-spot-instances-work.md)\.
![\[A sample EC2 fleet\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/ec2-fleet.png) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-fleet.md |
69c1b29b4910-1 | You can specify an unlimited number of instance types per EC2 Fleet\. Those instance types can be provisioned using both On\-Demand and Spot purchasing options\. You can also specify multiple Availability Zones, specify different maximum Spot prices for each instance, and choose additional Spot options for each fleet\. Amazon EC2 uses the specified options to provision capacity when the fleet launches\.
While the fleet is running, if Amazon EC2 reclaims a Spot Instance because of a price increase or instance failure, EC2 Fleet can try to replace the instances with any of the instance types that you specify\. This makes it easier to regain capacity during a spike in Spot pricing\. You can develop a flexible and elastic resourcing strategy for each fleet\. For example, within specific fleets, your primary capacity can be On\-Demand supplemented with less\-expensive Spot capacity if available\.
If you have Reserved Instances and you specify On\-Demand Instances in your fleet, EC2 Fleet uses your Reserved Instances\. For example, if your fleet specifies an On\-Demand Instance as `c4.large`, and you have Reserved Instances for `c4.large`, you receive the Reserved Instance pricing\.
There is no additional charge for using EC2 Fleet\. You pay only for the EC2 instances that the fleet launches for you\.
**Topics**
+ [EC2 Fleet limitations](#EC2-fleet-limitations)
+ [EC2 Fleet limits](#ec2-fleet-limits)
+ [EC2 Fleet configuration strategies](ec2-fleet-configuration-strategies.md)
+ [Managing an EC2 Fleet](manage-ec2-fleet.md) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-fleet.md |
c7b8f37c5832-0 | The following limitations apply to EC2 Fleet:
+ EC2 Fleet is available only through the API or AWS CLI\.
+ An EC2 Fleet request can't span AWS Regions\. You need to create a separate EC2 Fleet for each Region\.
+ An EC2 Fleet request can't span different subnets from the same Availability Zone\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-fleet.md |
94f6c0b5342d-0 | The usual Amazon EC2 limits apply to instances launched by an EC2 Fleet, such as Spot request price limits, instance limits, and volume limits\. In addition, the following limits apply:
+ The number of active EC2 Fleets per AWS Region: 1,000 \* †
+ The number of Spot Instance pools \(unique combination of instance type and subnet\): 300\* ‡
+ The size of the user data in a launch specification: 16 KB †
+ The target capacity per EC2 Fleet: 10,000
+ The target capacity across all EC2 Fleets in a Region: 100,000 \*
+ An EC2 Fleet request can't span Regions\.
+ An EC2 Fleet request can't span different subnets from the same Availability Zone\.
If you need more than the default limits for target capacity, complete the AWS Support Center [Create case](https://console.aws.amazon.com/support/home#/case/create?issueType=service-limit-increase&limitType=service-code-ec2-fleet) form to request a limit increase\. For **Limit type**, choose **EC2 Fleet**, choose a Region, and then choose **Target Fleet Capacity per Fleet \(in units\)** or **Target Fleet Capacity per Region \(in units\)**, or both\.
\* These limits apply to both your EC2 Fleets and your Spot Fleets\.
† These are hard limits\. You cannot request a limit increase for these limits\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-fleet.md |
94f6c0b5342d-1 | † These are hard limits\. You cannot request a limit increase for these limits\.
‡ This limit only applies to fleets of type `request` or `maintain`\. This limit does not apply to `instant` fleets\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-fleet.md |
5fe9571707f5-0 | If you plan to use your T3 Spot Instances immediately and for a short duration, with no idle time for accruing CPU credits, we recommend that you launch your T3 Spot Instances in [`standard`](burstable-performance-instances-standard-mode.md) mode to avoid paying higher costs\.
If you launch your T3 Spot Instances in [`unlimited`](burstable-performance-instances-unlimited-mode.md) mode and burst CPU immediately, you'll spend surplus credits for bursting\. If you use the instance for a short duration, your instance doesn't have time to accrue CPU credits to pay down the surplus credits, and you are charged for the surplus credits when you terminate your instance\.
`Unlimited` mode for T3 Spot Instances is suitable only if the instance runs for long enough to accrue CPU credits for bursting\. Otherwise, paying for surplus credits makes T3 Spot Instances more expensive than M5 or C5 instances\. For more information, see [When to use unlimited mode versus fixed CPU](burstable-performance-instances-unlimited-mode-concepts.md#when-to-use-unlimited-mode)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-fleet.md |
3aeb8f3e07c6-0 | Launch credits are meant to provide a productive initial launch experience for T2 instances by providing sufficient compute resources to configure the instance\. Repeated launches of T2 instances to access new launch credits is not permitted\. If you require sustained CPU, you can earn credits \(by idling over some period\), use [T2 Unlimited](burstable-performance-instances-unlimited-mode.md), or use an instance type with dedicated CPU \(for example, `c4.large`\)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-fleet.md |
96a27b672ca2-0 | You can deregister an AMI when you have finished using it\. After you deregister an AMI, you can't use it to launch new instances\.
When you deregister an AMI, it doesn't affect any instances that you've already launched from the AMI\. You'll continue to incur usage costs for these instances\. Therefore, if you are finished with these instances, you should terminate them\.
The procedure that you'll use to clean up your AMI depends on whether it is backed by Amazon EBS or instance store\. For more information, see [Determining the root device type of your AMI](ComponentsAMIs.md#display-ami-root-device-type)\.
**Note**
An AMI must be owned by your account in order to deregister it\.
**Topics**
+ [Cleaning up your Amazon EBS\-backed AMI](#clean-up-ebs-ami)
+ [Cleaning up your instance store\-backed AMI](#clean-up-s3-ami) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/deregister-ami.md |
c3247568b98f-0 | When you deregister an Amazon EBS\-backed AMI, it doesn't affect the snapshot\(s\) that were created for the volume\(s\) of the instance during the AMI creation process\. You'll continue to incur storage costs for the snapshots\. Therefore, if you are finished with the snapshots, you should delete them\.
The following diagram illustrates the process for cleaning up your Amazon EBS\-backed AMI\.
![\[Process to clean up your Amazon EBS-backed AMI\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/ami_delete_ebs.png)
**To clean up your Amazon EBS\-backed AMI**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the navigation pane, choose **AMIs**\. Select the AMI, and take note of its ID — this can help you find the correct snapshot in the next step\. Choose **Actions**, and then **Deregister**\. When prompted for confirmation, choose **Continue**\.
**Note**
It may take a few minutes before the console removes the AMI from the list\. Choose **Refresh** to refresh the status\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/deregister-ami.md |
c3247568b98f-1 | It may take a few minutes before the console removes the AMI from the list\. Choose **Refresh** to refresh the status\.
1. In the navigation pane, choose **Snapshots**, and select the snapshot \(look for the AMI ID in the **Description** column\)\. Choose **Actions**, and then choose **Delete Snapshot**\. When prompted for confirmation, choose **Yes, Delete**\.
1. \(Optional\) If you are finished with an instance that you launched from the AMI, terminate it\. In the navigation pane, choose **Instances**\. Select the instance, choose **Actions**, then **Instance State**, and then **Terminate**\. When prompted for confirmation, choose **Yes, Terminate**\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/deregister-ami.md |
4bcf73d9cd13-0 | When you deregister an instance store\-backed AMI, it doesn't affect the files that you uploaded to Amazon S3 when you created the AMI\. You'll continue to incur usage costs for these files in Amazon S3\. Therefore, if you are finished with these files, you should delete them\.
The following diagram illustrates the process for cleaning up your instance store\-backed AMI\.
![\[Process to clean up your instance store-backed AMI\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/ami_delete_instance_store.png)
**To clean up your instance store\-backed AMI**
1. Deregister the AMI using the [deregister\-image](https://docs.aws.amazon.com/cli/latest/reference/ec2/deregister-image.html) command as follows\.
```
aws ec2 deregister-image --image-id ami_id
```
1. Delete the bundle in Amazon S3 using the [ec2\-delete\-bundle](ami-tools-commands.md#ami-delete-bundle) \(AMI tools\) command as follows\.
```
ec2-delete-bundle -b myawsbucket/myami -a your_access_key_id -s your_secret_access_key -p image
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/deregister-ami.md |
4bcf73d9cd13-1 | ```
1. \(Optional\) If you are finished with an instance that you launched from the AMI, you can terminate it using the [terminate\-instances](https://docs.aws.amazon.com/cli/latest/reference/ec2/terminate-instances.html) command as follows\.
```
aws ec2 terminate-instances --instance-ids instance_id
```
1. \(Optional\) 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**\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/deregister-ami.md |
5d2a13e7d094-0 | The EC2Rescue for Linux tool can be installed on an Amazon EC2 Linux instance that meets the following prerequisites\.
**Prerequisites**
+ Supported operating systems:
+ Amazon Linux 2
+ Amazon Linux 2016\.09\+
+ SUSE Linux Enterprise Server 12\+
+ RHEL 7\+
+ Ubuntu 16\.04\+
+ Software requirements:
+ Python 2\.7\.9\+ or 3\.2\+
If your system has the required Python version, you can install the standard build\. Otherwise, you can install the bundled build, which includes a minimal copy of Python\.
**To install the standard build**
1. From a working Linux instance, download the [EC2Rescue for Linux](https://s3.amazonaws.com/ec2rescuelinux/ec2rl.tgz) tool:
```
curl -O https://s3.amazonaws.com/ec2rescuelinux/ec2rl.tgz
```
1. \(Optional\) Before proceeding, you can optionally verify the signature of the EC2Rescue for Linux installation file\. For more information, see [\(Optional\) Verify the signature of EC2Rescue for Linux](ec2rl_verify.md)\.
1. Download the sha256 hash file:
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2rl_install.md |
5d2a13e7d094-1 | 1. Download the sha256 hash file:
```
curl -O https://s3.amazonaws.com/ec2rescuelinux/ec2rl.tgz.sha256
```
1. Verify the integrity of the tarball:
```
sha256sum -c ec2rl.tgz.sha256
```
1. Unpack the tarball:
```
tar -xvf ec2rl.tgz
```
1. Verify the installation by listing out the help file:
```
cd ec2rl-<version_number>
./ec2rl help
```
**To install the bundled build**
For a link to the download and a list of limitations, see [EC2Rescue for Linux](https://github.com/awslabs/aws-ec2rescue-linux/blob/master/README.md) on github\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2rl_install.md |
dff6349bd282-0 | Amazon Web Services \(AWS\) automatically provides data that you can use to monitor your Amazon Elastic Block Store \(Amazon EBS\) volumes\.
**Topics**
+ [EBS volume status checks](#monitoring-volume-checks)
+ [EBS volume events](#monitoring-vol-events)
+ [Working with an impaired volume](#work_volumes_impaired)
+ [Working with the Auto\-Enabled IO volume attribute](#volumeIO)
For additional monitoring information, see [Amazon CloudWatch metrics for Amazon EBS](using_cloudwatch_ebs.md) and [Amazon CloudWatch Events for Amazon EBS](ebs-cloud-watch-events.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-volume-status.md |
d20cb72d8176-0 | Volume status checks enable you to better understand, track, and manage potential inconsistencies in the data on an Amazon EBS volume\. They are designed to provide you with the information that you need to determine whether your Amazon EBS volumes are impaired, and to help you control how a potentially inconsistent volume is handled\.
Volume status checks are automated tests that run every 5 minutes and return a pass or fail status\. If all checks pass, the status of the volume is `ok`\. If a check fails, the status of the volume is `impaired`\. If the status is `insufficient-data`, the checks may still be in progress on the volume\. You can view the results of volume status checks to identify any impaired volumes and take any necessary actions\.
When Amazon EBS determines that a volume's data is potentially inconsistent, the default is that it disables I/O to the volume from any attached EC2 instances, which helps to prevent data corruption\. After I/O is disabled, the next volume status check fails, and the volume status is `impaired`\. In addition, you'll see an event that lets you know that I/O is disabled, and that you can resolve the impaired status of the volume by enabling I/O to the volume\. We wait until you enable I/O to give you the opportunity to decide whether to continue to let your instances use the volume, or to run a consistency check using a command, such as fsck, before doing so\.
**Note** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-volume-status.md |
d20cb72d8176-1 | **Note**
Volume status is based on the volume status checks, and does not reflect the volume state\. Therefore, volume status does not indicate volumes in the `error` state \(for example, when a volume is incapable of accepting I/O\.\) For information about volume states, see [Volume state](ebs-describing-volumes.md#volume-state)\.
If the consistency of a particular volume is not a concern, and you'd prefer that the volume be made available immediately if it's impaired, you can override the default behavior by configuring the volume to automatically enable I/O\. If you enable the **Auto\-Enable IO** volume attribute \(`autoEnableIO` in the API\), the volume status check continues to pass\. In addition, you'll see an event that lets you know that the volume was determined to be potentially inconsistent, but that its I/O was automatically enabled\. This enables you to check the volume's consistency or replace it at a later time\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-volume-status.md |
d20cb72d8176-2 | The I/O performance status check compares actual volume performance to the expected performance of a volume and alerts you if the volume is performing below expectations\. This status check is only available for Provisioned IOPS SSD \(`io1` and `io2`\) volumes that are attached to an instance\. It is not valid for General Purpose SSD \(`gp2`\), Throughput Optimized HDD \(`st1`\), Cold HDD \(`sc1`\), or Magnetic \(`standard`\) volumes\. The I/O performance status check is performed once every minute and CloudWatch collects this data every 5 minutes, so it may take up to 5 minutes from the moment you attach an `io1` or `io2` volume to an instance for this check to report the I/O performance status\.
**Important**
While initializing `io1` and `io2` volumes that were restored from snapshots, the performance of the volume may drop below 50 percent of its expected level, which causes the volume to display a `warning` state in the **I/O Performance** status check\. This is expected, and you can ignore the `warning` state on `io1` and `io2` volumes while you are initializing them\. For more information, see [Initializing Amazon EBS volumes](ebs-initialize.md)\.
The following table lists statuses for Amazon EBS volumes\.
| Volume status | I/O enabled status | I/O performance status \(only available for Provisioned IOPS volumes\) |
| --- | --- | --- | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-volume-status.md |
d20cb72d8176-3 | | --- | --- | --- |
| `ok` | Enabled \(I/O Enabled or I/O Auto\-Enabled\) | Normal \(Volume performance is as expected\) |
| `warning` | Enabled \(I/O Enabled or I/O Auto\-Enabled\) | Degraded \(Volume performance is below expectations\) Severely Degraded \(Volume performance is well below expectations\) |
| `impaired` | Enabled \(I/O Enabled or I/O Auto\-Enabled\) Disabled \(Volume is offline and pending recovery, or is waiting for the user to enable I/O\) | Stalled \(Volume performance is severely impacted\) Not Available \(Unable to determine I/O performance because I/O is disabled\) |
| `insufficient-data` | Enabled \(I/O Enabled or I/O Auto\-Enabled\) Insufficient Data | Insufficient Data |
To view and work with status checks, you can use the Amazon EC2 console, the API, or the command line interface\.
**To view status checks in the console**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the navigation pane, choose **Volumes**\. The **Volume Status** column displays the operational status of each volume\.
1. To view the status details of a volume, select the volume and choose **Status Checks**\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-volume-status.md |
d20cb72d8176-4 | 1. To view the status details of a volume, select the volume and choose **Status Checks**\.
![\[Viewing EBS volume status\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/AutoEnableSetting_statustab_gwt.png)
1. If you have a volume with a failed status check \(status is **impaired**\), see [Working with an impaired volume](#work_volumes_impaired)\.
Alternatively, you can choose **Events** in the navigator to view all the events for your instances and volumes\. For more information, see [EBS volume events](#monitoring-vol-events)\.
**To view volume status information with the command line**
You can use one of the following commands to view the status of your Amazon EBS volumes\. For more information about these command line interfaces, see [Accessing Amazon EC2](concepts.md#access-ec2)\.
+ [describe\-volume\-status](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-volume-status.html) \(AWS CLI\)
+ [Get\-EC2VolumeStatus](https://docs.aws.amazon.com/powershell/latest/reference/items/Get-EC2VolumeStatus.html) \(AWS Tools for Windows PowerShell\) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-volume-status.md |
a5c200a6a21a-0 | When Amazon EBS determines that a volume's data is potentially inconsistent, it disables I/O to the volume from any attached EC2 instances by default\. This causes the volume status check to fail, and creates a volume status event that indicates the cause of the failure\.
To automatically enable I/O on a volume with potential data inconsistencies, change the setting of the **Auto\-Enabled IO** volume attribute \(`autoEnableIO` in the API\)\. For more information about changing this attribute, see [Working with an impaired volume](#work_volumes_impaired)\.
Each event includes a start time that indicates the time at which the event occurred, and a duration that indicates how long I/O for the volume was disabled\. The end time is added to the event when I/O for the volume is enabled\.
Volume status events include one of the following descriptions:
Awaiting Action: Enable IO
Volume data is potentially inconsistent\. I/O is disabled for the volume until you explicitly enable it\. The event description changes to IO Enabled after you explicitly enable I/O\.
IO Enabled
I/O operations were explicitly enabled for this volume\.
IO Auto\-Enabled
I/O operations were automatically enabled on this volume after an event occurred\. We recommend that you check for data inconsistencies before continuing to use the data\.
Normal
For `io1` and `io2` volumes only\. Volume performance is as expected\.
Degraded
For `io1` and `io2` volumes only\. Volume performance is below expectations\.
Severely Degraded | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-volume-status.md |
a5c200a6a21a-1 | Degraded
For `io1` and `io2` volumes only\. Volume performance is below expectations\.
Severely Degraded
For `io1` and `io2` volumes only\. Volume performance is well below expectations\.
Stalled
For `io1` and `io2` volumes only\. Volume performance is severely impacted\.
You can view events for your volumes using the Amazon EC2 console, the API, or the command line interface\.
**To view events for your volumes in the console**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the navigation pane, choose **Events**\. All instances and volumes that have events are listed\.
1. You can filter by volume to view only volume status\. You can also filter on specific status types\.
1. Select a volume to view its specific event\.
![\[Viewing volume events\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/ViewVolEvents-gwt.png) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-volume-status.md |
a5c200a6a21a-2 | If you have a volume where I/O is disabled, see [Working with an impaired volume](#work_volumes_impaired)\. If you have a volume where I/O performance is below normal, this might be a temporary condition due to an action you have taken \(for example, creating a snapshot of a volume during peak usage, running the volume on an instance that cannot support the I/O bandwidth required, accessing data on the volume for the first time, etc\.\)\.
**To view events for your volumes with the command line**
You can use one of the following commands to view event information for your Amazon EBS volumes\. For more information about these command line interfaces, see [Accessing Amazon EC2](concepts.md#access-ec2)\.
+ [describe\-volume\-status](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-volume-status.html) \(AWS CLI\)
+ [Get\-EC2VolumeStatus](https://docs.aws.amazon.com/powershell/latest/reference/items/Get-EC2VolumeStatus.html) \(AWS Tools for Windows PowerShell\) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-volume-status.md |
9b0bb5b27ca9-0 | Use the following options if a volume is impaired because the volume's data is potentially inconsistent\.
**Topics**
+ [Option 1: Perform a consistency check on the volume attached to its instance](#work_volumes_impaired_option1)
+ [Option 2: Perform a consistency check on the volume using another instance](#work_volumes_impaired_option2)
+ [Option 3: Delete the volume if you no longer need it](#work_volumes_impaired_option3) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-volume-status.md |
7879288028b4-0 | The simplest option is to enable I/O and then perform a data consistency check on the volume while the volume is still attached to its Amazon EC2 instance\.
**To perform a consistency check on an attached volume**
1. Stop any applications from using the volume\.
1. Enable I/O on the volume\.
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the navigation pane, choose **Volumes**\.
1. Select the volume on which to enable I/O operations\.
1. In the details pane, choose **Enable Volume IO**, and then choose **Yes, Enable**\.
![\[Enable IO\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/EnableIO_volumepage_gwt.png)
1. Check the data on the volume\.
1. Run the fsck command\.
1. \(Optional\) Review any available application or system logs for relevant error messages\.
1. If the volume has been impaired for more than 20 minutes, you can contact the AWS Support Center\. Choose **Troubleshoot**, and then in the **Troubleshoot Status Checks** dialog box, choose **Contact Support** to submit a support case\.
**To enable I/O for a volume with the command line** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-volume-status.md |
7879288028b4-1 | **To enable I/O for a volume with the command line**
You can use one of the following commands to view event information for your Amazon EBS volumes\. For more information about these command line interfaces, see [Accessing Amazon EC2](concepts.md#access-ec2)\.
+ [enable\-volume\-io](https://docs.aws.amazon.com/cli/latest/reference/ec2/enable-volume-io.html) \(AWS CLI\)
+ [Enable\-EC2VolumeIO](https://docs.aws.amazon.com/powershell/latest/reference/items/Enable-EC2VolumeIO.html) \(AWS Tools for Windows PowerShell\) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-volume-status.md |
be24e347f9a0-0 | Use the following procedure to check the volume outside your production environment\.
**Important**
This procedure may cause the loss of write I/Os that were suspended when volume I/O was disabled\.
**To perform a consistency check on a volume in isolation**
1. Stop any applications from using the volume\.
1. Detach the volume from the instance\.
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the navigation pane, choose **Volumes**\.
1. Select the volume to detach\.
1. Choose **Actions**, **Force Detach Volume**\. You'll be prompted for confirmation\.
1. Enable I/O on the volume\.
1. In the navigation pane, choose **Volumes**\.
1. Select the volume that you detached in the previous step\.
1. In the details pane, choose **Enable Volume IO**, and then choose **Yes, Enable**\.
![\[Enable IO\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/EnableIO_volumepage_gwt.png) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-volume-status.md |
be24e347f9a0-1 | 1. Attach the volume to another instance\. For more information, see [Launch your instance](LaunchingAndUsingInstances.md) and [Attaching an Amazon EBS volume to an instance](ebs-attaching-volume.md)\.
1. Check the data on the volume\.
1. Run the fsck command\.
1. \(Optional\) Review any available application or system logs for relevant error messages\.
1. If the volume has been impaired for more than 20 minutes, you can contact the AWS Support Center\. Choose **Troubleshoot**, and then in the troubleshooting dialog box, choose **Contact Support** to submit a support case\.
**To enable I/O for a volume with the command line**
You can use one of the following commands to view event information for your Amazon EBS volumes\. For more information about these command line interfaces, see [Accessing Amazon EC2](concepts.md#access-ec2)\.
+ [enable\-volume\-io](https://docs.aws.amazon.com/cli/latest/reference/ec2/enable-volume-io.html) \(AWS CLI\)
+ [Enable\-EC2VolumeIO](https://docs.aws.amazon.com/powershell/latest/reference/items/Enable-EC2VolumeIO.html) \(AWS Tools for Windows PowerShell\) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-volume-status.md |
233a1fd10adc-0 | If you want to remove the volume from your environment, simply delete it\. For information about deleting a volume, see [Deleting an Amazon EBS volume](ebs-deleting-volume.md)\.
If you have a recent snapshot that backs up the data on the volume, you can create a new volume from the snapshot\. For more information, see [Creating a volume from a snapshot](ebs-creating-volume.md#ebs-create-volume-from-snapshot)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-volume-status.md |
322787e82e52-0 | When Amazon EBS determines that a volume's data is potentially inconsistent, it disables I/O to the volume from any attached EC2 instances by default\. This causes the volume status check to fail, and creates a volume status event that indicates the cause of the failure\. If the consistency of a particular volume is not a concern, and you prefer that the volume be made available immediately if it's **impaired**, you can override the default behavior by configuring the volume to automatically enable I/O\. If you enable the **Auto\-Enabled IO** volume attribute \(`autoEnableIO` in the API\), I/O between the volume and the instance is automatically re\-enabled and the volume's status check will pass\. In addition, you'll see an event that lets you know that the volume was in a potentially inconsistent state, but that its I/O was automatically enabled\. When this event occurs, you should check the volume's consistency and replace it if necessary\. For more information, see [EBS volume events](#monitoring-vol-events)\.
This procedure explains how to view and modify the **Auto\-Enabled IO** attribute of a volume\.
**To view the Auto\-Enabled IO attribute of a volume in the console**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the navigation pane, choose **Volumes**\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-volume-status.md |
322787e82e52-1 | 1. In the navigation pane, choose **Volumes**\.
1. Select the volume and choose **Status Checks**\. **Auto\-Enabled IO** displays the current setting \(**Enabled** or **Disabled**\) for your volume\.
![\[View Auto-Enable IO\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/AutoEnableSetting_statustab_gwt.png)
**To modify the Auto\-Enabled IO attribute of a volume in the console**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the navigation pane, choose **Volumes**\.
1. Select the volume and choose **Actions**, **Change Auto\-Enable IO Setting**\. Alternatively, choose the **Status Checks** tab, and for **Auto\-Enabled IO**, choose **Edit**\.
![\[Change Auto-Enable IO setting\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/ChangeAutoEnable-gwt.png)
1. Select the **Auto\-Enable Volume IO** check box to automatically enable I/O for an impaired volume\. To disable the feature, clear the check box\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-volume-status.md |
322787e82e52-2 | ![\[Modify Auto-Enable IO setting\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/ModifyAutoIO-gwt.png)
1. Choose **Save**\.
**To view or modify the autoEnableIO attribute of a volume with the command line**
You can use one of the following commands to view the `autoEnableIO` attribute of your Amazon EBS volumes\. For more information about these command line interfaces, see [Accessing Amazon EC2](concepts.md#access-ec2)\.
+ [describe\-volume\-attribute](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-volume-attribute.html) \(AWS CLI\)
+ [Get\-EC2VolumeAttribute](https://docs.aws.amazon.com/powershell/latest/reference/items/Get-EC2VolumeAttribute.html) \(AWS Tools for Windows PowerShell\)
To modify the `autoEnableIO` attribute of a volume, you can use one of the commands below\.
+ [modify\-volume\-attribute](https://docs.aws.amazon.com/cli/latest/reference/ec2/modify-volume-attribute.html) \(AWS CLI\) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-volume-status.md |
322787e82e52-3 | + [Edit\-EC2VolumeAttribute](https://docs.aws.amazon.com/powershell/latest/reference/items/Edit-EC2VolumeAttribute.html) \(AWS Tools for Windows PowerShell\) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-volume-status.md |
bf9904cc43ed-0 | To use a Dedicated Host, you first allocate hosts for use in your account\. You then launch instances onto the hosts by specifying *host* tenancy for the instance\. You must select a specific host for the instance to launch on to, or you can allow it to launch on to any host that has auto\-placement enabled and matches its instance type\. When an instance is stopped and restarted, the *Host affinity* setting determines whether it's restarted on the same, or a different, host\.
If you no longer need an On\-Demand host, you can stop the instances running on the host, direct them to launch on a different host, and then *release* the host\.
Dedicated Hosts are also integrated with AWS License Manager\. With License Manager, you can create a host resource group, which is a collection of Dedicated Hosts that are managed as a single entity\. When creating a host resource group, you specify the host management preferences, such as auto\-allocate and auto\-release, for the Dedicated Hosts\. This allows you to launch instances onto Dedicated Hosts without manually allocating and managing those hosts\. For more information, see [ Host Resource Groups](https://docs.aws.amazon.com/license-manager/latest/userguide/host-resource-groups.html) in the *AWS License Manager User Guide*\.
**Topics**
+ [Allocating Dedicated Hosts](#dedicated-hosts-allocating)
+ [Launching instances onto a Dedicated Host](#launching-dedicated-hosts-instances)
+ [Launching instances into a host resource group](#launching-hrg-instances) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/how-dedicated-hosts-work.md |
bf9904cc43ed-1 | + [Launching instances into a host resource group](#launching-hrg-instances)
+ [Understanding auto\-placement and affinity](#dedicated-hosts-understanding)
+ [Modifying Dedicated Host auto\-placement](#modify-host-auto-placement)
+ [Modifying the supported instance types](#modify-host-support)
+ [Modifying instance tenancy and affinity](#moving-instances-dedicated-hosts)
+ [Viewing Dedicated Hosts](#dedicated-hosts-managing)
+ [Tagging Dedicated Hosts](#dedicated-hosts-tagging)
+ [Monitoring Dedicated Hosts](#dedicated-hosts-monitoring)
+ [Releasing Dedicated Hosts](#dedicated-hosts-releasing)
+ [Purchasing Dedicated Host Reservations](#purchasing-dedicated-host-reservations)
+ [Viewing Dedicated Host reservations](#viewing-host-reservations)
+ [Tagging Dedicated Host Reservations](#tagging-host-reservations) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/how-dedicated-hosts-work.md |
7705ca8b0f81-0 | To begin using Dedicated Hosts, you must allocate Dedicated Hosts in your account using the Amazon EC2 console or the command line tools\. After you allocate the Dedicated Host, the Dedicated Host capacity is made available in your account immediately and you can start launching instances onto the Dedicated Host\.
Support for multiple instance types on the same Dedicated Host is available for the following instance families: `c5`, `m5`, `r5`, `c5n`, `r5n`, and `m5n`\. Other instance families support only a single instance type on the same Dedicated Host\.
You can allocate a Dedicated Host using the following methods\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/how-dedicated-hosts-work.md |
a39c20900b07-0 | **To allocate a Dedicated Host**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the navigation pane, choose **Dedicated Hosts** and then choose **Allocate Dedicated Host**\.
1. For **Instance family**, choose the instance family for the Dedicated Host\.
1. Specify whether the Dedicated Host supports multiple instance types within the selected instance family, or a specific instance type only\. Do one of the following\.
+ To configure the Dedicated Host to support multiple instance types in the selected instance family, for **Support multiple instance types**, choose **Enable**\. Enabling this allows you to launch different instance types from the same instance family onto the Dedicated Host\. For example, if you choose the `m5` instance family and choose this option, you can launch `m5.xlarge` and `m5.4xlarge` instances onto the Dedicated Host\.
+ To configure the Dedicated Host to support a single instance type within the selected instance family, clear **Support multiple instance types**, and then for **Instance type**, choose the instance type to support\. This allows you to launch a single instance type on the Dedicated Host\. For example, if you choose this option and specify `m5.4xlarge` as the supported instance type, you can launch only `m5.4xlarge` instances onto the Dedicated Host\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/how-dedicated-hosts-work.md |
a39c20900b07-1 | 1. For **Availability Zone**, choose the Availability Zone in which to allocate the Dedicated Host\.
1. To allow the Dedicated Host to accept untargeted instance launches that match its instance type, for **Instance auto\-placement**, choose **Enable**\. For more information about auto\-placement, see [Understanding auto\-placement and affinity](#dedicated-hosts-understanding)\.
1. To enable host recovery for the Dedicated Host, for **Host recovery**, choose **Enable**\. For more information, see [Host recovery](dedicated-hosts-recovery.md)\.
1. For **Quantity**, enter the number of Dedicated Hosts to allocate\.
1. \(Optional\) Choose **Add Tag** and enter a tag key and a tag value\.
1. Choose **Allocate**\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/how-dedicated-hosts-work.md |
0f5533cbd15d-0 | **To allocate a Dedicated Host**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the navigation pane, choose **Dedicated Hosts**, **Allocate Dedicated Host**\.
1. For **Instance family**, choose the instance family for the Dedicated Host\.
1. Specify whether the Dedicated Host supports multiple instance types within the selected instance family, or a specific instance type only\. Do one of the following\.
+ To configure the Dedicated Host to support multiple instance types in the selected instance family, select **Support multiple instance types**\. Enabling this allows you to launch different instance types from the same instance family onto the Dedicated Host\. For example, if you choose the `m5` instance family and choose this option, you can launch `m5.xlarge` and `m5.4xlarge` instances onto the Dedicated Host\. The instance family must be powered by the Nitro System\.
+ To configure the Dedicated Host to support a single instance type within the selected instance family, clear **Support multiple instance types**, and then for **Instance type**, choose the instance type to support\. This allows you to launch a single instance type on the Dedicated Host\. For example, if you choose this option and specify `m5.4xlarge` as the supported instance type, you can launch only `m5.4xlarge` instances onto the Dedicated Host\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/how-dedicated-hosts-work.md |
0f5533cbd15d-1 | 1. For **Availability Zone**, choose the Availability Zone in which to allocate the Dedicated Host\.
1. To allow the Dedicated Host to accept untargeted instance launches that match its instance type, for **Instance auto\-placement**, choose **Enable**\. For more information about auto\-placement, see [Understanding auto\-placement and affinity](#dedicated-hosts-understanding)\.
1. To enable host recovery for the Dedicated Host, for **Host recovery** choose **Enable**\. For more information, see [Host recovery](dedicated-hosts-recovery.md)\.
1. For **Quantity**, enter the number of Dedicated Hosts to allocate\.
1. \(Optional\) Choose **Add Tag** and enter a tag key and a tag value\.
1. Choose **Allocate host**\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/how-dedicated-hosts-work.md |
4013c17fafef-0 | **To allocate a Dedicated Host**
Use the [allocate\-hosts](https://docs.aws.amazon.com/cli/latest/reference/ec2/allocate-hosts.html) AWS CLI command\. The following command allocates a Dedicated Host that supports multiple instance types from the `m5` instance family in `us-east-1a` Availability Zone\. The host also has host recovery enabled and it has auto\-placement disabled\.
```
aws ec2 allocate-hosts --instance-family "m5" --availability-zone "us-east-1a" --auto-placement "off" --host-recovery "on" --quantity 1
```
The following command allocates a Dedicated Host that supports *untargeted* `m4.large` instance launches in the `eu-west-1a` Availability Zone, enables host recovery, and applies a tag with a key of `purpose` and a value of `production`\.
```
aws ec2 allocate-hosts --instance-type "m4.large" --availability-zone "eu-west-1a" --auto-placement "on" --host-recovery "on" --quantity 1 --tag-specifications 'ResourceType=dedicated-host,Tags=[{Key=purpose,Value=production}]'
```
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/how-dedicated-hosts-work.md |
765f89fae4f5-0 | **To allocate a Dedicated Host**
Use the [New\-EC2Host](https://docs.aws.amazon.com/powershell/latest/reference/items/New-EC2Host.html) AWS Tools for Windows PowerShell command\. The following command allocates a Dedicated Host that supports multiple instance types from the `m5` instance family in `us-east-1a` Availability Zone\. The host also has host recovery enabled and it has auto\-placement disabled\.
```
PS C:\> New-EC2Host -InstanceFamily m5 -AvailabilityZone us-east-1a -AutoPlacement Off -HostRecovery On -Quantity 1
```
The following commands allocate a Dedicated Host that supports *untargeted* `m4.large` instance launches in the `eu-west-1a` Availability Zone, enable host recovery, and apply a tag with a key of `purpose` and a value of `production`\.
The `TagSpecification` parameter used to tag a Dedicated Host on creation requires an object that specifies the type of resource to be tagged, the tag key, and the tag value\. The following commands create the required object\.
```
PS C:\> $tag = @{ Key="purpose"; Value="production" }
PS C:\> $tagspec = new-object Amazon.EC2.Model.TagSpecification
PS C:\> $tagspec.ResourceType = "dedicated-host" | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/how-dedicated-hosts-work.md |
765f89fae4f5-1 | PS C:\> $tagspec.ResourceType = "dedicated-host"
PS C:\> $tagspec.Tags.Add($tag)
```
The following command allocates the Dedicated Host and applies the tag specified in the `$tagspec` object\.
```
PS C:\> New-EC2Host -InstanceType m4.large -AvailabilityZone eu-west-1a -AutoPlacement On -HostRecovery On -Quantity 1 -TagSpecification $tagspec
```
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/how-dedicated-hosts-work.md |
0f8cf7372add-0 | After you have allocated a Dedicated Host, you can launch instances onto it\. You can't launch instances with `host` tenancy if you do not have active Dedicated Hosts with enough available capacity for the instance type that you are launching\.
**Note**
The instances launched onto Dedicated Hosts can only be launched in a VPC\. For more information, see [Introduction to VPC](https://docs.aws.amazon.com/vpc/latest/userguide/VPC_Introduction.html)\.
Before you launch your instances, take note of the limitations\. For more information, see [Dedicated Hosts restrictions](dedicated-hosts-overview.md#dedicated-hosts-limitations)\.
You can launch an instance onto a Dedicated Host using the following methods\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/how-dedicated-hosts-work.md |
0a8cbafb5fec-0 | **To launch an instance onto a specific Dedicated Host from the Dedicated Hosts page**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. Choose **Dedicated Hosts** in the navigation pane\.
1. On the **Dedicated Hosts** page, select a host and choose **Actions**, **Launch Instance\(s\) onto Host**\.
1. Select an AMI from the list\. SQL Server, SUSE, and RHEL AMIs provided by Amazon EC2 can't be used with Dedicated Hosts\.
1. On the **Choose an Instance Type** page, select the instance type to launch and then choose **Next: Configure Instance Details**\.
If the Dedicated Host supports a single instance type only, the supported instance type is selected by default and can't be changed\.
If the Dedicated Host supports multiple instance types, you must select an instance type within the supported instance family based on the available instance capacity of the Dedicated Host\. We recommend that you launch the larger instance sizes first, and then fill the remaining instance capacity with the smaller instance sizes as needed\.
1. On the **Configure Instance Details** page, configure the instance settings to suit your needs, and then for **Affinity**, choose one of the following options:
+ **Off**—The instance launches onto the specified host, but it is not guaranteed to restart on the same Dedicated Host if stopped\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/how-dedicated-hosts-work.md |
0a8cbafb5fec-1 | + **Off**—The instance launches onto the specified host, but it is not guaranteed to restart on the same Dedicated Host if stopped\.
+ **Host**—If stopped, the instance always restarts on this specific host\.
For more information about Affinity, see [Understanding auto\-placement and affinity](#dedicated-hosts-understanding)\.
The **Tenancy** and **Host** options are pre\-configured based on the host that you selected\.
1. Choose **Review and Launch**\.
1. On the **Review Instance Launch** page, choose **Launch**\.
1. When prompted, select an existing key pair or create a new one, and then choose **Launch Instances**\.
**To launch an instance onto a Dedicated Host using the Launch Instance wizard**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the navigation pane, choose **Instances**, **Launch Instance**\.
1. Select an AMI from the list\. SQL Server, SUSE, and RHEL AMIs provided by Amazon EC2 can't be used with Dedicated Hosts\.
1. Select the type of instance to launch and choose **Next: Configure Instance Details**\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/how-dedicated-hosts-work.md |
0a8cbafb5fec-2 | 1. Select the type of instance to launch and choose **Next: Configure Instance Details**\.
1. On the **Configure Instance Details** page, configure the instance settings to suit your needs, and then configure the following settings, which are specific to a Dedicated Host:
+ Tenancy—Choose **Dedicated Host \- Launch this instance on a Dedicated Host**\.
+ Host—Choose either **Use auto\-placement** to launch the instance on any Dedicated Host that has auto\-placement enabled, or select a specific Dedicated Host in the list\. The list displays only Dedicated Hosts that support the selected instance type\.
+ Affinity—Choose one of the following options:
+ **Off**—The instance launches onto the specified host, but it is not guaranteed to restart on it if stopped\.
+ **Host**—If stopped, the instance always restarts on the specified host\.
For more information, see [Understanding auto\-placement and affinity](#dedicated-hosts-understanding)\.
If you are unable to see these settings, check that you have selected a VPC in the **Network** menu\.
1. Choose **Review and Launch**\.
1. On the **Review Instance Launch** page, choose **Launch**\.
1. When prompted, select an existing key pair or create a new one, and then choose **Launch Instances**\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/how-dedicated-hosts-work.md |
f627696863b3-0 | **To launch an instance onto a Dedicated Host**
Use the [run\-instances](https://docs.aws.amazon.com/cli/latest/reference/ec2/run-instances.html) AWS CLI command and specify the instance affinity, tenancy, and host in the `Placement` request parameter\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/how-dedicated-hosts-work.md |
48e98f0035b4-0 | **To launch an instance onto a Dedicated Host**
Use the [New\-EC2Instance](https://docs.aws.amazon.com/powershell/latest/reference/items/New-EC2Instance.html) AWS Tools for Windows PowerShell command and specify the instance affinity, tenancy, and host in the `Placement` request parameter\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/how-dedicated-hosts-work.md |
7086e88cc6fe-0 | When you launch an instance into a host resource group that has a Dedicated Host with available instance capacity, Amazon EC2 launches the instance onto that host\. If the host resource group does not have a host with available instance capacity, Amazon EC2 automatically allocates a new host in the host resource group, and then launches the instance onto that host\. For more information, see [ Host Resource Groups](https://docs.aws.amazon.com/license-manager/latest/userguide/host-resource-groups.html) in the *AWS License Manager User Guide*\.
**Requirements and limits**
+ You must associate a core\- or socket\-based license configuration with the AMI\.
+ You can't use SQL Server, SUSE, or RHEL AMIs provided by Amazon EC2 with Dedicated Hosts\.
+ You can't target a specific host by choosing a host ID, and you can't enable instance affinity when launching an instance into a host resource group\.
You can launch an instance into a host resource group using the following methods\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/how-dedicated-hosts-work.md |
9244a023d45e-0 | **To launch an instance into a host resource group**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the navigation pane, choose **Instances**, **Launch Instance**\.
1. Select an AMI\.
1. Select the type of instance to launch and choose **Next: Configure Instance Details**\.
1. On the **Configure Instance Details** page, configure the instance settings to suit your needs, and then do the following:
1. For **Tenancy**, choose **Dedicated Host**\.
1. For **Host resource group**, choose **Launch instance into a host resource group**\.
1. For **Host resource group name**, choose the host resource group in which to launch the instance\.
1. Choose **Review and Launch**\.
1. On the **Review Instance Launch** page, choose **Launch**\.
1. When prompted, select an existing key pair or create a new one, and then choose **Launch Instances**\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/how-dedicated-hosts-work.md |
4cb5d7ab5b4c-0 | **To launch an instance into a host resource group**
Use the [run\-instances](https://docs.aws.amazon.com/cli/latest/reference/ec2/run-instances.html) AWS CLI command, and in the `Placement` request parameter, omit the Tenancy option and specify the host resource group ARN\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/how-dedicated-hosts-work.md |
71d4d87027b3-0 | **To launch an instance into a host resource group**
Use the [New\-EC2Instance](https://docs.aws.amazon.com/powershell/latest/reference/items/New-EC2Instance.html) AWS Tools for Windows PowerShell command, and in the `Placement` request parameter, omit the Tenancy option and specify the host resource group ARN\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/how-dedicated-hosts-work.md |
26efa1316e41-0 | Placement control for Dedicated Hosts happens on both the instance level and host level\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/how-dedicated-hosts-work.md |
dc485324fdae-0 | Auto\-placement is configured at the host level\. It allows you to manage whether instances that you launch are launched onto a specific host, or onto any available host that has matching configurations\.
When the auto\-placement of a Dedicated Host is *disabled*, it only accepts *Host* tenancy instance launches that specify its unique host ID\. This is the default setting for new Dedicated Hosts\.
When the auto\-placement of a Dedicated Host is *enabled*, it accepts any untargeted instance launches that match its instance type configuration\.
When launching an instance, you need to configure its tenancy\. Launching an instance onto a Dedicated Host without providing a specific `HostId` enables it to launch on any Dedicated Host that has auto\-placement *enabled* and that matches its instance type\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/how-dedicated-hosts-work.md |
1a9e5f4c66cf-0 | Host affinity is configured at the instance level\. It establishes a launch relationship between an instance and a Dedicated Host\.
When affinity is set to `Host`, an instance launched onto a specific host always restarts on the same host if stopped\. This applies to both targeted and untargeted launches\.
When affinity is set to `Off`, and you stop and restart the instance, it can be restarted on any available host\. However, it tries to launch back onto the last Dedicated Host on which it ran \(on a best\-effort basis\)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/how-dedicated-hosts-work.md |
e0403a96d642-0 | You can modify the auto\-placement settings of a Dedicated Host after you have allocated it to your AWS account, using one of the following methods\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/how-dedicated-hosts-work.md |
74f373a446a8-0 | **To modify the auto\-placement of a Dedicated Host**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the navigation pane, choose **Dedicated Hosts**\.
1. Select a host and choose **Actions**, **Modify host**\.
1. For **Instance auto\-placement**, choose **Enable** to enable auto\-placement, or clear **Enable** to disable auto\-placement\. For more information, see [Understanding auto\-placement and affinity](#dedicated-hosts-understanding)\.
1. Choose **Save**\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/how-dedicated-hosts-work.md |
aac7618648f9-0 | **To modify the auto\-placement of a Dedicated Host**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. Choose **Dedicated Hosts** in the navigation pane\.
1. On the **Dedicated Hosts** page, select a host and choose **Actions**, **Modify Auto\-Placement**\.
1. On the Modify Auto\-placement window, for **Allow instance auto\-placement**, choose **Yes** to enable auto\-placement, or choose **No** to disable auto\-placement\. For more information, see [Understanding auto\-placement and affinity](#dedicated-hosts-understanding)\.
1. Choose **Save**\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/how-dedicated-hosts-work.md |
111eae3c15f6-0 | **To modify the auto\-placement of a Dedicated Host**
Use the [modify\-hosts](https://docs.aws.amazon.com/cli/latest/reference/ec2/modify-hosts.html) AWS CLI command\. The following example enables auto\-placement for the specified Dedicated Host\.
```
aws ec2 modify-hosts --auto-placement on --host-ids h-012a3456b7890cdef
```
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/how-dedicated-hosts-work.md |
baeead443687-0 | **To modify the auto\-placement of a Dedicated Host**
Use the [Edit\-EC2Host](https://docs.aws.amazon.com/powershell/latest/reference/items/Edit-EC2Host.html) AWS Tools for Windows PowerShell command\. The following example enables auto\-placement for the specified Dedicated Host\.
```
PS C:\> Edit-EC2Host --AutoPlacement 1 --HostId h-012a3456b7890cdef
```
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/how-dedicated-hosts-work.md |
3110ec72de3f-0 | Support for multiple instance types on the same Dedicated Host is available for the following instance families: `c5`, `m5`, `r5`, `c5n`, `r5n`, and `m5n`\. Other instance families support only a single instance type on the same Dedicated Host\.
You can allocate a Dedicated Host using the following methods\.
You can modify a Dedicated Host to change the instance types that it supports\. If it currently supports a single instance type, you can modify it to support multiple instance types within that instance family\. Similarly, if it currently supports multiple instance types, you can modify it to support a specific instance type only\.
To modify a Dedicated Host to support multiple instance types, you must first stop all running instances on the host\. The modification takes approximately 10 minutes to complete\. The Dedicated Host transitions to the `pending` state while the modification is in progress\. You can't start stopped instances or launch new instances on the Dedicated Host while it is in the `pending` state\.
To modify a Dedicated Host that supports multiple instance types to support only a single instance type, the host must either have no running instances, or the running instances must be of the instance type that you want the host to support\. For example, to modify a host that supports multiple instance types in the `m5` instance family to support only `m5.large` instances, the Dedicated Host must either have no running instances, or it must have only `m5.large` instances running on it\.
You can modify the supported instance types using one of the following methods\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/how-dedicated-hosts-work.md |
09e74247f9cc-0 | **To modify the supported instance types for a Dedicated Host**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the Navigation pane, choose **Dedicated Host**\.
1. Select the Dedicated Host to modify and choose **Actions**, **Modify host**\.
1. Do one of the following, depending on the current configuration of the Dedicated Host:
+ If the Dedicated Host currently supports a specific instance type, **Support multiple instance types** is not enabled, and **Instance type** lists the supported instance type\. To modify the host to support multiple types in the current instance family, for **Support multiple instance types**, choose **Enable**\.
You must first stop all instances running on the host before modifying it to support multiple instance types\.
+ If the Dedicated Host currently supports multiple instance types in an instance family, **Enabled** is selected for **Support multiple instance types**\. To modify the host to support a specific instance type, for **Support multiple instance types**, clear **Enable**, and then for **Instance type**, select the specific instance type to support\.
You can't change the instance family supported by the Dedicated Host\.
1. Choose **Save**\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/how-dedicated-hosts-work.md |
bc176dbc0ed3-0 | **To modify the supported instance types for a Dedicated Host**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the Navigation pane, choose **Dedicated Host**\.
1. Select the Dedicated Host to modify and choose **Actions**, **Modify Supported Instance Types**\.
1. Do one of the following, depending on the current configuration of the Dedicated Host:
+ If the Dedicated Host currently supports a specific instance type, **No** is selected for **Support multiple instance types**\. To modify the host to support multiple types in the current instance family, for **Support multiple instance types**, select **Yes**\.
You must first stop all instances running on the host before modifying it to support multiple instance types\.
+ If the Dedicated Host currently supports multiple instance types in an instance family, **Yes** is selected for **Support multiple instance types**, and **Instance family** displays the supported instance family\. To modify the host to support a specific instance type, for **Support multiple instance types**, select **No**, and then for **Instance type**, select the specific instance type to support\.
You can't change the instance family supported by the Dedicated Host\.
1. Choose **Save**\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/how-dedicated-hosts-work.md |
61610d4e9ec3-0 | **To modify the supported instance types for a Dedicated Host**
Use the [modify\-hosts](https://docs.aws.amazon.com/cli/latest/reference/ec2/modify-hosts.html) AWS CLI command\.
The following command modifies a Dedicated Host to support multiple instance types within the `m5` instance family\.
```
aws ec2 modify-hosts --instance-family m5 --host-ids h-012a3456b7890cdef
```
The following command modifies a Dedicated Host to support `m5.xlarge` instances only\.
```
aws ec2 modify-hosts --instance-type m5.xlarge --instance-family --host-ids h-012a3456b7890cdef
```
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/how-dedicated-hosts-work.md |
a5b7796881b4-0 | **To modify the supported instance types for a Dedicated Host**
Use the [Edit\-EC2Host](https://docs.aws.amazon.com/powershell/latest/reference/items/Edit-EC2Host.html) AWS Tools for Windows PowerShell command\.
The following command modifies a Dedicated Host to support multiple instance types within the `m5` instance family\.
```
PS C:\> Edit-EC2Host --InstanceFamily m5 --HostId h-012a3456b7890cdef
```
The following command modifies a Dedicated Host to support `m5.xlarge` instances only\.
```
PS C:\> Edit-EC2Host --InstanceType m5.xlarge --HostId h-012a3456b7890cdef
```
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/how-dedicated-hosts-work.md |
37bbb0be43c3-0 | You can change the tenancy of an instance from `dedicated` to `host`, or from `host` to `dedicated`, after you have launched it\. You can also modify the affinity between the instance and the host\. To modify either instance tenancy or affinity, the instance must be in the `stopped` state\.
You can modify an instance's tenancy and affinity using the following methods\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/how-dedicated-hosts-work.md |
22d067109736-0 | **To modify instance tenancy or affinity**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. Choose **Instances**, and select the instance to modify\.
1. Choose **Actions**, **Instance State**, and **Stop**\.
1. Open the context \(right\-click\) menu on the instance and choose **Instance Settings**, **Modify Instance Placement**\.
1. On the **Modify Instance Placement** page, configure the following:
+ **Tenancy**—Choose one of the following:
+ Run a dedicated hardware instance—Launches the instance as a Dedicated Instance\. For more information, see [Dedicated Instances](dedicated-instance.md)\.
+ Launch the instance on a Dedicated Host—Launches the instance onto a Dedicated Host with configurable affinity\.
+ **Affinity**—Choose one of the following:
+ This instance can run on any one of my hosts—The instance launches onto any available Dedicated Host in your account that supports its instance type\.
+ This instance can only run on the selected host—The instance is only able to run on the Dedicated Host selected for **Target Host**\.
+ **Target Host**—Select the Dedicated Host that the instance must run on\. If no target host is listed, you might not have available, compatible Dedicated Hosts in your account\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/how-dedicated-hosts-work.md |
22d067109736-1 | For more information, see [Understanding auto\-placement and affinity](#dedicated-hosts-understanding)\.
1. Choose **Save**\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/how-dedicated-hosts-work.md |
8ef4c529ef5d-0 | **To modify instance tenancy or affinity**
Use the [modify\-instance\-placement](https://docs.aws.amazon.com/cli/latest/reference/ec2/modify-instance-placement.html) AWS CLI command\. The following example changes the specified instance's affinity from `default` to `host`, and specifies the Dedicated Host that the instance has affinity with\.
```
aws ec2 modify-instance-placement --instance-id i-1234567890abcdef0 --affinity host --host-id h-012a3456b7890cdef
```
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/how-dedicated-hosts-work.md |
593fc0c25fda-0 | **To modify instance tenancy or affinity**
Use the [Edit\-EC2InstancePlacement](https://docs.aws.amazon.com/powershell/latest/reference/items/Edit-EC2InstancePlacement.html) AWS Tools for Windows PowerShell command\. The following example changes the specified instance's affinity from `default` to `host`, and specifies the Dedicated Host that the instance has affinity with\.
```
PS C:\> Edit-EC2InstancePlacement -InstanceId i-1234567890abcdef0 -Affinity host -HostId h-012a3456b7890cdef
```
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/how-dedicated-hosts-work.md |
ff210392166a-0 | You can view details about a Dedicated Host and the individual instances on it using the following methods\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/how-dedicated-hosts-work.md |
1205cec35c7e-0 | **To view the details of a Dedicated Host**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the navigation pane, choose **Dedicated Hosts**\.
1. On the **Dedicated Hosts** page, select a host\.
1. For information about the host, choose **Details**\.
**Available vCPUs** indicates the vCPUs that are available on the Dedicated Host for new instance launches\. For example, a Dedicated Host that supports multiple instance types within the `c5` instance family, and that has no instances running on it, has 72 available vCPUs\. This means that you can launch different combinations of instance types onto the Dedicated Host to consume the 72 available vCPUs\.
For information about instances running on the host, choose **Running instances**\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/how-dedicated-hosts-work.md |
bb998c001eff-0 | **To view the details of a Dedicated Host**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the navigation pane, choose **Dedicated Hosts**\.
1. On the **Dedicated Hosts** page, select a host\.
1. For information about the host, choose **Description**\. **Available vCPUs** indicates the vCPUs that are available on the Dedicated Host for new instance launches\. For example, a Dedicated Host that supports multiple instance types within the `c5` instance family, and that has no instances running on it, has 72 available vCPUs\. This means that you can launch different combinations of instance types onto the Dedicated Host to consume the 72 available vCPUs\.
For information about instances running on the host, choose **Instances**\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/how-dedicated-hosts-work.md |
83beb3669703-0 | **To view the capacity of a Dedicated Host**
Use the [describe\-hosts](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-hosts.html) AWS CLI command\.
The following example uses the [describe\-hosts](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-hosts.html) \(AWS CLI\) command to view the available instance capacity for a Dedicated Host that supports multiple instance types within the `c5` instance family\. The Dedicated Host already has two `c5.4xlarge` instances and four `c5.2xlarge` instances running on it\.
```
$ aws ec2 describe-hosts --host-id h-012a3456b7890cdef
```
```
"AvailableInstanceCapacity": [
{ "AvailableCapacity": 2,
"InstanceType": "c5.xlarge",
"TotalCapacity": 18 },
{ "AvailableCapacity": 4,
"InstanceType": "c5.large",
"TotalCapacity": 36 }
],
"AvailableVCpus": 8
```
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/how-dedicated-hosts-work.md |
8013e997085a-0 | **To view the instance capacity of a Dedicated Host**
Use the [Get\-EC2Host](https://docs.aws.amazon.com/powershell/latest/reference/items/Get-EC2Host.html) AWS Tools for Windows PowerShell command\.
```
PS C:\> Get-EC2Host -HostId h-012a3456b7890cdef
```
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/how-dedicated-hosts-work.md |
fd3766e879af-0 | You can assign custom tags to your existing Dedicated Hosts to categorize them in different ways, for example, by purpose, owner, or environment\. This helps you to quickly find a specific Dedicated Host based on the custom tags that you assigned\. Dedicated Host tags can also be used for cost allocation tracking\.
You can also apply tags to Dedicated Hosts at the time of creation\. For more information, see [Allocating Dedicated Hosts](#dedicated-hosts-allocating)\.
You can tag a Dedicated Host using the following methods\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/how-dedicated-hosts-work.md |
b9712b612697-0 | **To tag a Dedicated Host**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the navigation pane, choose **Dedicated Hosts**\.
1. Select the Dedicated Host to tag, and then choose **Actions**, **Manage tags**\.
1. In the **Manage tags** screen, choose **Add tag**, and then specify the key and value for the tag\.
1. \(Optional\) Choose **Add tag** to add additional tags to the Dedicated Host\.
1. Choose **Save changes**\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/how-dedicated-hosts-work.md |
a6c66e721626-0 | **To tag a Dedicated Host**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the navigation pane, choose **Dedicated Hosts**\.
1. Select the Dedicated Host to tag, and then choose **Tags**\.
1. Choose **Add/Edit Tags**\.
1. In the **Add/Edit Tags** dialog box, choose **Create Tag**, and then specify the key and value for the tag\.
1. \(Optional\) Choose **Create Tag** to add additional tags to the Dedicated Host\.
1. Choose **Save**\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/how-dedicated-hosts-work.md |
bbb0593904a8-0 | **To tag a Dedicated Host**
Use the [create\-tags](https://docs.aws.amazon.com/cli/latest/reference/ec2/create-tags.html) AWS CLI command\.
The following command tags the specified Dedicated Host with `Owner=TeamA`\.
```
aws ec2 create-tags --resources h-abc12345678909876 --tags Key=Owner,Value=TeamA
```
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/how-dedicated-hosts-work.md |
3baa4b8a735c-0 | **To tag a Dedicated Host**
Use the [New\-EC2Tag](https://docs.aws.amazon.com/powershell/latest/reference/items/New-EC2Tag.html) AWS Tools for Windows PowerShell command\.
The `New-EC2Tag` command needs a `Tag` object, which specifies the key and value pair to be used for the Dedicated Host tag\. The following commands create a `Tag` object named `$tag`, with a key and value pair of `Owner` and `TeamA` respectively\.
```
PS C:\> $tag = New-Object Amazon.EC2.Model.Tag
PS C:\> $tag.Key = "Owner"
PS C:\> $tag.Value = "TeamA"
```
The following command tags the specified Dedicated Host with the `$tag` object\.
```
PS C:\> New-EC2Tag -Resource h-abc12345678909876 -Tag $tag
```
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/how-dedicated-hosts-work.md |
cec538601fbd-0 | Amazon EC2 constantly monitors the state of your Dedicated Hosts\. Updates are communicated on the Amazon EC2 console\. You can view information about a Dedicated Host using the following methods\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/how-dedicated-hosts-work.md |
Subsets and Splits