id
stringlengths 14
16
| text
stringlengths 1
2.43k
| source
stringlengths 99
229
|
|---|---|---|
b74e050ffc33-1 | "TargetSize": 2000,
"TargetVolumeType": "sc1",
"ModificationState": "modifying",
"VolumeId": "vol-22222222222222222",
"StartTime": "2017-01-19T22:23:22.158Z",
"Progress": 0,
"OriginalVolumeType": "gp2",
"OriginalIops": 300,
"OriginalSize": 1000
}
]
}
```
The next example describes all volumes with a modification state of either `optimizing` or `completed`, and then filters and formats the results to show only modifications that were initiated on or after February 1, 2017:
```
aws ec2 describe-volumes-modifications --filters Name=modification-state,Values="optimizing","completed" --query "VolumesModifications[?StartTime>='2017-02-01'].{ID:VolumeId,STATE:ModificationState}"
```
The following is example output with information about two volumes:
```
[
{
"STATE": "optimizing",
"ID": "vol-06397e7a0eEXAMPLE"
},
{
"STATE": "completed", | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-volume-modifications.md |
b74e050ffc33-2 | },
{
"STATE": "completed",
"ID": "vol-ba74e18c2aEXAMPLE"
}
]
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-volume-modifications.md |
432777df44bd-0 | With CloudWatch Events, you can create a notification rule for volume modification events\. You can use your rule to generate a notification message using [Amazon SNS](https://docs.aws.amazon.com/sns/latest/dg/) or to invoke a [Lambda function](https://docs.aws.amazon.com/lambda/latest/dg/) in response to matching events\.
**To monitor progress of a modification using CloudWatch Events**
1. Open the CloudWatch console at [https://console\.aws\.amazon\.com/cloudwatch/](https://console.aws.amazon.com/cloudwatch/)\.
1. Choose **Events**, **Create rule**\.
1. For **Build event pattern to match events by service**, choose **Custom event pattern**\.
1. For **Build custom event pattern**, replace the contents with the following and choose **Save**\.
```
{
"source": [
"aws.ec2"
],
"detail-type": [
"EBS Volume Notification"
],
"detail": {
"event": [
"modifyVolume"
]
}
}
```
The following is example event data:
```
{ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-volume-modifications.md |
432777df44bd-1 | }
}
```
The following is example event data:
```
{
"version": "0",
"id": "01234567-0123-0123-0123-012345678901",
"detail-type": "EBS Volume Notification",
"source": "aws.ec2",
"account": "012345678901",
"time": "2017-01-12T21:09:07Z",
"region": "us-east-1",
"resources": [
"arn:aws:ec2:us-east-1:012345678901:volume/vol-03a55cf56513fa1b6"
],
"detail": {
"result": "optimizing",
"cause": "",
"event": "modifyVolume",
"request-id": "01234567-0123-0123-0123-0123456789ab"
}
}
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-volume-modifications.md |
17a39b0999a8-0 | The `unlimited` mode is a credit configuration option for burstable performance instances\. It can be enabled or disabled at any time for a running or stopped instance\. You can set `unlimited` as the default credit option at the account level per AWS Region, per burstable performance instance family, so that all new burstable performance instances in the account launch using the default credit option\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/burstable-performance-instances-unlimited-mode-concepts.md |
4dfd80e91739-0 | If a burstable performance instance configured as `unlimited` depletes its CPU credit balance, it can spend *surplus* credits to burst beyond the [baseline](burstable-credits-baseline-concepts.md#baseline_performance)\. When its CPU utilization falls below the baseline, it uses the CPU credits that it earns to pay down the surplus credits that it spent earlier\. The ability to earn CPU credits to pay down surplus credits enables Amazon EC2 to average the CPU utilization of an instance over a 24\-hour period\. If the average CPU usage over a 24\-hour period exceeds the baseline, the instance is billed for the additional usage at a flat additional rate per vCPU\-hour\.
The following graph shows the CPU usage of a `t3.large`\. The baseline CPU utilization for a `t3.large` is 30%\. If the instance runs at 30% CPU utilization or less on average over a 24\-hour period, there is no additional charge because the cost is already covered by the instance hourly price\. However, if the instance runs at 40% CPU utilization on average over a 24\-hour period, as shown in the graph, the instance is billed for the additional 10% CPU usage at a flat additional rate per vCPU\-hour\.
![\[Image NOT FOUND\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/t3-cpu-usage.png)
For more information about the baseline utilization per vCPU for each instance type and how many credits each instance type earns, see the [credit table](burstable-credits-baseline-concepts.md#burstable-performance-instances-credit-table)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/burstable-performance-instances-unlimited-mode-concepts.md |
b84a4ff1766b-0 | When determining whether you should use a burstable performance instance in `unlimited` mode, such as T3, or a fixed performance instance, such as M5, you need to determine the breakeven CPU usage\. The breakeven CPU usage for a burstable performance instance is the point at which a burstable performance instance costs the same as a fixed performance instance\. The breakeven CPU usage helps you determine the following:
+ If the average CPU usage over a 24\-hour period is at or below the breakeven CPU usage, use a burstable performance instance in `unlimited` mode so that you can benefit from the lower price of a burstable performance instance while getting the same performance as a fixed performance instance\.
+ If the average CPU usage over a 24\-hour period is above the breakeven CPU usage, the burstable performance instance will cost more than the equivalently\-sized fixed performance instance\. If a T3 instance continuously bursts at 100% CPU, you end up paying approximately 1\.5 times the price of an equivalently\-sized M5 instance\.
The following graph shows the breakeven CPU usage point where a `t3.large` costs the same as an `m5.large`\. The breakeven CPU usage point for a `t3.large` is 42\.5%\. If the average CPU usage is at 42\.5%, the cost of running the `t3.large` is the same as an `m5.large`, and is more expensive if the average CPU usage is above 42\.5%\. If the workload needs less than 42\.5% average CPU usage, you can benefit from the lower price of the `t3.large` while getting the same performance as an `m5.large`\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/burstable-performance-instances-unlimited-mode-concepts.md |
b84a4ff1766b-1 | ![\[Image NOT FOUND\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/T3-unltd-when-to-use.png)
The following table shows how to calculate the breakeven CPU usage threshold so that you can determine when it's less expensive to use a burstable performance instance in `unlimited` mode or a fixed performance instance\. The columns in the table are labeled A through K\.
| Instance type | vCPUs | T3 price\*/hour | M5 price\*/hour | Price difference | T3 baseline utilization per vCPU \(%\) | Charge per vCPU hour for surplus credits | Charge per vCPU minute | Additional burst minutes available per vCPU | Additional CPU % available | Breakeven CPU % |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| A | B | C | D | E = D \- C | F | G | H = G / 60 | I = E / H | J = \(I / 60\) / B | K = F \+ J |
| t3\.large | 2 | $0\.0835 | $0\.096 | $0\.0125 | 30% | $0\.05 | $0\.000833 | 15 | 12\.5% | 42\.5% |
| |
| --- |
| \* Price is based on us\-east\-1 and Linux OS\. | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/burstable-performance-instances-unlimited-mode-concepts.md |
b84a4ff1766b-2 | | |
| --- |
| \* Price is based on us\-east\-1 and Linux OS\. |
The table provides the following information:
+ Column A shows the instance type, `t3.large`\.
+ Column B shows the number of vCPUs for the `t3.large`\.
+ Column C shows the price of a `t3.large` per hour\.
+ Column D shows the price of an `m5.large` per hour\.
+ Column E shows the price difference between the `t3.large` and the `m5.large`\.
+ Column F shows the baseline utilization per vCPU of the `t3.large`, which is 30%\. At the baseline, the hourly cost of the instance covers the cost of the CPU usage\.
+ Column G shows the flat additional rate per vCPU\-hour that an instance is charged if it bursts at 100% CPU after it has depleted its earned credits\.
+ Column H shows the flat additional rate per vCPU\-minute that an instance is charged if it bursts at 100% CPU after it has depleted its earned credits\.
+ Column I shows the number of additional minutes that the `t3.large` can burst per hour at 100% CPU while paying the same price per hour as an `m5.large`\.
+ Column J shows the additional CPU usage \(in %\) over baseline that the instance can burst while paying the same price per hour as an `m5.large`\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/burstable-performance-instances-unlimited-mode-concepts.md |
b84a4ff1766b-3 | + Column J shows the additional CPU usage \(in %\) over baseline that the instance can burst while paying the same price per hour as an `m5.large`\.
+ Column K shows the breakeven CPU usage \(in %\) that the `t3.large` can burst without paying more than the `m5.large`\. Anything above this, and the `t3.large` costs more than the `m5.large`\.
The following table shows the breakeven CPU usage \(in %\) for T3 instance types compared to the similarly\-sized M5 instance types\.
| T3 instance type | Breakeven CPU usage \(in %\) for T3 compared to M5 |
| --- | --- |
| t3\.large | 42\.5% |
| t3\.xlarge | 52\.5% |
| t3\.2xlarge | 52\.5% | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/burstable-performance-instances-unlimited-mode-concepts.md |
871669c7ed18-0 | If the average CPU utilization of an instance is at or below the baseline, the instance incurs no additional charges\. Because an instance earns a [maximum number of credits](burstable-credits-baseline-concepts.md#burstable-performance-instances-credit-table) in a 24\-hour period \(for example, a `t3.micro` instance can earn a maximum of 288 credits in a 24\-hour period\), it can spend surplus credits up to that maximum without being charged\.
However, if CPU utilization stays above the baseline, the instance cannot earn enough credits to pay down the surplus credits that it has spent\. The surplus credits that are not paid down are charged at a flat additional rate per vCPU\-hour\.
Surplus credits that were spent earlier are charged when any of the following occurs:
+ The spent surplus credits exceed the [maximum number of credits](burstable-credits-baseline-concepts.md#burstable-performance-instances-credit-table) the instance can earn in a 24\-hour period\. Spent surplus credits above the maximum are charged at the end of the hour\.
+ The instance is stopped or terminated\.
+ The instance is switched from `unlimited` to `standard`\.
Spent surplus credits are tracked by the CloudWatch metric `CPUSurplusCreditBalance`\. Surplus credits that are charged are tracked by the CloudWatch metric `CPUSurplusCreditsCharged`\. For more information, see [Additional CloudWatch metrics for burstable performance instances](burstable-performance-instances-monitoring-cpu-credits.md#burstable-performance-instances-cw-metrics)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/burstable-performance-instances-unlimited-mode-concepts.md |
39dae17abaef-0 | T2 Standard instances receive [launch credits](burstable-performance-instances-standard-mode-concepts.md#launch-credits), but T2 Unlimited instances do not\. A T2 Unlimited instance can burst beyond the baseline at any time with no additional charge, as long as its average CPU utilization is at or below the baseline over a rolling 24\-hour window or its lifetime, whichever is shorter\. As such, T2 Unlimited instances do not require launch credits to achieve high performance immediately after launch\.
If a T2 instance is switched from `standard` to `unlimited`, any accrued launch credits are removed from the `CPUCreditBalance` before the remaining `CPUCreditBalance` is carried over\.
T3 and T4g instances never receive launch credits\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/burstable-performance-instances-unlimited-mode-concepts.md |
a82e9a242f5a-0 | You can switch from `unlimited` to `standard`, and from `standard` to `unlimited`, at any time on a running or stopped instance\. For more information, see [Launching a burstable performance instance as Unlimited or Standard](burstable-performance-instances-how-to.md#launch-burstable-performance-instances) and [Modifying the credit specification of a burstable performance instance](burstable-performance-instances-how-to.md#modify-burstable-performance-instances)\.
You can set `unlimited` as the default credit option at the account level per AWS Region, per burstable performance instance family, so that all new burstable performance instances in the account launch using the default credit option\. For more information, see [Setting the default credit specification for the account](burstable-performance-instances-how-to.md#burstable-performance-instance-set-default-credit-specification-for-account)\.
You can check whether your burstable performance instance is configured as `unlimited` or `standard` using the Amazon EC2 console or the AWS CLI\. For more information, see [Viewing the credit specification of a burstable performance instance](burstable-performance-instances-how-to.md#describe-burstable-performance-instances) and [Viewing the default credit specification](burstable-performance-instances-how-to.md#burstable-performance-instances-get-default-credit-specification)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/burstable-performance-instances-unlimited-mode-concepts.md |
a65273525220-0 | `CPUCreditBalance` is a CloudWatch metric that tracks the number of credits accrued by an instance\. `CPUSurplusCreditBalance` is a CloudWatch metric that tracks the number of surplus credits spent by an instance\.
When you change an instance configured as `unlimited` to `standard`, the following occurs:
+ The `CPUCreditBalance` value remains unchanged and is carried over\.
+ The `CPUSurplusCreditBalance` value is immediately charged\.
When a `standard` instance is switched to `unlimited`, the following occurs:
+ The `CPUCreditBalance` value containing accrued earned credits is carried over\.
+ For T2 Standard instances, any launch credits are removed from the `CPUCreditBalance` value, and the remaining `CPUCreditBalance` value containing accrued earned credits is carried over\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/burstable-performance-instances-unlimited-mode-concepts.md |
4bb96aeb20b3-0 | To see if your instance is spending more credits than the baseline provides, you can use CloudWatch metrics to track usage, and you can set up hourly alarms to be notified of credit usage\. For more information, see [Monitoring your CPU credits](burstable-performance-instances-monitoring-cpu-credits.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/burstable-performance-instances-unlimited-mode-concepts.md |
a7d9c4227db3-0 | The following documentation can help you troubleshoot problems that you might have with your instance\.
**Topics**
+ [Troubleshooting instance launch issues](troubleshooting-launch.md)
+ [Troubleshooting connecting to your instance](TroubleshootingInstancesConnecting.md)
+ [Troubleshooting stopping your instance](TroubleshootingInstancesStopping.md)
+ [Troubleshooting terminating \(shutting down\) your instance](TroubleshootingInstancesShuttingDown.md)
+ [Troubleshooting instances with failed status checks](TroubleshootingInstances.md)
+ [Troubleshooting an unreachable instance](instance-console.md)
+ [Booting from the wrong volume](instance-booting-from-wrong-volume.md)
+ [Using EC2Rescue for Linux](Linux-Server-EC2Rescue.md)
+ [Sending a diagnostic interrupt \(for advanced users\)](diagnostic-interrupt.md)
For additional help with Windows instances, see [Troubleshooting Windows Instances](https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/troubleshooting-windows-instances.html) in the *Amazon EC2 User Guide for Windows Instances*\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-instance-troubleshoot.md |
e56596ce0766-0 | Cloud file storage is a method for storing data in the cloud that provides servers and applications access to data through shared file systems\. This compatibility makes cloud file storage ideal for workloads that rely on shared file systems and provides simple integration without code changes\.
There are many file storage solutions that exist, ranging from a single node file server on a compute instance using block storage as the underpinnings with no scalability or few redundancies to protect the data, to a do\-it\-yourself clustered solution, to a fully\-managed solution\. The following content introduces some of the storage services provided by AWS for use with Linux\.
**Topics**
+ [Using Amazon S3 with Amazon EC2](AmazonS3.md)
+ [Using Amazon EFS with Amazon EC2](AmazonEFS.md) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/file-storage.md |
c26494788c13-0 | An Amazon EC2 instance transitions through different states from the moment you launch it through to its termination\.
The following illustration represents the transitions between instance states\. Notice that you can't stop and start an instance store\-backed instance\. For more information about instance store\-backed instances, see [Storage for the root device](ComponentsAMIs.md#storage-for-the-root-device)\.
![\[The instance lifecycle\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/instance_lifecycle.png)
The following table provides a brief description of each instance state and indicates whether it is billed or not\.
**Note**
The table indicates billing for instance usage only\. Some AWS resources, such as Amazon EBS volumes and Elastic IP addresses, incur charges regardless of the instance's state\. For more information, see [Avoiding Unexpected Charges](https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/checklistforunwantedcharges.html) in the *AWS Billing and Cost Management User Guide*\.
| Instance state | Description | Instance usage billing |
| --- | --- | --- |
| `pending` | The instance is preparing to enter the `running` state\. An instance enters the `pending` state when it launches for the first time, or when it is started after being in the `stopped` state\. | Not billed |
| `running` | The instance is running and ready for use\. | Billed | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-instance-lifecycle.md |
c26494788c13-1 | | `running` | The instance is running and ready for use\. | Billed |
| `stopping` | The instance is preparing to be stopped or stop\-hibernated\. | Not billed if preparing to stop Billed if preparing to hibernate |
| `stopped` | The instance is shut down and cannot be used\. The instance can be started at any time\. | Not billed |
| `shutting-down` | The instance is preparing to be terminated\. | Not billed |
| `terminated` | The instance has been permanently deleted and cannot be started\. | Not billed Reserved Instances that applied to terminated instances are billed until the end of their term according to their payment option\. For more information, see [Reserved Instances](ec2-reserved-instances.md) |
**Note**
Rebooting an instance doesn't start a new instance billing period because the instance stays in the `running` state\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-instance-lifecycle.md |
0a9d43b673dc-0 | When you launch an instance, it enters the `pending` state\. The instance type that you specified at launch determines the hardware of the host computer for your instance\. We use the Amazon Machine Image \(AMI\) you specified at launch to boot the instance\. After the instance is ready for you, it enters the `running` state\. You can connect to your running instance and use it the way that you'd use a computer sitting in front of you\.
As soon as your instance transitions to the `running` state, you're billed for each second, with a one\-minute minimum, that you keep the instance running, even if the instance remains idle and you don't connect to it\.
For more information, see [Launch your instance](LaunchingAndUsingInstances.md) and [Connect to your Linux instance](AccessingInstances.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-instance-lifecycle.md |
d4ab3bf00c9b-0 | If your instance fails a status check or is not running your applications as expected, and if the root volume of your instance is an Amazon EBS volume, you can stop and start your instance to try to fix the problem\.
When you stop your instance, it enters the `stopping` state, and then the `stopped` state\. We don't charge usage or data transfer fees for your instance after you stop it, but we do charge for the storage for any Amazon EBS volumes\. While your instance is in the `stopped` state, you can modify certain attributes of the instance, including the instance type\.
When you start your instance, it enters the `pending` state, and we move the instance to a new host computer \(though in some cases, it remains on the current host\)\. When you stop and start your instance, you lose any data on the instance store volumes on the previous host computer\.
Your instance retains its private IPv4 address, which means that an Elastic IP address associated with the private IPv4 address or network interface is still associated with your instance\. If your instance has an IPv6 address, it retains its IPv6 address\.
Each time you transition an instance from `stopped` to `running`, we charge per second when the instance is running, with a minimum of one minute every time you start your instance\.
For more information, see [Stop and start your instance](Stop_Start.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-instance-lifecycle.md |
1db0e6564cf6-0 | When you hibernate an instance, we signal the operating system to perform hibernation \(suspend\-to\-disk\), which saves the contents from the instance memory \(RAM\) to your Amazon EBS root volume\. We persist the instance's Amazon EBS root volume and any attached Amazon EBS data volumes\. When you start your instance, the Amazon EBS root volume is restored to its previous state and the RAM contents are reloaded\. Previously attached data volumes are reattached and the instance retains its instance ID\.
When you hibernate your instance, it enters the `stopping` state, and then the `stopped` state\. We don't charge usage for a hibernated instance when it is in the `stopped` state, but we do charge while it is in the `stopping` state, unlike when you [stop an instance](#instance-stop-start) without hibernating it\. We don't charge usage for data transfer fees, but we do charge for the storage for any Amazon EBS volumes, including storage for the RAM data\.
When you start your hibernated instance, it enters the `pending` state, and we move the instance to a new host computer \(though in some cases, it remains on the current host\)\.
Your instance retains its private IPv4 address, which means that an Elastic IP address associated with the private IPv4 address or network interface is still associated with your instance\. If your instance has an IPv6 address, it retains its IPv6 address\.
For more information, see [Hibernate your Linux instance](Hibernate.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-instance-lifecycle.md |
4c178227e1a5-0 | You can reboot your instance using the Amazon EC2 console, a command line tool, and the Amazon EC2 API\. We recommend that you use Amazon EC2 to reboot your instance instead of running the operating system reboot command from your instance\.
Rebooting an instance is equivalent to rebooting an operating system\. The instance remains on the same host computer and maintains its public DNS name, private IP address, and any data on its instance store volumes\. It typically takes a few minutes for the reboot to complete, but the time it takes to reboot depends on the instance configuration\.
Rebooting an instance doesn't start a new instance billing period; per second billing continues without a further one\-minute minimum charge\.
For more information, see [Reboot your instance](ec2-instance-reboot.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-instance-lifecycle.md |
54c0b76d0b8f-0 | An instance is scheduled to be retired when AWS detects the irreparable failure of the underlying hardware hosting the instance\. When an instance reaches its scheduled retirement date, it is stopped or terminated by AWS\. If your instance root device is an Amazon EBS volume, the instance is stopped, and you can start it again at any time\. If your instance root device is an instance store volume, the instance is terminated, and cannot be used again\.
For more information, see [Instance retirement](instance-retirement.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-instance-lifecycle.md |
a802f89c4e53-0 | When you've decided that you no longer need an instance, you can terminate it\. As soon as the status of an instance changes to `shutting-down` or `terminated`, you stop incurring charges for that instance\.
If you enable termination protection, you can't terminate the instance using the console, CLI, or API\.
After you terminate an instance, it remains visible in the console for a short while, and then the entry is automatically deleted\. You can also describe a terminated instance using the CLI and API\. Resources \(such as tags\) are gradually disassociated from the terminated instance, therefore may no longer be visible on the terminated instance after a short while\. You can't connect to or recover a terminated instance\.
Each Amazon EBS\-backed instance supports the `InstanceInitiatedShutdownBehavior` attribute, which controls whether the instance stops or terminates when you initiate shutdown from within the instance itself \(for example, by using the shutdown command on Linux\)\. The default behavior is to stop the instance\. You can modify the setting of this attribute while the instance is running or stopped\.
Each Amazon EBS volume supports the `DeleteOnTermination` attribute, which controls whether the volume is deleted or preserved when you terminate the instance it is attached to\. The default is to delete the root device volume and preserve any other EBS volumes\.
For more information, see [Terminate your instance](terminating-instances.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-instance-lifecycle.md |
0f4cd998e880-0 | The following table summarizes the key differences between rebooting, stopping, hibernating, and terminating your instance\.
| Characteristic | Reboot | Stop/start \(Amazon EBS\-backed instances only\) | Hibernate \(Amazon EBS\-backed instances only\) | Terminate |
| --- | --- | --- | --- | --- |
| Host computer | The instance stays on the same host computer | We move the instance to a new host computer \(though in some cases, it remains on the current host\)\. | We move the instance to a new host computer \(though in some cases, it remains on the current host\)\. | None |
| Private and public IPv4 addresses | These addresses stay the same | The instance keeps its private IPv4 address\. The instance gets a new public IPv4 address, unless it has an Elastic IP address, which doesn't change during a stop/start\. | The instance keeps its private IPv4 address\. The instance gets a new public IPv4 address, unless it has an Elastic IP address, which doesn't change during a stop/start\. | None |
| Elastic IP addresses \(IPv4\) | The Elastic IP address remains associated with the instance | The Elastic IP address remains associated with the instance | The Elastic IP address remains associated with the instance | The Elastic IP address is disassociated from the instance |
| IPv6 address | The address stays the same | The instance keeps its IPv6 address | The instance keeps its IPv6 address | None | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-instance-lifecycle.md |
0f4cd998e880-1 | | IPv6 address | The address stays the same | The instance keeps its IPv6 address | The instance keeps its IPv6 address | None |
| Instance store volumes | The data is preserved | The data is erased | The data is erased | The data is erased |
| Root device volume | The volume is preserved | The volume is preserved | The volume is preserved | The volume is deleted by default |
| RAM \(contents of memory\) | The RAM is erased | The RAM is erased | The RAM is saved to a file on the root volume | The RAM is erased |
| Billing | The instance billing hour doesn't change\. | You stop incurring charges for an instance as soon as its state changes to `stopping`\. Each time an instance transitions from `stopped` to `running`, we start a new instance billing period, billing a minimum of one minute every time you start your instance\. | You incur charges while the instance is in the `stopping` state, but stop incurring charges when the instance is in the `stopped` state\. Each time an instance transitions from `stopped` to `running`, we start a new instance billing period, billing a minimum of one minute every time you start your instance\. | You stop incurring charges for an instance as soon as its state changes to `shutting-down`\. |
Operating system shutdown commands always terminate an instance store\-backed instance\. You can control whether operating system shutdown commands stop or terminate an Amazon EBS\-backed instance\. For more information, see [Changing the instance initiated shutdown behavior](terminating-instances.md#Using_ChangingInstanceInitiatedShutdownBehavior)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-instance-lifecycle.md |
a6c0c8ab4166-0 | When you request Spot Instances, we recommend that you use the default maximum price \(the On\-Demand price\)\. If you want to specify a maximum price, we recommend that you review the Spot price history before you do so\. You can view the Spot price history for the last 90 days, filtering by instance type, operating system, and Availability Zone\.
Spot Instance prices are set by Amazon EC2 and adjust gradually based on long\-term trends in supply and demand for Spot Instance capacity\. For the *current* Spot Instance prices see [Amazon EC2 Spot Instances Pricing](http://aws.amazon.com/ec2/spot/pricing/)\.
**To view the Spot price history \(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 **Spot Requests**\.
1. If you are new to Spot Instances, you see a welcome page\. Choose **Get started**, scroll to the bottom of the screen, and then choose **Cancel**\.
1. Choose **Pricing history**\.
1. Choose the operating system \(**Product**\), **Instance type**, and **Date range** for which to view the price history\. Move your pointer over the graph to display the prices at specific times in the selected date range\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-spot-instances-history.md |
a6c0c8ab4166-1 | ![\[The Spot Instance pricing history tool in the Amazon EC2 console.\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/spot-instance-pricing-history.png)
1. \(Optional\) To review the Spot price history for a specific Availability Zone, you can filter the Availability Zones by removing Availability Zones from the graph\. To remove an Availability Zone from the graph, select the zone to remove it\. You can also select a different product, instance type, or date range\.
**To view the Spot price history using the command line**
You can use one of the following commands\. For more information, see [Accessing Amazon EC2](concepts.md#access-ec2)\.
+ [describe\-spot\-price\-history](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-spot-price-history.html) \(AWS CLI\)
+ [Get\-EC2SpotPriceHistory](https://docs.aws.amazon.com/powershell/latest/reference/items/Get-EC2SpotPriceHistory.html) \(AWS Tools for Windows PowerShell\) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-spot-instances-history.md |
87751cba7959-0 | You can monitor your instances using Amazon CloudWatch, which collects and processes raw data from Amazon EC2 into readable, near real\-time metrics\. These statistics are recorded for a period of 15 months, so that you can access historical information and gain a better perspective on how your web application or service is performing\.
By default, Amazon EC2 sends metric data to CloudWatch in 5\-minute periods\. To send metric data for your instance to CloudWatch in 1\-minute periods, you can enable detailed monitoring on the instance\. For more information, see [Enable or disable detailed monitoring for your instances](using-cloudwatch-new.md)\.
The Amazon EC2 console displays a series of graphs based on the raw data from Amazon CloudWatch\. Depending on your needs, you might prefer to get data for your instances from Amazon CloudWatch instead of the graphs in the console\.
For more information about Amazon CloudWatch, see the [Amazon CloudWatch User Guide](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/)\.
**Topics**
+ [Enable or disable detailed monitoring for your instances](using-cloudwatch-new.md)
+ [List the available CloudWatch metrics for your instances](viewing_metrics_with_cloudwatch.md)
+ [Get statistics for metrics for your instances](monitoring_get_statistics.md)
+ [Graph metrics for your instances](graphs-in-the-aws-management-console.md)
+ [Create a CloudWatch alarm for an instance](using-cloudwatch-createalarm.md) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-cloudwatch.md |
87751cba7959-1 | + [Create a CloudWatch alarm for an instance](using-cloudwatch-createalarm.md)
+ [Create alarms that stop, terminate, reboot, or recover an instance](UsingAlarmActions.md) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-cloudwatch.md |
2b7a9296b774-0 | Storage optimized instances are designed for workloads that require high, sequential read and write access to very large data sets on local storage\. They are optimized to deliver tens of thousands of low\-latency, random I/O operations per second \(IOPS\) to applications\.<a name="d2-instances"></a>
**D2 instances**
These instances are well suited for the following:
+ Massive parallel processing \(MPP\) data warehouse
+ MapReduce and Hadoop distributed computing
+ Log or data processing applications<a name="h1-instances"></a>
**H1 instances**
These instances are well suited for the following:
+ Data\-intensive workloads such as MapReduce and distributed file systems
+ Applications requiring sequential access to large amounts of data on direct\-attached instance storage
+ Applications that require high\-throughput access to large quantities of data<a name="i3-instances"></a>
**I3 and I3en instances**
These instances are well suited for the following:
+ High frequency online transaction processing \(OLTP\) systems
+ Relational databases
+ NoSQL databases
+ Cache for in\-memory databases \(for example, Redis\)
+ Data warehousing applications
+ Distributed file systems
Bare metal instances provide your applications with direct access to physical resources of the host server, such as processors and memory\. These instances are well suited for the following: | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/storage-optimized-instances.md |
2b7a9296b774-1 | Bare metal instances provide your applications with direct access to physical resources of the host server, such as processors and memory\. These instances are well suited for the following:
+ Workloads that require access to low\-level hardware features \(for example, Intel VT\) that are not available or fully supported in virtualized environments
+ Applications that require a non\-virtualized environment for licensing or support
For more information, see [Amazon EC2 I3 Instances](https://aws.amazon.com/ec2/instance-types/i3)\.
**Topics**
+ [Hardware specifications](#storage-instances-hardware)
+ [Instance performance](#storage-performance)
+ [Network performance](#storage-network-performance)
+ [SSD I/O performance](#i2-instances-diskperf)
+ [Instance features](#storage-instances-features)
+ [Support for vCPUs](#d2-instances-cpu-support)
+ [Release notes](#storage-instance-release-notes) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/storage-optimized-instances.md |
766339c94217-0 | The primary data storage for D2 instances is HDD instance store volumes\. The primary data storage for I3 and I3en instances is non\-volatile memory express \(NVMe\) SSD instance store volumes\.
Instance store volumes persist only for the life of the instance\. When you stop or terminate an instance, the applications and data in its instance store volumes are erased\. We recommend that you regularly back up or replicate important data in your instance store volumes\. For more information, see [Amazon EC2 instance store](InstanceStorage.md) and [SSD instance store volumes](ssd-instance-store.md)\.
The following is a summary of the hardware specifications for storage optimized instances\.
| Instance type | Default vCPUs | Memory \(GiB\) |
| --- | --- | --- |
| d2\.xlarge | 4 | 30\.5 |
| d2\.2xlarge | 8 | 61 |
| d2\.4xlarge | 16 | 122 |
| d2\.8xlarge | 36 | 244 |
| h1\.2xlarge | 8 | 32 |
| h1\.4xlarge | 16 | 64 |
| h1\.8xlarge | 32 | 128 |
| h1\.16xlarge | 64 | 256 |
| i3\.large | 2 | 15\.25 |
| i3\.xlarge | 4 | 30\.5 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/storage-optimized-instances.md |
766339c94217-1 | | i3\.large | 2 | 15\.25 |
| i3\.xlarge | 4 | 30\.5 |
| i3\.2xlarge | 8 | 61 |
| i3\.4xlarge | 16 | 122 |
| i3\.8xlarge | 32 | 244 |
| i3\.16xlarge | 64 | 488 |
| i3\.metal | 72 | 512 |
| i3en\.large | 2 | 16 |
| i3en\.xlarge | 4 | 32 |
| i3en\.2xlarge | 8 | 64 |
| i3en\.3xlarge | 12 | 96 |
| i3en\.6xlarge | 24 | 192 |
| i3en\.12xlarge | 48 | 384 |
| i3en\.24xlarge | 96 | 768 |
| i3en\.metal | 96 | 768 |
For more information about the hardware specifications for each Amazon EC2 instance type, see [Amazon EC2 Instance Types](https://aws.amazon.com/ec2/instance-types/)\.
For more information about specifying CPU options, see [Optimizing CPU options](instance-optimize-cpu.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/storage-optimized-instances.md |
b6200794ae78-0 | To ensure the best disk throughput performance from your instance on Linux, we recommend that you use the most recent version of Amazon Linux 2 or the Amazon Linux AMI\.
For instances with NVMe instance store volumes, you must use a Linux AMI with kernel version 4\.4 or later\. Otherwise, your instance will not achieve the maximum IOPS performance available\.
D2 instances provide the best disk performance when you use a Linux kernel that supports persistent grants, an extension to the Xen block ring protocol that significantly improves disk throughput and scalability\. For more information about persistent grants, see [this article](https://blog.xenproject.org/2012/11/23/improving-block-protocol-scalability-with-persistent-grants/) in the Xen Project Blog\.
EBS\-optimized instances enable you to get consistently high performance for your EBS volumes by eliminating contention between Amazon EBS I/O and other network traffic from your instance\. Some storage optimized instances are EBS\-optimized by default at no additional cost\. For more information, see [Amazon EBS–optimized instances](ebs-optimized.md)\.
Some storage optimized instance types provide the ability to control processor C\-states and P\-states on Linux\. C\-states control the sleep levels that a core can enter when it is inactive, while P\-states control the desired performance \(in CPU frequency\) from a core\. For more information, see [Processor state control for your EC2 instance](processor_state_control.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/storage-optimized-instances.md |
efe81f21760e-0 | You can enable enhanced networking on supported instance types to provide lower latencies, lower network jitter, and higher packet\-per\-second \(PPS\) performance\. Most applications do not consistently need a high level of network performance, but can benefit from access to increased bandwidth when they send or receive data\. For more information, see [Enhanced networking on Linux](enhanced-networking.md)\.
The following is a summary of network performance for storage optimized instances that support enhanced networking\.
| Instance type | Network performance | Enhanced networking |
| --- | --- | --- |
| i3\.4xlarge and smaller | Up to 10 Gbps † | [ENA](enhanced-networking-ena.md) |
| i3\.8xlarge \| h1\.8xlarge | 10 Gbps | [ENA](enhanced-networking-ena.md) |
| i3en\.3xlarge and smaller | Up to 25 Gbps † | [ENA](enhanced-networking-ena.md) |
| i3\.16xlarge \| i3\.metal \| i3en\.6xlarge \| h1\.16xlarge | 25 Gbps | [ENA](enhanced-networking-ena.md) |
| i3en\.12xlarge | 50 Gbps | [ENA](enhanced-networking-ena.md) | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/storage-optimized-instances.md |
efe81f21760e-1 | | i3en\.12xlarge | 50 Gbps | [ENA](enhanced-networking-ena.md) |
| i3en\.24xlarge \| i3en\.metal | 100 Gbps | [ENA](enhanced-networking-ena.md) |
| d2\.xlarge | Moderate | [Intel 82599 VF](sriov-networking.md) |
| d2\.2xlarge \| d2\.4xlarge | High | [Intel 82599 VF](sriov-networking.md) |
| d2\.8xlarge | 10 Gbps | [Intel 82599 VF](sriov-networking.md) |
† These instances use a network I/O credit mechanism to allocate network bandwidth to instances based on average bandwidth utilization\. They accrue credits when their bandwidth is below their baseline bandwidth, and can use these credits when they perform network data transfers\. For more information, open a support case and ask about baseline bandwidth for the specific instance types that you are interested in\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/storage-optimized-instances.md |
80b784942242-0 | If you use a Linux AMI with kernel version 4\.4 or later and use all the SSD\-based instance store volumes available to your instance, you get the IOPS \(4,096 byte block size\) performance listed in the following table \(at queue depth saturation\)\. Otherwise, you get lower IOPS performance\.
| Instance Size | 100% Random Read IOPS | Write IOPS |
| --- | --- | --- |
| i3\.large \* | 100,125 | 35,000 |
| i3\.xlarge \* | 206,250 | 70,000 |
| i3\.2xlarge | 412,500 | 180,000 |
| i3\.4xlarge | 825,000 | 360,000 |
| i3\.8xlarge | 1\.65 million | 720,000 |
| i3\.16xlarge | 3\.3 million | 1\.4 million |
| i3\.metal | 3\.3 million | 1\.4 million |
| i3en\.large \* | 42,500 | 32,500 |
| i3en\.xlarge \* | 85,000 | 65,000 |
| i3en\.2xlarge \* | 170,000 | 130,000 |
| i3en\.3xlarge | 250,000 | 200,000 |
| i3en\.6xlarge | 500,000 | 400,000 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/storage-optimized-instances.md |
80b784942242-1 | | i3en\.6xlarge | 500,000 | 400,000 |
| i3en\.12xlarge | 1 million | 800,000 |
| i3en\.24xlarge | 2 million | 1\.6 million |
| i3en\.metal | 2 million | 1\.6 million |
\* For these instances, you can get up to the specified performance\.
As you fill your SSD\-based instance store volumes, the I/O performance that you get decreases\. This is due to the extra work that the SSD controller must do to find available space, rewrite existing data, and erase unused space so that it can be rewritten\. This process of garbage collection results in internal write amplification to the SSD, expressed as the ratio of SSD write operations to user write operations\. This decrease in performance is even larger if the write operations are not in multiples of 4,096 bytes or not aligned to a 4,096\-byte boundary\. If you write a smaller amount of bytes or bytes that are not aligned, the SSD controller must read the surrounding data and store the result in a new location\. This pattern results in significantly increased write amplification, increased latency, and dramatically reduced I/O performance\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/storage-optimized-instances.md |
80b784942242-2 | SSD controllers can use several strategies to reduce the impact of write amplification\. One such strategy is to reserve space in the SSD instance storage so that the controller can more efficiently manage the space available for write operations\. This is called *over\-provisioning*\. The SSD\-based instance store volumes provided to an instance don't have any space reserved for over\-provisioning\. To reduce write amplification, we recommend that you leave 10% of the volume unpartitioned so that the SSD controller can use it for over\-provisioning\. This decreases the storage that you can use, but increases performance even if the disk is close to full capacity\.
For instance store volumes that support TRIM, you can use the TRIM command to notify the SSD controller whenever you no longer need data that you've written\. This provides the controller with more free space, which can reduce write amplification and increase performance\. For more information, see [Instance store volume TRIM support](ssd-instance-store.md#InstanceStoreTrimSupport)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/storage-optimized-instances.md |
03757ccacc1d-0 | The following is a summary of features for storage optimized instances:
| | EBS only | Instance store | Placement group |
| --- | --- | --- | --- |
| D2 | No | HDD | Yes |
| H1 | No | HDD \* | Yes |
| I3 | No | NVMe \* | Yes |
| I3en | No | NVMe \* | Yes |
**\*** The root device volume must be an Amazon EBS volume\.
For more information, see the following:
+ [Amazon EBS and NVMe on Linux instances](nvme-ebs-volumes.md)
+ [Amazon EC2 instance store](InstanceStorage.md)
+ [Placement groups](placement-groups.md) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/storage-optimized-instances.md |
76b764fc87e6-0 | The `d2.8xlarge` instance type provides 36 vCPUs, which might cause launch issues in some Linux operating systems that have a vCPU limit of 32\. We strongly recommend that you use the latest AMIs when you launch `d2.8xlarge` instances\.
The following Linux AMIs support launching `d2.8xlarge` instances with 36 vCPUs:
+ Amazon Linux 2 \(HVM\)
+ Amazon Linux AMI 2018\.03 \(HVM\)
+ Ubuntu Server 14\.04 LTS \(HVM\) or later
+ Red Hat Enterprise Linux 7\.1 \(HVM\)
+ SUSE Linux Enterprise Server 12 \(HVM\)
If you must use a different AMI for your application, and your `d2.8xlarge` instance launch does not complete successfully \(for example, if your instance status changes to `stopped` during launch with a `Client.InstanceInitiatedShutdown` state transition reason\), modify your instance as described in the following procedure to support more than 32 vCPUs so that you can use the `d2.8xlarge` instance type\.
**To update an instance to support more than 32 vCPUs**
1. Launch a D2 instance using your AMI, choosing any D2 instance type other than `d2.8xlarge`\.
1. Update the kernel to the latest version by following your operating system\-specific instructions\. For example, for RHEL 6, use the following command:
```
sudo yum update -y kernel | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/storage-optimized-instances.md |
76b764fc87e6-1 | ```
sudo yum update -y kernel
```
1. Stop the instance\.
1. \(Optional\) Create an AMI from the instance that you can use to launch any additional `d2.8xlarge` instances that you need in the future\.
1. Change the instance type of your stopped instance to `d2.8xlarge` \(choose **Actions**, **Instance Settings**, **Change Instance Type**, and then follow the directions\)\.
1. Start the instance\. If the instance launches properly, you are done\. If the instance still does not boot properly, proceed to the next step\.
1. \(Optional\) If the instance still does not boot properly, the kernel on your instance may not support more than 32 vCPUs\. However, you may be able to boot the instance if you limit the vCPUs\.
1. Change the instance type of your stopped instance to any D2 instance type other than `d2.8xlarge` \(choose **Actions**, **Instance Settings**, **Change Instance Type**, and then follow the directions\)\.
1. Add the `maxcpus=32` option to your boot kernel parameters by following your operating system\-specific instructions\. For example, for RHEL 6, edit the `/boot/grub/menu.lst` file and add the following option to the most recent and active `kernel` entry:
```
default=0
timeout=1 | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/storage-optimized-instances.md |
76b764fc87e6-2 | ```
default=0
timeout=1
splashimage=(hd0,0)/boot/grub/splash.xpm.gz
hiddenmenu
title Red Hat Enterprise Linux Server (2.6.32-504.3.3.el6.x86_64)
root (hd0,0)
kernel /boot/vmlinuz-2.6.32-504.3.3.el6.x86_64 maxcpus=32 console=ttyS0 ro root=UUID=9996863e-b964-47d3-a33b-3920974fdbd9 rd_NO_LUKS KEYBOARDTYPE=pc KEYTABLE=us LANG=en_US.UTF-8 xen_blkfront.sda_is_xvda=1 console=ttyS0,115200n8 console=tty0 rd_NO_MD SYSFONT=latarcyrheb-sun16 crashkernel=auto rd_NO_LVM rd_NO_DM
initrd /boot/initramfs-2.6.32-504.3.3.el6.x86_64.img
```
1. Stop the instance\.
1. \(Optional\) Create an AMI from the instance that you can use to launch any additional `d2.8xlarge` instances that you need in the future\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/storage-optimized-instances.md |
76b764fc87e6-3 | 1. Change the instance type of your stopped instance to `d2.8xlarge` \(choose **Actions**, **Instance Settings**, **Change Instance Type**, and then follow the directions\)\.
1. Start the instance\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/storage-optimized-instances.md |
87a902bea81c-0 | + You must launch storage optimized instances using an HVM AMI\. For more information, see [Linux AMI virtualization types](virtualization_types.md)\.
+ Instances built on the [Nitro System](instance-types.md#ec2-nitro-instances) have the following requirements:
+ [NVMe drivers](nvme-ebs-volumes.md) must be installed
+ [Elastic Network Adapter \(ENA\) drivers](enhanced-networking-ena.md) must be installed
The following Linux AMIs meet these requirements:
+ Amazon Linux 2
+ Amazon Linux AMI 2018\.03
+ Ubuntu 14\.04 \(with `linux-aws` kernel\) or later
+ Red Hat Enterprise Linux 7\.4 or later
+ SUSE Linux Enterprise Server 12 SP2 or later
+ CentOS 7\.4\.1708 or later
+ FreeBSD 11\.1 or later
+ Debian GNU/Linux 9 or later
+ Launching a bare metal instance boots the underlying server, which includes verifying all hardware and firmware components\. This means that it can take 20 minutes from the time the instance enters the running state until it becomes available over the network\.
+ To attach or detach EBS volumes or secondary network interfaces from a bare metal instance requires PCIe native hotplug support\. Amazon Linux 2 and the latest versions of the Amazon Linux AMI support PCIe native hotplug, but earlier versions do not\. You must enable the following Linux kernel configuration options:
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/storage-optimized-instances.md |
87a902bea81c-1 | ```
CONFIG_HOTPLUG_PCI_PCIE=y
CONFIG_PCIEASPM=y
```
+ Bare metal instances use a PCI\-based serial device rather than an I/O port\-based serial device\. The upstream Linux kernel and the latest Amazon Linux AMIs support this device\. Bare metal instances also provide an ACPI SPCR table to enable the system to automatically use the PCI\-based serial device\. The latest Windows AMIs automatically use the PCI\-based serial device\.
+ With FreeBSD AMIs, bare metal instances take nearly an hour to boot and I/O to the local NVMe storage does not complete\. As a workaround, add the following line to `/boot/loader.conf` and reboot:
```
hw.nvme.per_cpu_io_queues="0"
```
+ The `d2.8xlarge` instance type has 36 vCPUs, which might cause launch issues in some Linux operating systems that have a vCPU limit of 32\. For more information, see [Support for vCPUs](#d2-instances-cpu-support)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/storage-optimized-instances.md |
87a902bea81c-2 | + There is a limit on the total number of instances that you can launch in a Region, and there are additional limits on some instance types\. For more information, see [How many instances can I run in Amazon EC2?](https://aws.amazon.com/ec2/faqs/#How_many_instances_can_I_run_in_Amazon_EC2) in the Amazon EC2 FAQ\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/storage-optimized-instances.md |
0143d063d73f-0 | The `standard` mode is a configuration option for burstable performance instances\. It can be enabled or disabled at any time for a running or stopped instance\. You can set `standard` as the default credit option at the account level per AWS Region, per burstable performance instance family, so that all new burstable performance instances in the account launch using the default credit option\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/burstable-performance-instances-standard-mode-concepts.md |
706b862c70df-0 | When a burstable performance instance configured as `standard` is in a running state, it continuously earns \(at a millisecond\-level resolution\) a set rate of earned credits per hour\. For T2 Standard, when the instance is stopped, it loses all its accrued credits, and its credit balance is reset to zero\. When it is restarted, it receives a new set of launch credits, and begins to accrue earned credits\. For T3 and T4g Standard instances, the CPU credit balance persists for seven days after the instance stops and the credits are lost thereafter\. If you start the instance within seven days, no credits are lost\.
T2 Standard instances receive two types of CPU credits: *earned credits* and *launch credits*\. When a T2 Standard instance is in a running state, it continuously earns \(at a millisecond\-level resolution\) a set rate of earned credits per hour\. At start, it has not yet earned credits for a good startup experience; therefore, to provide a good startup experience, it receives launch credits at start, which it spends first while it accrues earned credits\.
T3 and T4g Standard instances do not receive launch credits\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/burstable-performance-instances-standard-mode-concepts.md |
14f3bf8d840f-0 | T2 Standard instances get 30 launch credits per vCPU at launch or start\. For example, a `t2.micro` instance has one vCPU and gets 30 launch credits, while a `t2.xlarge` instance has four vCPUs and gets 120 launch credits\. Launch credits are designed to provide a good startup experience to allow instances to burst immediately after launch before they have accrued earned credits\.
Launch credits are spent first, before earned credits\. Unspent launch credits are accrued in the CPU credit balance, but do not count towards the CPU credit balance limit\. For example, a `t2.micro` instance has a CPU credit balance limit of 144 earned credits\. If it is launched and remains idle for 24 hours, its CPU credit balance reaches 174 \(30 launch credits \+ 144 earned credits\), which is over the limit\. However, after the instance spends the 30 launch credits, the credit balance cannot exceed 144\. For more information about the CPU credit balance limit for each instance size, see the [credit table](burstable-credits-baseline-concepts.md#burstable-performance-instances-credit-table)\.
The following table lists the initial CPU credit allocation received at launch or start, and the number of vCPUs\.
| Instance type | Launch credits | vCPUs |
| --- | --- | --- |
| t1\.micro | 15 | 1 |
| t2\.nano | 30 | 1 |
| t2\.micro | 30 | 1 |
| t2\.small | 30 | 1 |
| t2\.medium | 60 | 2 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/burstable-performance-instances-standard-mode-concepts.md |
14f3bf8d840f-1 | | t2\.small | 30 | 1 |
| t2\.medium | 60 | 2 |
| t2\.large | 60 | 2 |
| t2\.xlarge | 120 | 4 |
| t2\.2xlarge | 240 | 8 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/burstable-performance-instances-standard-mode-concepts.md |
7e579fdf6cdb-0 | There is a limit to the number of times T2 Standard instances can receive launch credits\. The default limit is 100 launches or starts of all T2 Standard instances combined per account, per Region, per rolling 24\-hour period\. For example, the limit is reached when one instance is stopped and started 100 times within a 24\-hour period, or when 100 instances are launched within a 24\-hour period, or other combinations that equate to 100 starts\. New accounts may have a lower limit, which increases over time based on your usage\.
**Tip**
To ensure that your workloads always get the performance they need, switch to [Unlimited mode for burstable performance instances](burstable-performance-instances-unlimited-mode.md) or consider using a larger instance size\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/burstable-performance-instances-standard-mode-concepts.md |
8b60634cc4a4-0 | The following table lists the differences between launch credits and earned credits\.
| | Launch credits | Earned credits |
| --- | --- | --- |
| **Credit earn rate** | T2 Standard instances get 30 launch credits per vCPU at launch or start\. If a T2 instance is switched from `unlimited` to `standard`, it does not get launch credits at the time of switching\. | Each T2 instance continuously earns \(at a millisecond\-level resolution\) a set rate of CPU credits per hour, depending on the instance size\. For more information about the number of CPU credits earned per instance size, see the [credit table](burstable-credits-baseline-concepts.md#burstable-performance-instances-credit-table)\. |
| **Credit earn limit** | The limit for receiving launch credits is 100 launches or starts of all T2 Standard instances combined per account, per Region, per rolling 24\-hour period\. New accounts may have a lower limit, which increases over time based on your usage\. | A T2 instance cannot accrue more credits than the CPU credit balance limit\. If the CPU credit balance has reached its limit, any credits that are earned after the limit is reached are discarded\. Launch credits do not count towards the limit\. For more information about the CPU credit balance limit for each T2 instance size, see the [credit table](burstable-credits-baseline-concepts.md#burstable-performance-instances-credit-table)\. |
| **Credit use** | Launch credits are spent first, before earned credits\. | Earned credits are spent only after all launch credits are spent\. | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/burstable-performance-instances-standard-mode-concepts.md |
8b60634cc4a4-1 | | **Credit use** | Launch credits are spent first, before earned credits\. | Earned credits are spent only after all launch credits are spent\. |
| **Credit expiration** | When a T2 Standard instance is running, launch credits do not expire\. When a T2 Standard instance stops or is switched to T2 Unlimited, all launch credits are lost\. | When a T2 instance is running, earned credits that have accrued do not expire\. When the T2 instance stops, all accrued earned credits are lost\. |
The number of accrued launch credits and accrued earned credits is tracked by the CloudWatch metric `CPUCreditBalance`\. For more information, see `CPUCreditBalance` in the [CloudWatch metrics table](burstable-performance-instances-monitoring-cpu-credits.md#burstable-performance-instances-CW-metrics-table)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/burstable-performance-instances-standard-mode-concepts.md |
75ecc5bc69ab-0 | An *Amazon Machine Image \(AMI\)* is a template that contains a software configuration \(for example, an operating system, an application server, and applications\)\. From an AMI, you launch an *instance*, which is a copy of the AMI running as a virtual server in the cloud\. You can launch multiple instances of an AMI, as shown in the following figure\.
![\[Launch multiple instances from an AMI\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/architecture_ami_instance.png)
Your instances keep running until you stop or terminate them, or until they fail\. If an instance fails, you can launch a new one from the AMI\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-instances-and-amis.md |
278b17ec1a46-0 | An instance is a virtual server in the cloud\. Its configuration at launch is a copy of the AMI that you specified when you launched the instance\.
You can launch different types of instances from a single AMI\. An *instance type* essentially determines the hardware of the host computer used for your instance\. Each instance type offers different compute and memory capabilities\. Select an instance type based on the amount of memory and computing power that you need for the application or software that you plan to run on the instance\. For more information about the hardware specifications for each Amazon EC2 instance type, see [Amazon EC2 Instance Types](https://aws.amazon.com/ec2/instance-types/)\.
After you launch an instance, it looks like a traditional host, and you can interact with it as you would any computer\. You have complete control of your instances; you can use sudo to run commands that require root privileges\.
Your AWS account has a limit on the number of instances that you can have running\. For more information about this limit, and how to request an increase, see [How many instances can I run in Amazon EC2](https://aws.amazon.com/ec2/faqs/#How_many_instances_can_I_run_in_Amazon_EC2) in the Amazon EC2 General FAQ\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-instances-and-amis.md |
1e14bdec6a80-0 | The root device for your instance contains the image used to boot the instance\. For more information, see [Amazon EC2 root device volume](RootDeviceStorage.md)\.
Your instance may include local storage volumes, known as instance store volumes, which you can configure at launch time with block device mapping\. For more information, see [Block device mapping](block-device-mapping-concepts.md)\. After these volumes have been added to and mapped on your instance, they are available for you to mount and use\. If your instance fails, or if your instance is stopped or terminated, the data on these volumes is lost; therefore, these volumes are best used for temporary data\. To keep important data safe, you should use a replication strategy across multiple instances, or store your persistent data in Amazon S3 or Amazon EBS volumes\. For more information, see [Storage](Storage.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-instances-and-amis.md |
9be11c8794a1-0 | + Use AWS Identity and Access Management \(IAM\) to control access to your AWS resources, including your instances\. You can create IAM users and groups under your AWS account, assign security credentials to each, and control the access that each has to resources and services in AWS\. For more information, see [Identity and access management for Amazon EC2](security-iam.md)\.
+ Restrict access by only allowing trusted hosts or networks to access ports on your instance\. For example, you can restrict SSH access by restricting incoming traffic on port 22\. For more information, see [Amazon EC2 security groups for Linux instances](ec2-security-groups.md)\.
+ Review the rules in your security groups regularly, and ensure that you apply the principle of *least privilege*—only open up permissions that you require\. You can also create different security groups to deal with instances that have different security requirements\. Consider creating a bastion security group that allows external logins, and keep the remainder of your instances in a group that does not allow external logins\.
+ Disable password\-based logins for instances launched from your AMI\. Passwords can be found or cracked, and are a security risk\. For more information, see [Disable password\-based remote logins for root](building-shared-amis.md#public-amis-disable-password-logins-for-root)\. For more information about sharing AMIs safely, see [Shared AMIs](sharing-amis.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-instances-and-amis.md |
cfa618a30647-0 | You can stop or terminate a running instance at any time\.
**Stopping an instance**
When an instance is stopped, the instance performs a normal shutdown, and then transitions to a `stopped` state\. All of its Amazon EBS volumes remain attached, and you can start the instance again at a later time\.
You are not charged for additional instance usage while the instance is in a stopped state\. A minimum of one minute is charged for every transition from a stopped state to a running state\. If the instance type was changed while the instance was stopped, you will be charged the rate for the new instance type after the instance is started\. All of the associated Amazon EBS usage of your instance, including root device usage, is billed using typical Amazon EBS prices\.
When an instance is in a stopped state, you can attach or detach Amazon EBS volumes\. You can also create an AMI from the instance, and you can change the kernel, RAM disk, and instance type\.
**Terminating an instance**
When an instance is terminated, the instance performs a normal shutdown\. The root device volume is deleted by default, but any attached Amazon EBS volumes are preserved by default, determined by each volume's `deleteOnTermination` attribute setting\. The instance itself is also deleted, and you can't start the instance again at a later time\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-instances-and-amis.md |
cfa618a30647-1 | To prevent accidental termination, you can disable instance termination\. If you do so, ensure that the `disableApiTermination` attribute is set to `true` for the instance\. To control the behavior of an instance shutdown, such as `shutdown -h` in Linux or `shutdown` in Windows, set the `instanceInitiatedShutdownBehavior` instance attribute to `stop` or `terminate` as desired\. Instances with Amazon EBS volumes for the root device default to `stop`, and instances with instance\-store root devices are always terminated as the result of an instance shutdown\.
For more information, see [Instance lifecycle](ec2-instance-lifecycle.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-instances-and-amis.md |
76514493c4d7-0 | Amazon Web Services \(AWS\) publishes many [Amazon Machine Images \(AMIs\)](finding-an-ami.md) that contain common software configurations for public use\. In addition, members of the AWS developer community have published their own custom AMIs\. You can also create your own custom AMI or AMIs; doing so enables you to quickly and easily start new instances that have everything you need\. For example, if your application is a website or a web service, your AMI could include a web server, the associated static content, and the code for the dynamic pages\. As a result, after you launch an instance from this AMI, your web server starts, and your application is ready to accept requests\.
All AMIs are categorized as either *backed by Amazon EBS*, which means that the root device for an instance launched from the AMI is an Amazon EBS volume, or *backed by instance store*, which means that the root device for an instance launched from the AMI is an instance store volume created from a template stored in Amazon S3\.
The description of an AMI indicates the type of root device \(either `ebs` or `instance store`\)\. This is important because there are significant differences in what you can do with each type of AMI\. For more information about these differences, see [Storage for the root device](ComponentsAMIs.md#storage-for-the-root-device)\.
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\. Existing instances launched from the AMI are not affected\. Therefore, if you are also finished with the instances launched from these AMIs, you should terminate them\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-instances-and-amis.md |
4e5a86e7d510-0 | You can specify multiple private IPv4 and IPv6 addresses for your instances\. The number of network interfaces and private IPv4 and IPv6 addresses that you can specify for an instance depends on the instance type\. For more information, see [IP addresses per network interface per instance type](using-eni.md#AvailableIpPerENI)\.
It can be useful to assign multiple IP addresses to an instance in your VPC to do the following:
+ Host multiple websites on a single server by using multiple SSL certificates on a single server and associating each certificate with a specific IP address\.
+ Operate network appliances, such as firewalls or load balancers, that have multiple IP addresses for each network interface\.
+ Redirect internal traffic to a standby instance in case your instance fails, by reassigning the secondary IP address to the standby instance\.
**Topics**
+ [How multiple IP addresses work](#MultipleIPReqs)
+ [Working with multiple IPv4 addresses](#working-with-multiple-ipv4)
+ [Working with multiple IPv6 addresses](#working-with-multiple-ipv6) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/MultipleIP.md |
89a3e6882b41-0 | The following list explains how multiple IP addresses work with network interfaces:
+ You can assign a secondary private IPv4 address to any network interface\. The network interface need not be attached to the instance\.
+ You can assign multiple IPv6 addresses to a network interface that's in a subnet that has an associated IPv6 CIDR block\.
+ You must choose a secondary IPv4 address from the IPv4 CIDR block range of the subnet for the network interface\.
+ You must choose IPv6 addresses from the IPv6 CIDR block range of the subnet for the network interface\.
+ You associate security groups with network interfaces, not individual IP addresses\. Therefore, each IP address you specify in a network interface is subject to the security group of its network interface\.
+ Multiple IP addresses can be assigned and unassigned to network interfaces attached to running or stopped instances\.
+ Secondary private IPv4 addresses that are assigned to a network interface can be reassigned to another one if you explicitly allow it\.
+ An IPv6 address cannot be reassigned to another network interface; you must first unassign the IPv6 address from the existing network interface\.
+ When assigning multiple IP addresses to a network interface using the command line tools or API, the entire operation fails if one of the IP addresses can't be assigned\.
+ Primary private IPv4 addresses, secondary private IPv4 addresses, Elastic IP addresses, and IPv6 addresses remain with a secondary network interface when it is detached from an instance or attached to an instance\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/MultipleIP.md |
89a3e6882b41-1 | + Although you can't detach the primary network interface from an instance, you can reassign the secondary private IPv4 address of the primary network interface to another network interface\.
The following list explains how multiple IP addresses work with Elastic IP addresses \(IPv4 only\):
+ Each private IPv4 address can be associated with a single Elastic IP address, and vice versa\.
+ When a secondary private IPv4 address is reassigned to another interface, the secondary private IPv4 address retains its association with an Elastic IP address\.
+ When a secondary private IPv4 address is unassigned from an interface, an associated Elastic IP address is automatically disassociated from the secondary private IPv4 address\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/MultipleIP.md |
0aa84d06582f-0 | You can assign a secondary private IPv4 address to an instance, associate an Elastic IPv4 address with a secondary private IPv4 address, and unassign a secondary private IPv4 address\.
**Topics**
+ [Assigning a secondary private IPv4 address](#ManageMultipleIP)
+ [Configuring the operating system on your instance to recognize secondary private IPv4 addresses](#StepTwoConfigOS)
+ [Associating an Elastic IP address with the secondary private IPv4 address](#StepThreeEIP)
+ [Viewing your secondary private IPv4 addresses](#view-privateIPs)
+ [Unassigning a secondary private IPv4 address](#UnassignSPIP) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/MultipleIP.md |
baba7b753b14-0 | You can assign the secondary private IPv4 address to the network interface for an instance as you launch the instance, or after the instance is running\. This section includes the following procedures\.
+ [To assign a secondary private IPv4 address when launching an instance](#assignIP-launch)
+ [To assign a secondary IPv4 address during launch using the command line](#assignIP-launch-cmd)
+ [To assign a secondary private IPv4 address to a network interface](#assignIP-existing)
+ [To assign a secondary private IPv4 to an existing instance using the command line](#assignIP-existing-cmd)<a name="assignIP-launch"></a>
**To assign a secondary private IPv4 address when launching an instance**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. Choose **Launch Instance**\.
1. Select an AMI, then choose an instance type and choose **Next: Configure Instance Details**\.
1. On the **Configure Instance Details** page, for **Network**, select a VPC and for **Subnet**, select a subnet\.
1. In the **Network Interfaces** section, do the following, and then choose **Next: Add Storage**: | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/MultipleIP.md |
baba7b753b14-1 | 1. In the **Network Interfaces** section, do the following, and then choose **Next: Add Storage**:
+ To add another network interface, choose **Add Device**\. The console enables you to specify up to two network interfaces when you launch an instance\. After you launch the instance, choose **Network Interfaces** in the navigation pane to add additional network interfaces\. The total number of network interfaces that you can attach varies by instance type\. For more information, see [IP addresses per network interface per instance type](using-eni.md#AvailableIpPerENI)\.
**Important**
When you add a second network interface, the system can no longer auto\-assign a public IPv4 address\. You will not be able to connect to the instance over IPv4 unless you assign an Elastic IP address to the primary network interface \(eth0\)\. You can assign the Elastic IP address after you complete the Launch wizard\. For more information, see [Working with Elastic IP addresses](elastic-ip-addresses-eip.md#working-with-eips)\.
+ For each network interface, under **Secondary IP addresses**, choose **Add IP**, and then enter a private IP address from the subnet range, or accept the default `Auto-assign` value to let Amazon select an address\.
1. On the next **Add Storage** page, you can specify volumes to attach to the instance besides the volumes specified by the AMI \(such as the root device volume\), and then choose **Next: Add Tags**\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/MultipleIP.md |
baba7b753b14-2 | 1. On the **Add Tags** page, specify tags for the instance, such as a user\-friendly name, and then choose **Next: Configure Security Group**\.
1. On the **Configure Security Group** page, select an existing security group or create a new one\. Choose **Review and Launch**\.
1. On the **Review Instance Launch** page, review your settings, and then choose **Launch** to choose a key pair and launch your instance\. If you're new to Amazon EC2 and haven't created any key pairs, the wizard prompts you to create one\.
**Important**
After you have added a secondary private IP address to a network interface, you must connect to the instance and configure the secondary private IP address on the instance itself\. For more information, see [Configuring the operating system on your instance to recognize secondary private IPv4 addresses](#StepTwoConfigOS)\.<a name="assignIP-launch-cmd"></a>
**To assign a secondary IPv4 address during launch using the command line**
+ You can use one of the following commands\. For more information about these command line interfaces, see [Accessing Amazon EC2](concepts.md#access-ec2)\.
+ The `--secondary-private-ip-addresses` option with the [run\-instances](https://docs.aws.amazon.com/cli/latest/reference/ec2/run-instances.html) command \(AWS CLI\) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/MultipleIP.md |
baba7b753b14-3 | + Define `-NetworkInterface` and specify the `PrivateIpAddresses` parameter with the [New\-EC2Instance](https://docs.aws.amazon.com/powershell/latest/reference/items/New-EC2Instance.html) command \(AWS Tools for Windows PowerShell\)\.<a name="assignIP-existing"></a>
**To assign a secondary private IPv4 address to a network interface**
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 **Network Interfaces**, and then select the network interface attached to the instance\.
1. Choose **Actions**, **Manage IP Addresses**\.
1. Under **IPv4 Addresses**, choose **Assign new IP**\.
1. Enter a specific IPv4 address that's within the subnet range for the instance, or leave the field blank to let Amazon select an IP address for you\.
1. \(Optional\) Choose **Allow reassignment** to allow the secondary private IP address to be reassigned if it is already assigned to another network interface\.
1. Choose **Yes, Update**\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/MultipleIP.md |
baba7b753b14-4 | 1. Choose **Yes, Update**\.
Alternatively, you can assign a secondary private IPv4 address to an instance\. Choose **Instances** in the navigation pane, select the instance, and then choose **Actions**, **Networking**, **Manage IP Addresses**\. You can configure the same information as you did in the steps above\. The IP address is assigned to the primary network interface \(eth0\) for the instance\. <a name="assignIP-existing-cmd"></a>
**To assign a secondary private IPv4 to an existing instance using the command line**
+ You can use one of the following commands\. For more information about these command line interfaces, see [Accessing Amazon EC2](concepts.md#access-ec2)\.
+ [assign\-private\-ip\-addresses](https://docs.aws.amazon.com/cli/latest/reference/ec2/assign-private-ip-addresses.html) \(AWS CLI\)
+ [Register\-EC2PrivateIpAddress](https://docs.aws.amazon.com/powershell/latest/reference/items/Register-EC2PrivateIpAddress.html) \(AWS Tools for Windows PowerShell\) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/MultipleIP.md |
cc39f434d149-0 | After you assign a secondary private IPv4 address to your instance, you need to configure the operating system on your instance to recognize the secondary private IP address\.
+ If you are using Amazon Linux, the ec2\-net\-utils package can take care of this step for you\. It configures additional network interfaces that you attach while the instance is running, refreshes secondary IPv4 addresses during DHCP lease renewal, and updates the related routing rules\. You can immediately refresh the list of interfaces by using the command `sudo service network restart` and then view the up\-to\-date list using `ip addr li`\. If you require manual control over your network configuration, you can remove the ec2\-net\-utils package\. For more information, see [Configuring your network interface using ec2\-net\-utils](using-eni.md#ec2-net-utils)\.
+ If you are using another Linux distribution, see the documentation for your Linux distribution\. Search for information about configuring additional network interfaces and secondary IPv4 addresses\. If the instance has two or more interfaces on the same subnet, search for information about using routing rules to work around asymmetric routing\.
For information about configuring a Windows instance, see [Configuring a secondary private IP address for your Windows instance in a VPC](https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/config-windows-multiple-ip.html) in the *Amazon EC2 User Guide for Windows Instances*\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/MultipleIP.md |
6db117f17b33-0 | **To associate an Elastic IP address with a secondary private IPv4 address**
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** Elastic IPs**\.
1. Choose **Actions**, and then select **Associate address**\.
1. For **Network interface**, select the network interface, and then select the secondary IP address from the **Private IP** list\.
1. Choose **Associate**\.
**To associate an Elastic IP address with a secondary private IPv4 address using the command line**
+ You can use one of the following commands\. For more information about these command line interfaces, see [Accessing Amazon EC2](concepts.md#access-ec2)\.
+ [associate\-address](https://docs.aws.amazon.com/cli/latest/reference/ec2/associate-address.html) \(AWS CLI\)
+ [Register\-EC2Address](https://docs.aws.amazon.com/powershell/latest/reference/items/Register-EC2Address.html) \(AWS Tools for Windows PowerShell\) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/MultipleIP.md |
c049ad0875c9-0 | **To view the private IPv4 addresses assigned to a network interface**
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 **Network Interfaces**\.
1. Select the network interface with private IP addresses to view\.
1. On the **Details** tab in the details pane, check the **Primary private IPv4 IP** and **Secondary private IPv4 IPs** fields for the primary private IPv4 address and any secondary private IPv4 addresses assigned to the network interface\.
**To view the private IPv4 addresses assigned to an 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 **Instances**\.
1. Select the instance with private IPv4 addresses to view\.
1. On the **Description** tab in the details pane, check the **Private IPs** and **Secondary private IPs** fields for the primary private IPv4 address and any secondary private IPv4 addresses assigned to the instance through its network interface\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/MultipleIP.md |
90c83be78f24-0 | If you no longer require a secondary private IPv4 address, you can unassign it from the instance or the network interface\. When a secondary private IPv4 address is unassigned from a network interface, the Elastic IP address \(if it exists\) is also disassociated\.
**To unassign a secondary private IPv4 address from an 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 **Instances**\.
1. Select an instance, choose **Actions**, **Networking**, **Manage IP Addresses**\.
1. Under **IPv4 Addresses**, choose **Unassign** for the IPv4 address to unassign\.
1. Choose **Yes, Update**\.
**To unassign a secondary private IPv4 address from a network interface**
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 **Network Interfaces**\.
1. Select the network interface, choose **Actions**, **Manage IP Addresses**\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/MultipleIP.md |
90c83be78f24-1 | 1. Select the network interface, choose **Actions**, **Manage IP Addresses**\.
1. Under **IPv4 Addresses**, choose **Unassign** for the IPv4 address to unassign\.
1. Choose **Yes, Update**\.
**To unassign a secondary private IPv4 address using the command line**
+ You can use one of the following commands\. For more information about these command line interfaces, see [Accessing Amazon EC2](concepts.md#access-ec2)\.
+ [unassign\-private\-ip\-addresses](https://docs.aws.amazon.com/cli/latest/reference/ec2/unassign-private-ip-addresses.html) \(AWS CLI\)
+ [Unregister\-EC2PrivateIpAddress](https://docs.aws.amazon.com/powershell/latest/reference/items/Unregister-EC2PrivateIpAddress.html) \(AWS Tools for Windows PowerShell\) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/MultipleIP.md |
99ca18422b7d-0 | You can assign multiple IPv6 addresses to your instance, view the IPv6 addresses assigned to your instance, and unassign IPv6 addresses from your instance\.
**Topics**
+ [Assigning multiple IPv6 addresses](#assign-multiple-ipv6)
+ [Viewing your IPv6 addresses](#view-secondary-ipv6)
+ [Unassigning an IPv6 address](#unassign-secondary-ipv6) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/MultipleIP.md |
4aa2aa043391-0 | You can assign one or more IPv6 addresses to your instance during launch or after launch\. To assign an IPv6 address to an instance, the VPC and subnet in which you launch the instance must have an associated IPv6 CIDR block\. For more information, see [VPCs and Subnets](https://docs.aws.amazon.com/vpc/latest/userguide/VPC_Subnets.html) in the *Amazon VPC User Guide*\.
**To assign multiple IPv6 addresses during launch**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. From the dashboard, choose **Launch Instance**\.
1. Select an AMI, choose an instance type, and choose **Next: Configure Instance Details**\. Ensure that you choose an instance type that support IPv6\. For more information, see [Instance types](instance-types.md)\.
1. On the **Configure Instance Details** page, select a VPC from the **Network** list, and a subnet from the **Subnet** list\.
1. In the **Network Interfaces** section, do the following, and then choose **Next: Add Storage**: | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/MultipleIP.md |
4aa2aa043391-1 | 1. In the **Network Interfaces** section, do the following, and then choose **Next: Add Storage**:
+ To assign a single IPv6 address to the primary network interface \(eth0\), under **IPv6 IPs**, choose **Add IP**\. To add a secondary IPv6 address, choose **Add IP** again\. You can enter an IPv6 address from the range of the subnet, or leave the default **Auto\-assign** value to let Amazon choose an IPv6 address from the subnet for you\.
+ Choose **Add Device** to add another network interface and repeat the steps above to add one or more IPv6 addresses to the network interface\. The console enables you to specify up to two network interfaces when you launch an instance\. After you launch the instance, choose **Network Interfaces** in the navigation pane to add additional network interfaces\. The total number of network interfaces that you can attach varies by instance type\. For more information, see [IP addresses per network interface per instance type](using-eni.md#AvailableIpPerENI)\.
1. Follow the next steps in the wizard to attach volumes and tag your instance\.
1. On the **Configure Security Group** page, select an existing security group or create a new one\. If you want your instance to be reachable over IPv6, ensure that your security group has rules that allow access from IPv6 addresses\. For more information, see [Security group rules reference](security-group-rules-reference.md)\. Choose **Review and Launch**\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/MultipleIP.md |
4aa2aa043391-2 | 1. On the **Review Instance Launch** page, review your settings, and then choose **Launch** to choose a key pair and launch your instance\. If you're new to Amazon EC2 and haven't created any key pairs, the wizard prompts you to create one\.
You can use the **Instances** screen Amazon EC2 console to assign multiple IPv6 addresses to an existing instance\. This assigns the IPv6 addresses to the primary network interface \(eth0\) for the instance\. To assign a specific IPv6 address to the instance, ensure that the IPv6 address is not already assigned to another instance or network interface\.
**To assign multiple IPv6 addresses to an existing 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 **Instances**\.
1. Select your instance, choose **Actions**, **Networking**, **Manage IP Addresses**\.
1. Under **IPv6 Addresses**, choose **Assign new IP** for each IPv6 address you want to add\. You can specify an IPv6 address from the range of the subnet, or leave the **Auto\-assign** value to let Amazon choose an IPv6 address for you\.
1. Choose **Yes, Update**\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/MultipleIP.md |
4aa2aa043391-3 | 1. Choose **Yes, Update**\.
Alternatively, you can assign multiple IPv6 addresses to an existing network interface\. The network interface must have been created in a subnet that has an associated IPv6 CIDR block\. To assign a specific IPv6 address to the network interface, ensure that the IPv6 address is not already assigned to another network interface\.
**To assign multiple IPv6 addresses to a network interface**
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 **Network Interfaces**\.
1. Select your network interface, choose **Actions**, **Manage IP Addresses**\.
1. Under **IPv6 Addresses**, choose **Assign new IP** for each IPv6 address you want to add\. You can specify an IPv6 address from the range of the subnet, or leave the **Auto\-assign** value to let Amazon choose an IPv6 address for you\.
1. Choose **Yes, Update**\.
**CLI overview**
You can use one of the following commands\. For more information about these command line interfaces, see [Accessing Amazon EC2](concepts.md#access-ec2)\.
+ **Assign an IPv6 address during launch**: | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/MultipleIP.md |
4aa2aa043391-4 | + **Assign an IPv6 address during launch**:
+ Use the `--ipv6-addresses` or `--ipv6-address-count` options with the [run\-instances](https://docs.aws.amazon.com/cli/latest/reference/ec2/run-instances.html) command \(AWS CLI\)
+ Define `-NetworkInterface` and specify the `Ipv6Addresses` or `Ipv6AddressCount` parameters with the [New\-EC2Instance](https://docs.aws.amazon.com/powershell/latest/reference/items/New-EC2Instance.html) command \(AWS Tools for Windows PowerShell\)\.
+ **Assign an IPv6 address to a network interface**:
+ [assign\-ipv6\-addresses](https://docs.aws.amazon.com/cli/latest/reference/ec2/assign-ipv6-addresses.html) \(AWS CLI\)
+ [Register\-EC2Ipv6AddressList](https://docs.aws.amazon.com/powershell/latest/reference/items/Register-EC2Ipv6AddressList.html) \(AWS Tools for Windows PowerShell\) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/MultipleIP.md |
2c49e8698d88-0 | You can view the IPv6 addresses for an instance or for a network interface\.
**To view the IPv6 addresses assigned to an 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 **Instances**\.
1. Select your instance\. In the details pane, review the **IPv6 IPs** field\.
**To view the IPv6 addresses assigned to a network interface**
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 **Network Interfaces**\.
1. Select your network interface\. In the details pane, review the **IPv6 IPs** field\.
**CLI overview**
You can use one of the following commands\. For more information about these command line interfaces, see [Accessing Amazon EC2](concepts.md#access-ec2)\.
+ **View the IPv6 addresses for an instance**:
+ [describe\-instances](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-instances.html) \(AWS CLI\) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/MultipleIP.md |
2c49e8698d88-1 | + [Get\-EC2Instance](https://docs.aws.amazon.com/powershell/latest/reference/items/Get-EC2Instance.html) \(AWS Tools for Windows PowerShell\)\.
+ **View the IPv6 addresses for a network interface**:
+ [describe\-network\-interfaces](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-network-interfaces.html) \(AWS CLI\)
+ [Get\-EC2NetworkInterface](https://docs.aws.amazon.com/powershell/latest/reference/items/Get-EC2NetworkInterface.html) \(AWS Tools for Windows PowerShell\) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/MultipleIP.md |
86eed3a36f7d-0 | You can unassign an IPv6 address from the primary network interface of an instance, or you can unassign an IPv6 address from a network interface\.
**To unassign an IPv6 address from an 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 **Instances**\.
1. Select your instance, choose **Actions**, **Networking**, **Manage IP Addresses**\.
1. Under **IPv6 Addresses**, choose **Unassign** for the IPv6 address to unassign\.
1. Choose **Yes, Update**\.
**To unassign an IPv6 address from a network interface**
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 **Network Interfaces**\.
1. Select your network interface, choose **Actions**, **Manage IP Addresses**\.
1. Under **IPv6 Addresses**, choose **Unassign** for the IPv6 address to unassign\.
1. Choose **Save**\.
**CLI overview** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/MultipleIP.md |
86eed3a36f7d-1 | 1. Choose **Save**\.
**CLI overview**
You can use one of the following commands\. For more information about these command line interfaces, see [Accessing Amazon EC2](concepts.md#access-ec2)\.
+ [unassign\-ipv6\-addresses](https://docs.aws.amazon.com/cli/latest/reference/ec2/unassign-ipv6-addresses.html) \(AWS CLI\)
+ [Unregister\-EC2Ipv6AddressList](https://docs.aws.amazon.com/powershell/latest/reference/items/Unregister-EC2Ipv6AddressList.html) \(AWS Tools for Windows PowerShell\)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/MultipleIP.md |
2b0c802114be-0 | Swap space in Linux can be used when a system requires more memory than it has been physically allocated\. When swap space is enabled, Linux systems can swap infrequently used memory pages from physical memory to swap space \(either a dedicated partition or a swap file in an existing file system\) and free up that space for memory pages that require high\-speed access\.
**Note**
Using swap space for memory paging is not as fast or efficient as using RAM\. If your workload is regularly paging memory into swap space, you should consider migrating to a larger instance type with more RAM\. For more information, see [Changing the instance type](ec2-instance-resize.md)\.
The `c1.medium` and `m1.small` instance types have a limited amount of physical memory to work with, and they are given a 900 MiB swap volume at launch time to act as virtual memory for Linux AMIs\. Although the Linux kernel sees this swap space as a partition on the root device, it is actually a separate instance store volume, regardless of your root device type\.
Amazon Linux automatically enables and uses this swap space, but your AMI may require some additional steps to recognize and use this swap space\. To see if your instance is using swap space, you can use the swapon \-s command\.
```
[ec2-user ~]$ swapon -s
Filename Type Size Used Priority
/dev/xvda3 partition 917500 0 -1
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-store-swap-volumes.md |
2b0c802114be-1 | Filename Type Size Used Priority
/dev/xvda3 partition 917500 0 -1
```
The above instance has a 900 MiB swap volume attached and enabled\. If you don't see a swap volume listed with this command, you may need to enable swap space for the device\. Check your available disks using the lsblk command\.
```
[ec2-user ~]$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
xvda1 202:1 0 8G 0 disk /
xvda3 202:3 0 896M 0 disk
```
Here, the swap volume `xvda3` is available to the instance, but it is not enabled \(notice that the `MOUNTPOINT` field is empty\)\. You can enable the swap volume with the swapon command\.
**Note**
You must prepend `/dev/` to the device name listed by lsblk\. Your device may be named differently, such as `sda3`, `sde3`, or `xvde3`\. Use the device name for your system in the command below\.
```
[ec2-user ~]$ sudo swapon /dev/xvda3
```
Now the swap space should show up in lsblk and swapon \-s output\.
```
[ec2-user ~]$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-store-swap-volumes.md |
2b0c802114be-2 | ```
[ec2-user ~]$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
xvda1 202:1 0 8G 0 disk /
xvda3 202:3 0 896M 0 disk [SWAP]
[ec2-user ~]$ swapon -s
Filename Type Size Used Priority
/dev/xvda3 partition 917500 0 -1
```
You also need to edit your `/etc/fstab` file so that this swap space is automatically enabled at every system boot\.
```
[ec2-user ~]$ sudo vim /etc/fstab
```
Append the following line to your `/etc/fstab` file \(using the swap device name for your system\):
```
/dev/xvda3 none swap sw 0 0
```
**To use an instance store volume as swap space**
Any instance store volume can be used as swap space\. For example, the `m3.medium` instance type includes a 4 GB SSD instance store volume that is appropriate for swap space\. If your instance store volume is much larger \(for example, 350 GB\), you may consider partitioning the volume with a smaller swap partition of 4\-8 GB and the rest for a data volume\.
**Note** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-store-swap-volumes.md |
2b0c802114be-3 | **Note**
This procedure applies only to instance types that support instance storage\. For a list of supported instance types, see [Instance store volumes](InstanceStorage.md#instance-store-volumes)\.
1. <a name="step_swap_start"></a>List the block devices attached to your instance to get the device name for your instance store volume\.
```
[ec2-user ~]$ lsblk -p
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
/dev/xvdb 202:16 0 4G 0 disk /media/ephemeral0
/dev/xvda1 202:1 0 8G 0 disk /
```
In this example, the instance store volume is `/dev/xdvb`\. Because this is an Amazon Linux instance, the instance store volume is formatted and mounted at `/media/ephemeral0`; not all Linux operating systems do this automatically\.
1. \(Optional\) If your instance store volume is mounted \(it lists a `MOUNTPOINT` in the lsblk command output\), unmount it with the following command\.
```
[ec2-user ~]$ sudo umount /dev/xvdb
```
1. <a name="step_mkswap"></a>Set up a Linux swap area on the device with the mkswap command\.
```
[ec2-user ~]$ sudo mkswap /dev/xvdb | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-store-swap-volumes.md |
2b0c802114be-4 | ```
[ec2-user ~]$ sudo mkswap /dev/xvdb
mkswap: /dev/xvdb: warning: wiping old ext3 signature.
Setting up swapspace version 1, size = 4188668 KiB
no label, UUID=b4f63d28-67ed-46f0-b5e5-6928319e620b
```
1. Enable the new swap space\.
```
[ec2-user ~]$ sudo swapon /dev/xvdb
```
1. <a name="step_swap_enable"></a>Verify that the new swap space is being used\.
```
[ec2-user ~]$ swapon -s
Filename Type Size Used Priority
/dev/xvdb partition 4188668 0 -1
```
1. Edit your `/etc/fstab` file so that this swap space is automatically enabled at every system boot\.
```
[ec2-user ~]$ sudo vim /etc/fstab
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-store-swap-volumes.md |
2b0c802114be-5 | ```
[ec2-user ~]$ sudo vim /etc/fstab
```
If your `/etc/fstab` file has an entry for `/dev/xvdb` \(or `/dev/sdb`\) change it to match the line below; if it does not have an entry for this device, append the following line to your `/etc/fstab` file \(using the swap device name for your system\):
```
/dev/xvdb none swap sw 0 0
```
**Important**
Instance store volume data is lost when an instance is stopped; this includes the instance store swap space formatting created in [Step 3](#step_mkswap)\. If you stop and restart an instance that has been configured to use instance store swap space, you must repeat [Step 1](#step_swap_start) through [Step 5](#step_swap_enable) on the new instance store volume\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-store-swap-volumes.md |
739840e7ee61-0 | You can view descriptive information about your EBS volumes\. For example, you can view information about all volumes in a specific Region or view detailed information about a single volume, including its size, volume type, whether the volume is encrypted, which master key was used to encrypt the volume, and the specific instance to which the volume is attached\.
You can get additional information about your EBS volumes, such as how much disk space is available, from the operating system on the instance\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-describing-volumes.md |
8ba2a316732d-0 | **To view information about an EBS volume using 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. \(Optional\) Use the **Filter** options in the Search bar to display only the volumes that interest you\. For example, if you know the instance ID you want to see volumes for, go to the Search bar and choose **Instance ID** from the filter menu, then choose the instance ID you want from the list provided\. To remove a filter, choose it again\.
1. To view more information about a volume, select it\.
1. In the details pane, you can inspect the information provided about the volume\. **Attachment information** shows the instance ID this volume is attached to and the device name under which it is attached\.
1. \(Optional\) Choose the **Attachment information** link to view instance details\.
**To view the EBS volumes that are attached to an instance using 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 **Instances**\.
1. To view more information about an instance, select it\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-describing-volumes.md |
8ba2a316732d-1 | 1. In the navigation pane, choose **Instances**\.
1. To view more information about an instance, select it\.
1. In the details pane, you can inspect the information provided about root and block devices\. Choose the device name link to show information on the volume attached under that device name\.
1. \(Optional\) Choose the **EBS ID** link to view details for the volume attached to this instance under the device name chosen in the prior step\.
**To view information about an EBS volume using the command line**
You can use one of the following commands to view volume attributes\. For more information, see [Accessing Amazon EC2](concepts.md#access-ec2)\.
+ [describe\-volumes](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-volumes.html) \(AWS CLI\)
+ [Get\-EC2Volume](https://docs.aws.amazon.com/powershell/latest/reference/items/Get-EC2Volume.html) \(AWS Tools for Windows PowerShell\) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-describing-volumes.md |
0e489d7b4cf9-0 | Volume state describes the availability of an Amazon EBS volume\. You can view the volume state in the **State** column on the **Volumes** page in the console, or by using the [describe\-volumes](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-volumes.html) AWS CLI command\.
The possible volume states are:
creating
The volume is being created\.
available
The volume is not attached to an instance\.
in\-use
The volume is attached to an instance\.
deleting
The volume is being deleted\.
deleted
The volume is deleted\.
error
The underlying hardware related to your EBS volume has failed, and the data associated with the volume is unrecoverable\. For information about how to restore the volume or recover the data on the volume, see [My EBS volume has a status of "error"](http://aws.amazon.com/premiumsupport/knowledge-center/ebs-error-status/)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-describing-volumes.md |
46c2044cd1ec-0 | You can get additional information about your EBS volumes from Amazon CloudWatch\. For more information, see [Amazon CloudWatch metrics for Amazon EBS](using_cloudwatch_ebs.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-describing-volumes.md |
e1ceafec301e-0 | You can get additional information about your EBS volumes, such as how much disk space is available, from the Linux operating system on the instance\. For example, use the following command:
```
[ec2-user ~]$ df -hT /dev/xvda1
Filesystem Type Size Used Avail Use% Mounted on
/dev/xvda1 xfs 8.0G 1.2G 6.9G 15% /
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-describing-volumes.md |
874a8579010d-0 | There are several GPU setting optimizations that you can perform to achieve the best performance on G3, G4, P2, P3, and P3dn instances\. By default, the NVIDIA driver uses an autoboost feature, which varies the GPU clock speeds\. By disabling the autoboost feature and setting the GPU clock speeds to their maximum frequency, you can consistently achieve the maximum performance with your GPU instances\. The following procedure helps you to configure the GPU settings to be persistent, disable the autoboost feature, and set the GPU clock speeds to their maximum frequency\.
**To optimize GPU settings**
1. Configure the GPU settings to be persistent\. This command can take several minutes to run\.
```
[ec2-user ~]$ sudo nvidia-persistenced
```
1. Disable the autoboost feature for all GPUs on the instance\.
```
[ec2-user ~]$ sudo nvidia-smi --auto-boost-default=0
```
**Note**
GPUs on P3, P3dn, and G4 instances do not support autoboost\.
1. Set all GPU clock speeds to their maximum frequency\. Use the memory and graphics clock speeds specified in the following commands\.
**Note**
Some versions of the NVIDIA driver do not allow setting application clock speed and throw a `"Setting applications clocks is not supported for GPU …"` error, which you can ignore\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/optimize_gpu.md |
Subsets and Splits