id
stringlengths 14
16
| text
stringlengths 1
2.43k
| source
stringlengths 99
229
|
|---|---|---|
7b51234a60df-0 | Before you begin, be sure that you've completed the steps in [Setting up with Amazon EC2](get-set-up-for-amazon-ec2.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/EC2_GetStarted.md |
d10256580cef-0 | You can launch a Linux instance using the AWS Management Console as described in the following procedure\. This tutorial is intended to help you launch your first instance quickly, so it doesn't cover all possible options\. For more information about the advanced options, see [Launching an instance using the Launch Instance Wizard](launching-instance.md)\.
**To launch an instance**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. From the console dashboard, choose **Launch Instance**\.
1. The **Choose an Amazon Machine Image \(AMI\)** page displays a list of basic configurations, called *Amazon Machine Images \(AMIs\)*, that serve as templates for your instance\. Select an HVM version of Amazon Linux 2\. Notice that these AMIs are marked "Free tier eligible\."
1. On the **Choose an Instance Type** page, you can select the hardware configuration of your instance\. Select the `t2.micro` instance type, which is selected by default\. The `t2.micro` instance type is eligible for the free tier\. In Regions where `t2.micro` is unavailable, you can use a `t3.micro` instance under the free tier\. For more information, see [AWS Free Tier](https://aws.amazon.com/free/)\.
1. Choose **Review and Launch** to let the wizard complete the other configuration settings for you\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/EC2_GetStarted.md |
d10256580cef-1 | 1. Choose **Review and Launch** to let the wizard complete the other configuration settings for you\.
1. On the **Review Instance Launch** page, under **Security Groups**, you'll see that the wizard created and selected a security group for you\. You can use this security group, or alternatively you can select the security group that you created when getting set up using the following steps:
1. Choose **Edit security groups**\.
1. On the **Configure Security Group** page, ensure that **Select an existing security group** is selected\.
1. Select your security group from the list of existing security groups, and then choose **Review and Launch**\.
1. On the **Review Instance Launch** page, choose **Launch**\.
1. When prompted for a key pair, select **Choose an existing key pair**, then select the key pair that you created when getting set up\.
**Warning**
Don't select **Proceed without a key pair**\. If you launch your instance without a key pair, then you can't connect to it\.
When you are ready, select the acknowledgement check box, and then choose **Launch Instances**\.
1. A confirmation page lets you know that your instance is launching\. Choose **View Instances** to close the confirmation page and return to the console\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/EC2_GetStarted.md |
d10256580cef-2 | 1. A confirmation page lets you know that your instance is launching\. Choose **View Instances** to close the confirmation page and return to the console\.
1. On the **Instances** screen, you can view the status of the launch\. It takes a short time for an instance to launch\. When you launch an instance, its initial state is `pending`\. After the instance starts, its state changes to `running` and it receives a public DNS name\. \(If the **Public DNS \(IPv4\)** column is hidden, choose **Show/Hide Columns** \(the gear\-shaped icon\) in the top right corner of the page and then select **Public DNS \(IPv4\)**\.\)
1. 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\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/EC2_GetStarted.md |
8001781aacc7-0 | There are several ways to connect to your Linux instance\. For more information, see [Connect to your Linux instance](AccessingInstances.md)\.
**Important**
You can't connect to your instance unless you launched it with a key pair for which you have the `.pem` file and you launched it with a security group that allows SSH access from your computer\. If you can't connect to your instance, see [Troubleshooting connecting to your instance](TroubleshootingInstancesConnecting.md) for assistance\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/EC2_GetStarted.md |
07d40eb69ce5-0 | After you've finished with the instance that you created for this tutorial, you should clean up by terminating the instance\. If you want to do more with this instance before you clean up, see [Next steps](#ec2-next-steps)\.
**Important**
Terminating an instance effectively deletes it; you can't reconnect to an instance after you've terminated it\.
If you launched an instance that is not within the [AWS Free Tier](https://aws.amazon.com/free/), you'll stop incurring charges for that instance as soon as the instance status changes to `shutting down` or `terminated`\. If you'd like to keep your instance for later, but not incur charges, you can stop the instance now and then start it again later\. For more information, see [Stopping Instances](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Stop_Start.html)\.
**To terminate your instance**
1. In the navigation pane, choose **Instances**\. In the list of instances, select the instance\.
1. Choose **Actions**, **Instance State**, **Terminate**\.
1. Choose **Yes, Terminate** when prompted for confirmation\.
Amazon EC2 shuts down and terminates your instance\. After your instance is terminated, it remains visible on the console for a short while, and then the entry is deleted\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/EC2_GetStarted.md |
7fe654c4806d-0 | After you start your instance, you might want to try some of the following exercises:
+ Learn how to remotely manage your EC2 instance using Run Command\. For more information, see [AWS Systems Manager Run Command](https://docs.aws.amazon.com/systems-manager/latest/userguide/execute-remote-commands.html) in the *AWS Systems Manager User Guide*\.
+ Configure a CloudWatch alarm to notify you if your usage exceeds the Free Tier\. For more information, see [Create a Billing Alarm](https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/free-tier-alarms.html) in the *AWS Billing and Cost Management User Guide*\.
+ Add an EBS volume\. For more information, see [Creating an Amazon EBS volume](ebs-creating-volume.md) and [Attaching an Amazon EBS volume to an instance](ebs-attaching-volume.md)\.
+ Install the LAMP stack\. For more information, see [Tutorial: Install a LAMP web server on Amazon Linux 2](ec2-lamp-amazon-linux-2.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/EC2_GetStarted.md |
067123736df2-0 | If you have stopped your Amazon EBS\-backed instance and it appears stuck in the `stopping` state, there may be an issue with the underlying host computer\.
There is no cost for any instance usage while an instance is not in the `running` state\.
Force the instance to stop using either the console or the AWS CLI\.
+ To force the instance to stop using the console, select the stuck instance, and choose **Actions**, **Instance State**, **Stop**, and **Yes, Forcefully Stop**\.
+ To force the instance to stop using the AWS CLI, use the [stop\-instances](https://docs.aws.amazon.com/cli/latest/reference/ec2/stop-instances.html) command and the `--force` option as follows:
```
aws ec2 stop-instances --instance-ids i-0123ab456c789d01e --force
```
If, after 10 minutes, the instance has not stopped, post a request for help in the [Amazon EC2 forum](https://forums.aws.amazon.com/forum.jspa?forumID=30)\. To help expedite a resolution, include the instance ID, and describe the steps that you've already taken\. Alternatively, if you have a support plan, create a technical support case in the [Support Center](https://console.aws.amazon.com/support/home#/)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstancesStopping.md |
c95a68ef541d-0 | To attempt to resolve the problem while you are waiting for assistance from the [Amazon EC2 forum](https://forums.aws.amazon.com/forum.jspa?forumID=30) or the [Support Center](https://console.aws.amazon.com/support/home#/), create a replacement instance\. Create an AMI of the stuck instance, and launch a new instance using the new AMI\.
**To create a replacement 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 select the stuck instance\.
1. Choose **Actions**, **Image**, **Create Image**\.
1. In the **Create Image** dialog box, fill in the following fields, and then choose **Create Image**:
1. Specify a name and description for the AMI\.
1. Choose **No reboot**\.
For more information, see [Creating a Linux AMI from an instance](creating-an-ami-ebs.md#how-to-create-ebs-ami)\.
1. Launch a new instance from the AMI and verify that the new instance is working\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstancesStopping.md |
c95a68ef541d-1 | 1. Launch a new instance from the AMI and verify that the new instance is working\.
1. Select the stuck instance, and choose **Actions**, **Instance State**, **Terminate**\. If the instance also gets stuck terminating, Amazon EC2 automatically forces it to terminate within a few hours\.
**To create a replacement instance using the CLI**
1. Create an AMI from the stuck instance using the [create\-image](https://docs.aws.amazon.com/cli/latest/reference/ec2/create-image.html) \(AWS CLI\) command and the `--no-reboot` option as follows:\.
```
aws ec2 create-image --instance-id i-0123ab456c789d01e --name "AMI" --description "AMI for replacement instance" --no-reboot
```
1. Launch a new instance from the AMI using the [run\-instances](https://docs.aws.amazon.com/cli/latest/reference/ec2/run-instances.html) \(AWS CLI\) command as follows:
```
aws ec2 run-instances --image-id ami-1a2b3c4d --count 1 --instance-type c3.large --key-name MyKeyPair --security-groups MySecurityGroup
```
1. Verify that the new instance is working\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstancesStopping.md |
c95a68ef541d-2 | ```
1. Verify that the new instance is working\.
1. Terminate the stuck instance using the [terminate\-instances](https://docs.aws.amazon.com/cli/latest/reference/ec2/terminate-instances.html) \(AWS CLI\) command as follows:
```
aws ec2 terminate-instances --instance-ids i-1234567890abcdef0
```
If you are unable to create an AMI from the instance as described in the previous procedures, you can set up a replacement instance as follows:
**\(Alternate\) To create a replacement instance using the console**
1. Select the instance and choose **Description**, **Block devices**\. Select each volume and write down its volume ID\. Be sure to note which volume is the root volume\.
1. In the navigation pane, choose **Volumes**\. Select each volume for the instance, and choose **Actions**, **Create Snapshot**\.
1. In the navigation pane, choose **Snapshots**\. Select the snapshot that you just created, and choose **Actions**, **Create Volume**\.
1. Launch an instance with the same operating system as the stuck instance\. Note the volume ID and device name of its root volume\.
1. In the navigation pane, choose **Instances**, select the instance that you just launched, choose **Actions**, **Instance State**, and then choose **Stop**\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstancesStopping.md |
c95a68ef541d-3 | 1. In the navigation pane, choose **Volumes**, select the root volume of the stopped instance, and choose **Actions**, **Detach Volume**\.
1. Select the root volume that you created from the stuck instance, choose **Actions**, **Attach Volume**, and attach it to the new instance as its root volume \(using the device name that you wrote down\)\. Attach any additional non\-root volumes to the instance\.
1. In the navigation pane, choose **Instances** and select the replacement instance\. Choose **Actions**, **Instance State**, **Start**\. Verify that the instance is working\.
1. Select the stuck instance, choose **Actions**, **Instance State**, **Terminate**\. If the instance also gets stuck terminating, Amazon EC2 automatically forces it to terminate within a few hours\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstancesStopping.md |
fc1074f74cb9-0 | If you lose the private key for an EBS\-backed instance, you can regain access to your instance\. You must stop the instance, detach its root volume and attach it to another instance as a data volume, modify the `authorized_keys` file with a new public key, move the volume back to the original instance, and restart the instance\. For more information about launching, connecting to, and stopping instances, see [Instance lifecycle](ec2-instance-lifecycle.md)\.
This procedure is not supported for instances with instance\-store backed root volumes\. To determine the root device type of your instance, open the Amazon EC2 console, choose **Instances**, select the instance, and check the value of **Root device type** in the details pane\. The value is either `ebs` or `instance store`\. If the root device is an instance store volume, you cannot use this procedure to regain access to your instance; you must have the private key to connect to the instance\.
**Topics**
+ [Step 1: Create a new key pair](#step-1-create-new-key-pair)
+ [Step 2: Get information about the original instance and its root volume](#step-2-get-info-about-original-instance)
+ [Step 3: Stop the original instance](#step-3-stop-original-instance)
+ [Step 4: Launch a temporary instance](#step-4-launch-temp-instance) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/replacing-lost-key-pair.md |
fc1074f74cb9-1 | + [Step 4: Launch a temporary instance](#step-4-launch-temp-instance)
+ [Step 5: Detach the root volume from the original instance and attach it to the temporary instance](#step-5-detach-root-volume-and-attach-to-temp-instance)
+ [Step 6: Add the new public key to `authorized_keys` on the original volume mounted to the temporary instance](#step-6-add-new-public-key-to-authorized_keys)
+ [Step 7: Unmount and detach the original volume from the temporary instance, and reattach it to the original instance](#step-7-unmount-detach-volume-and-reattach-to-original-instance)
+ [Step 8: Connect to the original instance using the new key pair](#step-8-connect-to-original-instance)
+ [Step 9: Clean up](#step-9-clean-up) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/replacing-lost-key-pair.md |
8aa323e78804-0 | Create a new key pair using either the Amazon EC2 console or a third\-party tool\. If you want to name your new key pair exactly the same as the lost private key, you must first delete the existing key pair\. For information about creating a new key pair, see [Option 1: Create a key pair using Amazon EC2](ec2-key-pairs.md#having-ec2-create-your-key-pair) or [Option 2: Import your own public key to Amazon | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/replacing-lost-key-pair.md |
8aa323e78804-1 | 2: Import your own public key to Amazon EC2](ec2-key-pairs.md#how-to-generate-your-own-key-and-import-it-to-aws)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/replacing-lost-key-pair.md |
006e351b2af1-0 | ------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/replacing-lost-key-pair.md |
df4cbc7e3ba4-0 | **To get information about your original instance**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. Choose **Instances** in the navigation pane, and then select the instance that you'd like to connect to\. \(We'll refer to this as the *original* instance\.\)
1. On the **Details** tab, write down the instance ID and AMI ID\.
1. On the **Networking** tab, write down the Availability Zone\.
1. On the **Storage** tab, note the device name for the root volume in **Root device name** \(for example, `/dev/xvda`\)\. Find this device name under **Block devices** and write down the volume ID \(for example, vol\-0a1234b5678c910de\)\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/replacing-lost-key-pair.md |
d215bf1b9436-0 | **To get information about your original instance**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. Choose **Instances** in the navigation pane, and then select the instance that you'd like to connect to\. \(We'll refer to this as the *original* instance\.\)
1. From the **Description** tab, save the following information that you need to complete this procedure\.
+ Write down the instance ID, AMI ID, and Availability Zone of the original instance\.
+ In the **Root device** field, take note of the device name for the root volume \(for example, `/dev/sda1` or `/dev/xvda`\)\. Choose the link and write down the volume ID in the **EBS ID** field \(vol\-*xxxxxxxxxxxxxxxxx*\)\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/replacing-lost-key-pair.md |
357ed79cdfe7-0 | Choose **Actions**, select **Instance State**, and then select **Stop**\. If **Stop** is disabled, either the instance is already stopped or its root device is an instance store volume\.
**Warning**
When you stop an instance, the data on any instance store volumes is erased\. To keep data from instance store volumes, be sure to back it up to persistent storage\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/replacing-lost-key-pair.md |
c7c3da644997-0 | Choose **Launch Instance**, and then use the launch wizard to launch a *temporary* instance with the following options:
+ On the **Choose an AMI** page, select the same AMI that you used to launch the original instance\. If this AMI is unavailable, you can create an AMI that you can use from the stopped instance\. For more information, see [Creating an Amazon EBS\-backed Linux AMI](creating-an-ami-ebs.md)\.
+ On the **Choose an Instance Type** page, leave the default instance type that the wizard selects for you\.
+ On the **Configure Instance Details** page, specify the same Availability Zone as the original instance\. If you're launching an instance in a VPC, select a subnet in this Availability Zone\.
+ On the **Add Tags** page, add the tag `Name=Temporary` to the instance to indicate that this is a temporary instance\.
+ On the **Review** page, choose **Launch**\. Create a new key pair, download it to a safe location on your computer, and then choose **Launch Instances**\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/replacing-lost-key-pair.md |
f028219cd222-0 | 1. In the navigation pane, choose **Volumes** and select the root device volume for the original instance \(you wrote down its volume ID in a previous step\)\. Choose **Actions**, **Detach Volume**, and then select **Yes, Detach**\. Wait for the state of the volume to become `available`\. \(You might need to choose the **Refresh** icon\.\)
1. With the volume still selected, choose **Actions**, and then select **Attach Volume**\. Select the instance ID of the temporary instance, write down the device name specified under **Device** \(for example, `/dev/sdf`\), and then choose **Attach**\.
**Note**
If you launched your original instance from an AWS Marketplace AMI and your volume contains AWS Marketplace codes, you must first stop the temporary instance before you can attach the volume\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/replacing-lost-key-pair.md |
d70c32e79818-0 | 1. Connect to the temporary instance\.
1. From the temporary instance, mount the volume that you attached to the instance so that you can access its file system\. For example, if the device name is `/dev/sdf`, use the following commands to mount the volume as `/mnt/tempvol`\.
**Note**
The device name might appear differently on your instance\. For example, devices mounted as `/dev/sdf` might show up as `/dev/xvdf` on the instance\. Some versions of Red Hat \(or its variants, such as CentOS\) might even increment the trailing letter by 4 characters, where `/dev/sdf` becomes `/dev/xvdk`\.
1. Use the lsblk command to determine if the volume is partitioned\.
```
[ec2-user ~]$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
xvda 202:0 0 8G 0 disk
└─xvda1 202:1 0 8G 0 part /
xvdf 202:80 0 101G 0 disk
└─xvdf1 202:81 0 101G 0 part
xvdg 202:96 0 30G 0 disk
```
In the preceding example, `/dev/xvda` and `/dev/xvdf` are partitioned volumes, and `/dev/xvdg` is not\. If your volume is partitioned, you mount the partition \(`/dev/xvdf1)` instead of the raw device \(`/dev/xvdf`\) in the next steps\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/replacing-lost-key-pair.md |
d70c32e79818-1 | 1. Create a temporary directory to mount the volume\.
```
[ec2-user ~]$ sudo mkdir /mnt/tempvol
```
1. Mount the volume \(or partition\) at the temporary mount point, using the volume name or device name that you identified earlier\. The required command depends on your operating system's file system\.
+ Amazon Linux, Ubuntu, and Debian
```
[ec2-user ~]$ sudo mount /dev/xvdf1 /mnt/tempvol
```
+ Amazon Linux 2, CentOS, SUSE Linux 12, and RHEL 7\.x
```
[ec2-user ~]$ sudo mount -o nouuid /dev/xvdf1 /mnt/tempvol
```
**Note**
If you get an error stating that the file system is corrupt, run the following command to use the **fsck** utility to check the file system and repair any issues:
```
[ec2-user ~]$ sudo fsck /dev/xvdf1
```
1. From the temporary instance, use the following command to update `authorized_keys` on the mounted volume with the new public key from the `authorized_keys` for the temporary instance\.
**Important** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/replacing-lost-key-pair.md |
d70c32e79818-2 | **Important**
The following examples use the Amazon Linux user name `ec2-user`\. You might need to substitute a different user name, such as `ubuntu` for Ubuntu instances\.
```
[ec2-user ~]$ cp .ssh/authorized_keys /mnt/tempvol/home/ec2-user/.ssh/authorized_keys
```
If this copy succeeded, you can go to the next step\.
\(Optional\) Otherwise, if you don't have permission to edit files in `/mnt/tempvol`, you must update the file using sudo and then check the permissions on the file to verify that you are able to log into the original instance\. Use the following command to check the permissions on the file\.
```
[ec2-user ~]$ sudo ls -l /mnt/tempvol/home/ec2-user/.ssh
total 4
-rw------- 1 222 500 398 Sep 13 22:54 authorized_keys
```
In this example output, *222* is the user ID and *500* is the group ID\. Next, use sudo to re\-run the copy command that failed\.
```
[ec2-user ~]$ sudo cp .ssh/authorized_keys /mnt/tempvol/home/ec2-user/.ssh/authorized_keys
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/replacing-lost-key-pair.md |
d70c32e79818-3 | ```
Run the following command again to determine whether the permissions changed\.
```
[ec2-user ~]$ sudo ls -l /mnt/tempvol/home/ec2-user/.ssh
```
If the user ID and group ID have changed, use the following command to restore them\.
```
[ec2-user ~]$ sudo chown 222:500 /mnt/tempvol/home/ec2-user/.ssh/authorized_keys
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/replacing-lost-key-pair.md |
e80ffe7787fc-0 | 1. From the temporary instance, unmount the volume that you attached so that you can reattach it to the original instance\. For example, use the following command to unmount the volume at `/mnt/tempvol`\.
```
[ec2-user ~]$ sudo umount /mnt/tempvol
```
1. Detach the volume from the temporary instance \(you unmounted it in the previous step\): From the Amazon EC2 console, select the root device volume for the original instance \(you wrote down volume ID in a previous step\), choose **Actions**, **Detach Volume**, and then select **Yes, Detach**\. Wait for the state of the volume to become `available`\. \(You might need to choose the **Refresh** icon\.\)
1. Reattach the volume to the original instance: With the volume still selected, choose **Actions**, **Attach Volume**\. Select the instance ID of the original instance, specify the device name that you noted earlier in [Step 2](#step-2-get-info-about-original-instance) for the original root device attachment \(`/dev/sda1` or `/dev/xvda`\), and then choose **Attach**\.
**Important**
If you don't specify the same device name as the original attachment, you cannot start the original instance\. Amazon EC2 expects the root device volume at `sda1` or `/dev/xvda`\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/replacing-lost-key-pair.md |
636ff15aeaaf-0 | Select the original instance, choose **Actions**, select **Instance State**, and then choose **Start**\. After the instance enters the `running` state, you can connect to it using the private key file for your new key pair\.
**Note**
If the name of your new key pair and corresponding private key file is different from the name of the original key pair, ensure that you specify the name of the new private key file when you connect to your instance\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/replacing-lost-key-pair.md |
727f9c602a2c-0 | \(Optional\) You can terminate the temporary instance if you have no further use for it\. Select the temporary instance, choose **Actions**, select **Instance State**, and then choose **Terminate**\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/replacing-lost-key-pair.md |
d9143beb8f60-0 | The Elastic Network Adapter \(ENA\) is designed to improve operating system health and reduce the chances of long\-term disruption because of unexpected hardware behavior and or failures\. The ENA architecture keeps device or driver failures as transparent to the system as possible\. This topic provides troubleshooting information for ENA\.
If you are unable to connect to your instance, start with the [Troubleshooting connectivity issues](#ena-connectivity-issues) section\.
If you are able to connect to your instance, you can gather diagnostic information by using the failure detection and recovery mechanisms that are covered in the later sections of this topic\.
**Topics**
+ [Troubleshooting connectivity issues](#ena-connectivity-issues)
+ [Keep\-alive mechanism](#ena-keep-alive)
+ [Register read timeout](#register-read-timeout-ena)
+ [Statistics](#statistics-ena)
+ [Driver error logs in syslog](#driver-error-logs-ena) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/troubleshooting-ena.md |
dbe638d80fb5-0 | If you lose connectivity while enabling enhanced networking, the `ena` module might be incompatible with your instance's current running kernel\. This can happen if you install the module for a specific kernel version \(without dkms, or with an improperly configured dkms\.conf file\) and then your instance kernel is updated\. If the instance kernel that is loaded at boot time does not have the `ena` module properly installed, your instance will not recognize the network adapter and your instance becomes unreachable\.
If you enable enhanced networking for a PV instance or AMI, this can also make your instance unreachable\.
If your instance becomes unreachable after enabling enhanced networking with ENA, you can disable the `enaSupport` attribute for your instance and it will fall back to the stock network adapter\.
**To disable enhanced networking with ENA \(EBS\-backed instances\)**
1. From your local computer, stop the instance using the Amazon EC2 console or one of the following commands: [stop\-instances](https://docs.aws.amazon.com/cli/latest/reference/ec2/stop-instances.html) \(AWS CLI\), [Stop\-EC2Instance](https://docs.aws.amazon.com/powershell/latest/reference/items/Stop-EC2Instance.html) \(AWS Tools for Windows PowerShell\)\. If your instance is managed by AWS OpsWorks, you should stop the instance in the AWS OpsWorks console so that the instance state remains in sync\.
**Important** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/troubleshooting-ena.md |
dbe638d80fb5-1 | **Important**
If you are using an instance store\-backed instance, you can't stop the instance\. Instead, proceed to [To disable enhanced networking with ENA \(instance store\-backed instances\)](#disable-enhanced-networking-ena-instance-store)\.
1. From your local computer, disable the enhanced networking attribute using the following command\.
+ [modify\-instance\-attribute](https://docs.aws.amazon.com/cli/latest/reference/ec2/modify-instance-attribute.html) \(AWS CLI\)
```
$ aws ec2 modify-instance-attribute --instance-id instance_id --no-ena-support
```
1. From your local computer, start the instance using the Amazon EC2 console or one of the following commands: [start\-instances](https://docs.aws.amazon.com/cli/latest/reference/ec2/start-instances.html) \(AWS CLI\), [Start\-EC2Instance](https://docs.aws.amazon.com/powershell/latest/reference/items/Start-EC2Instance.html) \(AWS Tools for Windows PowerShell\)\. If your instance is managed by AWS OpsWorks, you should start the instance in the AWS OpsWorks console so that the instance state remains in sync\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/troubleshooting-ena.md |
dbe638d80fb5-2 | 1. \(Optional\) Connect to your instance and try reinstalling the `ena` module with your current kernel version by following the steps in [Enabling enhanced networking with the Elastic Network Adapter \(ENA\) on Linux instances](enhanced-networking-ena.md)\.
<a name="disable-enhanced-networking-ena-instance-store"></a>
**To disable enhanced networking with ENA \(instance store\-backed instances\)**
If your instance is an instance store\-backed instance, create a new AMI as described in [Creating an instance store\-backed Linux AMI](creating-an-ami-instance-store.md)\. Be sure to disable the enhanced networking `enaSupport` attribute when you register the AMI\.
+ [register\-image](https://docs.aws.amazon.com/cli/latest/reference/ec2/register-image.html) \(AWS CLI\)
```
$ aws ec2 register-image --no-ena-support ...
```
+ [Register\-EC2Image](https://docs.aws.amazon.com/powershell/latest/reference/items/Register-EC2Image.html) \(AWS Tools for Windows PowerShell\)
```
C:\> Register-EC2Image -EnaSupport $false ...
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/troubleshooting-ena.md |
80f65e7bbe4e-0 | The ENA device posts keep\-alive events at a fixed rate \(usually once every second\)\. The ENA driver implements a watchdog mechanism, which checks for the presence of these keep\-alive messages\. If a message or messages are present, the watchdog is rearmed, otherwise the driver concludes that the device experienced a failure and then does the following:
+ Dumps its current statistics to syslog
+ Resets the ENA device
+ Resets the ENA driver state
The above reset procedure may result in some traffic loss for a short period of time \(TCP connections should be able to recover\), but should not otherwise affect the user\.
The ENA device may also indirectly request a device reset procedure, by not sending a keep\-alive notification, for example, if the ENA device reaches an unknown state after loading an irrecoverable configuration\.
Below is an example of the reset procedure:
```
[18509.800135] ena 0000:00:07.0 eth1: Keep alive watchdog timeout. // The watchdog process initiates a reset
[18509.815244] ena 0000:00:07.0 eth1: Trigger reset is on
[18509.825589] ena 0000:00:07.0 eth1: tx_timeout: 0 // The driver logs the current statistics
[18509.834253] ena 0000:00:07.0 eth1: io_suspend: 0 | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/troubleshooting-ena.md |
80f65e7bbe4e-1 | [18509.834253] ena 0000:00:07.0 eth1: io_suspend: 0
[18509.842674] ena 0000:00:07.0 eth1: io_resume: 0
[18509.850275] ena 0000:00:07.0 eth1: wd_expired: 1
[18509.857855] ena 0000:00:07.0 eth1: interface_up: 1
[18509.865415] ena 0000:00:07.0 eth1: interface_down: 0
[18509.873468] ena 0000:00:07.0 eth1: admin_q_pause: 0
[18509.881075] ena 0000:00:07.0 eth1: queue_0_tx_cnt: 0
[18509.888629] ena 0000:00:07.0 eth1: queue_0_tx_bytes: 0
[18509.895286] ena 0000:00:07.0 eth1: queue_0_tx_queue_stop: 0
.......
........
[18511.280972] ena 0000:00:07.0 eth1: free uncompleted tx skb qid 3 idx 0x7 // At the end of the down process, the driver discards incomplete packets. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/troubleshooting-ena.md |
80f65e7bbe4e-2 | [18511.420112] [ENA_COM: ena_com_validate_version] ena device version: 0.10 //The driver begins its up process
[18511.420119] [ENA_COM: ena_com_validate_version] ena controller version: 0.0.1 implementation version 1
[18511.420127] [ENA_COM: ena_com_admin_init] ena_defs : Version:[b9692e8] Build date [Wed Apr 6 09:54:21 IDT 2016]
[18512.252108] ena 0000:00:07.0: Device watchdog is Enabled
[18512.674877] ena 0000:00:07.0: irq 46 for MSI/MSI-X
[18512.674933] ena 0000:00:07.0: irq 47 for MSI/MSI-X
[18512.674990] ena 0000:00:07.0: irq 48 for MSI/MSI-X
[18512.675037] ena 0000:00:07.0: irq 49 for MSI/MSI-X
[18512.675085] ena 0000:00:07.0: irq 50 for MSI/MSI-X
[18512.675141] ena 0000:00:07.0: irq 51 for MSI/MSI-X | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/troubleshooting-ena.md |
80f65e7bbe4e-3 | [18512.675141] ena 0000:00:07.0: irq 51 for MSI/MSI-X
[18512.675188] ena 0000:00:07.0: irq 52 for MSI/MSI-X
[18512.675233] ena 0000:00:07.0: irq 53 for MSI/MSI-X
[18512.675279] ena 0000:00:07.0: irq 54 for MSI/MSI-X
[18512.772641] [ENA_COM: ena_com_set_hash_function] Feature 10 isn't supported
[18512.772647] [ENA_COM: ena_com_set_hash_ctrl] Feature 18 isn't supported
[18512.775945] ena 0000:00:07.0: Device reset completed successfully // The reset process is complete
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/troubleshooting-ena.md |
ad41ad93574d-0 | The ENA architecture suggests a limited usage of memory mapped I/O \(MMIO\) read operations\. MMIO registers are accessed by the ENA device driver only during its initialization procedure\.
If the driver logs \(available in dmesg output\) indicate failures of read operations, this may be caused by an incompatible or incorrectly compiled driver, a busy hardware device, or hardware failure\.
Intermittent log entries that indicate failures on read operations should not be considered an issue; the driver will retry them in this case\. However, a sequence of log entries containing read failures indicate a driver or hardware problem\.
Below is an example of driver log entry indicating a read operation failure due to a timeout:
```
[ 47.113698] [ENA_COM: ena_com_reg_bar_read32] reading reg failed for timeout. expected: req id[1] offset[88] actual: req id[57006] offset[0]
[ 47.333715] [ENA_COM: ena_com_reg_bar_read32] reading reg failed for timeout. expected: req id[2] offset[8] actual: req id[57007] offset[0]
[ 47.346221] [ENA_COM: ena_com_dev_reset] Reg read32 timeout occurred
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/troubleshooting-ena.md |
d58d270437e8-0 | If you experience insufficient network performance or latency issues, you should retrieve the device statistics and examine them\. These statistics can be obtained using ethtool, as shown below:
```
[ec2-user ~]$ ethtool –S ethN
NIC statistics:
tx_timeout: 0
io_suspend: 0
io_resume: 0
wd_expired: 0
interface_up: 1
interface_down: 0
admin_q_pause: 0
queue_0_tx_cnt: 4329
queue_0_tx_bytes: 1075749
queue_0_tx_queue_stop: 0
...
```
The following command output parameters are described below:
`tx_timeout: N`
The number of times that the Netdev watchdog was activated\.
`io_suspend: N`
Unsupported\. This value should always be zero\.
`io_resume: N`
Unsupported\. This value should always be zero\.
`wd_expired: N`
The number of times that the driver did not receive the keep\-alive event in the preceding 3 seconds\.
`interface_up: N`
The number of times that the ENA interface was brought up\.
`interface_down: N`
The number of times that the ENA interface was brought down\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/troubleshooting-ena.md |
d58d270437e8-1 | `interface_down: N`
The number of times that the ENA interface was brought down\.
`admin_q_pause: N`
The admin queue is in an unstable state\. This value should always be zero\.
`queue_N_tx_cnt: N`
The number of transmitted packets for queue *N*\.
`queue_N_tx_bytes: N`
The number of transmitted bytes for queue *N*\.
`queue_N_tx_queue_stop: N`
The number of times that queue *N* was full and stopped\.
`queue_N_tx_queue_wakeup: N`
The number of times that queue *N* resumed after being stopped\.
`queue_N_tx_dma_mapping_err: N`
Direct memory access error count\. If this value is not 0, it indicates low system resources\.
`queue_N_tx_napi_comp: N`
The number of times the `napi` handler called `napi_complete` for queue *N*\.
`queue_N_tx_poll: N`
The number of times the `napi` handler was scheduled for queue *N*\.
`queue_N_tx_doorbells: N`
The number of transmission doorbells for queue *N*\.
`queue_N_tx_linearize: N` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/troubleshooting-ena.md |
d58d270437e8-2 | The number of transmission doorbells for queue *N*\.
`queue_N_tx_linearize: N`
The number of times SKB linearization was attempted for queue *N*\.
`queue_N_tx_linearize_failed: N`
The number of times SKB linearization failed for queue *N*\.
`queue_N_tx_prepare_ctx_err: N`
The number of times `ena_com_prepare_tx` failed for queue *N*\. This value should always be zero; if not, see the driver logs\.
`queue_N_tx_missing_tx_comp: codeN`
The number of packets that were left uncompleted for queue *N*\. This value should always be zero\.
`queue_N_tx_bad_req_id: N`
Invalid `req_id` for queue *N*\. The valid `req_id` is zero, minus the `queue_size`, minus 1\.
`queue_N_rx_cnt: N`
The number of received packets for queue *N*\.
`queue_N_rx_bytes: N`
The number of received bytes for queue *N*\.
`queue_N_rx_refil_partial: N` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/troubleshooting-ena.md |
d58d270437e8-3 | The number of received bytes for queue *N*\.
`queue_N_rx_refil_partial: N`
The number of times the driver did not succeed in refilling the empty portion of the `rx` queue with the buffers for queue *N*\. If this value is not zero, it indicates low memory resources\.
`queue_N_rx_bad_csum: N`
The number of times the `rx` queue had a bad checksum for queue *N* \(only if `rx` checksum offload is supported\)\.
`queue_N_rx_page_alloc_fail: N`
The number of time that page allocation failed for queue *N*\. If this value is not zero, it indicates low memory resources\.
`queue_N_rx_skb_alloc_fail: N`
The number of time that SKB allocation failed for queue *N*\. If this value is not zero, it indicates low system resources\.
`queue_N_rx_dma_mapping_err: N`
Direct memory access error count\. If this value is not 0, it indicates low system resources\.
`queue_N_rx_bad_desc_num: N`
Too many buffers per packet\. If this value is not 0, it indicates usage of very small buffers\.
`queue_N_rx_small_copy_len_pkt: N` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/troubleshooting-ena.md |
d58d270437e8-4 | `queue_N_rx_small_copy_len_pkt: N`
Optimization: For packets smaller that this threshold, which is set by `sysfs`, the packet is copied directly to the stack to avoid allocation of a new page\.
`ena_admin_q_aborted_cmd: N`
The number of admin commands that were aborted\. This usually happens during the auto\-recovery procedure\.
`ena_admin_q_submitted_cmd: N`
The number of admin queue doorbells\.
`ena_admin_q_completed_cmd: N`
The number of admin queue completions\.
`ena_admin_q_out_of_space: N`
The number of times that the driver tried to submit new admin command, but the queue was full\.
`ena_admin_q_no_completion: N`
The number of times that the driver did not get an admin completion for a command\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/troubleshooting-ena.md |
9db91ebca614-0 | The ENA driver writes log messages to syslog during system boot\. You can examine these logs to look for errors if you are experiencing issues\. Below is an example of information logged by the ENA driver in syslog during system boot, along with some annotations for select messages\.
```
Jun 3 22:37:46 ip-172-31-2-186 kernel: [ 478.416939] [ENA_COM: ena_com_validate_version] ena device version: 0.10
Jun 3 22:37:46 ip-172-31-2-186 kernel: [ 478.420915] [ENA_COM: ena_com_validate_version] ena controller version: 0.0.1 implementation version 1
Jun 3 22:37:46 ip-172-31-2-186 kernel: [ 479.256831] ena 0000:00:03.0: Device watchdog is Enabled
Jun 3 22:37:46 ip-172-31-2-186 kernel: [ 479.672947] ena 0000:00:03.0: creating 8 io queues. queue size: 1024
Jun 3 22:37:46 ip-172-31-2-186 kernel: [ 479.680885] [ENA_COM: ena_com_init_interrupt_moderation] Feature 20 isn't supported // Interrupt moderation is not supported by the device | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/troubleshooting-ena.md |
9db91ebca614-1 | Jun 3 22:37:46 ip-172-31-2-186 kernel: [ 479.691609] [ENA_COM: ena_com_get_feature_ex] Feature 10 isn't supported // RSS HASH function configuration is not supported by the device
Jun 3 22:37:46 ip-172-31-2-186 kernel: [ 479.694583] [ENA_COM: ena_com_get_feature_ex] Feature 18 isn't supported //RSS HASH input source configuration is not supported by the device
Jun 3 22:37:46 ip-172-31-2-186 kernel: [ 479.697433] [ENA_COM: ena_com_set_host_attributes] Set host attribute isn't supported
Jun 3 22:37:46 ip-172-31-2-186 kernel: [ 479.701064] ena 0000:00:03.0 (unnamed net_device) (uninitialized): Cannot set host attributes
Jun 3 22:37:46 ip-172-31-2-186 kernel: [ 479.704917] ena 0000:00:03.0: Elastic Network Adapter (ENA) found at mem f3000000, mac addr 02:8a:3c:1e:13:b5 Queues 8
Jun 3 22:37:46 ip-172-31-2-186 kernel: [ 480.805037] EXT4-fs (xvda1): re-mounted. Opts: (null) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/troubleshooting-ena.md |
9db91ebca614-2 | Jun 3 22:37:46 ip-172-31-2-186 kernel: [ 481.025842] NET: Registered protocol family 10
```
**Which errors can I ignore?**
The following warnings that may appear in your system's error logs can be ignored for the Elastic Network Adapter:
Set host attribute isn't supported
Host attributes are not supported for this device\.
failed to alloc buffer for rx queue
This is a recoverable error, and it indicates that there may have been a memory pressure issue when the error was thrown\.
Feature *X* isn't supported
The referenced feature is not supported by the Elastic Network Adapter\. Possible values for *X* include:
+ **10**: RSS Hash function configuration is not supported for this device\.
+ **12**: RSS Indirection table configuration is not supported for this device\.
+ **18**: RSS Hash Input configuration is not supported for this device\.
+ **20**: Interrupt moderation is not supported for this device\.
+ **27**: The Elastic Network Adapter driver does not support polling the Ethernet capabilities from snmpd\.
Failed to config AENQ
The Elastic Network Adapter does not support AENQ configuration\.
Trying to set unsupported AENQ events
This error indicates an attempt to set an AENQ events group that is not supported by the Elastic Network Adapter\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/troubleshooting-ena.md |
dcf09d919a74-0 | You can improve the security posture of your VPC by configuring Amazon EC2 to use an interface VPC endpoint\. Interface endpoints are powered by AWS PrivateLink, a technology that enables you to privately access Amazon EC2 APIs by restricting all network traffic between your VPC and Amazon EC2 to the Amazon network\. With interface endpoints, you also don't need an internet gateway, a NAT device, or a virtual private gateway\.
You are not required to configure AWS PrivateLink, but it's recommended\. For more information about AWS PrivateLink and VPC endpoints, see [Interface VPC Endpoints \(AWS PrivateLink\)](https://docs.aws.amazon.com/vpc/latest/userguide/vpce-interface.html)\.
**Topics**
+ [Create an interface VPC endpoint](#create-endpoint)
+ [Create an interface VPC endpoint policy](#endpoint-policy) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/interface-vpc-endpoints.md |
00a89b7f972d-0 | Create an endpoint for Amazon EC2 using the following service name:
+ **`com.amazonaws.region.ec2`** — Creates an endpoint for the Amazon EC2 API actions\.
For more information, see [Creating an Interface Endpoint](https://docs.aws.amazon.com/vpc/latest/userguide/vpce-interface.html#create-interface-endpoint) in the *Amazon VPC User Guide*\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/interface-vpc-endpoints.md |
360b47449e48-0 | You can attach a policy to your VPC endpoint to control access to the Amazon EC2 API\. The policy specifies:
+ The principal that can perform actions\.
+ The actions that can be performed\.
+ The resource on which the actions can be performed\.
**Important**
When a non\-default policy is applied to an interface VPC endpoint for Amazon EC2, certain failed API requests, such as those failing from `RequestLimitExceeded`, might not be logged to AWS CloudTrail or Amazon CloudWatch\.
For more information, see [ Controlling Access to Services with VPC Endpoints](https://docs.aws.amazon.com/vpc/latest/userguide/vpc-endpoints-access.html) in the * Amazon VPC User Guide*\.
The following example shows a VPC endpoint policy that denies permission to create unencrypted volumes or to launch instances with unencrypted volumes\. The example policy also grants permission to perform all other Amazon EC2 actions\.
```
{
"Version": "2012-10-17",
"Statement": [
{
"Action": "ec2:*",
"Effect": "Allow",
"Resource": "*",
"Principal": "*"
},
{
"Action": [
"ec2:CreateVolume"
],
"Effect": "Deny", | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/interface-vpc-endpoints.md |
360b47449e48-1 | "Action": [
"ec2:CreateVolume"
],
"Effect": "Deny",
"Resource": "*",
"Principal": "*",
"Condition": {
"Bool": {
"ec2:Encrypted": "false"
}
}
},
{
"Action": [
"ec2:RunInstances"
],
"Effect": "Deny",
"Resource": "*",
"Principal": "*",
"Condition": {
"Bool": {
"ec2:Encrypted": "false"
}
}
}]
}
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/interface-vpc-endpoints.md |
52e248dcb903-0 | With an Amazon EBS\-backed Linux instance, you can back up the root device volume of the instance by creating a snapshot\. When you have a snapshot of the root device volume of an instance, you can terminate that instance and then later launch a new instance from the snapshot\. This can be useful if you don't have the original AMI that you launched an instance from, but you need to be able to launch an instance using the same image\.
Use the following procedure to create an AMI from the root volume of your instance using the console\. If you prefer, you can use one of the following commands instead: [register\-image](https://docs.aws.amazon.com/cli/latest/reference/ec2/register-image.html) \(AWS CLI\) or [Register\-EC2Image](https://docs.aws.amazon.com/powershell/latest/reference/items/Register-EC2Image.html) \(AWS Tools for Windows PowerShell\)\. You specify the snapshot using the block device mapping\.
**To create an AMI from your root volume using the console**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the navigation pane, choose **Elastic Block Store**, **Snapshots**\.
1. Choose **Create Snapshot**\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-launch-snapshot.md |
52e248dcb903-1 | 1. Choose **Create Snapshot**\.
1. For **Volumes**, start typing the name or ID of the root volume, and then select it from the list of options\.
1. Choose the snapshot that you just created, and then choose **Actions**, **Create Image**\.
1. In the **Create Image from EBS Snapshot** dialog box, provide the following information and 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)\.
+ \(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 are required to 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\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-launch-snapshot.md |
52e248dcb903-2 | + \(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)\.
1. In the navigation pane, choose **AMIs**\.
1. Choose the AMI that you just created, and then choose **Launch**\. Follow the wizard to launch your instance\. For more information about how to configure 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/instance-launch-snapshot.md |
b05476350422-0 | Use the Amazon Linux 2 virtual machine \(VM\) images for on\-premises development and testing\. These images are available for use on the following virtualization platforms:
+ VMWare
+ KVM
+ VirtualBox \(Oracle VM\)
+ Microsoft Hyper\-V
To use the Amazon Linux 2 virtual machine images with one of the supported virtualization platforms, do the following:
+ [Step 1: Prepare the `seed.iso` boot image](#amazon-linux-2-virtual-machine-prepare)
+ [Step 2: Download the Amazon Linux 2 VM image](#amazon-linux-2-virtual-machine-download)
+ [Step 3: Boot and connect to your new VM](#amazon-linux-2-virtual-machine-boot) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/amazon-linux-2-virtual-machine.md |
ca342604df98-0 | The `seed.iso` boot image includes the initial configuration information that is needed to boot your new VM, such as the network configuration, host name, and user data\.
**Note**
The `seed.iso` boot image includes only the configuration information required to boot the VM\. It does not include the Amazon Linux 2 operating system files\.
To generate the `seed.iso` boot image, you need two configuration files:
+ `meta-data`—This file includes the hostname and static network settings for the VM\.
+ `user-data`—This file configures user accounts, and specifies their passwords, key pairs, and access mechanisms\. By default, the Amazon Linux 2 VM image creates a `ec2-user` user account\. You use the `user-data` configuration file to set the password for the default user account\.
**To create the `seed.iso` boot disc**
1. Create a new folder named `seedconfig` and navigate into it\.
1. Create the `meta-data` configuration file\.
1. Create a new file named `meta-data`\.
1. Open the `meta-data` file using your preferred editor and add the following\.
```
local-hostname: vm_hostname | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/amazon-linux-2-virtual-machine.md |
08eae65ceeeb-0 | network-interfaces: |
auto eth0
iface eth0 inet static
address 192.168.1.10
network 192.168.1.0
netmask 255.255.255.0
broadcast 192.168.1.255
gateway 192.168.1.254
```
Replace *vm\_hostname* with a VM host name of your choice, and configure the network settings as required\.
1. Save and close the `meta-data` configuration file\.
For an example `meta-data` configuration file that specifies a VM hostname \(`amazonlinux.onprem`\), configures the default network interface \(`eth0`\), and specifies static IP addresses for the necessary network devices, see the [ sample Seed\.iso file](https://cdn.amazonlinux.com/os-images/2.0.20190612/)\.
1. Create the `user-data` configuration file\.
1. Create a new file named `user-data`\.
1. Open the `user-data` file using your preferred editor and add the following\.
```
#cloud-config
#vim:syntax=yaml
users: | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/amazon-linux-2-virtual-machine.md |
863e25accfa6-0 | - default
chpasswd:
list: |
ec2-user:plain_text_password | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/amazon-linux-2-virtual-machine.md |
7ed50b1142ea-0 | ```
Replace *plain\_text\_password* with a password of your choice for the default `ec2-user` user account\.
1. \(Optional\) By default, cloud\-init applies network settings each time the VM boots\. Add the following to prevent cloud\-init from applying network settings at each boot, and to retain the network settings applied during the first boot\.
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/amazon-linux-2-virtual-machine.md |
0095de8bf203-0 | boot, add following ‘write_files’ section:
write_files:
- path: /etc/cloud/cloud.cfg.d/80_disable_network_after_firstboot.cfg
content: | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/amazon-linux-2-virtual-machine.md |
6278a0b851fc-0 | network:
config: disabled
```
1. Save and close the `user-data` configuration file\.
You can also create additional user accounts and specify their access mechanisms, passwords, and key pairs\. For more information about the supported directives, see [ Modules](http://cloudinit.readthedocs.io/en/latest/topics/modules.html)\. For an example `user-data` file that creates three additional users and specifies a custom password for the default `ec2-user` user account, see the [ sample Seed\.iso file](https://cdn.amazonlinux.com/os-images/2.0.20190612/)\.
1. Create the `seed.iso` boot image using the `meta-data` and `user-data` configuration files\.
For Linux, use a tool such as **genisoimage**\. Navigate into the `seedconfig` folder, and execute the following command\.
```
$ genisoimage -output seed.iso -volid cidata -joliet -rock user-data meta-data
```
For macOS, use a tool such as **hdiutil**\. Navigate one level up from the `seedconfig` folder, and execute the following command\.
```
$ hdiutil makehybrid -o seed.iso -hfs -joliet -iso -default-volume-name cidata seedconfig/
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/amazon-linux-2-virtual-machine.md |
06341035f92e-0 | We offer a different Amazon Linux 2 VM image for each of the supported virtualization platforms\. Download the correct VM image for your chosen platform:
+ [ VMWare](https://cdn.amazonlinux.com/os-images/latest/vmware/)
+ [ KVM](https://cdn.amazonlinux.com/os-images/latest/kvm/)
+ [ Oracle VirtualBox](https://cdn.amazonlinux.com/os-images/latest/virtualbox/)
+ [ Microsoft Hyper\-V](https://cdn.amazonlinux.com/os-images/latest/hyperv/) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/amazon-linux-2-virtual-machine.md |
9fb0efa73dd6-0 | To boot and connect to your new VM, you must have the `seed.iso` boot image \(created in Step 1\) and an Amazon Linux 2 VM image \(downloaded in Step 2\)\. The steps vary depending on your chosen VM platform\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/amazon-linux-2-virtual-machine.md |
c3c2d9e3399b-0 | The VM image for VMware is made available in the OVF format\.
**To boot the VM using VMWare vSphere**
1. Create a new datastore for the `seed.iso` file, or add it to an existing datastore\.
1. Deploy the OVF template, but do not start the VM yet\.
1. In the **Navigator** panel, right\-click the new virtual machine and choose **Edit Settings**\.
1. On the **Virtual Hardware** tab, for **New device**, choose **CD/DVD Drive**, and then choose **Add**\.
1. For **New CD/DVD Drive**, choose **Datastore ISO File**\. Select the datastore to which you added the `seed.iso` file, browse to and select the `seed.iso` file, and then choose **OK**\.
1. For **New CD/DVD Drive**, select **Connect**, and then choose **OK**\.
After you have associated the datastore with the VM, you should be able to boot it\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/amazon-linux-2-virtual-machine.md |
e0656ed81285-0 | **To boot the VM using KVM**
1. Open the **Create new VM** wizard\.
1. For Step 1, choose **Import existing disk image**\.
1. For Step 2, browse to and select the VM image\. For **OS type** and **Version**, choose **Linux** and **Red Hat Enterprise Linux 7\.0** respectively\.
1. For Step 3, specify the amount of RAM and the number of CPUs to use\.
1. For Step 4, enter a name for the new VM and select **Customize configuration before install**, and choose **Finish**\.
1. In the Configuration window for the VM, choose **Add Hardware**\.
1. In the **Add New Virtual Hardware** window, choose **Storage**\.
1. In the Storage configuration, choose **Select or create custom storage**\. For **Device type**, choose **CDROM device**\. Choose **Manage**, **Browse Local**, and then navigate to and select the `seed.iso` file\. Choose **Finish**\.
1. Choose **Begin Installation**\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/amazon-linux-2-virtual-machine.md |
35357cde6969-0 | **To boot the VM using Oracle VirtualBox**
1. Open the **Create Virtual Machine** wizard\.
1. When prompted to select a **Type** and a **Version**, select **Linux** and **RHEL \(64\-bit\)** respectively\.
1. When prompted to configure the hard disk, choose **Use an existing virtual hard disk file**, select the VM image, and then choose **Create**\.
1. Before you start the VM, you must load the `seed.iso` file in the virtual machine's virtual optical drive:
1. Select the new VM, choose **Settings**, and then choose **Storage**\.
1. In the **Storage Devices** list, under **Controller: IDE**, choose the *empty* optical drive\.
1. In the **Attributes** section for the optical drive, choose the browse button, select **Choose Virtual Optical Disk File**, and then select the `seed.iso` file\.
After you have added the `seed.iso` file to the virtual optical drive, you should be able to boot the VM\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/amazon-linux-2-virtual-machine.md |
582c6cea10b3-0 | The VM image for Microsoft Hyper\-V is compressed into a zip file\. You must extract the contents of the zip file\.
**To boot the VM using Microsoft Hyper\-V**
1. Open the new **Virtual Machine Wizard**\.
1. When prompted to select a generation, select **Generation 1**\.
1. When prompted to configure the network adapter, for **Connection** choose **External**\.
1. When prompted to connect a virtual hard disk, choose **Use an existing virtual hard disk**, choose **Browse**, and then navigate to and select the VM image\. Choose **Finish** to create the VM\.
1. Right\-click the new VM and choose **Settings**\. In the **Settings** window, under **IDE Controller 1**, choose **DVD Drive**\.
1. For the DVD drive, choose **Image file** and then browse to and select the `seed.iso` file\.
1. Apply the changes and start the VM\.
------
After the VM has booted, log in using one of the user accounts that is defined in the `user-data` configuration file\. For virtualization platforms other than VMWare, you can disconnect the `seed.iso` boot image from the VM after you have logged in for the first time\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/amazon-linux-2-virtual-machine.md |
aa7a0eb4ad9b-0 | With target tracking scaling policies, you select a metric and set a target value\. Spot Fleet creates and manages the CloudWatch alarms that trigger the scaling policy and calculates the scaling adjustment based on the metric and the target value\. The scaling policy adds or removes capacity as required to keep the metric at, or close to, the specified target value\. In addition to keeping the metric close to the target value, a target tracking scaling policy also adjusts to the fluctuations in the metric due to a fluctuating load pattern and minimizes rapid fluctuations in the capacity of the fleet\.
You can create multiple target tracking scaling policies for a Spot Fleet, provided that each of them uses a different metric\. The fleet scales based on the policy that provides the largest fleet capacity\. This enables you to cover multiple scenarios and ensure that there is always enough capacity to process your application workloads\.
To ensure application availability, the fleet scales out proportionally to the metric as fast as it can, but scales in more gradually\.
When a Spot Fleet terminates an instance because the target capacity was decreased, the instance receives a Spot Instance interruption notice\.
Do not edit or delete the CloudWatch alarms that Spot Fleet manages for a target tracking scaling policy\. Spot Fleet deletes the alarms automatically when you delete the target tracking scaling policy\.
**Limitation**
+ The Spot Fleet request must have a request type of `maintain`\. Automatic scaling is not supported for one\-time requests or Spot blocks\.
**To configure a target tracking policy \(console\)** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/spot-fleet-target-tracking.md |
aa7a0eb4ad9b-1 | **To configure a target tracking policy \(console\)**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the navigation pane, choose **Spot Requests**\.
1. Select your Spot Fleet request and choose **Auto Scaling**\.
1. If automatic scaling is not configured, choose **Configure**\.
1. Use **Scale capacity between** to set the minimum and maximum capacity for your fleet\. Automatic scaling does not scale your fleet below the minimum capacity or above the maximum capacity\.
1. For **Policy name**, type a name for the policy\.
1. Choose a **Target metric**\.
1. Enter a **Target value** for the metric\.
1. \(Optional\) Set **Cooldown period** to modify the default cooldown period\.
1. \(Optional\) Select **Disable scale\-in** to omit creating a scale\-in policy based on the current configuration\. You can create a scale\-in policy using a different configuration\.
1. Choose **Save**\.
**To configure a target tracking policy using the AWS CLI** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/spot-fleet-target-tracking.md |
aa7a0eb4ad9b-2 | 1. Choose **Save**\.
**To configure a target tracking policy using the AWS CLI**
1. Register the Spot Fleet request as a scalable target using the [register\-scalable\-target](https://docs.aws.amazon.com/cli/latest/reference/application-autoscaling/register-scalable-target.html) command\.
1. Create a scaling policy using the [put\-scaling\-policy](https://docs.aws.amazon.com/cli/latest/reference/application-autoscaling/put-scaling-policy.html) command\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/spot-fleet-target-tracking.md |
e2ebfc5ce5a3-0 | An instance reboot is equivalent to an operating system reboot\. In most cases, it takes only a few minutes to reboot your instance\. When you reboot an instance, it keeps its public DNS name \(IPv4\), private IPv4 address, IPv6 address \(if applicable\), and any data on its instance store volumes\.
Rebooting an instance doesn't start a new instance billing period \(with a minimum one\-minute charge\), unlike stopping and starting your instance\.
We might schedule your instance for a reboot for necessary maintenance, such as to apply updates that require a reboot\. No action is required on your part; we recommend that you wait for the reboot to occur within its scheduled window\. For more information, see [Scheduled events for your instances](monitoring-instances-status-check_sched.md)\.
We recommend that you use the Amazon EC2 console, a command line tool, or the Amazon EC2 API to reboot your instance instead of running the operating system reboot command from your instance\. If you use the Amazon EC2 console, a command line tool, or the Amazon EC2 API to reboot your instance, we perform a hard reboot if the instance does not cleanly shut down within a few minutes\. If you use AWS CloudTrail, then using Amazon EC2 to reboot your instance also creates an API record of when your instance was rebooted\.
**To reboot an instance using the console**
1. Open the Amazon EC2 console\.
1. In the navigation pane, choose **Instances**\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-instance-reboot.md |
e2ebfc5ce5a3-1 | 1. Open the Amazon EC2 console\.
1. In the navigation pane, choose **Instances**\.
1. Select the instance and choose **Actions**, **Instance State**, **Reboot**\.
1. Choose **Yes, Reboot** when prompted for confirmation\. The instance will remain in a "running" state\.
**To reboot 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)\.
+ [reboot\-instances](https://docs.aws.amazon.com/cli/latest/reference/ec2/reboot-instances.html) \(AWS CLI\)
+ [Restart\-EC2Instance](https://docs.aws.amazon.com/powershell/latest/reference/items/Restart-EC2Instance.html) \(AWS Tools for Windows PowerShell\) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-instance-reboot.md |
935c8c0ee883-0 | Before you can launch an instance, you must select an AMI to use\. As you select an AMI, consider the following requirements you might have for the instances that you'll launch:
+ The Region
+ The operating system
+ The architecture: 32\-bit \(`i386`\), 64\-bit \(`x86_64`\), or 64\-bit ARM \(arm64\)
+ The root device type: Amazon EBS or instance store
+ The provider \(for example, Amazon Web Services\)
+ Additional software \(for example, SQL server\)
If you need to find a Windows AMI, see [Finding a Windows AMI](https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/finding-an-ami.html) in the *Amazon EC2 User Guide for Windows Instances*\.
**Topics**
+ [Finding a Linux AMI using the Amazon EC2 console](#finding-an-ami-console)
+ [Finding an AMI using the AWS CLI](#finding-an-ami-aws-cli)
+ [Finding the latest Amazon Linux AMI using Systems Manager](#finding-an-ami-parameter-store)
+ [Using a Systems Manager parameter to find an AMI](#using-systems-manager-parameter-to-find-AMI)
+ [Finding a Quick Start AMI](#finding-quick-start-ami) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/finding-an-ami.md |
113ab30d8580-0 | You can find Linux AMIs using the Amazon EC2 console\. You can select from the list of AMIs when you use the launch wizard to launch an instance, or you can search through all available AMIs using the **Images** page\. AMI IDs are unique to each AWS Region\.
**To find a Linux AMI using the launch wizard**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. From the navigation bar, select the Region in which to launch your instances\. You can select any Region that's available to you, regardless of your location\.
1. From the console dashboard, choose **Launch instance**\.
1. On the **Quick Start** tab, select from one of the commonly used AMIs in the list\. If you don't see the AMI that you need, select the **My AMIs**, **AWS Marketplace**, or **Community AMIs** tab to find additional AMIs\. For more information, see [Step 1: Choose an Amazon Machine Image \(AMI\)](launching-instance.md#step-1-AMI)\.
**To find a Linux AMI using the Images page**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/finding-an-ami.md |
113ab30d8580-1 | 1. From the navigation bar, select the Region in which to launch your instances\. You can select any Region that's available to you, regardless of your location\.
1. In the navigation pane, choose **AMIs**\.
1. \(Optional\) Use the **Filter** options to scope the list of displayed AMIs to see only the AMIs that interest you\. For example, to list all Linux AMIs provided by AWS, select **Public images**\. Choose the Search bar and select **Owner** from the menu, then select **Amazon images**\. Choose the Search bar again to select **Platform** and then the operating system from the list provided\.
1. \(Optional\) Choose the **Show/Hide Columns** icon to select which image attributes to display, such as the root device type\. Alternatively, you can select an AMI from the list and view its properties in the **Details** tab\.
1. Before you select an AMI, it's important that you check whether it's backed by instance store or by Amazon EBS and that you are aware of the effects of this difference\. For more information, see [Storage for the root device](ComponentsAMIs.md#storage-for-the-root-device)\.
1. To launch an instance from this AMI, select it and then choose **Launch**\. For more information about launching an instance using the console, see [Launching your instance from an AMI](launching-instance.md#choose-an-instance-type-page)\. If you're not ready to launch the instance now, make note of the AMI ID for later\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/finding-an-ami.md |
78e24f33878c-0 | You can use AWS CLI commands for Amazon EC2 to list only the Linux AMIs that meet your needs\. After locating an AMI that meets your needs, make note of its ID so that you can use it to launch instances\. For more information, see [Launching an Instance Using the AWS CLI](https://docs.aws.amazon.com/cli/latest/userguide/cli-ec2-launch.html#launching-instances) in the *AWS Command Line Interface User Guide*\.
The [describe\-images](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-images.html) command supports filtering parameters\. For example, use the `--owners` parameter to display public AMIs owned by Amazon\.
```
aws ec2 describe-images --owners self amazon
```
You can add the following filter to the previous command to display only AMIs backed by Amazon EBS\.
```
--filters "Name=root-device-type,Values=ebs"
```
**Important**
Omitting the `--owners` flag from the describe\-images command will return all images for which you have launch permissions, regardless of ownership\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/finding-an-ami.md |
23e9f518ef50-0 | Amazon EC2 provides AWS Systems Manager public parameters for AWS\-maintained public AMIs that you can use when launching instances\. For example, the EC2\-provided parameter `/aws/service/ami-amazon-linux-latest/amzn2-ami-hvm-x86_64-gp2` is available in all Regions and always points to the latest version of the Amazon Linux 2 AMI in a given Region\.
The Amazon EC2 AMI public parameters are available from the following paths:
+ `/aws/service/ami-amazon-linux-latest`
+ `/aws/service/ami-windows-latest`
You can view a list of all Linux AMIs in the current AWS Region by using the following command in the AWS CLI\.
```
aws ssm get-parameters-by-path --path /aws/service/ami-amazon-linux-latest --query Parameters[].Name
```
**To launch an instance using a public parameter**
The following example uses the EC2\-provided public parameter to launch an `m5.xlarge` instance using the latest Amazon Linux 2 AMI\.
To specify the parameter in the command, use the following syntax: `resolve:ssm:public-parameter`, where `resolve:ssm` is the standard prefix and `public-parameter` is the path and name of the public parameter\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/finding-an-ami.md |
23e9f518ef50-1 | In this example, the `--count` and `--security-group` parameters are not included\. For `--count`, the default is 1\. If you have a default VPC and a default security group, they are used\.
```
aws ec2 run-instances
--image-id resolve:ssm:/aws/service/ami-amazon-linux-latest/amzn2-ami-hvm-x86_64-gp2
--instance-type m5.xlarge
--key-name MyKeyPair
```
For more information, see [Using public parameters](https://docs.aws.amazon.com/systems-manager/latest/userguide/parameter-store-public-parameters.html) in the *AWS Systems Manager User Guide* and [Query for the latest Amazon Linux AMI IDs Using AWS Systems Manager Parameter Store](http://aws.amazon.com/blogs/compute/query-for-the-latest-amazon-linux-ami-ids-using-aws-systems-manager-parameter-store/)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/finding-an-ami.md |
3896250f4082-0 | When you launch an instance using the EC2 launch wizard in the console, you can either select an AMI from the list, or you can select an AWS Systems Manager parameter that points to an AMI ID\. If you use automation code to launch your instances, you can specify the Systems Manager parameter instead of the AMI ID\.
A Systems Manager parameter is a customer\-defined key\-value pair that you can create in Systems Manager Parameter Store\. The Parameter Store provides a central store to externalize your application configuration values\. For more information, see [AWS Systems Manager Parameter Store](https://docs.aws.amazon.com/systems-manager/latest/userguide/systems-manager-parameter-store.html) in the *AWS Systems Manager User Guide*\.
When you create a parameter that points to an AMI ID, make sure that you specify the data type as `aws:ec2:image`\. This data type ensures that when the parameter is created or modified, the parameter value is validated as an AMI ID\. For more information, see [Native parameter support for Amazon Machine Image IDs](https://docs.aws.amazon.com/systems-manager/latest/userguide/parameter-store-ec2-aliases.html) in the *AWS Systems Manager User Guide*\.
**Topics**
+ [Use cases](#systems-manager-parameter-use-case)
+ [Launching an instance using a Systems Manager parameter](#systems-manager-parameter-launch-instance)
+ [Permissions](#systems-manager-permissions)
+ [Limitations](#AMI-systems-manager-parameter-limitations) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/finding-an-ami.md |
a6160f57018e-0 | By using Systems Manager parameters to point to AMI IDs, you can make it easier for your users to select the correct AMI when launching instances, and you can simplify the maintenance of automation code\.
**Easier for users**
If you require instances to be launched using a specific AMI, and if that AMI is updated regularly, we recommend that you require your users to select a Systems Manager parameter to find the AMI\. By requiring your users to select a Systems Manager parameter, you can ensure that the latest AMI is used to launch instances\.
For example, every month in your organization you might create a new version of your AMI that has the latest operating system and application patches\. You also require your users to launch instances using the latest version of your AMI\. To ensure that your users use the latest version, you can create a Systems Manager parameter \(for example, `golden-ami`\) that points to the correct AMI ID\. Each time a new version of the AMI is created, you update the AMI ID value in the parameter so that it always points to the latest AMI\. Your users don't need to know about the periodic updates to the AMI, because they continue to select the same Systems Manager parameter every time\. By having users select a Systems Manager parameter, you make it easier for them to select the correct AMI for an instance launch\.
**Simplify automation code maintenance** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/finding-an-ami.md |
a6160f57018e-1 | **Simplify automation code maintenance**
If you use automation code to launch your instances, you can specify the Systems Manager parameter instead of the AMI ID\. If a new version of the AMI is created, you change the AMI ID value in the parameter so that it points to the latest AMI\. The automation code that references the parameter doesn’t need to be modified every time a new version of the AMI is created\. This greatly simplifies maintenance of automation and helps drive down deployment costs\.
**Note**
Running instances are not affected when you change the AMI ID to which the Systems Manager parameter points\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/finding-an-ami.md |
3ebf26642597-0 | You can launch an instance using the the console or the AWS CLI\. Instead of specifying an AMI ID, you can specify an AWS Systems Manager parameter that points to an AMI ID\.
**To find a Linux AMI using a Systems Manager parameter \(console\)**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. From the navigation bar, select the Region in which to launch your instances\. You can select any Region that's available to you, regardless of your location\.
1. From the console dashboard, choose **Launch instance**\.
1. Choose **Search by Systems Manager parameter** \(at top right\)\.
1. For **Systems Manager parameter**, select a parameter\. The corresponding AMI ID appears next to **Currently resolves to**\.
1. Choose **Search**\. The AMIs that match the AMI ID appear in the list\.
1. Select the AMI from the list, and choose **Select**\.
For more information about launching an instance from an AMI using the launch wizard, see [Step 1: Choose an Amazon Machine Image \(AMI\)](launching-instance.md#step-1-AMI)\.
**To launch an instance using an AWS Systems Manager parameter instead of an AMI ID \(AWS CLI\)** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/finding-an-ami.md |
3ebf26642597-1 | **To launch an instance using an AWS Systems Manager parameter instead of an AMI ID \(AWS CLI\)**
The following example uses the Systems Manager parameter `golden-ami` to launch an `m5.xlarge` instance\. The parameter points to an AMI ID\.
To specify the parameter in the command, use the following syntax: `resolve:ssm:/parameter-name`, where `resolve:ssm` is the standard prefix and `parameter-name` is the unique parameter name\. Note that the parameter name is case\-sensitive\. Backslashes for the parameter name are only necessary when the parameter is part of a hierarchy, for example, `/amis/production/golden-ami`\. You can omit the backslash if the parameter is not part of a hierarchy\.
In this example, the `--count` and `--security-group` parameters are not included\. For `--count`, the default is 1\. If you have a default VPC and a default security group, they are used\.
```
aws ec2 run-instances
--image-id resolve:ssm:/golden-ami
--instance-type m5.xlarge
...
```
**To launch an instance using a specific version of an AWS Systems Manager parameter \(AWS CLI\)** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/finding-an-ami.md |
3ebf26642597-2 | ```
**To launch an instance using a specific version of an AWS Systems Manager parameter \(AWS CLI\)**
Systems Manager parameters have version support\. Each iteration of a parameter is assigned a unique version number\. You can reference the version of the parameter as follows `resolve:ssm:parameter-name:version`, where `version` is the unique version number\. By default, the latest version of the parameter is used when no version is specified\.
The following example uses version 2 of the parameter\.
In this example, the `--count` and `--security-group` parameters are not included\. For `--count`, the default is 1\. If you have a default VPC and a default security group, they are used\.
```
aws ec2 run-instances
--image-id resolve:ssm:/golden-ami:2
--instance-type m5.xlarge
...
```
**To launch an instance using a public parameter provided by AWS**
Amazon EC2 provides Systems Manager public parameters for public AMIs provided by AWS\. For example, the public parameter /aws/service/ami\-amazon\-linux\-latest/amzn2\-ami\-hvm\-x86\_64\-gp2 is available in all Regions and always points to the latest version of the Amazon Linux 2 AMI in the Region\.
```
aws ec2 run-instances | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/finding-an-ami.md |
3ebf26642597-3 | ```
aws ec2 run-instances
--image-id resolve:ssm:/aws/service/ami-amazon-linux-latest/amzn2-ami-hvm-x86_64-gp2
--instance-type m5.xlarge
...
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/finding-an-ami.md |
59225d5b4fe5-0 | If you use Systems Manager parameters that point to AMI IDs in the launch instance wizard, you must add `ssm:DescribeParameters` and `ssm:GetParameters` to your IAM policy\. `ssm:DescribeParameters` grants your IAM users the permission to view and select Systems Manager parameters\. `ssm:GetParameters` grants your IAM users the permission to get the values of the Systems Manager parameters\. You can also restrict access to specific Systems Manager parameters\. For more information, see [Using | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/finding-an-ami.md |
59225d5b4fe5-1 | Manager parameters\. For more information, see [Using the EC2 launch wizard](iam-policies-ec2-console.md#ex-launch-wizard)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/finding-an-ami.md |
5b784b41971b-0 | AMIs and Systems Manager parameters are Region specific\. To use the same Systems Manager parameter name across Regions, create a Systems Manager parameter in each Region with the same name \(for example, `golden-ami`\)\. In each Region, point the Systems Manager parameter to an AMI in that Region\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/finding-an-ami.md |
1df617e731ca-0 | When you launch an instance using the Amazon EC2 console, the **Choose an Amazon Machine Image \(AMI\)** page includes a list of popular AMIs on the **Quick Start** tab\. If you want to automate launching an instance using one of these quick start AMIs, you'll need to programatically locate the ID of the current version of the AMI\.
To locate the current version of a Quick Start AMI, you can enumerate all AMIs with its AMI name, and then find the one with the most recent creation date\.
**Example: Find the current Amazon Linux 2 AMI**
```
aws ec2 describe-images \
--owners amazon \
--filters 'Name=name,Values=amzn2-ami-hvm-2.0.????????.?-x86_64-gp2' 'Name=state,Values=available' \
--query 'reverse(sort_by(Images, &CreationDate))[:1].ImageId' \
--output text
```
**Example: Find the current Amazon Linux AMI**
```
aws ec2 describe-images \
--owners amazon \
--filters 'Name=name,Values=amzn-ami-hvm-????.??.?.????????-x86_64-gp2' 'Name=state,Values=available' \ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/finding-an-ami.md |
1df617e731ca-1 | --query 'reverse(sort_by(Images, &CreationDate))[:1].ImageId' \
--output text
```
**Example: Find the current Ubuntu Server 16\.04 LTS AMI**
```
aws ec2 describe-images \
--owners 099720109477 \
--filters 'Name=name,Values=ubuntu/images/hvm-ssd/ubuntu-xenial-16.04-amd64-server-????????' 'Name=state,Values=available' \
--query 'reverse(sort_by(Images, &CreationDate))[:1].ImageId' \
--output text
```
**Example: Find the current Red Hat Enterprise Linux 7\.5 AMI**
```
aws ec2 describe-images \
--owners 309956199498 \
--filters 'Name=name,Values=RHEL-7.5_HVM_GA*' 'Name=state,Values=available' \
--query 'reverse(sort_by(Images, &CreationDate))[:1].ImageId' \
--output text
```
**Example: Find the current SUSE Linux Enterprise Server 15 AMI**
```
aws ec2 describe-images \ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/finding-an-ami.md |
1df617e731ca-2 | **Example: Find the current SUSE Linux Enterprise Server 15 AMI**
```
aws ec2 describe-images \
--owners amazon \
--filters 'Name=name,Values=suse-sles-15-v????????-hvm-ssd-x86_64' 'Name=state,Values=available' \
--query 'reverse(sort_by(Images, &CreationDate))[:1].ImageId' \
--output text
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/finding-an-ami.md |
69668422c29e-0 | The following procedures are for creating an instance store\-backed AMI from an instance store\-backed instance\. Before you begin, ensure that you've read the [Prerequisites](creating-an-ami-instance-store.md#bundle-ami-prerequisites)\.
**Topics**
+ [Creating an AMI from an instance store\-backed Amazon Linux instance](#amazon_linux_instructions)
+ [Creating an AMI from an instance store\-backed Ubuntu instance](#ubuntu_instructions) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/create-instance-store-ami.md |
d81bab122a52-0 | This section describes the creation of an AMI from an Amazon Linux instance\. The following procedures may not work for instances running other Linux distributions\. For Ubuntu\-specific procedures, see [Creating an AMI from an instance store\-backed Ubuntu instance](#ubuntu_instructions)\.
**To prepare to use the AMI tools \(HVM instances only\)**
1. The AMI tools require GRUB Legacy to boot properly\. Use the following command to install GRUB:
```
[ec2-user ~]$ sudo yum install -y grub
```
1. Install the partition management packages with the following command:
```
[ec2-user ~]$ sudo yum install -y gdisk kpartx parted
```
**To create an AMI from an instance store\-backed Amazon Linux instance**
This procedure assumes that you have satisfied the prerequisites in [Prerequisites](creating-an-ami-instance-store.md#bundle-ami-prerequisites)\.
1. Upload your credentials to your instance\. We use these credentials to ensure that only you and Amazon EC2 can access your AMI\.
1. Create a temporary directory on your instance for your credentials as follows:
```
[ec2-user ~]$ mkdir /tmp/cert
```
This enables you to exclude your credentials from the created image\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/create-instance-store-ami.md |
d81bab122a52-1 | ```
This enables you to exclude your credentials from the created image\.
1. Copy your X\.509 certificate and corresponding private key from your computer to the `/tmp/cert` directory on your instance using a secure copy tool such as [scp](AccessingInstancesLinux.md#AccessingInstancesLinuxSCP)\. The `-i my-private-key.pem` option in the following scp command is the private key you use to connect to your instance with SSH, not the X\.509 private key\. For example:
```
you@your_computer:~ $ scp -i my-private-key.pem /path/to/pk-HKZYKTAIG2ECMXYIBH3HXV4ZBEXAMPLE.pem /path/to/cert-HKZYKTAIG2ECMXYIBH3HXV4ZBEXAMPLE.pem [email protected]:/tmp/cert/
pk-HKZYKTAIG2ECMXYIBH3HXV4ZBEXAMPLE.pem 100% 717 0.7KB/s 00:00
cert-HKZYKTAIG2ECMXYIBH3HXV4ZBEXAMPLE.pem 100% 685 0.7KB/s 00:00
```
Alternatively, because these are plain text files, you can open the certificate and key in a text editor and copy their contents into new files in `/tmp/cert`\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/create-instance-store-ami.md |
d81bab122a52-2 | Alternatively, because these are plain text files, you can open the certificate and key in a text editor and copy their contents into new files in `/tmp/cert`\.
1. <a name="step_with_bundle_path_amazon_linux"></a>Prepare the bundle to upload to Amazon S3 by running the [ec2\-bundle\-vol](ami-tools-commands.md#ami-bundle-vol) command from inside your instance\. Be sure to specify the `-e` option to exclude the directory where your credentials are stored\. By default, the bundle process excludes files that might contain sensitive information\. These files include `*.sw`, `*.swo`, `*.swp`, `*.pem`, `*.priv`, `*id_rsa*`, `*id_dsa*` `*.gpg`, `*.jks`, `*/.ssh/authorized_keys`, and `*/.bash_history`\. To include all of these files, use the `--no-filter` option\. To include some of these files, use the `--include` option\.
**Important** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/create-instance-store-ami.md |
d81bab122a52-3 | **Important**
By default, the AMI bundling process creates a compressed, encrypted collection of files in the `/tmp` directory that represents your root volume\. If you do not have enough free disk space in `/tmp` to store the bundle, you need to specify a different location for the bundle to be stored with the `-d /path/to/bundle/storage` option\. Some instances have ephemeral storage mounted at `/mnt` or `/media/ephemeral0` that you can use, or you can also [create](ebs-creating-volume.md), [attach](ebs-attaching-volume.md), and [mount](ebs-using-volumes.md) a new Amazon EBS volume to store the bundle\.
1. You must run the ec2\-bundle\-vol command as root\. For most commands, you can use sudo to gain elevated permissions, but in this case, you should run sudo \-E su to keep your environment variables\.
```
[ec2-user ~]$ sudo -E su
```
Note that bash prompt now identifies you as the root user, and that the dollar sign has been replaced by a hash tag, signalling that you are in a root shell:
```
[root ec2-user]#
```
1. To create the AMI bundle, run the [ec2\-bundle\-vol](ami-tools-commands.md#ami-bundle-vol) command as follows:
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/create-instance-store-ami.md |
d81bab122a52-4 | ```
[root ec2-user]# ec2-bundle-vol -k /tmp/cert/pk-HKZYKTAIG2ECMXYIBH3HXV4ZBEXAMPLE.pem -c /tmp/cert/cert-HKZYKTAIG2ECMXYIBH3HXV4ZBEXAMPLE.pem -u 123456789012 -r x86_64 -e /tmp/cert --partition gpt
```
**Note**
For the China \(Beijing\) and AWS GovCloud \(US\-West\) Regions, use the `--ec2cert` parameter and specify the certificates as per the [prerequisites](creating-an-ami-instance-store.md#bundle-ami-prerequisites)\.
It can take a few minutes to create the image\. When this command completes, your `/tmp` \(or non\-default\) directory contains the bundle \(`image.manifest.xml`, plus multiple `image.part.`*xx* files\)\.
1. Exit from the root shell\.
```
[root ec2-user]# exit
```
1. \(Optional\) To add more instance store volumes, edit the block device mappings in the `image.manifest.xml` file for your AMI\. For more information, see [Block device mapping](block-device-mapping-concepts.md)\.
1. Create a backup of your `image.manifest.xml` file\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/create-instance-store-ami.md |
d81bab122a52-5 | 1. Create a backup of your `image.manifest.xml` file\.
```
[ec2-user ~]$ sudo cp /tmp/image.manifest.xml /tmp/image.manifest.xml.bak
```
1. Reformat the `image.manifest.xml` file so that it is easier to read and edit\.
```
[ec2-user ~]$ sudo xmllint --format /tmp/image.manifest.xml.bak > sudo /tmp/image.manifest.xml
```
1. Edit the block device mappings in `image.manifest.xml` with a text editor\. The example below shows a new entry for the `ephemeral1` instance store volume\.
**Note**
For a list of excluded files, see [ec2\-bundle\-vol](ami-tools-commands.md#ami-bundle-vol)\.
```
<block_device_mapping>
<mapping>
<virtual>ami</virtual>
<device>sda</device>
</mapping>
<mapping>
<virtual>ephemeral0</virtual>
<device>sdb</device>
</mapping>
<mapping>
<virtual>ephemeral1</virtual>
<device>sdc</device>
</mapping>
<mapping> | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/create-instance-store-ami.md |
d81bab122a52-6 | <device>sdc</device>
</mapping>
<mapping>
<virtual>root</virtual>
<device>/dev/sda1</device>
</mapping>
</block_device_mapping>
```
1. Save the `image.manifest.xml` file and exit your text editor\.
1. To upload your bundle to Amazon S3, run the [ec2\-upload\-bundle](ami-tools-commands.md#ami-upload-bundle) command as follows\.
```
[ec2-user ~]$ ec2-upload-bundle -b my-s3-bucket/bundle_folder/bundle_name -m /tmp/image.manifest.xml -a your_access_key_id -s your_secret_access_key
```
**Important**
To register your AMI in a Region other than US East \(N\. Virginia\), you must specify both the target Region with the `--region` option and a bucket path that already exists in the target Region or a unique bucket path that can be created in the target Region\.
1. \(Optional\) After the bundle is uploaded to Amazon S3, you can remove the bundle from the `/tmp` directory on the instance using the following rm command:
```
[ec2-user ~]$ sudo rm /tmp/image.manifest.xml /tmp/image.part.* /tmp/image | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/create-instance-store-ami.md |
d81bab122a52-7 | [ec2-user ~]$ sudo rm /tmp/image.manifest.xml /tmp/image.part.* /tmp/image
```
**Important**
If you specified a path with the `-d /path/to/bundle/storage` option in [Step 2](#step_with_bundle_path_amazon_linux), use that path instead of `/tmp`\.
1. To register your AMI, run the [register\-image](https://docs.aws.amazon.com/cli/latest/reference/ec2/register-image.html) command as follows\.
```
[ec2-user ~]$ aws ec2 register-image --image-location my-s3-bucket/bundle_folder/bundle_name/image.manifest.xml --name AMI_name --virtualization-type hvm
```
**Important**
If you previously specified a Region for the [ec2\-upload\-bundle](ami-tools-commands.md#ami-upload-bundle) command, specify that Region again for this command\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/create-instance-store-ami.md |
90f553446088-0 | This section describes the creation of an AMI from an Ubuntu Linux instance with an instance store volume as the root volume\. The following procedures may not work for instances running other Linux distributions\. For procedures specific to Amazon Linux, see [Creating an AMI from an instance store\-backed Amazon Linux instance](#amazon_linux_instructions)\.
**To prepare to use the AMI tools \(HVM instances only\)**
The AMI tools require GRUB Legacy to boot properly\. However, Ubuntu is configured to use GRUB 2\. You must check to see that your instance uses GRUB Legacy, and if not, you need to install and configure it\.
HVM instances also require partitioning tools to be installed for the AMI tools to work properly\.
1. GRUB Legacy \(version 0\.9*x* or less\) must be installed on your instance\. Check to see if GRUB Legacy is present and install it if necessary\.
1. Check the version of your GRUB installation\.
```
ubuntu:~$ grub-install --version
grub-install (GRUB) 1.99-21ubuntu3.10
```
In this example, the GRUB version is greater than 0\.9*x*, so you must install GRUB Legacy\. Proceed to [Step 2](#grub-install-step)\. If GRUB Legacy is already present, you can skip to [Step 2](#partition)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/create-instance-store-ami.md |
Subsets and Splits