id
stringlengths 14
16
| text
stringlengths 1
2.43k
| source
stringlengths 99
229
|
|---|---|---|
be7d3d39adf0-1 | Snapshots are incremental backups, meaning that only the blocks on the volume that have changed after your most recent snapshot are saved\. If you have a volume with 100 GiB of data, but only 5 GiB of data have changed since your last snapshot, only the 5 GiB of modified data is written to Amazon S3\. Even though snapshots are saved incrementally, the snapshot deletion process is designed so that you need to retain only the most recent snapshot\.
To help categorize and manage your volumes and snapshots, you can tag them with metadata of your choice\. For more information, see [Tagging your Amazon EC2 resources](Using_Tags.md)\.
To back up your volumes automatically, you can use [Amazon Data Lifecycle Manager](snapshot-lifecycle.md) or [AWS Backup](https://docs.aws.amazon.com/aws-backup/latest/devguide/)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-volumes.md |
274f2935918d-0 | EBS volumes support live configuration changes while in production\. You can modify volume type, volume size, and IOPS capacity without service interruptions\. For more information, see [Amazon EBS Elastic Volumes](ebs-modify-volume.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-volumes.md |
3734f9ef885c-0 | You can see the credit balance for each instance in the Amazon EC2 per\-instance metrics of the CloudWatch console\.
**Topics**
+ [Additional CloudWatch metrics for burstable performance instances](#burstable-performance-instances-cw-metrics)
+ [Calculating CPU credit usage](#burstable-performance-instances-calculating-credit-use) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/burstable-performance-instances-monitoring-cpu-credits.md |
d1b49dd65ba2-0 | Burstable performance instances have these additional CloudWatch metrics, which are updated every five minutes:
+ `CPUCreditUsage` – The number of CPU credits spent during the measurement period\.
+ `CPUCreditBalance` – The number of CPU credits that an instance has accrued\. This balance is depleted when the CPU bursts and CPU credits are spent more quickly than they are earned\.
+ `CPUSurplusCreditBalance` – The number of surplus CPU credits spent to sustain CPU utilization when the `CPUCreditBalance` value is zero\.
+ `CPUSurplusCreditsCharged` – The number of surplus CPU credits exceeding the [maximum number of CPU credits](burstable-credits-baseline-concepts.md#burstable-performance-instances-credit-table) that can be earned in a 24\-hour period, and thus attracting an additional charge\.
The last two metrics apply only to instances configured as `unlimited`\.
The following table describes the CloudWatch metrics for burstable performance instances\. For more information, see [List the available CloudWatch metrics for your instances](viewing_metrics_with_cloudwatch.md)\.
| Metric | Description |
| --- | --- | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/burstable-performance-instances-monitoring-cpu-credits.md |
d1b49dd65ba2-1 | | Metric | Description |
| --- | --- |
| CPUCreditUsage | The number of CPU credits spent by the instance for CPU utilization\. One CPU credit equals one vCPU running at 100% utilization for one minute or an equivalent combination of vCPUs, utilization, and time \(for example, one vCPU running at 50% utilization for two minutes or two vCPUs running at 25% utilization for two minutes\)\. CPU credit metrics are available at a five\-minute frequency only\. If you specify a period greater than five minutes, use the `Sum` statistic instead of the `Average` statistic\. Units: Credits \(vCPU\-minutes\) | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/burstable-performance-instances-monitoring-cpu-credits.md |
d1b49dd65ba2-2 | | CPUCreditBalance | The number of earned CPU credits that an instance has accrued since it was launched or started\. For T2 Standard, the `CPUCreditBalance` also includes the number of launch credits that have been accrued\. Credits are accrued in the credit balance after they are earned, and removed from the credit balance when they are spent\. The credit balance has a maximum limit, determined by the instance size\. After the limit is reached, any new credits that are earned are discarded\. For T2 Standard, launch credits do not count towards the limit\. The credits in the `CPUCreditBalance` are available for the instance to spend to burst beyond its baseline CPU utilization\. When an instance is running, credits in the `CPUCreditBalance` do not expire\. When a T3 or T4g instance stops, the `CPUCreditBalance` value persists for seven days\. Thereafter, all accrued credits are lost\. When a T2 instance stops, the `CPUCreditBalance` value does not persist, and all accrued credits are lost\. CPU credit metrics are available at a five\-minute frequency only\. Units: Credits \(vCPU\-minutes\) |
| CPUSurplusCreditBalance | The number of surplus credits that have been spent by an `unlimited` instance when its `CPUCreditBalance` value is zero\. The `CPUSurplusCreditBalance` value is paid down by earned CPU credits\. If the number of surplus credits exceeds the maximum number of credits that the instance can earn in a 24\-hour period, the spent surplus credits above the maximum incur an additional charge\. Units: Credits \(vCPU\-minutes\) | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/burstable-performance-instances-monitoring-cpu-credits.md |
d1b49dd65ba2-3 | | CPUSurplusCreditsCharged | The number of spent surplus credits that are not paid down by earned CPU credits, and which thus incur an additional charge\. Spent surplus credits are charged when any of the following occurs: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/burstable-performance-instances-monitoring-cpu-credits.html) Units: Credits \(vCPU\-minutes\) | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/burstable-performance-instances-monitoring-cpu-credits.md |
e11ce6878b9d-0 | The CPU credit usage of instances is calculated using the instance CloudWatch metrics described in the preceding table\.
Amazon EC2 sends the metrics to CloudWatch every five minutes\. A reference to the *prior* value of a metric at any point in time implies the previous value of the metric, sent *five minutes ago*\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/burstable-performance-instances-monitoring-cpu-credits.md |
827559ea9a59-0 | + The CPU credit balance increases if CPU utilization is below the baseline, when the credits spent are less than the credits earned in the prior five\-minute interval\.
+ The CPU credit balance decreases if CPU utilization is above the baseline, when the credits spent are more than the credits earned in the prior five\-minute interval\.
Mathematically, this is captured by the following equation:
**Example**
```
CPUCreditBalance = prior CPUCreditBalance + [Credits earned per hour * (5/60) - CPUCreditUsage]
```
The size of the instance determines the number of credits that the instance can earn per hour and the number of earned credits that it can accrue in the credit balance\. For information about the number of credits earned per hour, and the credit balance limit for each instance size, see the [credit table](burstable-credits-baseline-concepts.md#burstable-performance-instances-credit-table)\.
**Example**
This example uses a `t3.nano` instance\. To calculate the `CPUCreditBalance` value of the instance, use the preceding equation as follows:
+ `CPUCreditBalance` – The current credit balance to calculate\.
+ `prior CPUCreditBalance` – The credit balance five minutes ago\. In this example, the instance had accrued two credits\.
+ `Credits earned per hour` – A `t3.nano` instance earns six credits per hour\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/burstable-performance-instances-monitoring-cpu-credits.md |
827559ea9a59-1 | + `Credits earned per hour` – A `t3.nano` instance earns six credits per hour\.
+ `5/60` – Represents the five\-minute interval between CloudWatch metric publication\. Multiply the credits earned per hour by 5/60 \(five minutes\) to get the number of credits that the instance earned in the past five minutes\. A `t3.nano` instance earns 0\.5 credits every five minutes\.
+ `CPUCreditUsage` – How many credits the instance spent in the past five minutes\. In this example, the instance spent one credit in the past five minutes\.
Using these values, you can calculate the `CPUCreditBalance` value:
**Example**
```
CPUCreditBalance = 2 + [0.5 - 1] = 1.5
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/burstable-performance-instances-monitoring-cpu-credits.md |
aad64a1163aa-0 | When a burstable performance instance needs to burst above the baseline, it always spends accrued credits before spending surplus credits\. When it depletes its accrued CPU credit balance, it can spend surplus credits to burst CPU for as long as it needs\. When CPU utilization falls below the baseline, surplus credits are always paid down before the instance accrues earned credits\.
We use the term `Adjusted balance` in the following equations to reflect the activity that occurs in this five\-minute interval\. We use this value to arrive at the values for the `CPUCreditBalance` and `CPUSurplusCreditBalance` CloudWatch metrics\.
**Example**
```
Adjusted balance = [prior CPUCreditBalance - prior CPUSurplusCreditBalance] + [Credits earned per hour * (5/60) - CPUCreditUsage]
```
A value of `0` for `Adjusted balance` indicates that the instance spent all its earned credits for bursting, and no surplus credits were spent\. As a result, both `CPUCreditBalance` and `CPUSurplusCreditBalance` are set to `0`\.
A positive `Adjusted balance` value indicates that the instance accrued earned credits, and previous surplus credits, if any, were paid down\. As a result, the `Adjusted balance` value is assigned to `CPUCreditBalance`, and the `CPUSurplusCreditBalance` is set to `0`\. The instance size determines the [maximum number of credits](burstable-credits-baseline-concepts.md#burstable-performance-instances-credit-table) that it can accrue\.
**Example** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/burstable-performance-instances-monitoring-cpu-credits.md |
aad64a1163aa-1 | **Example**
```
CPUCreditBalance = min [max earned credit balance, Adjusted balance]
CPUSurplusCreditBalance = 0
```
A negative `Adjusted balance` value indicates that the instance spent all its earned credits that it accrued and, in addition, also spent surplus credits for bursting\. As a result, the `Adjusted balance` value is assigned to `CPUSurplusCreditBalance` and `CPUCreditBalance` is set to `0`\. Again, the instance size determines the [maximum number of credits](burstable-credits-baseline-concepts.md#burstable-performance-instances-credit-table) that it can accrue\.
**Example**
```
CPUSurplusCreditBalance = min [max earned credit balance, -Adjusted balance]
CPUCreditBalance = 0
```
If the surplus credits spent exceed the maximum credits that the instance can accrue, the surplus credit balance is set to the maximum, as shown in the preceding equation\. The remaining surplus credits are charged as represented by the `CPUSurplusCreditsCharged` metric\.
**Example**
```
CPUSurplusCreditsCharged = max [-Adjusted balance - max earned credit balance, 0]
```
Finally, when the instance terminates, any surplus credits tracked by the `CPUSurplusCreditBalance` are charged\. If the instance is switched from `unlimited` to `standard`, any remaining `CPUSurplusCreditBalance` is also charged\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/burstable-performance-instances-monitoring-cpu-credits.md |
8a044882d0d2-0 | When you launch an instance, the *root device volume* contains the image used to boot the instance\. When we introduced Amazon EC2, all AMIs were backed by Amazon EC2 instance store, which means the root device for an instance launched from the AMI is an instance store volume created from a template stored in Amazon S3\. After we introduced Amazon EBS, we introduced AMIs that are backed by Amazon EBS\. This means that the root device for an instance launched from the AMI is an Amazon EBS volume created from an Amazon EBS snapshot\.
You can choose between AMIs backed by Amazon EC2 instance store and AMIs backed by Amazon EBS\. We recommend that you use AMIs backed by Amazon EBS, because they launch faster and use persistent storage\.
**Important**
Only the following instance types support an instance store volume as the root device: C3, D2, G2, I2, M3, and R3\.
For more information about the device names Amazon EC2 uses for your root volumes, see [Device naming on Linux instances](device_naming.md)\.
**Topics**
+ [Root device storage concepts](#RootDeviceStorageConcepts)
+ [Choosing an AMI by root device type](#choose-an-ami-by-root-device)
+ [Determining the root device type of your instance](#display-instance-root-device-type)
+ [Changing the root volume to persist](#Using_RootDeviceStorage) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/RootDeviceStorage.md |
920e5520d16f-0 | You can launch an instance from either an instance store\-backed AMI or an Amazon EBS\-backed AMI\. The description of an AMI includes which type of AMI it is; you'll see the root device referred to in some places as either `ebs` \(for Amazon EBS\-backed\) or `instance store` \(for instance store\-backed\)\. This is important because there are significant differences between 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)\.
**Instance store\-backed instances**
Instances that use instance stores for the root device automatically have one or more instance store volumes available, with one volume serving as the root device volume\. When an instance is launched, the image that is used to boot the instance is copied to the root volume\. Note that you can optionally use additional instance store volumes, depending on the instance type\.
Any data on the instance store volumes persists as long as the instance is running, but this data is deleted when the instance is terminated \(instance store\-backed instances do not support the **Stop** action\) or if it fails \(such as if an underlying drive has issues\)\.
![\[Root device on an Amazon EC2 instance store-backed instance\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/instance_store_backed_instance.png) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/RootDeviceStorage.md |
920e5520d16f-1 | After an instance store\-backed instance fails or terminates, it cannot be restored\. If you plan to use Amazon EC2 instance store\-backed instances, we highly recommend that you distribute the data on your instance stores across multiple Availability Zones\. You should also back up critical data from your instance store volumes to persistent storage on a regular basis\.
For more information, see [Amazon EC2 instance store](InstanceStorage.md)\.
**Amazon EBS\-backed instances**
Instances that use Amazon EBS for the root device automatically have an Amazon EBS volume attached\. When you launch an Amazon EBS\-backed instance, we create an Amazon EBS volume for each Amazon EBS snapshot referenced by the AMI you use\. You can optionally use other Amazon EBS volumes or instance store volumes, depending on the instance type\.
![\[Root device volume and other Amazon EBS volumes of an Amazon EBS-backed instance\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/ebs_backed_instance.png)
An Amazon EBS\-backed instance can be stopped and later restarted without affecting data stored in the attached volumes\. There are various instance– and volume\-related tasks you can do when an Amazon EBS\-backed instance is in a stopped state\. For example, you can modify the properties of the instance, change its size, or update the kernel it is using, or you can attach your root volume to a different running instance for debugging or any other purpose\.
If an Amazon EBS\-backed instance fails, you can restore your session by following one of these methods: | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/RootDeviceStorage.md |
920e5520d16f-2 | If an Amazon EBS\-backed instance fails, you can restore your session by following one of these methods:
+ Stop and then start again \(try this method first\)\.
+ Automatically snapshot all relevant volumes and create a new AMI\. For more information, see [Creating an Amazon EBS\-backed Linux AMI](creating-an-ami-ebs.md)\.
+ Attach the volume to the new instance by following these steps:
1. Create a snapshot of the root volume\.
1. Register a new AMI using the snapshot\.
1. Launch a new instance from the new AMI\.
1. Detach the remaining Amazon EBS volumes from the old instance\.
1. Reattach the Amazon EBS volumes to the new instance\.
For more information, see [Amazon EBS volumes](ebs-volumes.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/RootDeviceStorage.md |
fb884315bd9b-0 | The AMI that you specify when you launch your instance determines the type of root device volume that your instance has\.
**To choose an Amazon EBS\-backed AMI using the console**
1. Open the Amazon EC2 console\.
1. In the navigation pane, choose **AMIs**\.
1. From the filter lists, select the image type \(such as **Public images**\)\. In the search bar choose **Platform** to select the operating system \(such as **Amazon Linux**\), and **Root Device Type** to select **EBS images**\.
1. \(Optional\) To get additional information to help you make your choice, choose the **Show/Hide Columns** icon, update the columns to display, and choose **Close**\.
1. Choose an AMI and write down its AMI ID\.
**To choose an instance store\-backed AMI using the console**
1. Open the Amazon EC2 console\.
1. In the navigation pane, choose **AMIs**\.
1. From the filter lists, select the image type \(such as **Public images**\)\. In the search bar, choose **Platform** to select the operating system \(such as **Amazon Linux**\), and **Root Device Type** to select **Instance store**\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/RootDeviceStorage.md |
fb884315bd9b-1 | 1. \(Optional\) To get additional information to help you make your choice, choose the **Show/Hide Columns** icon, update the columns to display, and choose **Close**\.
1. Choose an AMI and write down its AMI ID\.
**To verify the type of the root device volume of an AMI 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)\.
+ [describe\-images](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-images.html) \(AWS CLI\)
+ [Get\-EC2Image](https://docs.aws.amazon.com/powershell/latest/userguide/pstools-ec2-get-amis.html#pstools-ec2-get-image) \(AWS Tools for Windows PowerShell\) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/RootDeviceStorage.md |
91aa524fec71-0 | **To determine the root device type of an instance using the console**
1. Open the Amazon EC2 console\.
1. In the navigation pane, choose **Instances**, and select the instance\.
1. Check the value of **Root device type** in the **Description** tab as follows:
+ If the value is `ebs`, this is an Amazon EBS\-backed instance\.
+ If the value is `instance store`, this is an instance store\-backed instance\.
**To determine the root device type of an 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)\.
+ [describe\-instances](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-instances.html) \(AWS CLI\)
+ [Get\-EC2Instance](https://docs.aws.amazon.com/powershell/latest/reference/items/Get-EC2Instance.html) \(AWS Tools for Windows PowerShell\) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/RootDeviceStorage.md |
b0f687c4826c-0 | By default, the root volume for an AMI backed by Amazon EBS is deleted when the instance terminates\. You can change the default behavior to ensure that the volume persists after the instance terminates\. To change the default behavior, set the `DeleteOnTermination` attribute to `false` using a block device mapping\.
**Topics**
+ [Configuring the root volume to persist during instance launch](#Using_ChangeRootDeviceVolumeToPersist)
+ [Configuring the root volume to persist for an existing instance](#set-deleteOnTermination-aws-cli)
+ [Confirming that a root volume is configured to persist](#Using_ConfirmRootDeviceVolumeToPersist) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/RootDeviceStorage.md |
1bc51b90605f-0 | You can configure the root volume to persist when you launch an instance using the Amazon EC2 console or the command line tools\.
**To configure the root volume to persist when you launch 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** and then choose **Launch Instance**\.
1. On the **Choose an Amazon Machine Image \(AMI\)** page, select the AMI to use and choose **Select**\.
1. Follow the wizard to complete the **Choose an Instance Type** and **Configure Instance Details** pages\.
1. On the **Add Storage** page, deselect **Delete On Termination** for the root volume\.
1. Complete the remaining wizard pages, and then choose **Launch**\.
**To configure the root volume to persist when you launch an instance using the AWS CLI**
Use the [run\-instances](https://docs.aws.amazon.com/cli/latest/reference/ec2/run-instances.html) command and include a block device mapping that sets the `DeleteOnTermination` attribute to `false`\.
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/RootDeviceStorage.md |
1bc51b90605f-1 | ```
$ aws ec2 run-instances --block-device-mappings file://mapping.json ...other parameters...
```
Specify the following in `mapping.json`\.
```
[
{
"DeviceName": "/dev/sda1",
"Ebs": {
"DeleteOnTermination": false
}
}
]
```
**To configure the root volume to persist when you launch an instance using the Tools for Windows PowerShell**
Use the [New\-EC2Instance](https://docs.aws.amazon.com/powershell/latest/reference/items/New-EC2Instance.html) command and include a block device mapping that sets the `DeleteOnTermination` attribute to `false`\.
```
C:\> $ebs = New-Object Amazon.EC2.Model.EbsBlockDevice
C:\> $ebs.DeleteOnTermination = $false
C:\> $bdm = New-Object Amazon.EC2.Model.BlockDeviceMapping
C:\> $bdm.DeviceName = "dev/xvda"
C:\> $bdm.Ebs = $ebs | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/RootDeviceStorage.md |
1bc51b90605f-2 | C:\> $bdm.DeviceName = "dev/xvda"
C:\> $bdm.Ebs = $ebs
C:\> New-EC2Instance -ImageId ami-0abcdef1234567890 -BlockDeviceMapping $bdm ...other parameters...
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/RootDeviceStorage.md |
5e00418f2345-0 | You can configure the root volume to persist for a running instance using the command line tools only\.
**To configure the root volume to persist for an existing instance using the AWS CLI**
Use the [modify\-instance\-attribute](https://docs.aws.amazon.com/cli/latest/reference/ec2/modify-instance-attribute.html) command with a block device mapping that sets the `DeleteOnTermination` attribute to `false`\.
```
aws ec2 modify-instance-attribute --instance-id i-1234567890abcdef0 --block-device-mappings "[{\"DeviceName\": \"/dev/xvda\",\"Ebs\":{\"DeleteOnTermination\":false}}]"
```
**To configure the root volume to persist for an existing instance using the AWS Tools for Windows PowerShell**
Use the [Edit\-EC2InstanceAttribute](https://docs.aws.amazon.com/powershell/latest/reference/items/Edit-EC2InstanceAttribute.html) command with a block device mapping that sets the `DeleteOnTermination` attribute to `false`\.
```
C:\> $ebs = New-Object Amazon.EC2.Model.EbsInstanceBlockDeviceSpecification
C:\> $ebs.DeleteOnTermination = $false | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/RootDeviceStorage.md |
5e00418f2345-1 | C:\> $ebs.DeleteOnTermination = $false
C:\> $bdm = New-Object Amazon.EC2.Model.InstanceBlockDeviceMappingSpecification
C:\> $bdm.DeviceName = "/dev/xvda"
C:\> $bdm.Ebs = $ebs
C:\> Edit-EC2InstanceAttribute -InstanceId i-1234567890abcdef0 -BlockDeviceMapping $bdm
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/RootDeviceStorage.md |
9103b25244a5-0 | You can confirm that a root volume is configured to persist using the Amazon EC2 console or the command line tools\.
**To confirm that a root volume is configured to persist using the Amazon EC2 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** and then select the instance\.
1. In the **Description** tab, choose the entry for **Root device**\. If **Delete on termination** is set to `false`, the volume is configured to persist\.
**To confirm that a root volume is configured to persist using the AWS CLI**
Use the [describe\-instances](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-instances.html) command and verify that the `DeleteOnTermination` attribute in the `BlockDeviceMappings` response element is set to `false`\.
```
$ aws ec2 describe-instances --instance-id i-1234567890abcdef0
```
```
...
"BlockDeviceMappings": [
{
"DeviceName": "/dev/sda1",
"Ebs": {
"Status": "attached", | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/RootDeviceStorage.md |
9103b25244a5-1 | "DeviceName": "/dev/sda1",
"Ebs": {
"Status": "attached",
"DeleteOnTermination": false,
"VolumeId": "vol-1234567890abcdef0",
"AttachTime": "2013-07-19T02:42:39.000Z"
}
}
...
```
**To confirm that a root volume is configured to persist using the AWS Tools for Windows PowerShell**
Use the [ Get\-EC2Instance](https://docs.aws.amazon.com/powershell/latest/reference/items/Get-EC2Instance.html) and verify that the `DeleteOnTermination` attribute in the `BlockDeviceMappings` response element is set to `false`\.
```
C:\> (Get-EC2Instance -InstanceId i-i-1234567890abcdef0).Instances.BlockDeviceMappings.Ebs
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/RootDeviceStorage.md |
67c9be538f9e-0 | Amazon EC2 and Amazon EBS are integrated with AWS CloudTrail, a service that provides a record of actions taken by a user, role, or an AWS service in Amazon EC2 and Amazon EBS\. CloudTrail captures all API calls for Amazon EC2 and Amazon EBS as events, including calls from the console and from code calls to the APIs\. If you create a trail, you can enable continuous delivery of CloudTrail events to an Amazon S3 bucket, including events for Amazon EC2 and Amazon EBS\. If you don't configure a trail, you can still view the most recent events in the CloudTrail console in **Event history**\. Using the information collected by CloudTrail, you can determine the request that was made to Amazon EC2 and Amazon EBS, the IP address from which the request was made, who made the request, when it was made, and additional details\.
To learn more about CloudTrail, see the [AWS CloudTrail User Guide](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitor-with-cloudtrail.md |
7ee4c9dd0662-0 | CloudTrail is enabled on your AWS account when you create the account\. When activity occurs in Amazon EC2 and Amazon EBS, that activity is recorded in a CloudTrail event along with other AWS service events in **Event history**\. You can view, search, and download recent events in your AWS account\. For more information, see [Viewing Events with CloudTrail Event History](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/view-cloudtrail-events.html)\.
For an ongoing record of events in your AWS account, including events for Amazon EC2 and Amazon EBS, create a trail\. A trail enables CloudTrail to deliver log files to an Amazon S3 bucket\. By default, when you create a trail in the console, the trail applies to all Regions\. The trail logs events from all Regions in the AWS partition and delivers the log files to the Amazon S3 bucket that you specify\. Additionally, you can configure other AWS services to further analyze and act upon the event data collected in CloudTrail logs\. For more information, see:
+ [Overview for Creating a Trail](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudtrail-create-and-update-a-trail.html)
+ [CloudTrail Supported Services and Integrations](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudtrail-aws-service-specific-topics.html#cloudtrail-aws-service-specific-topics-integrations) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitor-with-cloudtrail.md |
7ee4c9dd0662-1 | + [Configuring Amazon SNS Notifications for CloudTrail](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/getting_notifications_top_level.html)
+ [Receiving CloudTrail Log Files from Multiple Regions](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/receive-cloudtrail-log-files-from-multiple-regions.html) and [Receiving CloudTrail Log Files from Multiple Accounts](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudtrail-receive-logs-from-multiple-accounts.html)
All Amazon EC2 actions, and Amazon EBS management actions, are logged by CloudTrail and are documented in the [Amazon EC2 API Reference](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/)\. For example, calls to the [RunInstances](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/ApiReference-query-RunInstances.html), [DescribeInstances](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/ApiReference-query-DescribeInstances.html), or [CreateImage](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/ApiReference-query-CreateImage.html) actions generate entries in the CloudTrail log files\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitor-with-cloudtrail.md |
7ee4c9dd0662-2 | Every event or log entry contains information about who generated the request\. The identity information helps you determine the following:
+ Whether the request was made with root or IAM user credentials\.
+ Whether the request was made with temporary security credentials for a role or federated user\.
+ Whether the request was made by another AWS service\.
For more information, see the [CloudTrail userIdentity Element](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/cloudtrail-event-reference-user-identity.html)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitor-with-cloudtrail.md |
299f2bedfb9f-0 | A trail is a configuration that enables delivery of events as log files to an Amazon S3 bucket that you specify\. CloudTrail log files contain one or more log entries\. An event represents a single request from any source and includes information about the requested action, the date and time of the action, request parameters, and so on\. CloudTrail log files are not an ordered stack trace of the public API calls, so they do not appear in any specific order\.
The following log file record shows that a user terminated an instance\.
```
{
"Records":[
{
"eventVersion":"1.03",
"userIdentity":{
"type":"Root",
"principalId":"123456789012",
"arn":"arn:aws:iam::123456789012:root",
"accountId":"123456789012",
"accessKeyId":"AKIAIOSFODNN7EXAMPLE",
"userName":"user"
},
"eventTime":"2016-05-20T08:27:45Z",
"eventSource":"ec2.amazonaws.com",
"eventName":"TerminateInstances",
"awsRegion":"us-west-2",
"sourceIPAddress":"198.51.100.1", | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitor-with-cloudtrail.md |
299f2bedfb9f-1 | "awsRegion":"us-west-2",
"sourceIPAddress":"198.51.100.1",
"userAgent":"aws-cli/1.10.10 Python/2.7.9 Windows/7botocore/1.4.1",
"requestParameters":{
"instancesSet":{
"items":[{
"instanceId":"i-1a2b3c4d"
}]
}
},
"responseElements":{
"instancesSet":{
"items":[{
"instanceId":"i-1a2b3c4d",
"currentState":{
"code":32,
"name":"shutting-down"
},
"previousState":{
"code":16,
"name":"running"
}
}]
}
},
"requestID":"be112233-1ba5-4ae0-8e2b-1c302EXAMPLE",
"eventID":"6e12345-2a4e-417c-aa78-7594fEXAMPLE",
"eventType":"AwsApiCall", | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitor-with-cloudtrail.md |
299f2bedfb9f-2 | "eventType":"AwsApiCall",
"recipientAccountId":"123456789012"
}
]
}
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitor-with-cloudtrail.md |
5178d1058f74-0 | Use AWS CloudTrail to audit the users that connect to your instances via EC2 Instance Connect\.
**To audit SSH activity via EC2 Instance Connect using the AWS CloudTrail console**
1. Open the AWS CloudTrail console at [https://console.aws.amazon.com/cloudtrail/](https://console.aws.amazon.com/cloudtrail/)\.
1. Verify that you are in the correct Region\.
1. In the navigation pane, choose **Event history**\.
1. For **Filter**, choose **Event source**, **ec2\-instance\-connect\.amazonaws\.com**\.
1. \(Optional\) For **Time range**, select a time range\.
1. Choose the **Refresh events** icon\.
1. The page displays the events that correspond to the `[SendSSHPublicKey](https://docs.aws.amazon.com/ec2-instance-connect/latest/APIReference/API_SendSSHPublicKey.html)` API calls\. Expand an event using the arrow to view additional details, such as the user name and AWS access key that was used to make the SSH connection, and the source IP address\.
1. To display the full event information in JSON format, choose **View event**\. The **requestParameters** field contains the destination instance ID, OS user name, and public key that were used to make the SSH connection\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitor-with-cloudtrail.md |
5178d1058f74-1 | ```
{
"eventVersion": "1.05",
"userIdentity": {
"type": "IAMUser",
"principalId": "ABCDEFGONGNOMOOCB6XYTQEXAMPLE",
"arn": "arn:aws:iam::1234567890120:user/IAM-friendly-name",
"accountId": "123456789012",
"accessKeyId": "ABCDEFGUKZHNAW4OSN2AEXAMPLE",
"userName": "IAM-friendly-name",
"sessionContext": {
"attributes": {
"mfaAuthenticated": "false",
"creationDate": "2018-09-21T21:37:58Z"}
}
},
"eventTime": "2018-09-21T21:38:00Z",
"eventSource": "ec2-instance-connect.amazonaws.com",
"eventName": "SendSSHPublicKey ",
"awsRegion": "us-west-2",
"sourceIPAddress": "123.456.789.012", | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitor-with-cloudtrail.md |
5178d1058f74-2 | "sourceIPAddress": "123.456.789.012",
"userAgent": "aws-cli/1.15.61 Python/2.7.10 Darwin/16.7.0 botocore/1.10.60",
"requestParameters": {
"instanceId": "i-0123456789EXAMPLE",
"osUser": "ec2-user",
"SSHKey": {
"publicKey": "ssh-rsa ABCDEFGHIJKLMNO01234567890EXAMPLE"
}
"responseElements": null,
"requestID": "1a2s3d4f-bde6-11e8-a892-f7ec64543add",
"eventID": "1a2w3d4r5-a88f-4e28-b3bf-30161f75be34",
"eventType": "AwsApiCall",
"recipientAccountId": "0987654321"
}
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitor-with-cloudtrail.md |
5178d1058f74-3 | "recipientAccountId": "0987654321"
}
```
If you have configured your AWS account to collect CloudTrail events in an S3 bucket, you can download and audit the information programmatically\. For more information, see [Getting and Viewing Your CloudTrail Log Files](https://docs.aws.amazon.com/awscloudtrail/latest/userguide/get-and-view-cloudtrail-log-files.html) in the *AWS CloudTrail User Guide*\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitor-with-cloudtrail.md |
ca41479c2d76-0 | After you launch your instance, you can connect to it and use it the way that you'd use a computer sitting in front of you\.
The following instructions explain how to connect to your instance using PuTTY, a free SSH client for Windows\. If you receive an error while attempting to connect to your instance, see [Troubleshooting Connecting to Your Instance](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstancesConnecting.html)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/putty.md |
5647e336496a-0 | Before you connect to your Linux instance using PuTTY, complete the following prerequisites\.
**Verify that the instance is ready**
After you launch an instance, it can take a few minutes for the instance to be ready so that you can connect to it\. Check that your instance has passed its status checks\. You can view this information in the **Status Checks** column on the **Instances** page\.
**Verify the general prerequisites for connecting to your instance**
To find the public DNS name or IP address of your instance and the user name that you should use to connect to your instance, see [General prerequisites for connecting to your instance](connection-prereqs.md)\.
**Install PuTTY on your local computer**
Download and install PuTTY from the [PuTTY download page](http://www.chiark.greenend.org.uk/~sgtatham/putty/)\. If you already have an older version of PuTTY installed, we recommend that you download the latest version\. Be sure to install the entire suite\.
**Convert your private key using PuTTYgen**
Locate the private key \(\.pem file\) for the key pair that you specified when you launched the instance\. Convert the \.pem file to a \.ppk file for use with PuTTY\. For more information, follow the steps in the next section\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/putty.md |
785e02e2b49f-0 | PuTTY does not natively support the private key format for SSH keys\. PuTTY provides a tool named PuTTYgen, which converts keys to the required format for PuTTY\. You must convert your private key \(\.pem file\) into this format \(\.ppk file\) as follows in order to connect to your instance using PuTTY\.
**To convert your private key**
1. From the **Start** menu, choose **All Programs**, **PuTTY**, **PuTTYgen**\.
1. Under **Type of key to generate**, choose **RSA**\. If you're using an older version of PuTTYgen, choose **SSH\-2 RSA**\.
![\[RSA key in PuTTYgen\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/puttygen-key-type.png)
1. Choose **Load**\. By default, PuTTYgen displays only files with the extension `.ppk`\. To locate your `.pem` file, choose the option to display files of all types\.
![\[Select all file types\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/puttygen-load-key.png) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/putty.md |
785e02e2b49f-1 | 1. Select your `.pem` file for the key pair that you specified when you launched your instance and choose **Open**\. PuTTYgen displays a notice that the `.pem` file was successfully imported\. Choose **OK**\.
1. To save the key in the format that PuTTY can use, choose **Save private key**\. PuTTYgen displays a warning about saving the key without a passphrase\. Choose **Yes**\.
**Note**
A passphrase on a private key is an extra layer of protection\. Even if your private key is discovered, it can't be used without the passphrase\. The downside to using a passphrase is that it makes automation harder because human intervention is needed to log on to an instance, or to copy files to an instance\.
1. Specify the same name for the key that you used for the key pair \(for example, `my-key-pair`\) and choose **Save**\. PuTTY automatically adds the `.ppk` file extension\.
Your private key is now in the correct format for use with PuTTY\. You can now connect to your instance using PuTTY's SSH client\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/putty.md |
c973ec472a39-0 | Use the following procedure to connect to your Linux instance using PuTTY\. You need the `.ppk` file that you created for your private key\. For more information, see [Convert your private key using PuTTYgen](#putty-private-key) in the preceding section\. If you receive an error while attempting to connect to your instance, see [Troubleshooting Connecting to Your Instance](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstancesConnecting.html)\.
**To connect to your instance using PuTTY**
1. Start PuTTY \(from the **Start** menu, choose **All Programs, PuTTY, PuTTY**\)\.
1. In the **Category** pane, choose **Session** and complete the following fields:
1. In the **Host Name** box, do one of the following:
+ \(Public DNS\) To connect using your instance's public DNS name, enter *my\-instance\-user\-name*@*my\-instance\-public\-dns\-name*\.
+ \(IPv6\) Alternatively, if your instance has an IPv6 address, to connect using your instance's IPv6 address, enter *my\-instance\-user\-name*@*my\-instance\-IPv6\-address*\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/putty.md |
c973ec472a39-1 | For information about how to get the user name for your instance, and the public DNS name or IPv6 address of your instance, see [Get information about your instance](connection-prereqs.md#connection-prereqs-get-info-about-instance)\.
1. Ensure that the **Port** value is 22\.
1. Under **Connection type**, select **SSH**\.
![\[PuTTY configuration - Session\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/putty-session-config.png)
1. \(Optional\) You can configure PuTTY to automatically send 'keepalive' data at regular intervals to keep the session active\. This is useful to avoid disconnecting from your instance due to session inactivity\. In the **Category** pane, choose **Connection**, and then enter the required interval in the **Seconds between keepalives** field\. For example, if your session disconnects after 10 minutes of inactivity, enter 180 to configure PuTTY to send keepalive data every 3 minutes\.
1. In the **Category** pane, expand **Connection**, expand **SSH**, and then choose **Auth**\. Complete the following:
1. Choose **Browse**\.
1. Select the `.ppk` file that you generated for your key pair and choose **Open**\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/putty.md |
c973ec472a39-2 | 1. Select the `.ppk` file that you generated for your key pair and choose **Open**\.
1. \(Optional\) If you plan to start this session again later, you can save the session information for future use\. Under **Category**, choose **Session**, enter a name for the session in **Saved Sessions**, and then choose **Save**\.
1. Choose **Open**\.
1. If this is the first time you have connected to this instance, PuTTY displays a security alert dialog box that asks whether you trust the host to which you are connecting\.
1. \(Optional\) Verify that the fingerprint in the security alert dialog box matches the fingerprint that you previously obtained in [\(Optional\) Get the instance fingerprint](connection-prereqs.md#connection-prereqs-fingerprint)\. If these fingerprints don't match, someone might be attempting a "man\-in\-the\-middle" attack\. If they match, continue to the next step\.
1. Choose **Yes**\. A window opens and you are connected to your instance\.
**Note**
If you specified a passphrase when you converted your private key to PuTTY's format, you must provide that passphrase when you log in to the instance\.
If you receive an error while attempting to connect to your instance, see [Troubleshooting Connecting to Your Instance](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstancesConnecting.html)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/putty.md |
a785c67af465-0 | The PuTTY Secure Copy client \(PSCP\) is a command line tool that you can use to transfer files between your Windows computer and your Linux instance\. If you prefer a graphical user interface \(GUI\), you can use an open source GUI tool named WinSCP\. For more information, see [Transferring files to your Linux instance using WinSCP](#Transfer_WinSCP)\.
To use PSCP, you need the private key you generated in [Convert your private key using PuTTYgen](#putty-private-key)\. You also need the public DNS name of your Linux instance, or the IPv6 address if your instance has one\.
The following example transfers the file `Sample_file.txt` from the C:\\ drive on a Windows computer to the `my-instance-user-name` home directory on an Amazon Linux instance\. To transfer a file, use one of the following commands\.
+ \(Public DNS\) To transfer a file using your instance's public DNS name, enter the following command\.
```
pscp -i C:\path\my-key-pair.ppk C:\path\Sample_file.txt my-instance-user-name@my-instance-public-dns-name:/home/my-instance-user-name/Sample_file.txt
```
+ \(IPv6\) Alternatively, if your instance has an IPv6 address, to transfer a file using your instance's IPv6 address, enter the following command\. The IPv6 address must be enclosed in square brackets \(`[ ]`\)\.
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/putty.md |
a785c67af465-1 | ```
pscp -i C:\path\my-key-pair.ppk C:\path\Sample_file.txt my-instance-user-name@[my-instance-IPv6-address]:/home/my-instance-user-name/Sample_file.txt
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/putty.md |
fa3ca0617a7e-0 | WinSCP is a GUI\-based file manager for Windows that allows you to upload and transfer files to a remote computer using the SFTP, SCP, FTP, and FTPS protocols\. WinSCP allows you to drag and drop files from your Windows computer to your Linux instance or synchronize entire directory structures between the two systems\.
To use WinSCP, you need the private key that you generated in [Convert your private key using PuTTYgen](#putty-private-key)\. You also need the public DNS name of your Linux instance\.
1. Download and install WinSCP from [http://winscp\.net/eng/download\.php](http://winscp.net/eng/download.php)\. For most users, the default installation options are OK\.
1. Start WinSCP\.
1. At the **WinSCP login** screen, for **Host name**, enter one of the following:
+ \(Public DNS or IPv4 address\) To log in using your instance's public DNS name or public IPv4 address, enter the public DNS name or public IPv4 address for your instance\.
+ \(IPv6\) Alternatively, if your instance has an IPv6 address, to log in using your instance's IPv6 address, enter the IPv6 address for your instance\.
1. For **User name**, enter the default user name for your AMI\.
+ For Amazon Linux 2 or the Amazon Linux AMI, the user name is `ec2-user`\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/putty.md |
fa3ca0617a7e-1 | + For Amazon Linux 2 or the Amazon Linux AMI, the user name is `ec2-user`\.
+ For a CentOS AMI, the user name is `centos`\.
+ For a Debian AMI, the user name is `admin`\.
+ For a Fedora AMI, the user name is `ec2-user` or `fedora`\.
+ For a RHEL AMI, the user name is `ec2-user` or `root`\.
+ For a SUSE AMI, the user name is `ec2-user` or `root`\.
+ For an Ubuntu AMI, the user name is `ubuntu`\.
+ Otherwise, if `ec2-user` and `root` don't work, check with the AMI provider\.
1. Specify the private key for your instance\. For **Private key**, enter the path to your private key, or choose the "**\.\.\.**" button to browse for the file\. To open the advanced site settings, for newer versions of WinSCP, choose **Advanced**\. To find the **Private key file** setting, under **SSH**, choose **Authentication**\.
Here is a screenshot from WinSCP version 5\.9\.4:
![\[WinSCP Advanced screen\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/WinSCP-keypair.png) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/putty.md |
fa3ca0617a7e-2 | WinSCP requires a PuTTY private key file \(`.ppk`\)\. You can convert a `.pem` security key file to the `.ppk` format using PuTTYgen\. For more information, see [Convert your private key using PuTTYgen](#putty-private-key)\.
1. \(Optional\) In the left panel, choose **Directories**\. For **Remote directory**, enter the path for the directory to which to add files\. To open the advanced site settings for newer versions of WinSCP, choose **Advanced**\. To find the **Remote directory** setting, under **Environment**, choose **Directories**\.
1. Choose **Login**\. To add the host fingerprint to the host cache, choose **Yes**\.
![\[WinSCP screen\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/WinSCP-connection.png)
1. After the connection is established, in the connection window your Linux instance is on the right and your local machine is on the left\. You can drag and drop files directly into the remote file system from your local machine\. For more information on WinSCP, see the project documentation at [http://winscp\.net/eng/docs/start](http://winscp.net/eng/docs/start)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/putty.md |
fa3ca0617a7e-3 | If you receive a "Cannot execute SCP to start transfer" error, you must first install scp on your Linux instance\. For some operating systems, this is located in the `openssh-clients` package\. For Amazon Linux variants, such as the Amazon ECS\-optimized AMI, use the following command to install scp\.
```
[ec2-user ~]$ sudo yum install -y openssh-clients
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/putty.md |
904ee282634a-0 | The base distribution of Amazon Linux contains many software packages and utilities that are required for basic server operations\. However, many more software packages are available in various software repositories, and even more packages are available for you to build from source code\.
**Topics**
+ [Updating instance software on your Amazon Linux instance](install-updates.md)
+ [Adding repositories on an Amazon Linux instance](add-repositories.md)
+ [Finding software packages on an Amazon Linux instance](find-software.md)
+ [Installing software packages on an Amazon Linux instance](install-software.md)
+ [Preparing to compile software on an Amazon Linux instance](compile-software.md)
It is important to keep software up\-to\-date\. Many packages in a Linux distribution are updated frequently to fix bugs, add features, and protect against security exploits\. For more information, see [Updating instance software on your Amazon Linux instance](install-updates.md)\.
By default, Amazon Linux instances launch with the following repositories enabled:
+ Amazon Linux 2: `amzn2-core` and `amzn2extra-docker`
+ Amazon Linux AMI: `amzn-main` and `amzn-updates` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/managing-software.md |
904ee282634a-1 | + Amazon Linux AMI: `amzn-main` and `amzn-updates`
While there are many packages available in these repositories that are updated by Amazon Web Services, there may be a package that you wish to install that is contained in another repository\. For more information, see [Adding repositories on an Amazon Linux instance](add-repositories.md)\. For help finding packages in enabled repositories, see [Finding software packages on an Amazon Linux instance](find-software.md)\. For information about installing software on an Amazon Linux instance, see [Installing software packages on an Amazon Linux instance](install-software.md)\.
Not all software is available in software packages stored in repositories; some software must be compiled on an instance from its source code\. For more information, see [Preparing to compile software on an Amazon Linux instance](compile-software.md)\.
Amazon Linux instances manage their software using the yum package manager\. The yum package manager can install, remove, and update software, as well as manage all of the dependencies for each package\. Debian\-based Linux distributions, like Ubuntu, use the apt\-get command and dpkg package manager, so the yum examples in the following sections do not work for those distributions\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/managing-software.md |
bfb51cc27d39-0 | Amazon EC2 provides the following purchasing options to enable you to optimize your costs based on your needs:
+ **On\-Demand Instances** – Pay, by the second, for the instances that you launch\.
+ **Savings Plans** – Reduce your Amazon EC2 costs by making a commitment to a consistent amount of usage, in USD per hour, for a term of 1 or 3 years\.
+ **Reserved Instances** – Reduce your Amazon EC2 costs by making a commitment to a consistent instance configuration, including instance type and Region, for a term of 1 or 3 years\.
+ **Scheduled Instances** – Purchase instances that are always available on the specified recurring schedule, for a one\-year term\.
+ **Spot Instances** – Request unused EC2 instances, which can reduce your Amazon EC2 costs significantly\.
+ **Dedicated Hosts** – Pay for a physical host that is fully dedicated to running your instances, and bring your existing per\-socket, per\-core, or per\-VM software licenses to reduce costs\.
+ **Dedicated Instances** – Pay, by the hour, for instances that run on single\-tenant hardware\.
+ **Capacity Reservations** – Reserve capacity for your EC2 instances in a specific Availability Zone for any duration\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-purchasing-options.md |
bfb51cc27d39-1 | + **Capacity Reservations** – Reserve capacity for your EC2 instances in a specific Availability Zone for any duration\.
If you require a capacity reservation, purchase Reserved Instances or Capacity Reservations for a specific Availability Zone, or purchase Scheduled Instances\. Spot Instances are a cost\-effective choice if you can be flexible about when your applications run and if they can be interrupted\. Dedicated Hosts or Dedicated Instances can help you address compliance requirements and reduce costs by using your existing server\-bound software licenses\. For more information, see [Amazon EC2 Pricing](https://aws.amazon.com/ec2/pricing/)\.
For more information about Savings Plans, see the [AWS Savings Plans User Guide](https://docs.aws.amazon.com/savingsplans/latest/userguide/)\.
**Topics**
+ [Determining the instance lifecycle](#check-instance-lifecycle)
+ [On\-Demand Instances](ec2-on-demand-instances.md)
+ [Reserved Instances](ec2-reserved-instances.md)
+ [Scheduled Reserved Instances](ec2-scheduled-instances.md)
+ [Spot Instances](using-spot-instances.md)
+ [Dedicated Hosts](dedicated-hosts-overview.md)
+ [Dedicated Instances](dedicated-instance.md)
+ [On\-Demand Capacity Reservations](ec2-capacity-reservations.md) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-purchasing-options.md |
c5c06b774be0-0 | The lifecycle of an instance starts when it is launched and ends when it is terminated\. The purchasing option that you choose affects the lifecycle of the instance\. For example, an On\-Demand Instance runs when you launch it and ends when you terminate it\. A Spot Instance runs as long as capacity is available and your maximum price is higher than the Spot price\. You can launch a Scheduled Instance during its scheduled time period; Amazon EC2 launches the instances and then terminates them three minutes before the time period ends\.
Use the following procedure to determine the lifecycle of an instance\.
**To determine the instance lifecycle 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. Select the instance\.
1. On the **Description** tab, find **Tenancy**\. If the value is `host`, the instance is running on a Dedicated Host\. If the value is `dedicated`, the instance is a Dedicated Instance\.
1. On the **Description** tab, find **Lifecycle**\. If the value is `spot`, the instance is a Spot Instance\. If the value is `scheduled`, the instance is a Scheduled Instance\. If the value is `normal`, the instance is either an On\-Demand Instance or a Reserved Instance\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-purchasing-options.md |
c5c06b774be0-1 | 1. \(Optional\) If you have purchased a Reserved Instance and want to verify that it is being applied, you can check the usage reports for Amazon EC2\. For more information, see [Amazon EC2 usage reports](usage-reports.md)\.
**To determine the instance lifecycle using the AWS CLI**
Use the following [describe\-instances](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-instances.html) command:
```
aws ec2 describe-instances --instance-ids i-1234567890abcdef0
```
If the instance is running on a Dedicated Host, the output contains the following information:
```
"Tenancy": "host"
```
If the instance is a Dedicated Instance, the output contains the following information:
```
"Tenancy": "dedicated"
```
If the instance is a Spot Instance, the output contains the following information:
```
"InstanceLifecycle": "spot"
```
If the instance is a Scheduled Instance, the output contains the following information:
```
"InstanceLifecycle": "scheduled"
```
Otherwise, the output does not contain `InstanceLifecycle`\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-purchasing-options.md |
54fdeb8db234-0 | You can delete your instance when you no longer need it\. This is referred to as *terminating* your instance\. As soon as the state of an instance changes to `shutting-down` or `terminated`, you stop incurring charges for that instance\.
You can't connect to or start an instance after you've terminated it\. However, you can launch additional instances using the same AMI\. If you'd rather stop and start your instance, or hibernate it, see [Stop and start your instance](Stop_Start.md) or [Hibernate your Linux instance](Hibernate.md)\. For more information, see [Differences between reboot, stop, hibernate, and terminate](ec2-instance-lifecycle.md#lifecycle-differences)\.
**Topics**
+ [Instance termination](#termination-overview)
+ [What happens when you terminate an instance](#what-happens-terminate)
+ [Terminating an instance](#terminating-instances-console)
+ [Enabling termination protection](#Using_ChangingDisableAPITermination)
+ [Changing the instance initiated shutdown behavior](#Using_ChangingInstanceInitiatedShutdownBehavior)
+ [Preserving Amazon EBS volumes on instance termination](#preserving-volumes-on-termination)
+ [Troubleshooting](#troubleshoot-instance-terminate) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/terminating-instances.md |
b21b47ff8afe-0 | After you terminate an instance, it remains visible in the console for a short while, and then the entry is automatically deleted\. You cannot delete the terminated instance entry yourself\. After an instance is terminated, resources such as tags and volumes are gradually disassociated from the instance and may no longer be visible on the terminated instance after a short while\.
When an instance terminates, the data on any instance store volumes associated with that instance is deleted\.
By default, Amazon EBS root device volumes are automatically deleted when the instance terminates\. However, by default, any additional EBS volumes that you attach at launch, or any EBS volumes that you attach to an existing instance persist even after the instance terminates\. This behavior is controlled by the volume's `DeleteOnTermination` attribute, which you can modify\. For more information, see [Preserving Amazon EBS volumes on instance termination](#preserving-volumes-on-termination)\.
You can prevent an instance from being terminated accidentally by someone using the AWS Management Console, the CLI, and the API\. This feature is available for both Amazon EC2 instance store\-backed and Amazon EBS\-backed instances\. Each instance has a `DisableApiTermination` attribute with the default value of `false` \(the instance can be terminated through Amazon EC2\)\. You can modify this instance attribute while the instance is running or stopped \(in the case of Amazon EBS\-backed instances\)\. For more information, see [Enabling termination protection](#Using_ChangingDisableAPITermination)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/terminating-instances.md |
b21b47ff8afe-1 | You can control whether an instance should stop or terminate when shutdown is initiated from the instance using an operating system command for system shutdown\. For more information, see [Changing the instance initiated shutdown behavior](#Using_ChangingInstanceInitiatedShutdownBehavior)\.
If you run a script on instance termination, your instance might have an abnormal termination, because we have no way to ensure that shutdown scripts run\. Amazon EC2 attempts to shut an instance down cleanly and run any system shutdown scripts; however, certain events \(such as hardware failure\) may prevent these system shutdown scripts from running\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/terminating-instances.md |
e4a3f13db503-0 | When an EC2 instance is terminated using the `terminate-instances` command, the following is registered at the OS level:
+ The API request will send a button press event to the guest\.
+ Various system services will be stopped as a result of the button press event\. **systemd** handles a graceful shutdown of the system\. Graceful shutdown is triggered by the ACPI shutdown button press event from the hypervisor\.
+ ACPI shutdown will be initiated\.
+ The instance will shut down when the graceful shutdown process exits\. There is no configurable OS shutdown time\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/terminating-instances.md |
ddbed8d61956-0 | **Important**
By default, when you initiate a shutdown from an Amazon EBS\-backed instance \(using the **shutdown** or **poweroff** commands\), the instance stops\. The **halt** command does not initiate a shutdown\. If used, the instance will not terminate; instead, it places the CPU into `HLT` and the instance will remain running\.
You can terminate an instance using the AWS Management Console or the command line\.
**To terminate an instance using the console**
1. Before you terminate the instance, verify that you won't lose any data by checking that your Amazon EBS volumes won't be deleted on termination and that you've copied any data that you need from your instance store volumes to Amazon EBS or Amazon S3\.
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, and choose **Actions**, **Instance State**, **Terminate**\.
1. Choose **Yes, Terminate** when prompted for confirmation\.
**To terminate an 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)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/terminating-instances.md |
ddbed8d61956-1 | + [terminate\-instances](https://docs.aws.amazon.com/cli/latest/reference/ec2/terminate-instances.html) \(AWS CLI\)
+ [Stop\-EC2Instance](https://docs.aws.amazon.com/powershell/latest/reference/items/Stop-EC2Instance.html) \(AWS Tools for Windows PowerShell\) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/terminating-instances.md |
0a3078ffa7f2-0 | By default, you can terminate your instance using the Amazon EC2 console, command line interface, or API\. To prevent your instance from being accidentally terminated using Amazon EC2, you can enable *termination protection* for the instance\. The `DisableApiTermination` attribute controls whether the instance can be terminated using the console, CLI, or API\. By default, termination protection is disabled for your instance\. You can set the value of this attribute when you launch the instance, while the instance is running, or while the instance is stopped \(for Amazon EBS\-backed instances\)\.
The `DisableApiTermination` attribute does not prevent you from terminating an instance by initiating shutdown from the instance \(using an operating system command for system shutdown\) when the `InstanceInitiatedShutdownBehavior` attribute is set\. For more information, see [Changing the instance initiated shutdown behavior](#Using_ChangingInstanceInitiatedShutdownBehavior)\.
**Limitations**
You can't enable termination protection for Spot Instances—a Spot Instance is terminated when the Spot price exceeds the amount you're willing to pay for Spot Instances\. However, you can prepare your application to handle Spot Instance interruptions\. For more information, see [Spot Instance interruptions](spot-interruptions.md)\.
The `DisableApiTermination` attribute does not prevent Amazon EC2 Auto Scaling from terminating an instance\. For instances in an Auto Scaling group, use the following Amazon EC2 Auto Scaling features instead of Amazon EC2 termination protection: | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/terminating-instances.md |
0a3078ffa7f2-1 | + To prevent instances that are part of an Auto Scaling group from terminating on scale in, use instance protection\. For more information, see [Instance Protection](https://docs.aws.amazon.com/autoscaling/ec2/userguide/as-instance-termination.html#instance-protection) in the *Amazon EC2 Auto Scaling User Guide*\.
+ To prevent Amazon EC2 Auto Scaling from terminating unhealthy instances, suspend the `ReplaceUnhealthy` process\. For more information, see [Suspending and Resuming Scaling Processes](https://docs.aws.amazon.com/autoscaling/ec2/userguide/as-suspend-resume-processes.html) in the *Amazon EC2 Auto Scaling User Guide*\.
+ To specify which instances Amazon EC2 Auto Scaling should terminate first, choose a termination policy\. For more information, see [Customizing the Termination Policy](https://docs.aws.amazon.com/autoscaling/ec2/userguide/as-instance-termination.html#custom-termination-policy) in the *Amazon EC2 Auto Scaling User Guide*\.
**To enable termination protection for an instance at launch time**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. On the dashboard, choose **Launch Instance** and follow the directions in the wizard\.
1. On the **Configure Instance Details** page, select the **Enable termination protection** check box\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/terminating-instances.md |
0a3078ffa7f2-2 | 1. On the **Configure Instance Details** page, select the **Enable termination protection** check box\.
**To enable termination protection for a running or stopped instance**
1. Select the instance, and choose **Actions**, **Instance Settings**, **Change Termination Protection**\.
1. Choose **Yes, Enable**\.
**To disable termination protection for a running or stopped instance**
1. Select the instance, and choose **Actions**, **Instance Settings**, **Change Termination Protection**\.
1. Choose **Yes, Disable**\.
**To enable or disable termination protection 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)\.
+ [modify\-instance\-attribute](https://docs.aws.amazon.com/cli/latest/reference/ec2/modify-instance-attribute.html) \(AWS CLI\)
+ [Edit\-EC2InstanceAttribute](https://docs.aws.amazon.com/powershell/latest/reference/items/Edit-EC2InstanceAttribute.html) \(AWS Tools for Windows PowerShell\) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/terminating-instances.md |
ea4bcc42265e-0 | By default, when you initiate a shutdown from an Amazon EBS\-backed instance \(using a command such as shutdown or poweroff\), the instance stops \(Note that halt does not issue a poweroff command and, if used, the instance will not terminate; instead, it will place the CPU into HLT and the instance will remain running\)\. You can change this behavior using the `InstanceInitiatedShutdownBehavior` attribute for the instance so that it terminates instead\. You can update this attribute while the instance is running or stopped\.
You can update the `InstanceInitiatedShutdownBehavior` attribute using the Amazon EC2 console or the command line\. The `InstanceInitiatedShutdownBehavior` attribute only applies when you perform a shutdown from the operating system of the instance itself; it does not apply when you stop an instance using the `StopInstances` API or the Amazon EC2 console\.
**To change the shutdown behavior of 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. Select the instance, and choose **Actions**, **Instance Settings**, **Change Shutdown Behavior**\. The current behavior is already selected\.
1. To change the behavior, select an option from the **Shutdown behavior** list, and then choose **Apply**\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/terminating-instances.md |
ea4bcc42265e-1 | 1. To change the behavior, select an option from the **Shutdown behavior** list, and then choose **Apply**\.
![\[The Change Shutdown Behavior dialog box\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/shutdown_behavior_dialog.png)
**To change the shutdown behavior of an 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)\.
+ [modify\-instance\-attribute](https://docs.aws.amazon.com/cli/latest/reference/ec2/modify-instance-attribute.html) \(AWS CLI\)
+ [Edit\-EC2InstanceAttribute](https://docs.aws.amazon.com/powershell/latest/reference/items/Edit-EC2InstanceAttribute.html) \(AWS Tools for Windows PowerShell\) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/terminating-instances.md |
0bd90cd6574f-0 | When an instance terminates, Amazon EC2 uses the value of the `DeleteOnTermination` attribute for each attached Amazon EBS volume to determine whether to preserve or delete the volume\.
The default value for the `DeleteOnTermination` attribute differs depending on whether the volume is the root volume of the instance or a non\-root volume attached to the instance\.
Root volume
By default, the `DeleteOnTermination` attribute for the root volume of an instance is set to `true`\. Therefore, the default is to delete the root volume of the instance when the instance terminates\. The `DeleteOnTermination` attribute can be set by the creator of an AMI as well as by the person who launches an instance\. When the attribute is changed by the creator of an AMI or by the person who launches an instance, the new setting overrides the original AMI default setting\. We recommend that you verify the default setting for the `DeleteOnTermination` attribute after you launch an instance with an AMI\.
Non\-root volume
By default, when you [attach a non\-root EBS volume to an instance](ebs-attaching-volume.md), its `DeleteOnTermination` attribute is set to `false`\. Therefore, the default is to preserve these volumes\. After the instance terminates, you can take a snapshot of the preserved volume or attach it to another instance\. You must delete a volume to avoid incurring further charges\. For more information, see [Deleting an Amazon EBS volume](ebs-deleting-volume.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/terminating-instances.md |
0bd90cd6574f-1 | To verify the value of the `DeleteOnTermination` attribute for an EBS volume that is in use, look at the instance's block device mapping\. For more information, see [Viewing the EBS volumes in an instance block device mapping](block-device-mapping-concepts.md#view-instance-bdm)\.
You can change the value of the `DeleteOnTermination` attribute for a volume when you launch the instance or while the instance is running\.
**Topics**
+ [Changing the root volume to persist at launch using the console](#delete-on-termination-console)
+ [Changing the root volume to persist at launch using the command line](#delete-on-termination-cli)
+ [Changing the root volume of a running instance to persist using the command line](#delete-on-termination-running-instance) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/terminating-instances.md |
070eb69f128b-0 | Using the console, you can change the `DeleteOnTermination` attribute when you launch an instance\. To change this attribute for a running instance, you must use the command line\.
**To change the root volume of an instance to persist at launch using the console**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. From the console dashboard, select **Launch Instance**\.
1. On the **Choose an Amazon Machine Image \(AMI\)** page, choose an AMI and choose **Select**\.
1. Follow the wizard to complete the **Choose an Instance Type** and **Configure Instance Details** pages\.
1. On the **Add Storage** page, deselect the **Delete On Termination** check box for the root volume\.
1. Complete the remaining wizard pages, and then choose **Launch**\.
You can verify the setting by viewing details for the root device volume on the instance's details pane\. Next to **Block devices**, choose the entry for the root device volume\. By default, **Delete on termination** is `True`\. If you change the default behavior, **Delete on termination** is `False`\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/terminating-instances.md |
2a6ec58b2b68-0 | When you launch an EBS\-backed instance, you can use one of the following commands to change the root device volume to persist\. For more information about these command line interfaces, see [Accessing Amazon EC2](concepts.md#access-ec2)\.
+ [run\-instances](https://docs.aws.amazon.com/cli/latest/reference/ec2/run-instances.html) \(AWS CLI\)
+ [New\-EC2Instance](https://docs.aws.amazon.com/powershell/latest/reference/items/New-EC2Instance.html) \(AWS Tools for Windows PowerShell\)
For example, add the following option to your `run-instances` command:
```
--block-device-mappings file://mapping.json
```
Specify the following in `mapping.json`:
```
[
{
"DeviceName": "/dev/sda1",
"Ebs": {
"DeleteOnTermination": false,
"SnapshotId": "snap-1234567890abcdef0",
"VolumeType": "gp2"
}
}
]
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/terminating-instances.md |
dc9e0b662017-0 | You can use one of the following commands to change the root device volume of a running EBS\-backed instance to persist\. For more information about these command line interfaces, see [Accessing Amazon EC2](concepts.md#access-ec2)\.
+ [modify\-instance\-attribute](https://docs.aws.amazon.com/cli/latest/reference/ec2/modify-instance-attribute.html) \(AWS CLI\)
+ [Edit\-EC2InstanceAttribute](https://docs.aws.amazon.com/powershell/latest/reference/items/Edit-EC2InstanceAttribute.html) \(AWS Tools for Windows PowerShell\)
For example, use the following command:
```
aws ec2 modify-instance-attribute --instance-id i-1234567890abcdef0 --block-device-mappings file://mapping.json
```
Specify the following in `mapping.json`:
```
[
{
"DeviceName": "/dev/sda1",
"Ebs": {
"DeleteOnTermination": false
}
}
]
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/terminating-instances.md |
e169f38966b3-0 | If you terminate your instance and another instance starts, most likely you have configured automatic scaling through a feature like EC2 Fleet or Amazon EC2 Auto Scaling\.
If your instance is in the `shutting-down` state for longer than usual, it should be cleaned up \(terminated\) by automated processes within the Amazon EC2 service\. For more information, see [Delayed instance termination](TroubleshootingInstancesShuttingDown.md#instance-stuck-terminating)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/terminating-instances.md |
e911956e0151-0 | You can use the AMI tools to create and manage instance store\-backed Linux AMIs\. To use the tools, you must install them on your Linux instance\. The AMI tools are available as both an RPM and as a \.zip file for Linux distributions that don't support RPM\.
**To set up the AMI tools using the RPM**
1. Install Ruby using the package manager for your Linux distribution, such as yum\. For example:
```
[ec2-user ~]$ sudo yum install -y ruby
```
1. Download the RPM file using a tool such as wget or curl\. For example:
```
[ec2-user ~]$ wget https://s3.amazonaws.com/ec2-downloads/ec2-ami-tools.noarch.rpm
```
1. Verify the RPM file's signature using the following command:
```
[ec2-user ~]$ rpm -K ec2-ami-tools.noarch.rpm
```
The command above should indicate that the file's SHA1 and MD5 hashes are `OK.` If the command indicates that the hashes are `NOT OK`, use the following command to view the file's Header SHA1 and MD5 hashes:
```
[ec2-user ~]$ rpm -Kv ec2-ami-tools.noarch.rpm
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/set-up-ami-tools.md |
e911956e0151-1 | ```
[ec2-user ~]$ rpm -Kv ec2-ami-tools.noarch.rpm
```
Then, compare your file's Header SHA1 and MD5 hashes with the following verified AMI tools hashes to confirm the file's authenticity:
+ Header SHA1: a1f662d6f25f69871104e6a62187fa4df508f880
+ MD5: 9faff05258064e2f7909b66142de6782
If your file's Header SHA1 and MD5 hashes match the verified AMI tools hashes, continue to the next step\.
1. Install the RPM using the following command:
```
[ec2-user ~]$ sudo yum install ec2-ami-tools.noarch.rpm
```
1. Verify your AMI tools installation using the [ec2\-ami\-tools\-version](ami-tools-commands.md#ami-tools-version) command\.
```
[ec2-user ~]$ ec2-ami-tools-version
```
**Note**
If you receive a load error such as "cannot load such file \-\- ec2/amitools/version \(LoadError\)", complete the next step to add the location of your AMI tools installation to your `RUBYLIB` path\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/set-up-ami-tools.md |
e911956e0151-2 | 1. \(Optional\) If you received an error in the previous step, add the location of your AMI tools installation to your `RUBYLIB` path\.
1. Run the following command to determine the paths to add\.
```
[ec2-user ~]$ rpm -qil ec2-ami-tools | grep ec2/amitools/version
/usr/lib/ruby/site_ruby/ec2/amitools/version.rb
/usr/lib64/ruby/site_ruby/ec2/amitools/version.rb
```
In the above example, the missing file from the previous load error is located at `/usr/lib/ruby/site_ruby` and `/usr/lib64/ruby/site_ruby`\.
1. Add the locations from the previous step to your `RUBYLIB` path\.
```
[ec2-user ~]$ export RUBYLIB=$RUBYLIB:/usr/lib/ruby/site_ruby:/usr/lib64/ruby/site_ruby
```
1. Verify your AMI tools installation using the [ec2\-ami\-tools\-version](ami-tools-commands.md#ami-tools-version) command\.
```
[ec2-user ~]$ ec2-ami-tools-version
```
**To set up the AMI tools using the \.zip file** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/set-up-ami-tools.md |
e911956e0151-3 | ```
**To set up the AMI tools using the \.zip file**
1. Install Ruby and unzip using the package manager for your Linux distribution, such as apt\-get\. For example:
```
[ec2-user ~]$ sudo apt-get update -y && sudo apt-get install -y ruby unzip
```
1. Download the \.zip file using a tool such as wget or curl\. For example:
```
[ec2-user ~]$ wget https://s3.amazonaws.com/ec2-downloads/ec2-ami-tools.zip
```
1. Unzip the files into a suitable installation directory, such as `/usr/local/ec2`\.
```
[ec2-user ~]$ sudo mkdir -p /usr/local/ec2
$ sudo unzip ec2-ami-tools.zip -d /usr/local/ec2
```
Notice that the \.zip file contains a folder ec2\-ami\-tools\-*x*\.*x*\.*x*, where *x*\.*x*\.*x* is the version number of the tools \(for example, `ec2-ami-tools-1.5.7`\)\.
1. Set the `EC2_AMITOOL_HOME` environment variable to the installation directory for the tools\. For example: | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/set-up-ami-tools.md |
e911956e0151-4 | 1. Set the `EC2_AMITOOL_HOME` environment variable to the installation directory for the tools\. For example:
```
[ec2-user ~]$ export EC2_AMITOOL_HOME=/usr/local/ec2/ec2-ami-tools-x.x.x
```
1. Add the tools to your `PATH` environment variable\. For example:
```
[ec2-user ~]$ export PATH=$EC2_AMITOOL_HOME/bin:$PATH
```
1. You can verify your AMI tools installation using the [ec2\-ami\-tools\-version](ami-tools-commands.md#ami-tools-version) command\.
```
[ec2-user ~]$ ec2-ami-tools-version
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/set-up-ami-tools.md |
d92fad586733-0 | Certain commands in the AMI tools require a signing certificate \(also known as X\.509 certificate\)\. You must create the certificate and then upload it to AWS\. For example, you can use a third\-party tool such as OpenSSL to create the certificate\.
**To create a signing certificate**
1. Install and configure OpenSSL\.
1. Create a private key using the `openssl genrsa` command and save the output to a `.pem` file\. We recommend that you create a 2048\- or 4096\-bit RSA key\.
```
openssl genrsa 2048 > private-key.pem
```
1. Generate a certificate using the `openssl req` command\.
```
openssl req -new -x509 -nodes -sha256 -days 365 -key private-key.pem -outform PEM -out certificate.pem
```
To upload the certificate to AWS, use the [upload\-signing\-certificate](https://docs.aws.amazon.com/cli/latest/reference/iam/upload-signing-certificate.html) command\.
```
aws iam upload-signing-certificate --user-name user-name --certificate-body file://path/to/certificate.pem
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/set-up-ami-tools.md |
d92fad586733-1 | ```
To list the certificates for a user, use the [list\-signing\-certificates](https://docs.aws.amazon.com/cli/latest/reference/iam/list-signing-certificates.html) command:
```
aws iam list-signing-certificates --user-name user-name
```
To disable or re\-enable a signing certificate for a user, use the [update\-signing\-certificate](https://docs.aws.amazon.com/cli/latest/reference/iam/update-signing-certificate.html) command\. The following command disables the certificate:
```
aws iam update-signing-certificate --certificate-id OFHPLP4ZULTHYPMSYEX7O4BEXAMPLE --status Inactive --user-name user-name
```
To delete a certificate, use the [delete\-signing\-certificate](https://docs.aws.amazon.com/cli/latest/reference/iam/delete-signing-certificate.html) command:
```
aws iam delete-signing-certificate --user-name user-name --certificate-id OFHPLP4ZULTHYPMSYEX7O4BEXAMPLE
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/set-up-ami-tools.md |
c0212aca7510-0 | If you require high processing capability, you'll benefit from using accelerated computing instances, which provide access to hardware\-based compute accelerators such as Graphics Processing Units \(GPUs\) or Field Programmable Gate Arrays \(FPGAs\)\. Accelerated computing instances enable more parallelism for higher throughput on compute\-intensive workloads\.
GPU\-based instances provide access to NVIDIA GPUs with thousands of compute cores\. You can use GPU\-based accelerated computing instances to accelerate scientific, engineering, and rendering applications by leveraging the CUDA or Open Computing Language \(OpenCL\) parallel computing frameworks\. You can also use them for graphics applications, including game streaming, 3\-D application streaming, and other graphics workloads\.
FPGA\-based instances provide access to large FPGAs with millions of parallel system logic cells\. You can use FPGA\-based accelerated computing instances to accelerate workloads such as genomics, financial analysis, real\-time video processing, big data analysis, and security workloads by leveraging custom hardware accelerations\. You can develop these accelerations using hardware description languages such as Verilog or VHDL, or by using higher\-level languages such as OpenCL parallel computing frameworks\. You can either develop your own hardware acceleration code or purchase hardware accelerations through the [AWS Marketplace](https://aws.amazon.com/marketplace/)\.
**Important**
FPGA\-based instances do not support Microsoft Windows\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/accelerated-computing-instances.md |
c0212aca7510-1 | **Important**
FPGA\-based instances do not support Microsoft Windows\.
You can cluster accelerated computing instances into a cluster placement group\. Cluster placement groups provide low latency and high\-bandwidth connectivity between the instances within a single Availability Zone\. For more information, see [Placement groups](placement-groups.md)\.
**Topics**
+ [Accelerated computing instance families](#gpu-instance-families)
+ [Hardware specifications](#gpu-instance-specifications)
+ [Instance performance](#gpu-instance-performance)
+ [Network performance](#gpu-network-performance)
+ [Instance features](#gpu-instances-features)
+ [Release notes](#gpu-instance-current-limitations)
+ [Installing NVIDIA drivers on Linux instances](install-nvidia-driver.md)
+ [Activate NVIDIA GRID Virtual Applications](activate_grid.md)
+ [Optimizing GPU settings](optimize_gpu.md)
+ [FPGA development](fpga-getting-started.md)
+ [Getting started with AWS Inferentia development](inf-getting-started.md)
For information about Windows accelerated computing instances, see [Windows Accelerated Computing Instances](https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/accelerated-computing-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/accelerated-computing-instances.md |
f543824ecc60-0 | Accelerated computing instance families use hardware accelerators, or co\-processors, to perform some functions, such as floating point number calculations, graphics processing, or data pattern matching, more efficiently than is possible in software running on CPUs\. The following accelerated computing instance families are available for you to launch in Amazon EC2\.
**F1 instances**
F1 instances use Xilinx UltraScale\+ VU9P FPGAs and are designed to accelerate computationally intensive algorithms, such as data\-flow or highly parallel operations not suited to general purpose CPUs\. Each FPGA in an F1 instance contains approximately 2\.5 million logic elements and approximately 6,800 Digital Signal Processing \(DSP\) engines, along with 64 GiB of local DDR ECC protected memory, connected to the instance by a dedicated PCIe Gen3 x16 connection\. F1 instances provide local NVMe SSD volumes\.
Developers can use the FPGA Developer AMI and AWS Hardware Developer Kit to create custom hardware accelerations for use on F1 instances\. The FPGA Developer AMI includes development tools for full\-cycle FPGA development in the cloud\. Using these tools, developers can create and share Amazon FPGA Images \(AFIs\) that can be loaded onto the FPGA of an F1 instance\.
For more information, see [Amazon EC2 F1 Instances](https://aws.amazon.com/ec2/instance-types/f1/)\.
**Inf1 instances**
Inf1 instances use AWS Inferentia machine learning inference chips\. Inferentia was developed to enable highly cost\-effective low latency inference performance at any scale\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/accelerated-computing-instances.md |
f543824ecc60-1 | Developers can use the AWS Deep Learning AMI which comes with prepackaged and optimized software for AWS Inferentia\.
For more information, see [Amazon EC2 Inf1 Instances](https://aws.amazon.com/ec2/instance-types/inf1/)\.
<a name="p3-instances"></a>
**P3 instances**
P3 instances use NVIDIA Tesla V100 GPUs and are designed for general purpose GPU computing using the CUDA or OpenCL programming models or through a machine learning framework\. P3 instances provide high\-bandwidth networking, powerful half, single, and double\-precision floating\-point capabilities, and up to 32 GiB of memory per GPU, which makes them ideal for deep learning, computational fluid dynamics, computational finance, seismic analysis, molecular modeling, genomics, rendering, and other server\-side GPU compute workloads\. Tesla V100 GPUs do not support graphics mode\.
For more information, see [Amazon EC2 P3 Instances](https://aws.amazon.com/ec2/instance-types/p3)\.
P3 instances support NVIDIA NVLink peer to peer transfers\.
To view topology information about the system, run the following command:
```
nvidia-smi topo -m
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/accelerated-computing-instances.md |
f543824ecc60-2 | ```
nvidia-smi topo -m
```
For more information, see [NVIDIA NVLink](https://devblogs.nvidia.com/parallelforall/how-nvlink-will-enable-faster-easier-multi-gpu-computing/)\.
<a name="p2-instances"></a>
**P2 instances**
P2 instances use NVIDIA Tesla K80 GPUs and are designed for general purpose GPU computing using the CUDA or OpenCL programming models\. P2 instances provide high\-bandwidth networking, powerful single and double precision floating\-point capabilities, and 12 GiB of memory per GPU, which makes them ideal for deep learning, graph databases, high\-performance databases, computational fluid dynamics, computational finance, seismic analysis, molecular modeling, genomics, rendering, and other server\-side GPU compute workloads\.
P2 instances support NVIDIA GPUDirect peer to peer transfers\.
To view topology information about the system, run the following command:
```
nvidia-smi topo -m
```
For more information, see [NVIDIA GPUDirect](https://developer.nvidia.com/gpudirect)\.
<a name="g4-instances"></a>
**G4 instances** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/accelerated-computing-instances.md |
f543824ecc60-3 | <a name="g4-instances"></a>
**G4 instances**
G4 instances use NVIDIA Tesla GPUs and provide a cost\-effective, high\-performance platform for general purpose GPU computing using the CUDA or machine learning frameworks along with graphics applications using DirectX or OpenGL\. G4 instances provide high\- bandwidth networking, powerful half and single\-precision floating\-point capabilities, along with INT8 and INT4 precisions\. Each GPU has 16 GiB of GDDR6 memory, making G4 instances well\-suited for machine learning inference, video transcoding, and graphics applications like remote graphics workstations and game streaming in the cloud\.
G4 instances support NVIDIA GRID Virtual Workstation\. For more information, see [NVIDIA Marketplace offerings](http://aws.amazon.com/marketplace/search/results/?page=1&filters=instance_types&instance_types=g4dn.xlarge&searchTerms=NVIDIA%20GRID)\.
<a name="g3-instances"></a>
**G3 instances** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/accelerated-computing-instances.md |
f543824ecc60-4 | <a name="g3-instances"></a>
**G3 instances**
G3 instances use NVIDIA Tesla M60 GPUs and provide a cost\-effective, high\-performance platform for graphics applications using DirectX or OpenGL\. G3 instances also provide NVIDIA GRID Virtual Workstation features, such as support for four monitors with resolutions up to 4096x2160, and NVIDIA GRID Virtual Applications\. G3 instances are well\-suited for applications such as 3D visualizations, graphics\-intensive remote workstations, 3D rendering, video encoding, virtual reality, and other server\-side graphics workloads requiring massively parallel processing power\.
G3 instances support NVIDIA GRID Virtual Workstation and NVIDIA GRID Virtual Applications\. To activate either of these features, see [Activate NVIDIA GRID Virtual Applications](activate_grid.md)\.
<a name="g2-instances"></a>
**G2 instances**
G2 instances use NVIDIA GRID K520 GPUs and provide a cost\-effective, high\-performance platform for graphics applications using DirectX or OpenGL\. NVIDIA GRID GPUs also support NVIDIA’s fast capture and encode API operations\. Example applications include video creation services, 3D visualizations, streaming graphics\-intensive applications, and other server\-side graphics workloads\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/accelerated-computing-instances.md |
41b4fca3f07c-0 | The following is a summary of the hardware specifications for accelerated computing instances\.
| Instance type | Default vCPUs | Memory \(GiB\) | Accelerators |
| --- | --- | --- | --- |
| p2\.xlarge | 4 | 61 | 1 |
| p2\.8xlarge | 32 | 488 | 8 |
| p2\.16xlarge | 64 | 732 | 16 |
| p3\.2xlarge | 8 | 61 | 1 |
| p3\.8xlarge | 32 | 244 | 4 |
| p3\.16xlarge | 64 | 488 | 8 |
| p3dn\.24xlarge | 96 | 768 | 8 |
| g2\.2xlarge | 8 | 15 | 1 |
| g2\.8xlarge | 32 | 60 | 4 |
| g3s\.xlarge | 4 | 30\.5 | 1 |
| g3\.4xlarge | 16 | 122 | 1 |
| g3\.8xlarge | 32 | 244 | 2 |
| g3\.16xlarge | 64 | 488 | 4 |
| g4dn\.xlarge | 4 | 16 | 1 |
| g4dn\.2xlarge | 8 | 32 | 1 |
| g4dn\.4xlarge | 16 | 64 | 1 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/accelerated-computing-instances.md |
41b4fca3f07c-1 | | g4dn\.4xlarge | 16 | 64 | 1 |
| g4dn\.8xlarge | 32 | 128 | 1 |
| g4dn\.12xlarge | 48 | 192 | 4 |
| g4dn\.16xlarge | 64 | 256 | 1 |
| g4dn\.metal | 96 | 384 | 8 |
| f1\.2xlarge | 8 | 122 | 1 |
| f1\.4xlarge | 16 | 244 | 2 |
| f1\.16xlarge | 64 | 976 | 8 |
| inf1\.xlarge | 4 | 8 | 1 |
| inf1\.2xlarge | 8 | 16 | 1 |
| inf1\.6xlarge | 24 | 48 | 4 |
| inf1\.24xlarge | 96 | 192 | 16 |
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/accelerated-computing-instances.md |
ecbcd1946a0e-0 | There are several GPU setting optimizations that you can perform to achieve the best performance on your instances\. For more information, see [Optimizing GPU settings](optimize_gpu.md)\.
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 accelerated computing instances are EBS\-optimized by default at no additional cost\. For more information, see [Amazon EBS–optimized instances](ebs-optimized.md)\.
Some accelerated computing 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/accelerated-computing-instances.md |
6dd9a994264f-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 accelerated computing instances that support enhanced networking\.
| Instance type | Network performance | Enhanced networking |
| --- | --- | --- |
| f1\.2xlarge \| f1\.4xlarge \| g3\.4xlarge \| p3\.2xlarge | Up to 10 Gbps † | [ENA](enhanced-networking-ena.md) |
| g3s\.xlarge \| g3\.8xlarge \| p2\.8xlarge \| p3\.8xlarge | 10 Gbps | [ENA](enhanced-networking-ena.md) |
| g4dn\.xlarge \| g4dn\.2xlarge \| g4dn\.4xlarge \| inf1\.xlarge \| inf1\.2xlarge | Up to 25 Gbps † | [ENA](enhanced-networking-ena.md) | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/accelerated-computing-instances.md |
6dd9a994264f-1 | | f1\.16xlarge \| g3\.16xlarge \| inf1\.6xlarge \| p2\.16xlarge \| p3\.16xlarge | 25 Gbps | [ENA](enhanced-networking-ena.md) |
| g4dn\.8xlarge \| g4dn\.12xlarge \| g4dn\.16xlarge | 50 Gbps | [ENA](enhanced-networking-ena.md) |
| g4dn\.metal \| inf1\.24xlarge \| p3dn\.24xlarge | 100 Gbps | [ENA](enhanced-networking-ena.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/accelerated-computing-instances.md |
7804eba7fd9b-0 | The following is a summary of features for accelerated computing instances\.
| | EBS only | NVMe EBS | Instance store | Placement group |
| --- | --- | --- | --- | --- |
| G2 | No | No | SSD | Yes |
| G3 | Yes | No | No | Yes |
| G4 | No | Yes | NVMe \* | Yes |
| Inf1 | Yes | No | No | Yes |
| P2 | Yes | No | No | Yes |
| P3 | p3dn\.24xlarge: No All other sizes: Yes | p3dn\.24xlarge: Yes All other sizes: No | p3dn\.24xlarge: NVMe \* | Yes |
| F1 | No | 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/accelerated-computing-instances.md |
2986d454d965-0 | + You must launch the instance using an HVM AMI\.
+ 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
+ GPU\-based instances can't access the GPU unless the NVIDIA drivers are installed\. For more information, see [Installing NVIDIA drivers on Linux instances](install-nvidia-driver.md)\.
+ 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\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/accelerated-computing-instances.md |
2986d454d965-1 | + 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:
```
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\.
+ There is a limit of 100 AFIs per Region\.
+ 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/accelerated-computing-instances.md |
7633f8400bd0-0 | An Amazon Machine Image \(AMI\) provides the information required to launch an instance\. You must specify an AMI when you launch an instance\. You can launch multiple instances from a single AMI when you need multiple instances with the same configuration\. You can use different AMIs to launch instances when you need instances with different configurations\.
An AMI includes the following:
+ One or more EBS snapshots, or, for instance\-store\-backed AMIs, a template for the root volume of the instance \(for example, an operating system, an application server, and applications\)\.
+ Launch permissions that control which AWS accounts can use the AMI to launch instances\.
+ A block device mapping that specifies the volumes to attach to the instance when it's launched\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/AMIs.md |
13f08960b5d4-0 | The following diagram summarizes the AMI lifecycle\. After you create and register an AMI, you can use it to launch new instances\. \(You can also launch instances from an AMI if the AMI owner grants you launch permissions\.\) You can copy an AMI within the same Region or to different Regions\. When you no longer require an AMI, you can deregister it\.
![\[The AMI lifecycle (create, register, launch, copy, deregister).\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/ami_lifecycle.png)
You can search for an AMI that meets the criteria for your instance\. You can search for AMIs provided by AWS or AMIs provided by the community\. For more information, see [AMI types](ComponentsAMIs.md) and [Finding a Linux AMI](finding-an-ami.md)\.
After you launch an instance from an AMI, you can connect to it\. When you are connected to an instance, you can use it just like you use any other server\. For information about launching, connecting, and using your instance, see [Amazon EC2 instances](Instances.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/AMIs.md |
cec7b42c9f64-0 | You can launch an instance from an existing AMI, customize the instance, and then save this updated configuration as a custom AMI\. Instances launched from this new custom AMI include the customizations that you made when you created the AMI\.
The root storage device of the instance determines the process you follow to create an AMI\. The root volume of an instance is either an Amazon EBS volume or an instance store volume\. For more information about the root device volume, see [Amazon EC2 root device volume](RootDeviceStorage.md)\.
+ To create an Amazon EBS\-backed AMI, see [Creating an Amazon EBS\-backed Linux AMI](creating-an-ami-ebs.md)\.
+ To create an instance store\-backed AMI, see [Creating an instance store\-backed Linux AMI](creating-an-ami-instance-store.md)\.
To help categorize and manage your AMIs, you can assign custom *tags* to them\. For more information, see [Tagging your Amazon EC2 resources](Using_Tags.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/AMIs.md |
258f4b164788-0 | After you create an AMI, you can keep it private so that only you can use it, or you can share it with a specified list of AWS accounts\. You can also make your custom AMI public so that the community can use it\. Building a safe, secure, usable AMI for public consumption is a fairly straightforward process, if you follow a few simple guidelines\. For information about how to create and use shared AMIs, see [Shared AMIs](sharing-amis.md)\.
You can purchase AMIs from a third party, including AMIs that come with service contracts from organizations such as Red Hat\. You can also create an AMI and sell it to other Amazon EC2 users\. For more information about buying or selling AMIs, see [Paid AMIs](paid-amis.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/AMIs.md |
Subsets and Splits