id
stringlengths 14
16
| text
stringlengths 1
2.43k
| source
stringlengths 99
229
|
|---|---|---|
038c7a905cb3-0 | **To create a new launch template using defined parameters 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 **Launch Templates**, and then choose **Create launch template**\.
1. For **Launch template name**, enter a descriptive name for the launch template\. To tag the launch template on creation, choose **Show Tags**, **Add Tag**, and then enter a tag key and value pair\.
1. For **Template version description**, provide a brief description of the launch template version\.
1. For **Launch template contents**, provide the following information:
+ **AMI ID**: An AMI from which to launch the instance\. To search through all available AMIs, choose **Search for AMI**\. To select a commonly used AMI, choose **Quick Start**\. Or, choose **AWS Marketplace** or **Community AMIs**\. You can use an AMI that you own or [find a suitable AMI](finding-an-ami.md)\.
+ **Instance type**: Ensure that the instance type is compatible with the AMI that you've specified\. For more information, see [Instance types](instance-types.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-launch-templates.md |
038c7a905cb3-1 | + **Key pair name**: The key pair for the instance\. For more information, see [Amazon EC2 key pairs and Linux instances](ec2-key-pairs.md)\.
+ **Network type**: If applicable, whether to launch the instance into a VPC or EC2\-Classic\. If you choose **VPC**, specify the subnet in the **Network interfaces** section\. If you choose **Classic**, ensure that the specified instance type is supported in EC2\-Classic and specify the Availability Zone for the instance\.
+ **Security Groups**: One or more security groups to associate with the instance\. For more information, see [Amazon EC2 security groups for Linux instances](ec2-security-groups.md)\.
1. For **Network interfaces**, you can specify up to two [network interfaces](using-eni.md) for the instance\.
+ **Device**: The device number for the network interface, for example, `eth0` for the primary network interface\. If you leave the field blank, AWS creates the primary network interface\.
+ **Network interface**: The ID of the network interface, or leave blank to let AWS create a new network interface\.
+ **Description**: \(Optional\) A description for the new network interface\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-launch-templates.md |
038c7a905cb3-2 | + **Description**: \(Optional\) A description for the new network interface\.
+ **Subnet**: The subnet in which to create a new network interface\. For the primary network interface \(`eth0`\), this is the subnet in which the instance is launched\. If you've entered an existing network interface for `eth0`, the instance is launched in the subnet in which the network interface is located\.
+ **Auto\-assign public IP**: Whether to automatically assign a public IP address to the network interface with the device index of `eth0`\. This setting can only be enabled for a single, new network interface\.
+ **Primary IP**: A private IPv4 address from the range of your subnet\. Leave blank to let AWS choose a private IPv4 address for you\.
+ **Secondary IP**: A secondary private IPv4 address from the range of your subnet\. Leave blank to let AWS choose one for you\.
+ \(IPv6\-only\) **IPv6 IPs**: An IPv6 address from the range of the subnet\.
+ **Security group ID**: The ID of a security group in your VPC with which to associate the network interface\.
+ **Delete on termination**: Whether the network interface is deleted when the instance is deleted\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-launch-templates.md |
038c7a905cb3-3 | + **Delete on termination**: Whether the network interface is deleted when the instance is deleted\.
+ **Elastic Fabric Adapter**: Indicates whether the network interface is an Elastic Fabric Adapter\. For more information, see [ Elastic Fabric Adapter](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/efa.html)\.
1. For **Storage \(Volumes\)**, specify volumes to attach to the instance besides the volumes specified by the AMI\.
+ **Volume type**: The instance store or Amazon EBS volumes with which to associate your instance\. The type of volume depends on the instance type that you've chosen\. For more information, see [Amazon EC2 instance store](InstanceStorage.md) and [Amazon EBS volumes](ebs-volumes.md)\.
+ **Device name**: A device name for the volume\.
+ **Snapshot**: The ID of the snapshot from which to create the volume\.
+ **Size**: For Amazon EBS volumes, the storage size\.
+ **Volume type**: For Amazon EBS volumes, the volume type\. For more information, see [Amazon EBS volume types](ebs-volume-types.md)\.
+ **IOPS**: For the Provisioned IOPS SSD volume type, the number of I/O operations per second \(IOPS\) that the volume can support\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-launch-templates.md |
038c7a905cb3-4 | + **Delete on termination**: For Amazon EBS volumes, whether to delete the volume when the instance is terminated\. For more information, see [Preserving Amazon EBS volumes on instance termination](terminating-instances.md#preserving-volumes-on-termination)\.
+ **Encrypted**: If the instance type supports EBS encryption, you can enable encryption for the volume\. If you have enabled encryption by default in this Region, encryption is enabled for you\. For more information, see [Amazon EBS encryption](EBSEncryption.md)\.
+ **Key**: The CMK to use for EBS encryption\. You can specify the ARN of any customer master key \(CMK\) that you created using the AWS Key Management Service\. If you specify a CMK, you must also use **Encrypted** to enable encryption\.
1. For **Instance tags**, specify [tags](Using_Tags.md) by providing key and value combinations\. You can tag the instance, the volumes, or both\.
1. For **Advanced Details**, expand the section to view the fields and specify any additional parameters for the instance\.
+ **Purchasing option**: The purchasing model\. Choose **Request Spot instances** to request Spot Instances at the Spot price, capped at the On\-Demand price, and choose **Customize Spot parameters** to change the default Spot Instance settings\. If you do not request a Spot Instance, EC2 launches an On\-Demand Instance by default\. For more information, see [Spot Instances](using-spot-instances.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-launch-templates.md |
038c7a905cb3-5 | + **IAM instance profile**: An AWS Identity and Access Management \(IAM\) instance profile to associate with the instance\. For more information, see [IAM roles for Amazon EC2](iam-roles-for-amazon-ec2.md)\.
+ **Shutdown behavior**: Whether the instance should stop or terminate when shut down\. For more information, see [Changing the instance initiated shutdown behavior](terminating-instances.md#Using_ChangingInstanceInitiatedShutdownBehavior)\.
+ **Stop \- Hibernate behavior**: Whether the instance is enabled for hibernation\. This field is only valid for instances that meet the hibernation prerequisites\. For more information, see [Hibernate your Linux instance](Hibernate.md)\.
+ **Termination protection**: Whether to prevent accidental termination\. For more information, see [Enabling termination protection](terminating-instances.md#Using_ChangingDisableAPITermination)\.
+ **Monitoring**: Whether to enable detailed monitoring of the instance using Amazon CloudWatch\. Additional charges apply\. For more information, see [Monitoring your instances using CloudWatch](using-cloudwatch.md)\.
+ **T2/T3 Unlimited**: Whether to enable applications to burst beyond the baseline for as long as needed\. This field is only valid for T2 and T3 instances\. Additional charges may apply\. For more information, see [Burstable performance instances](burstable-performance-instances.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-launch-templates.md |
038c7a905cb3-6 | + **Placement group name**: Specify a placement group in which to launch the instance\. Not all instance types can be launched in a placement group\. For more information, see [Placement groups](placement-groups.md)\.
+ **EBS\-optimized instance**: Provides additional, dedicated capacity for Amazon EBS I/O\. Not all instance types support this feature, and additional charges apply\. For more information, see [Amazon EBS–optimized instances](ebs-optimized.md)\.
+ **Tenancy**: Choose whether to run your instance on shared hardware \(**Shared**\), isolated, dedicated hardware \(**Dedicated**\), or on a Dedicated Host \(**Dedicated host**\)\. If you choose to launch the instance onto a Dedicated Host, you can specify whether to launch the instance into a host resource group or you can target a specific Dedicated Host\. Additional charges may apply\. For more information, see [Dedicated Instances](dedicated-instance.md) and [Dedicated Hosts](dedicated-hosts-overview.md)\.
+ **RAM disk ID**: A RAM disk for the instance\. If you have specified a kernel, you may need to specify a specific RAM disk with the drivers to support it\. Only valid for paravirtual \(PV\) AMIs\.
+ **Kernel ID**: A kernel for the instance\. Only valid for paravirtual \(PV\) AMIs\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-launch-templates.md |
038c7a905cb3-7 | + **Kernel ID**: A kernel for the instance\. Only valid for paravirtual \(PV\) AMIs\.
+ **User data**: You can specify user data to configure an instance during launch, or to run a configuration script\. For more information, see [Running commands on your Linux instance at launch](user-data.md)\.
1. Choose **Create launch template**\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-launch-templates.md |
6a97cae89893-0 | **To create a launch template using the AWS CLI**
+ Use the [create\-launch\-template](https://docs.aws.amazon.com/cli/latest/reference/ec2/create-launch-template.html) command\. The following example creates a launch template that specifies the following:
+ A tag for the launch template \(`purpose`=`production`\)
+ The instance type \(`r4.4xlarge`\) and AMI \(`ami-8c1be5f6`\) to launch
+ The number of cores \(`4`\) and threads per core \(`2`\) for a total of 8 vCPUs \(4 cores x 2 threads\)
+ The subnet in which to launch the instance \(`subnet-7b16de0c`\)
The template assigns a public IP address and an IPv6 address to the instance and creates a tag for the instance\(`Name`=`webserver`\)\.
```
aws ec2 create-launch-template \
--launch-template-name TemplateForWebServer \
--version-description WebVersion1 \
--tag-specifications 'ResourceType=launch-template,Tags=[{Key=purpose,Value=production}]' \
--launch-template-data file://template-data.json
```
The following is an example `template-data.json` file\.
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-launch-templates.md |
6a97cae89893-1 | ```
The following is an example `template-data.json` file\.
```
{
"NetworkInterfaces": [{
"AssociatePublicIpAddress": true,
"DeviceIndex": 0,
"Ipv6AddressCount": 1,
"SubnetId": "subnet-7b16de0c"
}],
"ImageId": "ami-8c1be5f6",
"InstanceType": "r4.4xlarge",
"TagSpecifications": [{
"ResourceType": "instance",
"Tags": [{
"Key":"Name",
"Value":"webserver"
}]
}],
"CpuOptions": {
"CoreCount":4,
"ThreadsPerCore":2
}
}
```
The following is example output\.
```
{
"LaunchTemplate": {
"LatestVersionNumber": 1,
"LaunchTemplateId": "lt-01238c059e3466abc",
"LaunchTemplateName": "TemplateForWebServer",
"DefaultVersionNumber": 1, | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-launch-templates.md |
6a97cae89893-2 | "LaunchTemplateName": "TemplateForWebServer",
"DefaultVersionNumber": 1,
"CreatedBy": "arn:aws:iam::123456789012:root",
"CreateTime": "2017-11-27T09:13:24.000Z"
}
}
```
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-launch-templates.md |
017f054d4608-0 | ------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-launch-templates.md |
35b7c7c3bd82-0 | **To create a launch template from an existing launch template 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 **Launch Templates**, and then choose **Create launch template**\.
1. For **Launch template name**, enter a descriptive name for the launch template\.
1. For **Template version description**, provide a brief description of the launch template version\.
1. To tag the launch template on creation, expand **Template tags**, choose **Add tag**, and then enter a tag key and value pair\.
1. Expand **Source template**, and for **Launch template name** choose a launch template on which to base the new launch template\.
1. For **Source template version**, choose the launch template version on which to base the new launch template\.
1. Adjust any launch parameters as required, and then choose **Create launch template**\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-launch-templates.md |
0274d49cbac0-0 | **To create a launch template from an existing launch template 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 **Launch Templates**\.
1. Choose **Create launch template**\. Provide a name, description, and tags for the launch template\.
1. For **Source template**, choose a launch template on which to base the new launch template\.
1. For **Source template version**, choose the launch template version on which to base the new launch template\.
1. Adjust any launch parameters as required, and then choose **Create launch template**\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-launch-templates.md |
37d0fff582b4-0 | **To get launch template data from an instance using the AWS CLI**
+ Use the [get\-launch\-template\-data](https://docs.aws.amazon.com/cli/latest/reference/ec2/get-launch-template-data.html) command and specify the instance ID\. You can use the output as a base to create a new launch template or launch template version\. By default, the output includes a top\-level `LaunchTemplateData` object, which cannot be specified in your launch template data\. Use the `--query` option to exclude this object\.
```
aws ec2 get-launch-template-data \
--instance-id i-0123d646e8048babc \
--query "LaunchTemplateData"
```
The following is example output\.
```
{
"Monitoring": {},
"ImageId": "ami-8c1be5f6",
"BlockDeviceMappings": [
{
"DeviceName": "/dev/xvda",
"Ebs": {
"DeleteOnTermination": true
}
}
],
"EbsOptimized": false,
"Placement": {
"Tenancy": "default",
"GroupName": "", | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-launch-templates.md |
37d0fff582b4-1 | "Placement": {
"Tenancy": "default",
"GroupName": "",
"AvailabilityZone": "us-east-1a"
},
"InstanceType": "t2.micro",
"NetworkInterfaces": [
{
"Description": "",
"NetworkInterfaceId": "eni-35306abc",
"PrivateIpAddresses": [
{
"Primary": true,
"PrivateIpAddress": "10.0.0.72"
}
],
"SubnetId": "subnet-7b16de0c",
"Groups": [
"sg-7c227019"
],
"Ipv6Addresses": [
{
"Ipv6Address": "2001:db8:1234:1a00::123"
}
],
"PrivateIpAddress": "10.0.0.72"
}
]
}
```
You can write the output directly to a file, for example:
```
aws ec2 get-launch-template-data \
--instance-id i-0123d646e8048babc \ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-launch-templates.md |
37d0fff582b4-2 | aws ec2 get-launch-template-data \
--instance-id i-0123d646e8048babc \
--query "LaunchTemplateData" >> instance-data.json
```
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-launch-templates.md |
e30e3cb59bbb-0 | **To create a launch template from 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**, **Create Template From Instance**\.
1. Provide a name, description, and tags, and adjust the launch parameters as required\.
**Note**
When you create a launch template from an instance, the instance's network interface IDs and IP addresses are not included in the template\.
1. Choose **Create Template From Instance**\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-launch-templates.md |
e89cac548efa-0 | You can create launch template versions for a specific launch template, set the default version, describe a launch template version, and delete versions that you no longer require\.
**Topics**
+ [Creating a launch template version](#create-launch-template-version)
+ [Setting the default launch template version](#set-default-launch-template-version)
+ [Describing a launch template version](#describe-launch-template-version)
+ [Deleting a launch template version](#delete-launch-template-version) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-launch-templates.md |
bd5aed652806-0 | When you create a launch template version, you can specify new launch parameters or use an existing version as the base for the new version\. For more information about the launch parameters, see [Creating a launch template](#create-launch-template)\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-launch-templates.md |
59965879d220-0 | **To create a launch template version 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 **Launch Templates**\.
1. Select a launch template, and then choose **Actions**, **Modify template \(Create new version\)**\.
1. For **Template version description**, enter a description for the launch template version\.
1. \(Optional\) Expand **Source template** and select a version of the launch template to use as a base for the new launch template version\. The new launch template version inherits the launch parameters from this launch template version\.
1. Modify the launch parameters as required, and choose **Create launch template**\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-launch-templates.md |
3268cb913567-0 | **To create a launch template version 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 **Launch Templates**\.
1. Choose **Create launch template**\.
1. For **What would you like to do**, choose **Create a new template version**
1. For **Launch template name**, select the name of the existing launch template from the list\.
1. For **Template version description**, enter a description for the launch template version\.
1. \(Optional\) Select a version of the launch template, or a version of a different launch template, to use as a base for the new launch template version\. The new launch template version inherits the launch parameters from this launch template version\.
1. Modify the launch parameters as required, and choose **Create launch template**\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-launch-templates.md |
c18a28464697-0 | **To create a launch template version using the AWS CLI**
+ Use the [create\-launch\-template\-version](https://docs.aws.amazon.com/cli/latest/reference/ec2/create-launch-template-version.html) command\. You can specify a source version on which to base the new version\. The new version inherits the launch parameters from this version, and you can override parameters using `--launch-template-data`\. The following example creates a new version based on version 1 of the launch template and specifies a different AMI ID\.
```
aws ec2 create-launch-template-version \
--launch-template-id lt-0abcd290751193123 \
--version-description WebVersion2 \
--source-version 1 \
--launch-template-data "ImageId=ami-c998b6b2"
```
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-launch-templates.md |
eac4c933592c-0 | You can set the default version for the launch template\. When you launch an instance from a launch template and do not specify a version, the instance is launched using the parameters of the default version\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-launch-templates.md |
43050f8d0f10-0 | **To set the default launch template version 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 **Launch Templates**\.
1. Select the launch template and choose **Actions**, **Set default version**\.
1. For **Template version**, select the version number to set as the default version and choose **Set as default version**\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-launch-templates.md |
f31e64e3ac55-0 | **To set the default launch template version 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 **Launch Templates**\.
1. Select the launch template and choose **Actions**, **Set default version**\.
1. For **Default version**, select the version number and choose **Set as default version**\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-launch-templates.md |
05f120df12e0-0 | **To set the default launch template version using the AWS CLI**
+ Use the [modify\-launch\-template](https://docs.aws.amazon.com/cli/latest/reference/ec2/modify-launch-template.html) command and specify the version that you want to set as the default\.
```
aws ec2 modify-launch-template \
--launch-template-id lt-0abcd290751193123 \
--default-version 2
```
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-launch-templates.md |
4154165348ee-0 | Using the console, you can view all the versions of the selected launch template, or get a list of the launch templates whose latest or default version matches a specific version number\. Using the AWS CLI, you can describe all versions, individual versions, or a range of versions of a specified launch template\. You can also describe all the latest versions or all the default versions of all the launch templates in your account\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-launch-templates.md |
ca9490db1039-0 | **To describe a launch template version 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 **Launch Templates**\.
1. You can view a version of a specific launch template, or get a list of the launch templates whose latest or default version matches a specific version number\.
+ To view a version of a launch template: Select the launch template\. On the **Versions** tab, from **Version**, select a version to view its details\.
+ To get a list of all the launch templates whose latest version matches a specific version number: From the search bar, choose **Latest version**, and then choose a version number\.
+ To get a list of all the launch templates whose default version matches a specific version number: From the search bar, choose **Default version**, and then choose a version number\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-launch-templates.md |
a607c94a9702-0 | **To describe a launch template version using the AWS CLI**
+ Use the [describe\-launch\-template\-versions](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-launch-template-versions.html) command and specify the version numbers\. In the following example, versions 1 and 3 are specified\.
```
aws ec2 describe-launch-template-versions \
--launch-template-id lt-0abcd290751193123 \
--versions 1 3
```
**To describe all the latest and default launch template versions in your account using the AWS CLI**
+ Use the [describe\-launch\-template\-versions](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-launch-template-versions.html) command and specify `$Latest`, `$Default`, or both\. You must omit the launch template ID and name in the call\. You cannot specify version numbers\.
```
aws ec2 describe-launch-template-versions \
--versions "$Latest,$Default"
```
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-launch-templates.md |
d8936268b42d-0 | If you no longer require a launch template version, you can delete it\. You cannot replace the version number after you delete it\. You cannot delete the default version of the launch template; you must first assign a different version as the default\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-launch-templates.md |
95f9d53da205-0 | **To delete a launch template version 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 **Launch Templates**\.
1. Select the launch template and choose **Actions**, **Delete template version**\.
1. Select the version to delete and choose **Delete**\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-launch-templates.md |
16e0d90ed513-0 | **To delete a launch template version 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 **Launch Templates**\.
1. Select the launch template and choose **Actions**, **Delete template version**\.
1. Select the version to delete and choose **Delete launch template version**\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-launch-templates.md |
884b5c84f890-0 | **To delete a launch template version using the AWS CLI**
+ Use the [delete\-launch\-template\-versions](https://docs.aws.amazon.com/cli/latest/reference/ec2/delete-launch-template-versions.html) command and specify the version numbers to delete\.
```
aws ec2 delete-launch-template-versions \
--launch-template-id lt-0abcd290751193123 \
--versions 1
```
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-launch-templates.md |
d8dbda1e53c6-0 | You can use the parameters contained in a launch template to launch an instance\. You have the option to override or add launch parameters before you launch the instance\.
Instances that are launched using a launch template are automatically assigned two tags with the keys `aws:ec2launchtemplate:id` and `aws:ec2launchtemplate:version`\. You cannot remove or edit these tags\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-launch-templates.md |
2dca3cc372ba-0 | **To launch an instance from a launch template 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 **Launch Templates**\.
1. Select the launch template and choose **Actions**, **Launch instance from template**\.
1. For **Source template version**, select the launch template version to use\.
1. For **Number of instances**, specify the number of instances to launch\.
1. \(Optional\) You can override or add launch template parameters by changing and adding parameters in the **Instance details** section\.
1. Choose **Launch instance from template**\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-launch-templates.md |
6de9da8b8bd0-0 | **To launch an instance from a launch template 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 **Launch Templates**\.
1. Select the launch template and choose **Actions**, **Launch instance from template**\.
1. Select the launch template version to use\.
1. \(Optional\) You can override or add launch template parameters by changing and adding parameters in the **Instance details** section\.
1. Choose **Launch instance from template**\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-launch-templates.md |
324c965a3920-0 | **To launch an instance from a launch template using the AWS CLI**
+ Use the [run\-instances](https://docs.aws.amazon.com/cli/latest/reference/ec2/run-instances.html) command and specify the `--launch-template` parameter\. Optionally specify the launch template version to use\. If you don't specify the version, the default version is used\.
```
aws ec2 run-instances \
--launch-template LaunchTemplateId=lt-0abcd290751193123,Version=1
```
+ To override a launch template parameter, specify the parameter in the [run\-instances](https://docs.aws.amazon.com/cli/latest/reference/ec2/run-instances.html) command\. The following example overrides the instance type that's specified in the launch template \(if any\)\.
```
aws ec2 run-instances \
--launch-template LaunchTemplateId=lt-0abcd290751193123 \
--instance-type t2.small
```
+ If you specify a nested parameter that's part of a complex structure, the instance is launched using the complex structure as specified in the launch template plus any additional nested parameters that you specify\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-launch-templates.md |
324c965a3920-1 | In the following example, the instance is launched with the tag `Owner=TeamA` as well as any other tags that are specified in the launch template\. If the launch template has an existing tag with a key of `Owner`, the value is replaced with `TeamA`\.
```
aws ec2 run-instances \
--launch-template LaunchTemplateId=lt-0abcd290751193123 \
--tag-specifications "ResourceType=instance,Tags=[{Key=Owner,Value=TeamA}]"
```
In the following example, the instance is launched with a volume with the device name `/dev/xvdb` as well as any other block device mappings that are specified in the launch template\. If the launch template has an existing volume defined for `/dev/xvdb`, its values are replaced with the specified values\.
```
aws ec2 run-instances \
--launch-template LaunchTemplateId=lt-0abcd290751193123 \
--block-device-mappings "DeviceName=/dev/xvdb,Ebs={VolumeSize=20,VolumeType=gp2}"
```
If the instance fails to launch or the state immediately goes to `terminated` instead of `running`, see [Troubleshooting instance launch issues](troubleshooting-launch.md)\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-launch-templates.md |
093408ee9cab-0 | You can create an Auto Scaling group and specify a launch template to use for the group\. When Amazon EC2 Auto Scaling launches instances in the Auto Scaling group, it uses the launch parameters defined in the associated launch template\. For more information, see [Creating an Auto Scaling Group Using a Launch Template](https://docs.aws.amazon.com/autoscaling/ec2/userguide/create-asg-launch-template.html) in the *Amazon EC2 Auto Scaling User Guide*\.
Before you can create an Auto Scaling group using a launch template, you must create a launch template that includes the parameters required to launch an instance in an Auto Scaling group, such as the ID of the AMI\. The new console provides guidance to help you create a template that you can use with Auto Scaling\.
**To create a launch template to use with Auto Scaling 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 **Launch Templates**, and then choose **Create launch template**\.
1. For **Launch template name**, enter a descriptive name for the launch template\.
1. For **Template version description**, provide a brief description of the launch template version\.
1. Under **Auto Scaling guidance**, select the checkbox to have Amazon EC2 provide guidance to help create a template to use with Auto Scaling\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-launch-templates.md |
093408ee9cab-1 | 1. Under **Auto Scaling guidance**, select the checkbox to have Amazon EC2 provide guidance to help create a template to use with Auto Scaling\.
1. Modify the launch parameters as required\. Because you selected Auto Scaling guidance, some fields are required and some fields are not available\. For considerations to keep in mind when creating a launch template, and for information about how to configure the launch parameters for Auto Scaling, see [Creating a Launch Template for an Auto Scaling Group](https://docs.aws.amazon.com/autoscaling/ec2/userguide/create-launch-template.html) in the *Amazon EC2 Auto Scaling User Guide*\.
1. Choose **Create launch template**\.
1. \(Optional\) To create an Auto Scaling group using this launch template, in the **Next steps** page, choose **Create Auto Scaling group**\.
**To create or update an Amazon EC2 Auto Scaling group with a launch template using the AWS CLI**
+ Use the [create\-auto\-scaling\-group](https://docs.aws.amazon.com/cli/latest/reference/autoscaling/create-auto-scaling-group.html) or the [update\-auto\-scaling\-group](https://docs.aws.amazon.com/cli/latest/reference/autoscaling/update-auto-scaling-group.html) command and specify the `--launch-template` parameter\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-launch-templates.md |
22c9a5adda49-0 | You can create an EC2 Fleet request and specify a launch template in the instance configuration\. When Amazon EC2 fulfills the EC2 Fleet request, it uses the launch parameters defined in the associated launch template\. You can override some of the parameters that are specified in the launch template\.
For more information, see [Creating an EC2 Fleet](manage-ec2-fleet.md#create-ec2-fleet)\.
**To create an EC2 Fleet with a launch template using the AWS CLI**
+ Use the [create\-fleet](https://docs.aws.amazon.com/cli/latest/reference/ec2/create-fleet.html) command\. Use the `--launch-template-configs` parameter to specify the launch template and any overrides for the launch template\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-launch-templates.md |
46c50b89ee9d-0 | You can create a Spot Fleet request and specify a launch template in the instance configuration\. When Amazon EC2 fulfills the Spot Fleet request, it uses the launch parameters defined in the associated launch template\. You can override some of the parameters that are specified in the launch template\.
For more information, see [Spot Fleet requests](spot-fleet-requests.md)\.
**To create a Spot Fleet request with a launch template using the AWS CLI**
+ Use the [request\-spot\-fleet](https://docs.aws.amazon.com/cli/latest/reference/ec2/request-spot-fleet.html) command\. Use the `LaunchTemplateConfigs` parameter to specify the launch template and any overrides for the launch template\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-launch-templates.md |
259f93e075c9-0 | If you no longer require a launch template, you can delete it\. Deleting a launch template deletes all of its versions\.
**To delete a launch template \(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 **Launch Templates**\.
1. Select the launch template and choose **Actions**, **Delete template**\.
1. Choose **Delete launch template**\.
**To delete a launch template \(AWS CLI\)**
+ Use the [delete\-launch\-template](https://docs.aws.amazon.com/cli/latest/reference/ec2/delete-launch-template.html) \(AWS CLI\) command and specify the launch template\.
```
aws ec2 delete-launch-template --launch-template-id lt-01238c059e3466abc
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-launch-templates.md |
cf2b13382afb-0 | This tutorial helps you to launch an EFA and MPI\-enabled instance cluster for HPC workloads\. In this tutorial, you will perform the following steps:
**Topics**
+ [Step 1: Prepare an EFA\-enabled security group](#efa-start-security)
+ [Step 2: Launch a temporary instance](#efa-start-tempinstance)
+ [Step 3: Install the EFA software](#efa-start-enable)
+ [Step 4: Disable ptrace protection](#efa-start-ptrace)
+ [Step 5: \(Optional\) Install Intel MPI](#efa-start-impi)
+ [Step 6: Install your HPC application](#efa-start-hpc-app)
+ [Step 7: Create an EFA\-enabled AMI](#efa-start-ami)
+ [Step 8: Launch EFA\-enabled instances into a cluster placement group](#efa-start-instances)
+ [Step 9: Terminate the temporary instance](#efa-start-terminate)
+ [Step 10: Enable passwordless SSH](#efa-start-passwordless) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/efa-start.md |
3d6507f8615f-0 | An EFA requires a security group that allows all inbound and outbound traffic to and from the security group itself\.
**To create an EFA\-enabled security group**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the navigation pane, choose **Security Groups** and then choose **Create Security Group**\.
1. In the **Create Security Group** window, do the following:
1. For **Security group name**, enter a descriptive name for the security group, such as `EFA-enabled security group`\.
1. \(Optional\) For **Description**, enter a brief description of the security group\.
1. For **VPC**, select the VPC into which you intend to launch your EFA\-enabled instances\.
1. Choose **Create**\.
1. Select the security group that you created, and on the **Description** tab, copy the **Group ID**\.
1. On the **Inbound** and **Outbound** tabs, do the following:
1. Choose **Edit**\.
1. For **Type**, choose **All traffic**\.
1. For **Source**, choose **Custom**\.
1. Paste the security group ID that you copied into the field\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/efa-start.md |
3d6507f8615f-1 | 1. For **Source**, choose **Custom**\.
1. Paste the security group ID that you copied into the field\.
1. Choose **Save**\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/efa-start.md |
34c72e08c5d4-0 | Launch a temporary instance that you can use to install and configure the EFA software components\. You use this instance to create an EFA\-enabled AMI from which you can launch your EFA\-enabled instances\.
**To launch a temporary instance**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. Choose **Launch Instance**\.
1. On the **Choose an AMI** page, choose **Select** for one of the following supported AMIs: Amazon Linux, Amazon Linux 2, RHEL 7\.6, RHEL 7\.7, RHEL 7\.8, CentOS 7, Ubuntu 16\.04, and Ubuntu 18\.04\.
1. On the **Choose an Instance Type** page, select one of the following supported instance types and then choose **Next: Configure Instance Details**: `c5n.18xlarge`, `c5n.metal`, `g4dn.metal`, `i3en.24xlarge`, `i3en.metal`, `inf1.24xlarge`, `m5dn.24xlarge`, `m5n.24xlarge`, `p3dn.24xlarge`, `r5dn.24xlarge`, and `r5n.24xlarge`\.
1. On the **Configure Instance Details** page, do the following: | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/efa-start.md |
34c72e08c5d4-1 | 1. On the **Configure Instance Details** page, do the following:
1. For **Elastic Fabric Adapter**, choose **Enable**\.
1. In the **Network Interfaces** section, for device **eth0**, choose **New network interface**\.
1. Choose **Next: Add Storage**\.
1. On the **Add Storage** page, specify the volumes to attach to the instances in addition to the volumes that are specified by the AMI \(such as the root device volume\)\. Then choose **Next: Add Tags**\.
1. On the **Add Tags** page, specify a tag that you can use to identify the temporary instance, and then choose **Next: Configure Security Group**\.
1. On the **Configure Security Group** page, for **Assign a security group**, select **Select an existing security group**, and then select the security group that you created in **Step 1**\.
1. On the **Review Instance Launch** page, review the settings, and then choose **Launch** to choose a key pair and to launch your instance\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/efa-start.md |
99cb46882c4e-0 | Install the EFA\-enabled kernel, EFA drivers, Libfabric, and Open MPI stack that is required to support EFA on your temporary instance\.
The steps differ depending on whether you intend to use EFA with Open MPI, with Intel MPI, or with Open MPI and Intel MPI\.
**To install the EFA software**
1. Connect to the instance you launched\. For more information, see [Connect to your Linux instance](AccessingInstances.md)\.
1. To ensure that all of your software packages are up to date, perform a quick software update on your instance\. This process may take a few minutes\.
+ Amazon Linux, Amazon Linux 2, RHEL 7\.6/7\.7/7\.8, CentOS 7
```
$ sudo yum update -y
```
+ Ubuntu 16\.04 and Ubuntu 18\.04
```
$ sudo apt-get update -y
```
```
$ sudo apt-get upgrade -y
```
1. Download the EFA software installation files\. The software installation files are packaged into a compressed tarball \(`.tar.gz`\) file\. To download the latest *stable* version, use the following command\.
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/efa-start.md |
99cb46882c4e-1 | ```
$ curl -O https://efa-installer.amazonaws.com/aws-efa-installer-1.9.5.tar.gz
```
You can also get the latest version by replacing the version number with `latest` in the preceding command\.
1. \(Optional\) Verify the authenticity and integrity of the EFA tarball \(`.tar.gz`\) file\. We recommend that you do this to verify the identity of the software publisher and to check that the file has not been altered or corrupted since it was published\. If you do not want to verify the tarball file, skip this step\.
**Note**
Alternatively, if you prefer to verify the tarball file by using an MD5 or SHA256 checksum instead, see [Verifying the EFA installer using a checksum](efa-verify.md)\.
1. Download the public GPG key and import it into your keyring\.
```
$ wget https://efa-installer.amazonaws.com/aws-efa-installer.key
```
```
$ gpg --import aws-efa-installer.key
```
The command should return a key value\. Make a note of the key value, because you need it in the next step\.
1. Verify the GPG key's fingerprint\. Run the following command and specify the key value from the previous step\.
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/efa-start.md |
99cb46882c4e-2 | 1. Verify the GPG key's fingerprint\. Run the following command and specify the key value from the previous step\.
```
$ gpg --fingerprint key_value
```
The command should return a fingerprint that is identical to `4E90 91BC BB97 A96B 26B1 5E59 A054 80B1 DD2D 3CCC`\. If the fingerprint does not match, don't run the EFA installation script, and contact AWS Support\.
1. Download the signature file and verify the signature of the EFA tarball file\.
```
$ wget https://efa-installer.amazonaws.com/aws-efa-installer-1.9.5.tar.gz.sig
```
```
$ gpg --verify ./aws-efa-installer-1.9.5.tar.gz.sig
```
The following shows example output\.
```
gpg: Signature made Wed 29 Jul 2020 12:50:13 AM UTC using RSA key ID DD2D3CCC
gpg: Good signature from "Amazon EC2 EFA <[email protected]>"
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/efa-start.md |
99cb46882c4e-3 | gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint: 4E90 91BC BB97 A96B 26B1 5E59 A054 80B1 DD2D 3CCC
```
If the result includes `Good signature`, and the fingerprint matches the fingerprint returned in the previous step, proceed to the next step\. If not, don't run the EFA installation script, and contact AWS Support\.
1. Extract the files from the compressed `.tar.gz` file and navigate into the extracted directory\.
```
$ tar -xf aws-efa-installer-1.9.5.tar.gz
```
```
$ cd aws-efa-installer
```
1. Install the EFA software\. Do one of the following depending on your use case\.
+ **Open MPI and Intel MPI**
If you intend to use EFA with Open MPI and Intel MPI, you must install the EFA software with Libfabric and Open MPI, and you must complete Step 5: \(Optional\) Install Intel MPI\. To install the EFA software with Libfabric and Open MPI, run the following command\.
```
$ sudo ./efa_installer.sh -y
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/efa-start.md |
99cb46882c4e-4 | ```
$ sudo ./efa_installer.sh -y
```
Libfabric is installed in the `/opt/amazon/efa` directory, while Open MPI is installed in the `/opt/amazon/openmpi` directory\.
+ **Open MPI only**
If you intend to use EFA with Open MPI only, you must install the EFA software with Libfabric and Open MPI, and you can skip Step 5: \(Optional\) Install Intel MPI\. To install the EFA software with Libfabric and Open MPI, run the following command\.
```
$ sudo ./efa_installer.sh -y
```
Libfabric is installed in the `/opt/amazon/efa` directory, while Open MPI is installed in the `/opt/amazon/openmpi` directory\.
+ **Intel MPI only**
If you intend to use EFA with Intel MPI only, you can install the EFA software without Libfabric and Open MPI\. In this case, Intel MPI uses its embedded Libfabric\. If you choose to do this, you must complete Step 5: \(Optional\) Install Intel MPI\.
To install the EFA software without Libfabric and Open MPI, run the following command\.
```
$ sudo ./efa_installer.sh -y --minimal
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/efa-start.md |
99cb46882c4e-5 | ```
$ sudo ./efa_installer.sh -y --minimal
```
1. Log out of the instance and then log back in\.
1. Confirm that the EFA software components were successfully installed\.
```
$ fi_info -p efa
```
The command should return information about the Libfabric EFA interfaces\. The following example shows the command output\.
```
provider: efa
fabric: EFA-fe80::94:3dff:fe89:1b70
domain: efa_0-rdm
version: 2.0
type: FI_EP_RDM
protocol: FI_PROTO_EFA
provider: efa
fabric: EFA-fe80::94:3dff:fe89:1b70
domain: efa_0-dgrm
version: 2.0
type: FI_EP_DGRAM
protocol: FI_PROTO_EFA
provider: efa;ofi_rxd
fabric: EFA-fe80::94:3dff:fe89:1b70
domain: efa_0-dgrm
version: 1.0
type: FI_EP_RDM
protocol: FI_PROTO_RXD
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/efa-start.md |
fb3657b5d370-0 | To improve your HPC application's performance, Libfabric uses the instance's local memory for interprocess communications when the processes are running on the same instance\.
The shared memory feature uses Cross Memory Attach \(CMA\), which is not supported with *ptrace protection*\. If you are using a Linux distribution that has ptrace protection enabled by default, such as Ubuntu, you must disable it\. If your Linux distribution does not have ptrace protection enabled by default, skip this step\.
**To disable ptrace protection**
Do one of the following:
+ To temporarily disable ptrace protection for testing purposes, run the following command\.
```
$ sudo sysctl -w kernel.yama.ptrace_scope=0
```
+ To permanently disable ptrace protection, add `kernel.yama.ptrace_scope = 0` to `/etc/sysctl.d/10-ptrace.conf` and reboot the instance\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/efa-start.md |
a600f50fda4b-0 | **Important**
If you intend to only use Open MPI, skip this step\. Perform this step only if you intend to use Intel MPI\.
Intel MPI requires an additional installation and environment variable configuration\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/efa-start.md |
08b6e7d74dbb-0 | Ensure that the user performing the following steps has sudo permissions\.
**To install Intel MPI**
1. To download the Intel MPI installation files, see the [ Intel Developer Zone website](https://software.intel.com/en-us/mpi-library/choose-download/linux)\.
You must register before you can download the installation files\. After you have registered, do the following:
1. For **Product**, choose **Intel MPI Library for Linux**\.
1. For **Version**, choose **2019 Update 7**, and then choose **Full Product**\.
1. The installation files are packaged into a compressed `.tar.gz` file\. Extract the files from the compressed `.tar.gz` file and navigate into the extracted directory\.
```
$ tar -xf file_name.tgz
```
```
$ cd directory_name
```
1. Open `silent.cfg` using your preferred text editor\. In line 10, change `ACCEPT_EULA=decline` to `ACCEPT_EULA=accept`\. Save the changes and close the file\.
1. Run the installation script\.
```
$ sudo ./install.sh -s silent.cfg
```
Intel MPI is installed in the `/opt/intel/impi/` directory by default\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/efa-start.md |
08b6e7d74dbb-1 | ```
Intel MPI is installed in the `/opt/intel/impi/` directory by default\.
1. Add the Intel MPI environment variables to the corresponding shell startup scripts to ensure that they are set each time that the instance starts\. Do one of the following depending on your shell\.
+ For **bash**, add the following environment variable to `/home/username/.bashrc` and `/home/username/.bash_profile`\.
```
source /opt/intel/compilers_and_libraries/linux/mpi/intel64/bin/mpivars.sh
```
+ For **csh and tcsh**, add the following environment variable to `/home/username/.cshrc`\.
```
source /opt/intel/compilers_and_libraries/linux/mpi/intel64/bin/mpivars.csh
```
1. Log out of the instance and then log back in\.
1. Run the following command to confirm that Intel MPI was successfully installed\.
```
$ which mpicc
```
Ensure that the returned path includes the `/opt/intel/` subdirectory\.
**Note**
If you no longer want to use Intel MPI, remove the environment variables from the shell startup scripts\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/efa-start.md |
67ac04fea9a5-0 | Install the HPC application on the temporary instance\. The installation procedure varies depending on the specific HPC application\. For more information about installing software on your Linux instance, see [Managing Software on Your Linux Instance](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/managing-software.html)\.
**Note**
You might need to refer to your HPC application’s documentation for installation instructions\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/efa-start.md |
688aa4e30cd6-0 | After you have installed the required software components, you create an AMI that you can reuse to launch your EFA\-enabled instances\.
**To create an AMI from your temporary instance**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the navigation pane, choose **Instances**\.
1. Select the temporary instance that you created and choose **Actions**, **Image**, **Create Image**\.
1. In the **Create Image** window, do the following:
1. For **Image name**, enter a descriptive name for the AMI\.
1. \(Optional\) For **Image description**, enter a brief description of the AMI\.
1. Choose **Create Image** and then choose **Close**\.
1. In the navigation pane, choose **AMIs**\.
1. Locate the AMI you created in the list\. Wait for the Status to transition from `pending` to `available` before continuing to the next step\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/efa-start.md |
3cc4e84b08b9-0 | Launch your EFA\-enabled instances into a cluster placement group using the EFA\-enabled AMI that you created in **Step 7**, and the EFA\-enabled security group that you created in **Step 1**\.
**Note**
It is not an absolute requirement to launch your EFA\-enabled instances into a cluster placement group\. However, we do recommend running your EFA\-enabled instances in a cluster placement group as it launches the instances into a low\-latency group in a single Availability Zone\.
**To launch your EFA\-enabled instances into a cluster placement group**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. Choose **Launch Instance**\.
1. On the **Choose an AMI** page, choose **My AMIs**, find the AMI that you created in **Step 7**, and then choose **Select**\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/efa-start.md |
3cc4e84b08b9-1 | 1. On the **Choose an Instance Type** page, select one of the following supported instance types and then choose **Next: Configure Instance Details**: `c5n.18xlarge`, `c5n.metal`, `g4dn.metal`, `i3en.24xlarge`, `i3en.metal`, `inf1.24xlarge`, `m5dn.24xlarge`, `m5n.24xlarge`, `p3dn.24xlarge`, `r5dn.24xlarge`, and `r5n.24xlarge`\.
1. On the **Configure Instance Details** page, do the following:
1. For **Number of instances**, enter the number of EFA\-enabled instances that you want to launch\.
1. For **Network** and **Subnet**, select the VPC and subnet into which to launch the instances\.
1. For **Placement group**, select **Add instance to placement group**\.
1. For **Placement group name**, select **Add to a new placement group**, enter a descriptive name for the placement group, and then for **Placement group strategy**, select **cluster**\.
1. For **EFA**, choose **Enable**\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/efa-start.md |
3cc4e84b08b9-2 | 1. For **EFA**, choose **Enable**\.
1. In the **Network Interfaces** section, for device **eth0**, choose **New network interface**\. You can optionally specify a primary IPv4 address and one or more secondary IPv4 addresses\. If you're launching the instance into a subnet that has an associated IPv6 CIDR block, you can optionally specify a primary IPv6 address and one or more secondary IPv6 addresses\.
1. Choose **Next: Add Storage**\.
1. On the **Add Storage** page, specify the volumes to attach to the instances in addition to the volumes specified by the AMI \(such as the root device volume\), and then choose **Next: Add Tags**\.
1. On the **Add Tags** page, specify tags for the instances, such as a user\-friendly name, and then choose **Next: Configure Security Group**\.
1. On the **Configure Security Group** page, for **Assign a security group**, select **Select an existing security group**, and then select the security group that you created in **Step 1**\.
1. Choose **Review and Launch**\.
1. On the **Review Instance Launch** page, review the settings, and then choose **Launch** to choose a key pair and to launch your instances\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/efa-start.md |
fe95bcab88be-0 | At this point, you no longer need the temporary instance that you launched\. You can terminate the instance to stop incurring charges for it\.
**To terminate the temporary instance**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the navigation pane, choose **Instances**\.
1. Select the temporary instance that you created and then choose **Actions**, **Instance State**, **Terminate**, **Yes, Terminate**\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/efa-start.md |
811dd6678c84-0 | To enable your applications to run across all of the instances in your cluster, you must enable passwordless SSH access from the leader node to the member nodes\. The leader node is the instance from which you run your applications\. The remaining instances in the cluster are the member nodes\.
**To enable passwordless SSH between the instances in the cluster**
1. Select one instance in the cluster as the leader node, and connect to it\.
1. Disable `strictHostKeyChecking` and enable `ForwardAgent` on the leader node\. Open `~/.ssh/config` using your preferred text editor and add the following\.
```
Host *
ForwardAgent yes
Host *
StrictHostKeyChecking no
```
1. Generate an RSA key pair\.
```
$ ssh-keygen -t rsa -N "" -f /home/ubuntu/.ssh/id_rsa
```
The key pair is created in the `$HOME/.ssh/` directory\.
1. Change the permissions of the private key on the leader node\.
```
$ chmod 600 ~/.ssh/id_rsa
```
1. Open `~/.ssh/id_rsa.pub` using your preferred text editor and copy the key\.
1. For each member node in the cluster, do the following: | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/efa-start.md |
811dd6678c84-1 | 1. For each member node in the cluster, do the following:
1. Connect to the instance\.
1. Open `~/.ssh/authorized_keys` using your preferred text editor and add the public key that you copied earlier\.
1. To test that the passwordless SSH is functioning as expected, connect to your leader node and run the following command\.
```
$ ssh member_node_private_ip
```
You should connect to the member node without being prompted for a key or password\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/efa-start.md |
b1639c3ae867-0 | To create an Amazon EBS\-backed Linux AMI, start from an instance that you've launched from an existing Amazon EBS\-backed Linux AMI\. This can be an AMI you have obtained from the AWS Marketplace, an AMI you have created using the [AWS Server Migration Service](https://aws.amazon.com/server-migration-service/) or [VM Import/Export](https://docs.aws.amazon.com/vm-import/latest/userguide/what-is-vmimport.html), or any other AMI you can access\. After you customize the instance to suit your needs, create and register a new AMI, which you can use to launch new instances with these customizations\.
The procedures described below work for Amazon EC2 instances backed by encrypted Amazon EBS volumes \(including the root volume\) as well as for unencrypted volumes\.
The AMI creation process is different for instance store\-backed AMIs\. For more information about the differences between Amazon EBS\-backed and instance store\-backed instances, and how to determine the root device type for your instance, see [Storage for the root device](ComponentsAMIs.md#storage-for-the-root-device)\. For more information about creating an instance store\-backed Linux AMI, see [Creating an instance store\-backed Linux AMI](creating-an-ami-instance-store.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/creating-an-ami-ebs.md |
b1639c3ae867-1 | For more information about creating an Amazon EBS\-backed Windows AMI, see [Creating an Amazon EBS\-Backed Windows AMI](https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/Creating_EBSbacked_WinAMI.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/creating-an-ami-ebs.md |
073d3626117e-0 | First, launch an instance from an AMI that's similar to the AMI that you'd like to create\. You can connect to your instance and customize it\. When the instance is configured correctly, ensure data integrity by stopping the instance before you create an AMI, then create the image\. When you create an Amazon EBS\-backed AMI, we automatically register it for you\.
Amazon EC2 powers down the instance before creating the AMI to ensure that everything on the instance is stopped and in a consistent state during the creation process\. If you're confident that your instance is in a consistent state appropriate for AMI creation, you can tell Amazon EC2 not to power down and reboot the instance\. Some file systems, such as XFS, can freeze and unfreeze activity, making it safe to create the image without rebooting the instance\.
During the AMI\-creation process, Amazon EC2 creates snapshots of your instance's root volume and any other EBS volumes attached to your instance\. You're charged for the snapshots until you deregister the AMI and delete the snapshots\. For more information, see [Deregistering your Linux AMI](deregister-ami.md)\. If any volumes attached to the instance are encrypted, the new AMI only launches successfully on instances that support Amazon EBS encryption\. For more information, see [Amazon EBS encryption](EBSEncryption.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/creating-an-ami-ebs.md |
073d3626117e-1 | Depending on the size of the volumes, it can take several minutes for the AMI\-creation process to complete \(sometimes up to 24 hours\)\. You may find it more efficient to create snapshots of your volumes before creating your AMI\. This way, only small, incremental snapshots need to be created when the AMI is created, and the process completes more quickly \(the total time for snapshot creation remains the same\)\. For more information, see [Creating Amazon EBS snapshots](ebs-creating-snapshot.md)\.
After the process completes, you have a new AMI and snapshot created from the root volume of the instance\. When you launch an instance using the new AMI, we create a new EBS volume for its root volume using the snapshot\.
If you add instance\-store volumes or EBS volumes to your instance in addition to the root device volume, the block device mapping for the new AMI contains information for these volumes, and the block device mappings for instances that you launch from the new AMI automatically contain information for these volumes\. The instance\-store volumes specified in the block device mapping for the new instance are new and don't contain any data from the instance store volumes of the instance you used to create the AMI\. The data on EBS volumes persists\. For more information, see [Block device mapping](block-device-mapping-concepts.md)\.
**Note** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/creating-an-ami-ebs.md |
073d3626117e-2 | **Note**
When you create a new instance from an EBS\-backed AMI, you should initialize both its root volume and any additional EBS storage before putting it into production\. For more information, see [Initializing Amazon EBS Volumes](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-initialize.html)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/creating-an-ami-ebs.md |
b247ec8f439c-0 | You can create an AMI using the AWS Management Console or the command line\. The following diagram summarizes the process for creating an Amazon EBS\-backed AMI from a running EC2 instance\. Start with an existing AMI, launch an instance, customize it, create a new AMI from it, and finally launch an instance of your new AMI\. The steps in the following diagram match the steps in the procedure below\.
![\[Workflow for creating an AMI from an instance\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/running-instance.png)
**To create an AMI from an instance using the console**
1. Select an appropriate EBS\-backed AMI to serve as a starting point for your new AMI, and configure it as needed before launch\. For more information, see [Launching an instance using the Launch Instance Wizard](launching-instance.md)\.
1. Choose **Launch** to launch an instance of the EBS\-backed AMI that you've selected\. Accept the default values as you step through the wizard\. For more information, see [Launching an instance using the Launch Instance Wizard](launching-instance.md)\.
1. While the instance is running, connect to it\. You can perform any of the following actions on your instance to customize it for your needs:
+ Install software and applications
+ Copy data
+ Reduce start time by deleting temporary files, defragmenting your hard drive, and zeroing out free space
+ Attach additional Amazon EBS volumes | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/creating-an-ami-ebs.md |
b247ec8f439c-1 | + Reduce start time by deleting temporary files, defragmenting your hard drive, and zeroing out free space
+ Attach additional Amazon EBS volumes
1. \(Optional\) Create snapshots of all the volumes attached to your instance\. For more information about creating snapshots, see [Creating Amazon EBS snapshots](ebs-creating-snapshot.md)\.
1. In the navigation pane, choose **Instances**, select your instance, and then choose **Actions**, **Image**, **Create Image**\.
**Tip**
If this option is disabled, your instance isn't an Amazon EBS\-backed instance\.
1. In the **Create Image** dialog box, specify the following information, and then choose **Create Image**\.
+ **Image name** – A unique name for the image\.
+ **Image description** – An optional description of the image, up to 255 characters\.
+ **No reboot** – This option is not selected by default\. Amazon EC2 shuts down the instance, takes snapshots of any attached volumes, creates and registers the AMI, and then reboots the instance\. Select **No reboot** to avoid having your instance shut down\.
**Warning**
If you select **No reboot**, we can't guarantee the file system integrity of the created image\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/creating-an-ami-ebs.md |
b247ec8f439c-2 | **Warning**
If you select **No reboot**, we can't guarantee the file system integrity of the created image\.
+ **Instance Volumes** – The fields in this section enable you to modify the root volume, and add additional Amazon EBS and instance store volumes\. For information about each field, pause on the **i** icon next to each field to display field tooltips\. Some important points are listed below\.
+ To change the size of the root volume, locate **Root** in the **Volume Type** column, and for **Size \(GiB\)**, type the required value\.
+ If you select **Delete on Termination**, when you terminate the instance created from this AMI, the EBS volume is deleted\. If you clear **Delete on Termination**, when you terminate the instance, the EBS volume is not deleted\. For more information, see [Preserving Amazon EBS volumes on instance termination](terminating-instances.md#preserving-volumes-on-termination)\.
+ To add an Amazon EBS volume, choose **Add New Volume** \(which adds a new row\)\. For **Volume Type**, choose **EBS**, and fill in the fields in the row\. When you launch an instance from your new AMI, additional volumes are automatically attached to the instance\. Empty volumes must be formatted and mounted\. Volumes based on a snapshot must be mounted\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/creating-an-ami-ebs.md |
b247ec8f439c-3 | + To add an instance store volume, see [Adding instance store volumes to an AMI](add-instance-store-volumes.md#adding-instance-storage-ami)\. When you launch an instance from your new AMI, additional volumes are automatically initialized and mounted\. These volumes do not contain data from the instance store volumes of the running instance on which you based your AMI\.
1. To view the status of your AMI while it is being created, in the navigation pane, choose **AMIs**\. Initially, the status is `pending` but should change to `available` after a few minutes\.
\(Optional\) To view the snapshot that was created for the new AMI, choose **Snapshots**\. When you launch an instance from this AMI, we use this snapshot to create its root device volume\.
1. Launch an instance from your new AMI\. For more information, see [Launching an instance using the Launch Instance Wizard](launching-instance.md)\.
1. The new running instance contains all of the customizations that you applied in previous steps\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/creating-an-ami-ebs.md |
008b6dad9e34-0 | You can use one of the following commands\. For more information about these command line interfaces, see [Accessing Amazon EC2](concepts.md#access-ec2)\.
+ [create\-image](https://docs.aws.amazon.com/cli/latest/reference/ec2/create-image.html) \(AWS CLI\)
+ [New\-EC2Image](https://docs.aws.amazon.com/powershell/latest/reference/items/New-EC2Image.html) \(AWS Tools for Windows PowerShell\) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/creating-an-ami-ebs.md |
0780564a4205-0 | If you have a snapshot of the root device volume of an instance, you can create an AMI from this snapshot using the AWS Management Console or the command line\.
**To create an AMI from a snapshot 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, under **Elastic Block Store**, choose **Snapshots**\.
1. Choose the snapshot and choose **Actions**, **Create Image**\.
1. In the **Create Image from EBS Snapshot** dialog box, complete the fields to create your AMI, then choose **Create**\. If you're re\-creating a parent instance, then choose the same options as the parent instance\.
+ **Architecture**: Choose **i386** for 32\-bit or **x86\_64** for 64\-bit\.
+ **Root device name**: Enter the appropriate name for the root volume\. For more information, see [Device naming on Linux instances](device_naming.md)\.
+ **Virtualization type**: Choose whether instances launched from this AMI use paravirtual \(PV\) or hardware virtual machine \(HVM\) virtualization\. For more information, see [Linux AMI virtualization types](virtualization_types.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/creating-an-ami-ebs.md |
0780564a4205-1 | + \(PV virtualization type only\) **Kernel ID** and **RAM disk ID**: Choose the AKI and ARI from the lists\. If you choose the default AKI or don't choose an AKI, you must specify an AKI every time you launch an instance using this AMI\. In addition, your instance may fail the health checks if the default AKI is incompatible with the instance\.
+ \(Optional\) **Block Device Mappings**: Add volumes or expand the default size of the root volume for the AMI\. For more information about resizing the file system on your instance for a larger volume, see [Extending a Linux file system after resizing a volume](recognize-expanded-volume-linux.md)\.
**To create an AMI from a snapshot 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)\.
+ [register\-image](https://docs.aws.amazon.com/cli/latest/reference/ec2/register-image.html) \(AWS CLI\)
+ [Register\-EC2Image](https://docs.aws.amazon.com/powershell/latest/reference/items/Register-EC2Image.html) \(AWS Tools for Windows PowerShell\) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/creating-an-ami-ebs.md |
5e8b54143f90-0 | You can launch an instance from an AMI that you created from an instance or snapshot\.
**To launch an instance from your AMI**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the navigation pane, under **Images**, choose **AMIs**\.
1. Set the filter to **Owned by me** and select your AMI\.
1. Choose **Actions**, **Launch**\.
1. Follow the wizard to launch your instance\. For more information about each step in the wizard, see [Launching an instance using the Launch Instance Wizard](launching-instance.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/creating-an-ami-ebs.md |
c8010a5179d0-0 | With instance status monitoring, you can quickly determine whether Amazon EC2 has detected any problems that might prevent your instances from running applications\. Amazon EC2 performs automated checks on every running EC2 instance to identify hardware and software issues\. You can view the results of these status checks to identify specific and detectable problems\. The event status data augments the information that Amazon EC2 already provides about the state of each instance \(such as `pending`, `running`, `stopping`\) and the utilization metrics that Amazon CloudWatch monitors \(CPU utilization, network traffic, and disk activity\)\.
Status checks are performed every minute, returning a pass or a fail status\. If all checks pass, the overall status of the instance is **OK**\. If one or more checks fail, the overall status is **impaired**\. Status checks are built into Amazon EC2, so they cannot be disabled or deleted\.
When a status check fails, the corresponding CloudWatch metric for status checks is incremented\. For more information, see [Status check metrics](viewing_metrics_with_cloudwatch.md#status-check-metrics)\. You can use these metrics to create CloudWatch alarms that are triggered based on the result of the status checks\. For example, you can create an alarm to warn you if status checks fail on a specific instance\. For more information, see [Creating and editing status check alarms](#creating_status_check_alarms)\.
You can also create an Amazon CloudWatch alarm that monitors an Amazon EC2 instance and automatically recovers the instance if it becomes impaired due to an underlying issue\. For more information, see [Recover your instance](ec2-instance-recover.md)\.
**Topics** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-system-instance-status-check.md |
c8010a5179d0-1 | **Topics**
+ [Types of status checks](#types-of-instance-status-checks)
+ [Viewing status checks](#viewing_status)
+ [Reporting instance status](#reporting_status)
+ [Creating and editing status check alarms](#creating_status_check_alarms) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-system-instance-status-check.md |
c631b2c1e30f-0 | There are two types of status checks: system status checks and instance status checks\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-system-instance-status-check.md |
3936c591afa3-0 | System status checks monitor the AWS systems on which your instance runs\. These checks detect underlying problems with your instance that require AWS involvement to repair\. When a system status check fails, you can choose to wait for AWS to fix the issue, or you can resolve it yourself\. For instances backed by Amazon EBS, you can stop and start the instance yourself, which in most cases results in the instance being migrated to a new host\. For instances backed by instance store, you can terminate and replace the instance\.
The following are examples of problems that can cause system status checks to fail:
+ Loss of network connectivity
+ Loss of system power
+ Software issues on the physical host
+ Hardware issues on the physical host that impact network reachability | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-system-instance-status-check.md |
5c86fb81604b-0 | Instance status checks monitor the software and network configuration of your individual instance\. Amazon EC2 checks the health of the instance by sending an address resolution protocol \(ARP\) request to the network interface \(NIC\)\. These checks detect problems that require your involvement to repair\. When an instance status check fails, you typically must address the problem yourself \(for example, by rebooting the instance or by making instance configuration changes\)\.
The following are examples of problems that can cause instance status checks to fail:
+ Failed system status checks
+ Incorrect networking or startup configuration
+ Exhausted memory
+ Corrupted file system
+ Incompatible kernel | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-system-instance-status-check.md |
59044f6265ad-0 | Amazon EC2 provides you with several ways to view and work with status checks\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-system-instance-status-check.md |
d4efaafddb13-0 | You can view status checks using the AWS Management Console\.
**To view status checks \(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. On the **Instances** page, the **Status Checks** column lists the operational status of each instance\.
1. To view the status of a specific instance, select the instance, and then choose the **Status Checks** tab\.
![\[Viewing status\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/status-check-tab.png)
If you have an instance with a failed status check and the instance has been unreachable for over 20 minutes, choose **AWS Support** to submit a request for assistance\. To troubleshoot system or instance status check failures yourself, see [Troubleshooting instances with failed status checks](TroubleshootingInstances.md)\.
1. To review the CloudWatch metrics for status checks, select the instance, and then choose the **Monitoring** tab\. Scroll until you see the graphs for the following metrics:
+ **Status Check Failed \(Any\)**
+ **Status Check Failed \(Instance\)**
+ **Status Check Failed \(System\)** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-system-instance-status-check.md |
00ef28fde352-0 | You can view status checks for running instances using the [describe\-instance\-status](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-instance-status.html) \(AWS CLI\) command\.
To view the status of all instances, use the following command\.
```
aws ec2 describe-instance-status
```
To get the status of all instances with an instance status of `impaired`, use the following command\.
```
aws ec2 describe-instance-status \
--filters Name=instance-status.status,Values=impaired
```
To get the status of a single instance, use the following command\.
```
aws ec2 describe-instance-status \
--instance-ids i-1234567890abcdef0
```
Alternatively, use the following commands:
+ [Get\-EC2InstanceStatus](https://docs.aws.amazon.com/powershell/latest/reference/items/Get-EC2InstanceStatus.html) \(AWS Tools for Windows PowerShell\)
+ [DescribeInstanceStatus](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/ApiReference-query-DescribeInstanceStatus.html) \(Amazon EC2 Query API\) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-system-instance-status-check.md |
00ef28fde352-1 | If you have an instance with a failed status check, see [Troubleshooting instances with failed status checks](TroubleshootingInstances.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-system-instance-status-check.md |
3b5beb5035d9-0 | You can provide feedback if you are having problems with an instance whose status is not shown as impaired, or if you want to send AWS additional details about the problems you are experiencing with an impaired instance\.
We use reported feedback to identify issues impacting multiple customers, but do not respond to individual account issues\. Providing feedback does not change the status check results that you currently see for the instance\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-system-instance-status-check.md |
9c0077a9fb30-0 | **To report instance status \(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, choose the **Status Checks** tab, and choose **Submit feedback**\.
1. Complete the **Report Instance Status** form, and then choose **Submit**\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-system-instance-status-check.md |
bc50045d311a-0 | Use the [report\-instance\-status](https://docs.aws.amazon.com/cli/latest/reference/ec2/report-instance-status.html) \(AWS CLI\) command to send feedback about the status of an impaired instance\.
```
aws ec2 report-instance-status \
--instances i-1234567890abcdef0 \
--status impaired \
--reason-codes code
```
Alternatively, use the following commands:
+ [Send\-EC2InstanceStatus](https://docs.aws.amazon.com/powershell/latest/reference/items/Send-EC2InstanceStatus.html) \(AWS Tools for Windows PowerShell\)
+ [ReportInstanceStatus](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/ApiReference-query-ReportInstanceStatus.html) \(Amazon EC2 Query API\) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-system-instance-status-check.md |
2675d2e18c1a-0 | You can use the [status check metrics](viewing_metrics_with_cloudwatch.md#status-check-metrics) to create CloudWatch alarms to notify you when an instance has a failed status check\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-system-instance-status-check.md |
92fe7ff67049-0 | Use the following procedure to configure an alarm that sends you a notification by email, or stops, terminates, or recovers an instance when it fails a status check\.
**To create a status check alarm \(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, choose the **Status Checks** tab, and choose **Create Status Check Alarm**\.
1. Select **Send a notification to**\. Choose an existing SNS topic, or choose **create topic** to create a new one\. If creating a new topic, in **With these recipients**, enter your email address and the addresses of any additional recipients, separated by commas\.
1. \(Optional\) Select **Take the action**, and then select the action that you'd like to take\.
1. In **Whenever**, select the status check that you want to be notified about\.
If you selected **Recover this instance** in the previous step, select **Status Check Failed \(System\)**\.
1. In **For at least**, set the number of periods you want to evaluate and in **consecutive periods**, select the evaluation period duration before triggering the alarm and sending an email\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-system-instance-status-check.md |
92fe7ff67049-1 | 1. \(Optional\) In **Name of alarm**, replace the default name with another name for the alarm\.
1. Choose **Create Alarm**\.
**Important**
If you added an email address to the list of recipients or created a new topic, Amazon SNS sends a subscription confirmation email message to each new address\. Each recipient must confirm the subscription by choosing the link contained in that message\. Alert notifications are sent only to confirmed addresses\.
If you need to make changes to an instance status alarm, you can edit it\.
**To edit a status check alarm 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**, **CloudWatch Monitoring**, **Add/Edit Alarms**\.
1. In the **Alarm Details** dialog box, choose the name of the alarm\.
1. In the **Edit Alarm** dialog box, make the desired changes, and then choose **Save**\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-system-instance-status-check.md |
5facd389a91c-0 | In the following example, the alarm publishes a notification to an SNS topic, `arn:aws:sns:us-west-2:111122223333:my-sns-topic`, when the instance fails either the instance check or system status check for at least two consecutive periods\. The CloudWatch metric used is `StatusCheckFailed`\.
**To create a status check alarm using the AWS CLI**
1. Select an existing SNS topic or create a new one\. For more information, see [Using the AWS CLI with Amazon SNS](https://docs.aws.amazon.com/cli/latest/userguide/cli-sqs-queue-sns-topic.html) in the *AWS Command Line Interface User Guide*\.
1. Use the following [list\-metrics](https://docs.aws.amazon.com/cli/latest/reference/cloudwatch/list-metrics.html) command to view the available Amazon CloudWatch metrics for Amazon EC2\.
```
aws cloudwatch list-metrics --namespace AWS/EC2
```
1. Use the following [put\-metric\-alarm](https://docs.aws.amazon.com/cli/latest/reference/cloudwatch/put-metric-alarm.html) command to create the alarm\.
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-system-instance-status-check.md |
5facd389a91c-1 | ```
aws cloudwatch put-metric-alarm --alarm-name StatusCheckFailed-Alarm-for-i-1234567890abcdef0 --metric-name StatusCheckFailed --namespace AWS/EC2 --statistic Maximum --dimensions Name=InstanceId,Value=i-1234567890abcdef0 --unit Count --period 300 --evaluation-periods 2 --threshold 1 --comparison-operator GreaterThanOrEqualToThreshold --alarm-actions arn:aws:sns:us-west-2:111122223333:my-sns-topic
```
The period is the time frame, in seconds, in which Amazon CloudWatch metrics are collected\. This example uses 300, which is 60 seconds multiplied by 5 minutes\. The evaluation period is the number of consecutive periods for which the value of the metric must be compared to the threshold\. This example uses 2\. The alarm actions are the actions to perform when this alarm is triggered\. This example configures the alarm to send an email using Amazon SNS\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-system-instance-status-check.md |
837c8ba8b4e5-0 | On a given volume configuration, certain I/O characteristics drive the performance behavior for your EBS volumes\. SSD\-backed volumes—General Purpose SSD \(`gp2`\) and Provisioned IOPS SSD \(`io1` and `io2`\)—deliver consistent performance whether an I/O operation is random or sequential\. HDD\-backed volumes—Throughput Optimized HDD \(`st1`\) and Cold HDD \(`sc1`\)—deliver optimal performance only when I/O operations are large and sequential\. To understand how SSD and HDD volumes will perform | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-io-characteristics.md |
837c8ba8b4e5-1 | understand how SSD and HDD volumes will perform in your application, it is important to know the connection between demand on the volume, the quantity of IOPS available to it, the time it takes for an I/O operation to complete, and the volume's throughput limits\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-io-characteristics.md |
4d8c4f14e5b3-0 | IOPS are a unit of measure representing input/output operations per second\. The operations are measured in KiB, and the underlying drive technology determines the maximum amount of data that a volume type counts as a single I/O\. I/O size is capped at 256 KiB for SSD volumes and 1,024 KiB for HDD volumes because SSD volumes handle small or random I/O much more efficiently than HDD volumes\.
When small I/O operations are physically contiguous, Amazon EBS attempts to merge them into a single I/O operation up to the maximum size\. For example, for SSD volumes, a single 1,024 KiB I/O operation counts as 4 operations \(1,024÷256=4\), while 8 contiguous I/O operations at 32 KiB each count as 1 operation \(8×32=256\)\. However, 8 random non\-contiguous I/O operations at 32 KiB each count as 8 operations\. In this case, each I/O operation under 32 KiB counts as 1 operation\.
Similarly, for HDD\-backed volumes, both a single 1,024 KiB I/O operation and 8 sequential 128 KiB operations would count as one operation\. However, 8 random 128 KiB I/O operations would count as 8 operations\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-io-characteristics.md |
Subsets and Splits