id
stringlengths 14
16
| text
stringlengths 1
2.43k
| source
stringlengths 99
229
|
|---|---|---|
dfea2af13ebc-1 | "NotAfter" : "21 Jan 2019 09:17:23 GMT",
"State" : "active"
}
]
```
<a name="viewing-event-history"></a>
**To view event history about completed or canceled events for your instances using instance metadata**
You can retrieve information about completed or canceled events for your instances from [instance metadata](ec2-instance-metadata.md) using Instance Metadata Service Version 2 or Instance Metadata Service Version 1\.
IMDSv2
```
[ec2-user ~]$ TOKEN=`curl -X PUT "http://169.254.169.254/latest/api/token" -H "X-aws-ec2-metadata-token-ttl-seconds: 21600"` \
&& curl -H "X-aws-ec2-metadata-token: $TOKEN" –v http://169.254.169.254/latest/meta-data/events/maintenance/history
```
IMDSv1
```
[ec2-user ~]$ curl http://169.254.169.254/latest/meta-data/events/maintenance/history
```
The following is example output with information about a system reboot event that was canceled, and a system reboot event that was completed, in JSON format\.
```
[
{ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-instances-status-check_sched.md |
dfea2af13ebc-2 | ```
[
{
"NotBefore" : "21 Jan 2019 09:00:43 GMT",
"Code" : "system-reboot",
"Description" : "[Canceled] scheduled reboot",
"EventId" : "instance-event-0d59937288b749b32",
"NotAfter" : "21 Jan 2019 09:17:23 GMT",
"State" : "canceled"
},
{
"NotBefore" : "29 Jan 2019 09:00:43 GMT",
"Code" : "system-reboot",
"Description" : "[Completed] scheduled reboot",
"EventId" : "instance-event-0d59937288b749b32",
"NotAfter" : "29 Jan 2019 09:17:23 GMT",
"State" : "completed"
}
]
```
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-instances-status-check_sched.md |
bf5617484c79-0 | You can customize scheduled event notifications to include tags in the email notification\. This makes it easier to identify the affected resource \(instances or Dedicated Hosts\) and to prioritize actions for the upcoming event\.
When you customize event notifications to include tags, you can choose to include:
+ All of the tags that are associated with the affected resource
+ Only specific tags that are associated with the affected resource
For example, suppose that you assign `application`, `costcenter`, `project`, and `owner` tags to all of your instances\. You can choose to include all of the tags in event notifications\. Alternatively, if you'd like to see only the `owner` and `project` tags in event notifications, then you can choose to include only those tags\.
After you select the tags to include, the event notifications will include the resource ID \(instance ID or Dedicated Host ID\) and the tag key and value pairs that are associated with the affected resource\.
**Topics**
+ [Including tags in event notifications](#register-tags)
+ [Removing tags from event notifications](#deregister-tags)
+ [Viewing the tags to be included in event notifications](#view-tags) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-instances-status-check_sched.md |
9392c77688c6-0 | The tags that you choose to include apply to all resources \(instances and Dedicated Hosts\) in the selected Region\. To customize event notifications in other Regions, first select the required Region and then perform the following steps\.
You can include tags in event notifications using one of the following methods\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-instances-status-check_sched.md |
37b60ec2053c-0 | **To include tags in event notifications**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the navigation pane, choose **Events**\.
1. Choose **Actions**, **Manage event notifications**\.
1. Select **Include resource tags in event notifications**\.
1. Do one of the following, depending on the tags that you want to include in event notifications:
+ To include all of the tags associated with the affected instance or Dedicated Host, select **Include all resource tags**\.
+ To manually select the tags to include, select **Choose the tags to include**, and then for **Choose the tags to include**, enter the tag key and press **Enter**\.
1. Choose **Save**\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-instances-status-check_sched.md |
9855f6dad4ca-0 | **To include all tags in event notifications**
Use the [ register\-instance\-event\-notification\-attributes](https://docs.aws.amazon.com/cli/latest/reference/ec2/register-instance-event-notification-attributes.html) AWS CLI command and set the `IncludeAllTagsOfInstance` parameter to `true`\.
```
aws ec2 register-instance-event-notification-attributes --instance-tag-attribute "IncludeAllTagsOfInstance=true"
```
**To include specific tags in event notifications**
Use the [ register\-instance\-event\-notification\-attributes](https://docs.aws.amazon.com/cli/latest/reference/ec2/register-instance-event-notification-attributes.html) AWS CLI command and specify the tags to include using the `InstanceTagKeys` parameter\.
```
aws ec2 register-instance-event-notification-attributes --instance-tag-attribute 'InstanceTagKeys=["tag_key_1", "tag_key_2", "tag_key_3"]'
```
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-instances-status-check_sched.md |
9fce03bc754c-0 | You can remove tags from event notifications using one of the following methods\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-instances-status-check_sched.md |
801b87547fdd-0 | **To remove tags from event notifications**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the navigation pane, choose **Events**\.
1. Choose **Actions**, **Manage event notifications**\.
1. Do one of the following, depending on the tag that you want to remove from event notifications\.
+ To remove all tags from event notifications, clear **Include resource tags in event notifications**\.
+ To remove specific tags from event notifications, choose **Remove** \(**X**\) for the tags listed below the **Choose the tags to include** field\.
1. Choose **Save**\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-instances-status-check_sched.md |
85c8e405920c-0 | **To remove all tags from event notifications**
Use the [ deregister\-instance\-event\-notification\-attributes](https://docs.aws.amazon.com/cli/latest/reference/ec2/deregister-instance-event-notification-attributes.html) AWS CLI command and set the `IncludeAllTagsOfInstance` parameter to `false`\.
```
aws ec2 deregister-instance-event-notification-attributes --instance-tag-attribute "IncludeAllTagsOfInstance=false"
```
**To remove specific tags from event notifications**
Use the [ deregister\-instance\-event\-notification\-attributes](https://docs.aws.amazon.com/cli/latest/reference/ec2/deregister-instance-event-notification-attributes.html) AWS CLI command and specify the tags to remove using the `InstanceTagKeys` parameter\.
```
aws ec2 deregister-instance-event-notification-attributes --instance-tag-attribute 'InstanceTagKeys=["tag_key_1", "tag_key_2", "tag_key_3"]'
```
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-instances-status-check_sched.md |
fa4c1d80553d-0 | You can view the tags that are to be included in event notifications using one of the following methods\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-instances-status-check_sched.md |
7564e1ce046f-0 | **To view the tags that are to be included in event notifications**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the navigation pane, choose **Events**\.
1. Choose **Actions**, **Manage event notifications**\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-instances-status-check_sched.md |
62c72e8674d6-0 | **To view the tags that are to be included in event notifications**
Use the [ describe\-instance\-event\-notification\-attributes](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-instance-event-notification-attributes.html) AWS CLI command\.
```
aws ec2 describe-instance-event-notification-attributes
```
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-instances-status-check_sched.md |
24e267f5a8be-0 | When AWS detects irreparable failure of the underlying host for your instance, it schedules the instance to stop or terminate, depending on the type of root device for the instance\. If the root device is an EBS volume, the instance is scheduled to stop\. If the root device is an instance store volume, the instance is scheduled to terminate\. For more information, see [Instance retirement](instance-retirement.md)\.
**Important**
Any data stored on instance store volumes is lost when an instance is stopped or terminated\. This includes instance store volumes that are attached to an instance that has an EBS volume as the root device\. Be sure to save data from your instance store volumes that you might need later before the instance is stopped or terminated\.
**Actions for Instances Backed by Amazon EBS**
You can wait for the instance to stop as scheduled\. Alternatively, you can stop and start the instance yourself, which migrates it to a new host\. For more information about stopping your instance, in addition to information about the changes to your instance configuration when it's stopped, see [Stop and start your instance](Stop_Start.md)\.
You can automate an immediate stop and start in response to a scheduled instance stop event\. For more information, see [Automating Actions for EC2 Instances](https://docs.aws.amazon.com/health/latest/ug/cloudwatch-events-health.html#automating-instance-actions) in the *AWS Health User Guide*\.
**Actions for Instances Backed by Instance Store** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-instances-status-check_sched.md |
24e267f5a8be-1 | **Actions for Instances Backed by Instance Store**
We recommend that you launch a replacement instance from your most recent AMI and migrate all necessary data to the replacement instance before the instance is scheduled to terminate\. Then, you can terminate the original instance, or wait for it to terminate as scheduled\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-instances-status-check_sched.md |
727e370b668b-0 | When AWS must perform tasks such as installing updates or maintaining the underlying host, it can schedule the instance or the underlying host for a reboot\. You can [reschedule most reboot events](#reschedule-event) so that your instance is rebooted at a specific date and time that suits you\.
If you stop your linked [EC2\-Classic instance](vpc-classiclink.md#classiclink-limitations), it is automatically unlinked from the VPC and the VPC security groups are no longer associated with the instance\. You can link your instance to the VPC again after you've restarted it\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-instances-status-check_sched.md |
5bfbb24ca984-0 | You can view whether a reboot event is an instance reboot or a system reboot using one of the following methods\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-instances-status-check_sched.md |
4aeb3999e81e-0 | **To view the type of scheduled reboot event 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 **Events**\.
1. Choose **Resource type: instance** from the filter list\.
1. For each instance, view the value in the **Event type** column\. The value is either **system\-reboot** or **instance\-reboot**\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-instances-status-check_sched.md |
5cd16535d6ef-0 | **To view the type of scheduled reboot event 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 **Events**\.
1. Choose **Instance resources** from the filter list\.
1. For each instance, view the value in the **Event Type** column\. The value is either **system\-reboot** or **instance\-reboot**\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-instances-status-check_sched.md |
fbb823794488-0 | **To view the type of scheduled reboot event using the AWS CLI**
Use the [describe\-instance\-status](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-instance-status.html) command\.
```
aws ec2 describe-instance-status --instance-id i-1234567890abcdef0
```
For scheduled reboot events, the value for `Code` is either `system-reboot` or `instance-reboot`\. The following example output shows a `system-reboot` event\.
```
[
"Events": [
{
"InstanceEventId": "instance-event-0d59937288b749b32",
"Code": "system-reboot",
"Description": "The instance is scheduled for a reboot",
"NotAfter": "2019-03-14T22:00:00.000Z",
"NotBefore": "2019-03-14T20:00:00.000Z",
"NotBeforeDeadline": "2019-04-05T11:00:00.000Z"
}
]
]
```
------
<a name="schedevents_actions_instancereboot"></a> | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-instances-status-check_sched.md |
fbb823794488-1 | ```
------
<a name="schedevents_actions_instancereboot"></a>
**Actions for instance reboot**
You can wait for the instance reboot to occur within its scheduled maintenance window, [reschedule](#reschedule-event) the instance reboot to a date and time that suits you, or [reboot](ec2-instance-reboot.md) the instance yourself at a time that is convenient for you\.
After your instance is rebooted, the scheduled event is cleared and the event's description is updated\. The pending maintenance to the underlying host is completed, and you can begin using your instance again after it has fully booted\.
<a name="schedevents_actions_systemreboot"></a>
**Actions for system reboot**
It is not possible for you to reboot the system yourself\. You can wait for the system reboot to occur during its scheduled maintenance window, or you can [reschedule](#reschedule-event) the system reboot to a date and time that suits you\. A system reboot typically completes in a matter of minutes\. After the system reboot has occurred, the instance retains its IP address and DNS name, and any data on local instance store volumes is preserved\. After the system reboot is complete, the scheduled event for the instance is cleared, and you can verify that the software on your instance is operating as expected\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-instances-status-check_sched.md |
fbb823794488-2 | Alternatively, if it is necessary to maintain the instance at a different time and you can't reschedule the system reboot, then you can stop and start an Amazon EBS\-backed instance, which migrates it to a new host\. However, the data on the local instance store volumes is not preserved\. You can also automate an immediate instance stop and start in response to a scheduled system reboot event\. For more information, see [Automating Actions for EC2 Instances](https://docs.aws.amazon.com/health/latest/ug/cloudwatch-events-health.html#automating-instance-actions) in the *AWS Health User Guide*\. For an instance store\-backed instance, if you can't reschedule the system reboot, then you can launch a replacement instance from your most recent AMI, migrate all necessary data to the replacement instance before the scheduled maintenance window, and then terminate the original instance\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-instances-status-check_sched.md |
ca831042549f-0 | When AWS must maintain the underlying host for an instance, it schedules the instance for maintenance\. There are two types of maintenance events: network maintenance and power maintenance\.
During network maintenance, scheduled instances lose network connectivity for a brief period of time\. Normal network connectivity to your instance is restored after maintenance is complete\.
During power maintenance, scheduled instances are taken offline for a brief period, and then rebooted\. When a reboot is performed, all of your instance's configuration settings are retained\.
After your instance has rebooted \(this normally takes a few minutes\), verify that your application is working as expected\. At this point, your instance should no longer have a scheduled event associated with it, or if it does, the description of the scheduled event begins with **\[Completed\]**\. It sometimes takes up to 1 hour for the instance status description to refresh\. Completed maintenance events are displayed on the Amazon EC2 console dashboard for up to a week\.
**Actions for Instances Backed by Amazon EBS**
You can wait for the maintenance to occur as scheduled\. Alternatively, you can stop and start the instance, which migrates it to a new host\. For more information about stopping your instance, in addition to information about the changes to your instance configuration when it's stopped, see [Stop and start your instance](Stop_Start.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-instances-status-check_sched.md |
ca831042549f-1 | You can automate an immediate stop and start in response to a scheduled maintenance event\. For more information, see [Automating Actions for EC2 Instances](https://docs.aws.amazon.com/health/latest/ug/cloudwatch-events-health.html#automating-instance-actions) in the *AWS Health User Guide*\.
**Actions for instances backed by instance store**
You can wait for the maintenance to occur as scheduled\. Alternatively, if you want to maintain normal operation during a scheduled maintenance window, you can launch a replacement instance from your most recent AMI, migrate all necessary data to the replacement instance before the scheduled maintenance window, and then terminate the original instance\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-instances-status-check_sched.md |
b65c59b0d47d-0 | You can reschedule an event so that it occurs at a specific date and time that suits you\. Only events that have a deadline date can be rescheduled\. There are other [limitations for rescheduling an event](#limitations-for-rescheduling)\.
You can reschedule an event using one of the following methods\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-instances-status-check_sched.md |
fa5ca69c6082-0 | **To reschedule an event 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 **Events**\.
1. Choose **Resource type: instance** from the filter list\.
1. Select one or more instances, and then choose **Actions**, **Schedule event**\.
Only events that have an event deadline date, indicated by a value for **Deadline**, can be rescheduled\. If one of the selected events does not have a deadline date, **Actions**, **Schedule event** is disabled\.
1. For **New start time**, enter a new date and time for the event\. The new date and time must occur before the **Event deadline**\.
1. Choose **Save**\.
It might take 1\-2 minutes for the updated event start time to be reflected in the console\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-instances-status-check_sched.md |
5e41a2534d3d-0 | **To reschedule an event 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 **Events**\.
1. Choose **Instance resources** from the filter list\.
1. Select one or more instances, and then choose **Actions**, **Schedule Event**\.
Only events that have an event deadline date, indicated by a value for **Event Deadline**, can be rescheduled\.
1. For **Event start time**, enter a new date and time for the event\. The new date and time must occur before the **Event Deadline**\.
1. Choose **Schedule Event**\.
It might take 1\-2 minutes for the updated event start time to be reflected in the console\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-instances-status-check_sched.md |
d5afe12ebf10-0 | **To reschedule an event using the AWS CLI**
1. Only events that have an event deadline date, indicated by a value for `NotBeforeDeadline`, can be rescheduled\. Use the [describe\-instance\-status](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-instance-status.html) command to view the `NotBeforeDeadline` parameter value\.
```
aws ec2 describe-instance-status --instance-id i-1234567890abcdef0
```
The following example output shows a `system-reboot` event that can be rescheduled because `NotBeforeDeadline` contains a value\.
```
[
"Events": [
{
"InstanceEventId": "instance-event-0d59937288b749b32",
"Code": "system-reboot",
"Description": "The instance is scheduled for a reboot",
"NotAfter": "2019-03-14T22:00:00.000Z",
"NotBefore": "2019-03-14T20:00:00.000Z",
"NotBeforeDeadline": "2019-04-05T11:00:00.000Z"
}
]
]
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-instances-status-check_sched.md |
d5afe12ebf10-1 | }
]
]
```
1. To reschedule the event, use the [modify\-instance\-event\-start\-time](https://docs.aws.amazon.com/cli/latest/reference/ec2/modify-instance-event-start-time.html) command\. Specify the new event start time using the `not-before` parameter\. The new event start time must fall before the `NotBeforeDeadline`\.
```
aws ec2 modify-instance-event-start-time --instance-id i-1234567890abcdef0 --instance-event-id instance-event-0d59937288b749b32 --not-before 2019-03-25T10:00:00.000
```
It might take 1\-2 minutes before the [describe\-instance\-status](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-instance-status.html) command returns the updated `not-before` parameter value\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-instances-status-check_sched.md |
c1ad99c5c570-0 | + Only events with an event deadline date can be rescheduled\. The event can be rescheduled up to the event deadline date\. The **Deadline** column in the console and the `NotBeforeDeadline` field in the AWS CLI indicate if the event has a deadline date\.
+ Only events that have not yet started can be rescheduled\. The **Start time** column in the console and the `NotBefore` field in the AWS CLI indicate the event start time\. Events that are scheduled to start in the next 5 minutes cannot be rescheduled\.
+ The new event start time must be at least 60 minutes from the current time\.
+ If you reschedule multiple events using the console, the event deadline date is determined by the event with the earliest event deadline date\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring-instances-status-check_sched.md |
234047b698d5-0 | You can convert an instance store\-backed Linux AMI that you own to an Amazon EBS\-backed Linux AMI\.
**Important**
You can't convert an instance store\-backed Windows AMI to an Amazon EBS\-backed Windows AMI and you cannot convert an AMI that you do not own\.
**To convert an instance store\-backed AMI to an Amazon EBS\-backed AMI**
1. Launch an Amazon Linux instance from an Amazon EBS\-backed AMI\. For more information, see [Launching an instance using the Launch Instance Wizard](launching-instance.md)\. Amazon Linux instances have the AWS CLI and AMI tools pre\-installed\.
1. Upload the X\.509 private key that you used to bundle your instance store\-backed AMI to your instance\. We use this key to ensure that only you and Amazon EC2 can access your AMI\.
1. Create a temporary directory on your instance for your X\.509 private key as follows:
```
[ec2-user ~]$ mkdir /tmp/cert
```
1. Copy your X\.509 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 *my\-private\-key* parameter in the following command is the private key you use to connect to your instance with SSH\. For example:
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/Using_ConvertingS3toEBS.md |
234047b698d5-1 | ```
you@your_computer:~ $ scp -i my-private-key.pem /path/to/pk-HKZYKTAIG2ECMXYIBH3HXV4ZBEXAMPLE.pem [email protected]:/tmp/cert/
pk-HKZYKTAIG2ECMXYIBH3HXV4ZBEXAMPLE.pem 100% 717 0.7KB/s 00:00
```
1. Set environment variables for your AWS access key and secret key\.
```
[ec2-user ~]$ export AWS_ACCESS_KEY_ID=your_access_key_id
[ec2-user ~]$ export AWS_SECRET_ACCESS_KEY=your_secret_access_key
```
1. Prepare an Amazon EBS volume for your new AMI\.
1. Create an empty Amazon EBS volume in the same Availability Zone as your instance using the [create\-volume](https://docs.aws.amazon.com/cli/latest/reference/ec2/create-volume.html) command\. Note the volume ID in the command output\.
**Important**
This Amazon EBS volume must be the same size or larger than the original instance store root volume\.
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/Using_ConvertingS3toEBS.md |
234047b698d5-2 | **Important**
This Amazon EBS volume must be the same size or larger than the original instance store root volume\.
```
[ec2-user ~]$ aws ec2 create-volume --size 10 --region us-west-2 --availability-zone us-west-2b
```
1. Attach the volume to your Amazon EBS\-backed instance using the [attach\-volume](https://docs.aws.amazon.com/cli/latest/reference/ec2/attach-volume.html) command\.
```
[ec2-user ~]$ aws ec2 attach-volume --volume-id volume_id --instance-id instance_id --device /dev/sdb --region us-west-2
```
1. Create a folder for your bundle\.
```
[ec2-user ~]$ mkdir /tmp/bundle
```
1. Download the bundle for your instance store\-based AMI to `/tmp/bundle` using the [ec2\-download\-bundle](ami-tools-commands.md#ami-download-bundle) command\.
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/Using_ConvertingS3toEBS.md |
234047b698d5-3 | ```
[ec2-user ~]$ ec2-download-bundle -b my-s3-bucket/bundle_folder/bundle_name -m image.manifest.xml -a $AWS_ACCESS_KEY_ID -s $AWS_SECRET_ACCESS_KEY --privatekey /path/to/pk-HKZYKTAIG2ECMXYIBH3HXV4ZBEXAMPLE.pem -d /tmp/bundle
```
1. Reconstitute the image file from the bundle using the [ec2\-unbundle](ami-tools-commands.md#ami-unbundle) command\.
1. Change directories to the bundle folder\.
```
[ec2-user ~]$ cd /tmp/bundle/
```
1. Run the [ec2\-unbundle](ami-tools-commands.md#ami-unbundle) command\.
```
[ec2-user bundle]$ ec2-unbundle -m image.manifest.xml --privatekey /path/to/pk-HKZYKTAIG2ECMXYIBH3HXV4ZBEXAMPLE.pem
```
1. Copy the files from the unbundled image to the new Amazon EBS volume\.
```
[ec2-user bundle]$ sudo dd if=/tmp/bundle/image of=/dev/sdb bs=1M
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/Using_ConvertingS3toEBS.md |
234047b698d5-4 | [ec2-user bundle]$ sudo dd if=/tmp/bundle/image of=/dev/sdb bs=1M
```
1. Probe the volume for any new partitions that were unbundled\.
```
[ec2-user bundle]$ sudo partprobe /dev/sdb1
```
1. List the block devices to find the device name to mount\.
```
[ec2-user bundle]$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
/dev/sda 202:0 0 8G 0 disk
└─/dev/sda1 202:1 0 8G 0 part /
/dev/sdb 202:80 0 10G 0 disk
└─/dev/sdb1 202:81 0 10G 0 part
```
In this example, the partition to mount is `/dev/sdb1`, but your device name will likely be different\. If your volume is not partitioned, then the device to mount will be similar to `/dev/sdb` \(without a device partition trailing digit\)\.
1. Create a mount point for the new Amazon EBS volume and mount the volume\.
```
[ec2-user bundle]$ sudo mkdir /mnt/ebs
[ec2-user bundle]$ sudo mount /dev/sdb1 /mnt/ebs
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/Using_ConvertingS3toEBS.md |
234047b698d5-5 | [ec2-user bundle]$ sudo mount /dev/sdb1 /mnt/ebs
```
1. Open the `/etc/fstab` file on the EBS volume with your favorite text editor \(such as vim or nano\) and remove any entries for instance store \(ephemeral\) volumes\. Because the Amazon EBS volume is mounted on `/mnt/ebs`, the `fstab` file is located at `/mnt/ebs/etc/fstab`\.
```
[ec2-user bundle]$ sudo nano /mnt/ebs/etc/fstab | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/Using_ConvertingS3toEBS.md |
7822cf696faa-0 | LABEL=/ / ext4 defaults,noatime 1 1
tmpfs /dev/shm tmpfs defaults 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
sysfs /sys sysfs defaults 0 0
proc /proc proc defaults 0 0
/dev/sdb /media/ephemeral0 auto defaults,comment=cloudconfig 0 2
```
In this example, the last line should be removed\.
1. Unmount the volume and detach it from the instance\.
```
[ec2-user bundle]$ sudo umount /mnt/ebs
[ec2-user bundle]$ aws ec2 detach-volume --volume-id volume_id --region us-west-2
```
1. Create an AMI from the new Amazon EBS volume as follows\.
1. Create a snapshot of the new Amazon EBS volume\.
```
[ec2-user bundle]$ aws ec2 create-snapshot --region us-west-2 --description "your_snapshot_description" --volume-id volume_id
```
1. Check to see that your snapshot is complete\.
```
[ec2-user bundle]$ aws ec2 describe-snapshots --region us-west-2 --snapshot-id snapshot_id | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/Using_ConvertingS3toEBS.md |
7822cf696faa-1 | [ec2-user bundle]$ aws ec2 describe-snapshots --region us-west-2 --snapshot-id snapshot_id
```
1. Identify the processor architecture, virtualization type, and the kernel image \(`aki`\) used on the original AMI with the describe\-images command\. You need the AMI ID of the original instance store\-backed AMI for this step\.
```
[ec2-user bundle]$ aws ec2 describe-images --region us-west-2 --image-id ami-id --output text
IMAGES x86_64 amazon/amzn-ami-pv-2013.09.2.x86_64-s3 ami-8ef297be amazon available public machine aki-fc8f11cc instance-store paravirtual xen
```
In this example, the architecture is `x86_64` and the kernel image ID is `aki-fc8f11cc`\. Use these values in the following step\. If the output of the above command also lists an `ari` ID, take note of that as well\.
1. Register your new AMI with the snapshot ID of your new Amazon EBS volume and the values from the previous step\. If the previous command output listed an `ari` ID, include that in the following command with `--ramdisk-id ari_id`\.
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/Using_ConvertingS3toEBS.md |
7822cf696faa-2 | ```
[ec2-user bundle]$ aws ec2 register-image --region us-west-2 --name your_new_ami_name --block-device-mappings DeviceName=device-name,Ebs={SnapshotId=snapshot_id} --virtualization-type paravirtual --architecture x86_64 --kernel-id aki-fc8f11cc --root-device-name device-name
```
1. \(Optional\) After you have tested that you can launch an instance from your new AMI, you can delete the Amazon EBS volume that you created for this procedure\.
```
aws ec2 delete-volume --volume-id volume_id
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/Using_ConvertingS3toEBS.md |
ce6922515318-0 | In some situations, you may find that a volume other than the volume attached to `/dev/xvda` or `/dev/sda` has become the root volume of your instance\. This can happen when you have attached the root volume of another instance, or a volume created from the snapshot of a root volume, to an instance with an existing root volume\.
This is due to how the initial ramdisk in Linux works\. It chooses the volume defined as `/` in the `/etc/fstab`, and in some distributions, this is determined by the label attached to the volume partition\. Specifically, you find that your `/etc/fstab` looks something like the following:
```
LABEL=/ / ext4 defaults,noatime 1 1
tmpfs /dev/shm tmpfs defaults 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
sysfs /sys sysfs defaults 0 0
proc /proc proc defaults 0 0
```
If you check the label of both volumes, you see that they both contain the `/` label:
```
[ec2-user ~]$ sudo e2label /dev/xvda1
/
[ec2-user ~]$ sudo e2label /dev/xvdf1
/
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-booting-from-wrong-volume.md |
ce6922515318-1 | /
[ec2-user ~]$ sudo e2label /dev/xvdf1
/
```
In this example, you could end up having `/dev/xvdf1` become the root device that your instance boots to after the initial ramdisk runs, instead of the `/dev/xvda1` volume from which you had intended to boot\. To solve this, use the same e2label command to change the label of the attached volume that you do not want to boot from\.
In some cases, specifying a UUID in `/etc/fstab` can resolve this\. However, if both volumes come from the same snapshot, or the secondary is created from a snapshot of the primary volume, they share a UUID\.
```
[ec2-user ~]$ sudo blkid
/dev/xvda1: LABEL="/" UUID=73947a77-ddbe-4dc7-bd8f-3fe0bc840778 TYPE="ext4" PARTLABEL="Linux" PARTUUID=d55925ee-72c8-41e7-b514-7084e28f7334
/dev/xvdf1: LABEL="old/" UUID=73947a77-ddbe-4dc7-bd8f-3fe0bc840778 TYPE="ext4" PARTLABEL="Linux" PARTUUID=d55925ee-72c8-41e7-b514-7084e28f7334 | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-booting-from-wrong-volume.md |
ce6922515318-2 | ```
**To change the label of an attached ext4 volume**
1. Use the e2label command to change the label of the volume to something other than `/`\.
```
[ec2-user ~]$ sudo e2label /dev/xvdf1 old/
```
1. Verify that the volume has the new label\.
```
[ec2-user ~]$ sudo e2label /dev/xvdf1
old/
```
**To change the label of an attached xfs volume**
+ Use the xfs\_admin command to change the label of the volume to something other than `/`\.
```
[ec2-user ~]$ sudo xfs_admin -L old/ /dev/xvdf1
writing all SBs
new label = "old/"
```
After changing the volume label as shown, you should be able to reboot the instance and have the proper volume selected by the initial ramdisk when the instance boots\.
**Important**
If you intend to detach the volume with the new label and return it to another instance to use as the root volume, you must perform the above procedure again and change the volume label back to its original value\. Otherwise, the other instance does not boot because the ramdisk is unable to find the volume with the label `/`\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-booting-from-wrong-volume.md |
7c97ecbbd45c-0 | Amazon S3 is a repository for internet data\. Amazon S3 provides access to reliable, fast, and inexpensive data storage infrastructure\. It is designed to make web\-scale computing easier by enabling you to store and retrieve any amount of data, at any time, from within Amazon EC2 or anywhere on the web\. Amazon S3 stores data objects redundantly on multiple devices across multiple facilities and allows concurrent read or write access to these data objects by many separate clients or application threads\. You can use the redundant data stored in Amazon S3 to recover quickly and reliably from instance or application failures\.
Amazon EC2 uses Amazon S3 for storing Amazon Machine Images \(AMIs\)\. You use AMIs for launching EC2 instances\. In case of instance failure, you can use the stored AMI to immediately launch another instance, thereby allowing for fast recovery and business continuity\.
Amazon EC2 also uses Amazon S3 to store snapshots \(backup copies\) of the data volumes\. You can use snapshots for recovering data quickly and reliably in case of application or system failures\. You can also use snapshots as a baseline to create multiple new data volumes, expand the size of an existing data volume, or move data volumes across multiple Availability Zones, thereby making your data usage highly scalable\. For more information about using data volumes and snapshots, see [Amazon Elastic Block Store \(Amazon EBS\)](AmazonEBS.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/AmazonS3.md |
7c97ecbbd45c-1 | Objects are the fundamental entities stored in Amazon S3\. Every object stored in Amazon S3 is contained in a bucket\. Buckets organize the Amazon S3 namespace at the highest level and identify the account responsible for that storage\. Amazon S3 buckets are similar to internet domain names\. Objects stored in the buckets have a unique key value and are retrieved using a URL\. For example, if an object with a key value `/photos/mygarden.jpg` is stored in the `DOC-EXAMPLE-BUCKET1` bucket, then it is addressable using the URL `https://DOC-EXAMPLE-BUCKET1.s3.amazonaws.com/photos/mygarden.jpg`\.
For more information about the features of Amazon S3, see the [Amazon S3 product page](https://aws.amazon.com/s3)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/AmazonS3.md |
6f8a7353db71-0 | Given the benefits of Amazon S3 for storage, you might decide to use this service to store files and data sets for use with EC2 instances\. There are several ways to move data to and from Amazon S3 to your instances\. In addition to the examples discussed below, there are a variety of tools that people have written that you can use to access your data in Amazon S3 from your computer or your instance\. Some of the common ones are discussed in the AWS forums\.
If you have permission, you can copy a file to or from Amazon S3 and your instance using one of the following methods\.
**GET or wget**
The wget utility is an HTTP and FTP client that allows you to download public objects from Amazon S3\. It is installed by default in Amazon Linux and most other distributions, and available for download on Windows\. To download an Amazon S3 object, use the following command, substituting the URL of the object to download\.
```
[ec2-user ~]$ wget https://my_bucket.s3.amazonaws.com/path-to-file
```
This method requires that the object you request is public; if the object is not public, you receive an "ERROR 403: Forbidden" message\. If you receive this error, open the Amazon S3 console and change the permissions of the object to public\. For more information, see the [Amazon Simple Storage Service Developer Guide](https://docs.aws.amazon.com/AmazonS3/latest/dev/)\.
**AWS Command Line Interface** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/AmazonS3.md |
6f8a7353db71-1 | **AWS Command Line Interface**
The AWS Command Line Interface \(AWS CLI\) is a unified tool to manage your AWS services\. The AWS CLI enables users to authenticate themselves and download restricted items from Amazon S3 and also to upload items\. For more information, such as how to install and configure the tools, see the [AWS Command Line Interface detail page](https://aws.amazon.com/cli/)\.
The aws s3 cp command is similar to the Unix cp command\. You can copy files from Amazon S3 to your instance, copy files from your instance to Amazon S3, and copy files from one Amazon S3 location to another\.
Use the following command to copy an object from Amazon S3 to your instance\.
```
[ec2-user ~]$ aws s3 cp s3://my_bucket/my_folder/my_file.ext my_copied_file.ext
```
Use the following command to copy an object from your instance back into Amazon S3\.
```
[ec2-user ~]$ aws s3 cp my_copied_file.ext s3://my_bucket/my_folder/my_file.ext
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/AmazonS3.md |
6f8a7353db71-2 | ```
The aws s3 sync command can synchronize an entire Amazon S3 bucket to a local directory location\. This can be helpful for downloading a data set and keeping the local copy up\-to\-date with the remote set\. If you have the proper permissions on the Amazon S3 bucket, you can push your local directory back up to the cloud when you are finished by reversing the source and destination locations in the command\.
Use the following command to download an entire Amazon S3 bucket to a local directory on your instance\.
```
[ec2-user ~]$ aws s3 sync s3://remote_S3_bucket local_directory
```
**Amazon S3 API**
If you are a developer, you can use an API to access data in Amazon S3\. For more information, see the [Amazon Simple Storage Service Developer Guide](https://docs.aws.amazon.com/AmazonS3/latest/dev/)\. You can use this API and its examples to help develop your application and integrate it with other APIs and SDKs, such as the boto Python interface\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/AmazonS3.md |
0da560858e27-0 | Amazon EC2 provides enhanced networking capabilities through the Intel 82599 VF interface, which uses the Intel `ixgbevf` driver\.
**Topics**
+ [Requirements](#ixgbevf-requirements)
+ [Testing whether enhanced networking is enabled](#test-enhanced-networking)
+ [Enabling enhanced networking on Amazon Linux](#enable-enhanced-networking)
+ [Enabling enhanced networking on Ubuntu](#enhanced-networking-ubuntu)
+ [Enabling enhanced networking on other Linux distributions](#enhanced-networking-linux)
+ [Troubleshooting connectivity issues](#enhanced-networking-troubleshooting) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/sriov-networking.md |
a92bdc65ed54-0 | To prepare for enhanced networking using the Intel 82599 VF interface, set up your instance as follows:
+ Select from the following supported instance types: C3, C4, D2, I2, M4 \(excluding `m4.16xlarge`\), and R3\.
+ Launch the instance from an HVM AMI using Linux kernel version of 2\.6\.32 or later\. The latest Amazon Linux HVM AMIs have the modules required for enhanced networking installed and have the required attributes set\. Therefore, if you launch an Amazon EBS–backed, enhanced networking–supported instance using a current Amazon Linux HVM AMI, enhanced networking is already enabled for your instance\.
**Warning**
Enhanced networking is supported only for HVM instances\. Enabling enhanced networking with a PV instance can make it unreachable\. Setting this attribute without the proper module or module version can also make your instance unreachable\.
+ Ensure that the instance has internet connectivity\.
+ Install and configure the [AWS CLI](https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-getting-set-up.html) or the [AWS Tools for Windows PowerShell](https://docs.aws.amazon.com/powershell/latest/userguide/) on any computer you choose, preferably your local desktop or laptop\. For more information, see [Accessing Amazon EC2](concepts.md#access-ec2)\. Enhanced networking cannot be managed from the Amazon EC2 console\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/sriov-networking.md |
a92bdc65ed54-1 | + If you have important data on the instance that you want to preserve, you should back that data up now by creating an AMI from your instance\. Updating kernels and kernel modules, as well as enabling the `sriovNetSupport` attribute, might render incompatible instances or operating systems unreachable\. If you have a recent backup, your data will still be retained if this happens\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/sriov-networking.md |
713379304680-0 | Enhanced networking with the Intel 82599 VF interface is enabled if the `ixgbevf` module is installed on your instance and the `sriovNetSupport` attribute is set\.
**Instance attribute \(sriovNetSupport\)**
To check whether an instance has the enhanced networking `sriovNetSupport` attribute set, use one of the following commands:
+ [describe\-instance\-attribute](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-instance-attribute.html) \(AWS CLI\)
```
aws ec2 describe-instance-attribute --instance-id instance_id --attribute sriovNetSupport
```
+ [Get\-EC2InstanceAttribute](https://docs.aws.amazon.com/powershell/latest/reference/items/Get-EC2InstanceAttribute.html) \(AWS Tools for Windows PowerShell\)
```
Get-EC2InstanceAttribute -InstanceId instance-id -Attribute sriovNetSupport
```
If the attribute isn't set, `SriovNetSupport` is empty\. If the attribute is set, the value is simple, as shown in the following example output\.
```
"SriovNetSupport": {
"Value": "simple"
},
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/sriov-networking.md |
713379304680-1 | "SriovNetSupport": {
"Value": "simple"
},
```
**Image attribute \(sriovNetSupport\)**
To check whether an AMI already has the enhanced networking `sriovNetSupport` attribute set, use one of the following commands:
+ [describe\-images](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-images.html) \(AWS CLI\)
```
aws ec2 describe-images --image-id ami_id --query "Images[].SriovNetSupport"
```
+ [Get\-EC2Image](https://docs.aws.amazon.com/powershell/latest/reference/items/Get-EC2Image.html) \(AWS Tools for Windows PowerShell\)
```
(Get-EC2Image -ImageId ami-id).SriovNetSupport
```
If the attribute isn't set, `SriovNetSupport` is empty\. If the attribute is set, the value is simple\.
**Network interface driver** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/sriov-networking.md |
713379304680-2 | **Network interface driver**
Use the following command to verify that the module is being used on a particular interface, substituting the interface name that you want to check\. If you are using a single interface \(default\), this is `eth0`\. If the operating system supports [predictable network names](#predictable-network-names-sriov), this could be a name like `ens5`\.
In the following example, the `ixgbevf` module is not loaded, because the listed driver is `vif`\.
```
[ec2-user ~]$ ethtool -i eth0
driver: vif
version:
firmware-version:
bus-info: vif-0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: no
```
In this example, the `ixgbevf` module is loaded\. This instance has enhanced networking properly configured\.
```
[ec2-user ~]$ ethtool -i eth0
driver: ixgbevf
version: 4.0.3
firmware-version: N/A
bus-info: 0000:00:03.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: no | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/sriov-networking.md |
713379304680-3 | supports-statistics: yes
supports-test: yes
supports-eeprom-access: no
supports-register-dump: yes
supports-priv-flags: no
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/sriov-networking.md |
e5a26665c9a9-0 | The latest Amazon Linux HVM AMIs have the `ixgbevf` module required for enhanced networking installed and have the required `sriovNetSupport` attribute set\. Therefore, if you launch an instance type using a current Amazon Linux HVM AMI, enhanced networking is already enabled for your instance\. For more information, see [Testing whether enhanced networking is enabled](#test-enhanced-networking)\.
If you launched your instance using an older Amazon Linux AMI and it does not have enhanced networking enabled already, use the following procedure to enable enhanced networking\.
**Warning**
There is no way to disable the enhanced networking attribute after you've enabled it\.
**To enable enhanced networking**
1. <a name="amazon-linux-enhanced-networking-start-step"></a>Connect to your instance\.
1. From the instance, run the following command to update your instance with the newest kernel and kernel modules, including `ixgbevf`:
```
[ec2-user ~]$ sudo yum update
```
1. From your local computer, reboot your instance using the Amazon EC2 console or one of the following commands: [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/sriov-networking.md |
e5a26665c9a9-1 | 1. <a name="amazon-linux-enhanced-networking-stop-step"></a>Connect to your instance again and verify that the `ixgbevf` module is installed and at the minimum recommended version using the modinfo ixgbevf command from [Testing whether enhanced networking is enabled](#test-enhanced-networking)\.
1. \[EBS\-backed instance\] 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\.
\[Instance store\-backed instance\] You can't stop the instance to modify the attribute\. Instead, proceed to this procedure: [To enable enhanced networking \(instance store\-backed instances\)](#enhanced-networking-instance-store)\.
1. From your local computer, enable the enhanced networking attribute using one of the following commands:
+ [modify\-instance\-attribute](https://docs.aws.amazon.com/cli/latest/reference/ec2/modify-instance-attribute.html) \(AWS CLI\)
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/sriov-networking.md |
e5a26665c9a9-2 | ```
aws ec2 modify-instance-attribute --instance-id instance_id --sriov-net-support simple
```
+ [Edit\-EC2InstanceAttribute](https://docs.aws.amazon.com/powershell/latest/reference/items/Edit-EC2InstanceAttribute.html) \(AWS Tools for Windows PowerShell\)
```
Edit-EC2InstanceAttribute -InstanceId instance_id -SriovNetSupport "simple"
```
1. \(Optional\) Create an AMI from the instance, as described in [Creating an Amazon EBS\-backed Linux AMI](creating-an-ami-ebs.md) \. The AMI inherits the enhanced networking attribute from the instance\. Therefore, you can use this AMI to launch another instance with enhanced networking enabled by default\.
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/sriov-networking.md |
e5a26665c9a9-3 | 1. Connect to your instance and verify that the `ixgbevf` module is installed and loaded on your network interface using the ethtool \-i eth*n* command from [Testing whether enhanced networking is enabled](#test-enhanced-networking)\.<a name="enhanced-networking-instance-store"></a>
**To enable enhanced networking \(instance store\-backed instances\)**
Follow the previous procedure until the step where you stop the instance\. Create a new AMI as described in [Creating an instance store\-backed Linux AMI](creating-an-ami-instance-store.md), making sure to enable the enhanced networking 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 --sriov-net-support simple ...
```
+ [Register\-EC2Image](https://docs.aws.amazon.com/powershell/latest/reference/items/Register-EC2Image.html) \(AWS Tools for Windows PowerShell\)
```
Register-EC2Image -SriovNetSupport "simple" ...
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/sriov-networking.md |
a14f2c370812-0 | Before you begin, [check if enhanced networking is already enabled](#test-enhanced-networking) on your instance\.
The Quick Start Ubuntu HVM AMIs include the necessary drivers for enhanced networking\. If you have a version of `ixgbevf` earlier than 2\.16\.4, you can install the `linux-aws` kernel package to get the latest enhanced networking drivers\.
The following procedure provides the general steps for compiling the `ixgbevf` module on an Ubuntu instance\.<a name="ubuntu-enhanced-networking-procedure"></a>
**To install the linux\-aws kernel package**
1. <a name="ubuntu-enhanced-networking-start-step"></a>Connect to your instance\.
1. Update the package cache and packages\.
```
ubuntu:~$ sudo apt-get update && sudo apt-get upgrade -y linux-aws
```
**Important**
If during the update process, you are prompted to install `grub`, use `/dev/xvda` to install `grub`, and then choose to keep the current version of `/boot/grub/menu.lst`\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/sriov-networking.md |
94126f50fe75-0 | Before you begin, [check if enhanced networking is already enabled](#test-enhanced-networking) on your instance\. The latest Quick Start HVM AMIs include the necessary drivers for enhanced networking, therefore you do not need to perform additional steps\.
The following procedure provides the general steps if you need to enable enhanced networking with the Intel 82599 VF interface on a Linux distribution other than Amazon Linux or Ubuntu\. For more information, such as detailed syntax for commands, file locations, or package and tool support, see the specific documentation for your Linux distribution\.
**To enable enhanced networking on Linux**
1. <a name="other-linux-enhanced-networking-start-step"></a>Connect to your instance\.
1. Download the source for the `ixgbevf` module on your instance from Sourceforge at [https://sourceforge\.net/projects/e1000/files/ixgbevf%20stable/](https://sourceforge.net/projects/e1000/files/ixgbevf%20stable/)\.
Versions of `ixgbevf` earlier than 2\.16\.4, including version 2\.14\.2, do not build properly on some Linux distributions, including certain versions of Ubuntu\.
1. Compile and install the `ixgbevf` module on your instance\.
**Warning** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/sriov-networking.md |
94126f50fe75-1 | 1. Compile and install the `ixgbevf` module on your instance\.
**Warning**
If you compile the `ixgbevf` module for your current kernel and then upgrade your kernel without rebuilding the driver for the new kernel, your system might revert to the distribution\-specific `ixgbevf` module at the next reboot\. This could make your system unreachable if the distribution\-specific version is incompatible with enhanced networking\.
1. Run the sudo depmod command to update module dependencies\.
1. <a name="other-linux-enhanced-networking-stop-step"></a>Update `initramfs` on your instance to ensure that the new module loads at boot time\.
1. <a name="predictable-network-names-sriov"></a>Determine if your system uses predictable network interface names by default\. Systems that use systemd or udev versions 197 or greater can rename Ethernet devices and they do not guarantee that a single network interface will be named `eth0`\. This behavior can cause problems connecting to your instance\. For more information and to see other configuration options, see [Predictable Network Interface Names](https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/) on the freedesktop\.org website\.
1. You can check the systemd or udev versions on RPM\-based systems with the following command:
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/sriov-networking.md |
94126f50fe75-2 | 1. You can check the systemd or udev versions on RPM\-based systems with the following command:
```
[ec2-user ~]$ rpm -qa | grep -e '^systemd-[0-9]\+\|^udev-[0-9]\+'
systemd-208-11.el7_0.2.x86_64
```
In the above Red Hat Enterprise Linux 7 example, the systemd version is 208, so predictable network interface names must be disabled\.
1. Disable predictable network interface names by adding the `net.ifnames=0` option to the `GRUB_CMDLINE_LINUX` line in `/etc/default/grub`\.
```
[ec2-user ~]$ sudo sed -i '/^GRUB\_CMDLINE\_LINUX/s/\"$/\ net\.ifnames\=0\"/' /etc/default/grub
```
1. Rebuild the grub configuration file\.
```
[ec2-user ~]$ sudo grub2-mkconfig -o /boot/grub2/grub.cfg
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/sriov-networking.md |
94126f50fe75-3 | ```
1. \[EBS\-backed instance\] 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\.
\[Instance store\-backed instance\] You can't stop the instance to modify the attribute\. Instead, proceed to this procedure: [To enable enhanced networking \(instance store–backed instances\)](#other-linux-enhanced-networking-instance-store)\.
1. From your local computer, enable the enhanced networking attribute using one of the following commands:
+ [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 --sriov-net-support simple
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/sriov-networking.md |
94126f50fe75-4 | aws ec2 modify-instance-attribute --instance-id instance_id --sriov-net-support simple
```
+ [Edit\-EC2InstanceAttribute](https://docs.aws.amazon.com/powershell/latest/reference/items/Edit-EC2InstanceAttribute.html) \(AWS Tools for Windows PowerShell\)
```
Edit-EC2InstanceAttribute -InstanceId instance_id -SriovNetSupport "simple"
```
1. \(Optional\) Create an AMI from the instance, as described in [Creating an Amazon EBS\-backed Linux AMI](creating-an-ami-ebs.md) \. The AMI inherits the enhanced networking attribute from the instance\. Therefore, you can use this AMI to launch another instance with enhanced networking enabled by default\.
**Important**
If your instance operating system contains an `/etc/udev/rules.d/70-persistent-net.rules` file, you must delete it before creating the AMI\. This file contains the MAC address for the Ethernet adapter of the original instance\. If another instance boots with this file, the operating system will be unable to find the device and `eth0` might fail, causing boot issues\. This file is regenerated at the next boot cycle, and any instances launched from the AMI create their own version of the file\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/sriov-networking.md |
94126f50fe75-5 | 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\.
1. \(Optional\) Connect to your instance and verify that the module is installed\.<a name="other-linux-enhanced-networking-instance-store"></a>
**To enable enhanced networking \(instance store–backed instances\)**
Follow the previous procedure until the step where you stop the instance\. Create a new AMI as described in [Creating an instance store\-backed Linux AMI](creating-an-ami-instance-store.md), making sure to enable the enhanced networking 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 --sriov-net-support simple ...
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/sriov-networking.md |
94126f50fe75-6 | ```
aws ec2 register-image --sriov-net-support simple ...
```
+ [Register\-EC2Image](https://docs.aws.amazon.com/powershell/latest/reference/items/Register-EC2Image.html) \(AWS Tools for Windows PowerShell\)
```
Register-EC2Image -SriovNetSupport "simple" ...
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/sriov-networking.md |
a68d2e1db1a0-0 | If you lose connectivity while enabling enhanced networking, the `ixgbevf` module might be incompatible with the kernel\. Try installing the version of the `ixgbevf` module included with the distribution of Linux for your instance\.
If you enable enhanced networking for a PV instance or AMI, this can make your instance unreachable\.
For more information, see [How do I enable and configure enhanced networking on my EC2 instances?](http://aws.amazon.com/premiumsupport/knowledge-center/enable-configure-enhanced-networking/)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/sriov-networking.md |
8af2db6daddd-0 | When you purchase a Reserved Instance, you determine the scope of the Reserved Instance\. The scope is either regional or zonal\.
+ **Regional**: When you purchase a Reserved Instance for a Region, it's referred to as a *regional* Reserved Instance\.
+ **Zonal**: When you purchase a Reserved Instance for a specific Availability Zone, it's referred to as a *zonal* Reserved Instance\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/reserved-instances-scope.md |
03e89b72cb16-0 | The following table highlights some key differences between regional Reserved Instances and zonal Reserved Instances:
| | Regional Reserved Instances | Zonal Reserved Instances |
| --- | --- | --- |
| Availability Zone flexibility | The Reserved Instance discount applies to instance usage in any Availability Zone in the specified Region\. | No Availability Zone flexibility—the Reserved Instance discount applies to instance usage in the specified Availability Zone only\. |
| Capacity reservation | No capacity reservation—a regional Reserved Instance does not provide a capacity reservation\. | A zonal Reserved Instance provides a capacity reservation in the specified Availability Zone\. |
| Instance size flexibility | The Reserved Instance discount applies to instance usage within the instance family, regardless of size\. Only supported on Amazon Linux/Unix Reserved Instances with default tenancy\. For more information, see [Instance size flexibility determined by normalization factor](apply_ri.md#ri-normalization-factor)\. | No instance size flexibility—the Reserved Instance discount applies to instance usage for the specified instance type and size only\. |
For more information and examples, see [How Reserved Instances are applied](apply_ri.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/reserved-instances-scope.md |
c66f0c0d6b56-0 | On\-Demand Capacity Reservations enable you to reserve capacity for your Amazon EC2 instances in a specific Availability Zone for any duration\. This gives you the ability to create and manage Capacity Reservations independently from the billing discounts offered by Savings Plans or regional Reserved Instances\. By creating Capacity Reservations, you ensure that you always have access to EC2 capacity when you need it, for as long as you need it\. You can create Capacity Reservations at any time, without entering into a one\-year or three\-year term commitment, and the capacity is available immediately\. When you no longer need it, cancel the Capacity Reservation to stop incurring charges\.
When you create a Capacity Reservation, you specify:
+ The Availability Zone in which to reserve the capacity
+ The number of instances for which to reserve capacity
+ The instance attributes, including the instance type, tenancy, and platform/OS
Capacity Reservations can only be used by instances that match their attributes\. By default, they are automatically used by running instances that match the attributes\. If you don't have any running instances that match the attributes of the Capacity Reservation, it remains unused until you launch an instance with matching attributes\.
In addition, you can use Savings Plans and regional Reserved Instances with your Capacity Reservations to benefit from billing discounts\. AWS automatically applies your discount when the attributes of a Capacity Reservation match the attributes of a Savings Plan or regional Reserved Instance\. For more information, see [Billing discounts](capacity-reservations-pricing-billing.md#capacity-reservations-discounts)\.
**Topics**
+ [Differences between Capacity Reservations, Reserved Instances, and Savings Plans](#capacity-reservations-differences) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-capacity-reservations.md |
c66f0c0d6b56-1 | **Topics**
+ [Differences between Capacity Reservations, Reserved Instances, and Savings Plans](#capacity-reservations-differences)
+ [Supported platforms](#capacity-reservations-platforms)
+ [Capacity Reservation limits](#capacity-reservations-limits)
+ [Capacity Reservation limitations and restrictions](#capacity-reservations-limitations)
+ [Capacity Reservation pricing and billing](capacity-reservations-pricing-billing.md)
+ [Working with Capacity Reservations](capacity-reservations-using.md)
+ [Working with shared Capacity Reservations](capacity-reservation-sharing.md)
+ [CloudWatch metrics for On\-Demand Capacity Reservations](capacity-reservation-cw-metrics.md) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-capacity-reservations.md |
ec7991d13818-0 | The following table highlights key differences between Capacity Reservations, Reserved Instances, and Savings Plans:
| | Capacity Reservations | Zonal Reserved Instances | Regional Reserved Instances | Savings Plans |
| --- | --- | --- | --- | --- |
| Term | No commitment required\. Can be created and canceled as needed\. | Require fixed one\-year or three\-year commitment |
| Capacity benefit | Capacity reserved in a specific Availability Zone\. | Do not reserve capacity in an Availability Zone\. |
| Billing discount | No billing discount\. Instances launched into a Capacity Reservation are charged at their standard On\-Demand rates\. However, you can use Savings Plans or regional Reserved Instances with Capacity Reservations to get a billing discount\. Zonal Reserved Instances do not apply to Capacity Reservations\. | Provide billing discounts |
| Instance Limits | Limited to your On\-Demand Instance limits per Region\. | Limited to 20 per Availability Zone\. A limit increase can be requested\. | Limited to 20 per Region\. A limit increase can be requested\. | No limits\. |
For more information, see the following:
+ [Reserved Instances](ec2-reserved-instances.md)
+ [Savings Plans User Guide](https://docs.aws.amazon.com/savingsplans/latest/userguide/) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-capacity-reservations.md |
6e19f9e09a76-0 | You must create the Capacity Reservation with the correct platform to ensure that it properly matches with your instances\. Capacity Reservations support the following platforms:
+ Linux/UNIX
+ Linux with SQL Server Standard
+ Linux with SQL Server Web
+ Linux with SQL Server Enterprise
+ Red Hat Enterprise Linux
+ SUSE Linux
For more information about the supported Windows platforms, see [ Supported platforms](https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/ec2-capacity-reservations.html#capacity-reservations-platforms) in the *Amazon EC2 User Guide for Windows Instances*\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-capacity-reservations.md |
ceb9ba3eefc9-0 | The number of instances for which you are allowed to reserve capacity is based on your account's On\-Demand Instance limit\. You can reserve capacity for as many instances as that limit allows, minus the number of instances that are already running\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-capacity-reservations.md |
5e8707216d0b-0 | Before you create Capacity Reservations, take note of the following limitations and restrictions\.
+ Active and unused Capacity Reservations count toward your On\-Demand Instance limits
+ Capacity Reservations are not transferable from one AWS account to another\. However, you can share Capacity Reservations with other AWS accounts\. For more information, see [Working with shared Capacity Reservations](capacity-reservation-sharing.md)\.
+ Zonal Reserved Instance billing discounts do not apply to Capacity Reservations
+ Capacity Reservations can't be created in placement groups
+ Capacity Reservations can't be used with Dedicated Hosts
+ Capacity Reservations can't be used with Local Zones | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-capacity-reservations.md |
7b543a5db08e-0 | Amazon EC2 sends metrics to Amazon CloudWatch\. You can use the AWS Management Console, the AWS CLI, or an API to list the metrics that Amazon EC2 sends to CloudWatch\. By default, each data point covers the 5 minutes that follow the start time of activity for the instance\. If you've enabled detailed monitoring, each data point covers the next minute of activity from the start time\.
For information about getting the statistics for these metrics, see [Get statistics for metrics for your instances](monitoring_get_statistics.md)\.
**Topics**
+ [Instance metrics](#ec2-cloudwatch-metrics)
+ [CPU credit metrics](#cpu-credit-metrics)
+ [Amazon EBS metrics for Nitro\-based instances](#ebs-metrics-nitro)
+ [Status check metrics](#status-check-metrics)
+ [Traffic mirroring metrics](#traffic-mirroring-metrics)
+ [Amazon EC2 metric dimensions](#ec2-cloudwatch-dimensions)
+ [Amazon EC2 usage metrics](#service-quota-metrics)
+ [Listing metrics using the console](#list-ec2-metrics-console)
+ [Listing metrics using the AWS CLI](#list-ec2-metrics-cli) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/viewing_metrics_with_cloudwatch.md |
97b043f07f10-0 | The `AWS/EC2` namespace includes the following instance metrics\.
| Metric | Description |
| --- | --- |
| CPUUtilization | The percentage of allocated EC2 compute units that are currently in use on the instance\. This metric identifies the processing power required to run an application on a selected instance\. Depending on the instance type, tools in your operating system can show a lower percentage than CloudWatch when the instance is not allocated a full processor core\. Units: Percent |
| DiskReadOps | Completed read operations from all instance store volumes available to the instance in a specified period of time\. To calculate the average I/O operations per second \(IOPS\) for the period, divide the total operations in the period by the number of seconds in that period\. If there are no instance store volumes, either the value is 0 or the metric is not reported\. Units: Count |
| DiskWriteOps | Completed write operations to all instance store volumes available to the instance in a specified period of time\. To calculate the average I/O operations per second \(IOPS\) for the period, divide the total operations in the period by the number of seconds in that period\. If there are no instance store volumes, either the value is 0 or the metric is not reported\. Units: Count | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/viewing_metrics_with_cloudwatch.md |
97b043f07f10-1 | | DiskReadBytes | Bytes read from all instance store volumes available to the instance\. This metric is used to determine the volume of the data the application reads from the hard disk of the instance\. This can be used to determine the speed of the application\. The number reported is the number of bytes received during the period\. If you are using basic \(five\-minute\) monitoring, you can divide this number by 300 to find Bytes/second\. If you have detailed \(one\-minute\) monitoring, divide it by 60\. If there are no instance store volumes, either the value is 0 or the metric is not reported\. Units: Bytes |
| DiskWriteBytes | Bytes written to all instance store volumes available to the instance\. This metric is used to determine the volume of the data the application writes onto the hard disk of the instance\. This can be used to determine the speed of the application\. The number reported is the number of bytes received during the period\. If you are using basic \(five\-minute\) monitoring, you can divide this number by 300 to find Bytes/second\. If you have detailed \(one\-minute\) monitoring, divide it by 60\. If there are no instance store volumes, either the value is 0 or the metric is not reported\. Units: Bytes |
| NetworkIn | The number of bytes received on all network interfaces by the instance\. This metric identifies the volume of incoming network traffic to a single instance\. The number reported is the number of bytes received during the period\. If you are using basic \(five\-minute\) monitoring, you can divide this number by 300 to find Bytes/second\. If you have detailed \(one\-minute\) monitoring, divide it by 60\. Units: Bytes | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/viewing_metrics_with_cloudwatch.md |
97b043f07f10-2 | | NetworkOut | The number of bytes sent out on all network interfaces by the instance\. This metric identifies the volume of outgoing network traffic from a single instance\. The number reported is the number of bytes sent during the period\. If you are using basic \(five\-minute\) monitoring, you can divide this number by 300 to find Bytes/second\. If you have detailed \(one\-minute\) monitoring, divide it by 60\. Units: Bytes |
| NetworkPacketsIn | The number of packets received on all network interfaces by the instance\. This metric identifies the volume of incoming traffic in terms of the number of packets on a single instance\. This metric is available for basic monitoring only\. Units: Count Statistics: Minimum, Maximum, Average |
| NetworkPacketsOut | The number of packets sent out on all network interfaces by the instance\. This metric identifies the volume of outgoing traffic in terms of the number of packets on a single instance\. This metric is available for basic monitoring only\. Units: Count Statistics: Minimum, Maximum, Average |
| MetadataNoToken | The number of times the instance metadata service was succesfully accessed using a method that does not use a token\. This metric is used to determine if there are any processes accessing instance metadata that are using Instance Metadata Service Version 1, which does not use a token\. If all requests use token\-backed sessions, i\.e\., Instance Metadata Service Version 2, the value is 0\. For more information, see [Transitioning to using Instance Metadata Service Version 2](configuring-instance-metadata-service.md#instance-metadata-transition-to-version-2)\. Units: Count | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/viewing_metrics_with_cloudwatch.md |
ea0a1e9fa37c-0 | The `AWS/EC2` namespace includes the following CPU credit metrics for your [burstable performance instances](burstable-performance-instances.md)\.
| Metric | Description |
| --- | --- |
| CPUCreditUsage | The number of CPU credits spent by the instance for CPU utilization\. One CPU credit equals one vCPU running at 100% utilization for one minute or an equivalent combination of vCPUs, utilization, and time \(for example, one vCPU running at 50% utilization for two minutes or two vCPUs running at 25% utilization for two minutes\)\. CPU credit metrics are available at a five\-minute frequency only\. If you specify a period greater than five minutes, use the `Sum` statistic instead of the `Average` statistic\. Units: Credits \(vCPU\-minutes\) | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/viewing_metrics_with_cloudwatch.md |
ea0a1e9fa37c-1 | | CPUCreditBalance | The number of earned CPU credits that an instance has accrued since it was launched or started\. For T2 Standard, the `CPUCreditBalance` also includes the number of launch credits that have been accrued\. Credits are accrued in the credit balance after they are earned, and removed from the credit balance when they are spent\. The credit balance has a maximum limit, determined by the instance size\. After the limit is reached, any new credits that are earned are discarded\. For T2 Standard, launch credits do not count towards the limit\. The credits in the `CPUCreditBalance` are available for the instance to spend to burst beyond its baseline CPU utilization\. When an instance is running, credits in the `CPUCreditBalance` do not expire\. When a T3 or T3a instance stops, the `CPUCreditBalance` value persists for seven days\. Thereafter, all accrued credits are lost\. When a T2 instance stops, the `CPUCreditBalance` value does not persist, and all accrued credits are lost\. CPU credit metrics are available at a five\-minute frequency only\. Units: Credits \(vCPU\-minutes\) |
| CPUSurplusCreditBalance | The number of surplus credits that have been spent by an `unlimited` instance when its `CPUCreditBalance` value is zero\. The `CPUSurplusCreditBalance` value is paid down by earned CPU credits\. If the number of surplus credits exceeds the maximum number of credits that the instance can earn in a 24\-hour period, the spent surplus credits above the maximum incur an additional charge\. CPU credit metrics are available at a five\-minute frequency only\. Units: Credits \(vCPU\-minutes\) | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/viewing_metrics_with_cloudwatch.md |
ea0a1e9fa37c-2 | | CPUSurplusCreditsCharged | The number of spent surplus credits that are not paid down by earned CPU credits, and which thus incur an additional charge\. Spent surplus credits are charged when any of the following occurs: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/viewing_metrics_with_cloudwatch.html) CPU credit metrics are available at a five\-minute frequency only\. Units: Credits \(vCPU\-minutes\) | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/viewing_metrics_with_cloudwatch.md |
0e8ef7783e26-0 | The `AWS/EC2` namespace includes the following Amazon EBS metrics for the Nitro\-based instances that are not bare metal instances\. For the list of Nitro\-based instance types, see [Instances built on the Nitro System](instance-types.md#ec2-nitro-instances)\.
Metric values for Nitro\-based instances will always be integers \(whole numbers\), whereas values for Xen\-based instances support decimals\. Therefore, low instance CPU utilization on Nitro\-based instances may appear to be rounded down to 0\.
| Metric | Description |
| --- | --- |
| EBSReadOps | Completed read operations from all Amazon EBS volumes attached to the instance in a specified period of time\. To calculate the average read I/O operations per second \(Read IOPS\) for the period, divide the total operations in the period by the number of seconds in that period\. If you are using basic \(five\-minute\) monitoring, you can divide this number by 300 to calculate the Read IOPS\. If you have detailed \(one\-minute\) monitoring, divide it by 60\. Unit: Count | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/viewing_metrics_with_cloudwatch.md |
0e8ef7783e26-1 | | EBSWriteOps | Completed write operations to all EBS volumes attached to the instance in a specified period of time\. To calculate the average write I/O operations per second \(Write IOPS\) for the period, divide the total operations in the period by the number of seconds in that period\. If you are using basic \(five\-minute\) monitoring, you can divide this number by 300 to calculate the Write IOPS\. If you have detailed \(one\-minute\) monitoring, divide it by 60\. Unit: Count |
| EBSReadBytes | Bytes read from all EBS volumes attached to the instance in a specified period of time\. The number reported is the number of bytes read during the period\. If you are using basic \(five\-minute\) monitoring, you can divide this number by 300 to find Read Bytes/second\. If you have detailed \(one\-minute\) monitoring, divide it by 60\. Unit: Bytes |
| EBSWriteBytes | Bytes written to all EBS volumes attached to the instance in a specified period of time\. The number reported is the number of bytes written during the period\. If you are using basic \(five\-minute\) monitoring, you can divide this number by 300 to find Write Bytes/second\. If you have detailed \(one\-minute\) monitoring, divide it by 60\. Unit: Bytes |
| EBSIOBalance% | Available only for the smaller instance sizes\. Provides information about the percentage of I/O credits remaining in the burst bucket\. This metric is available for basic monitoring only\. The `Sum` statistic is not applicable to this metric\. Unit: Percent | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/viewing_metrics_with_cloudwatch.md |
0e8ef7783e26-2 | | EBSByteBalance% | Available only for the smaller instance sizes\. Provides information about the percentage of throughput credits remaining in the burst bucket\. This metric is available for basic monitoring only\. The `Sum` statistic is not applicable to this metric\. Unit: Percent |
For information about the metrics provided for your EBS volumes, see [Amazon EBS metrics](using_cloudwatch_ebs.md#ebs-metrics)\. For information about the metrics provided for your Spot fleets, see [CloudWatch metrics for Spot Fleet](spot-fleet-cloudwatch-metrics.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/viewing_metrics_with_cloudwatch.md |
c1fae91923e4-0 | The `AWS/EC2` namespace includes the following status check metrics\. By default, status check metrics are available at a 1\-minute frequency at no charge\. For a newly\-launched instance, status check metric data is only available after the instance has completed the initialization state \(within a few minutes of the instance entering the running state\)\. For more information about EC2 status checks, see [Status checks for your instances](monitoring-system-instance-status-check.md)\.
| Metric | Description |
| --- | --- |
| StatusCheckFailed | Reports whether the instance has passed both the instance status check and the system status check in the last minute\. This metric can be either 0 \(passed\) or 1 \(failed\)\. By default, this metric is available at a 1\-minute frequency at no charge\. Units: Count |
| StatusCheckFailed\_Instance | Reports whether the instance has passed the instance status check in the last minute\. This metric can be either 0 \(passed\) or 1 \(failed\)\. By default, this metric is available at a 1\-minute frequency at no charge\. Units: Count |
| StatusCheckFailed\_System | Reports whether the instance has passed the system status check in the last minute\. This metric can be either 0 \(passed\) or 1 \(failed\)\. By default, this metric is available at a 1\-minute frequency at no charge\. Units: Count | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/viewing_metrics_with_cloudwatch.md |
a62fd28263a9-0 | The `AWS/EC2` namespace includes metrics for mirrored traffic\. For more information, see [Monitoring mirrored traffic using Amazon CloudWatch](https://docs.aws.amazon.com/vpc/latest/mirroring/traffic-mirror-cloudwatch.html) in the *Amazon VPC Traffic Mirroring Guide*\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/viewing_metrics_with_cloudwatch.md |
649bb6eea497-0 | You can use the following dimensions to refine the metrics listed in the previous tables\.
| Dimension | Description |
| --- | --- |
| AutoScalingGroupName | This dimension filters the data you request for all instances in a specified capacity group\. An *Auto Scaling group* is a collection of instances you define if you're using Auto Scaling\. This dimension is available only for Amazon EC2 metrics when the instances are in such an Auto Scaling group\. Available for instances with Detailed or Basic Monitoring enabled\. |
| ImageId | This dimension filters the data you request for all instances running this Amazon EC2 Amazon Machine Image \(AMI\)\. Available for instances with Detailed Monitoring enabled\. |
| InstanceId | This dimension filters the data you request for the identified instance only\. This helps you pinpoint an exact instance from which to monitor data\. |
| InstanceType | This dimension filters the data you request for all instances running with this specified instance type\. This helps you categorize your data by the type of instance running\. For example, you might compare data from an m1\.small instance and an m1\.large instance to determine which has the better business value for your application\. Available for instances with Detailed Monitoring enabled\. | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/viewing_metrics_with_cloudwatch.md |
497767f03969-0 | You can use CloudWatch usage metrics to provide visibility into your account's usage of resources\. Use these metrics to visualize your current service usage on CloudWatch graphs and dashboards\.
Amazon EC2 usage metrics correspond to AWS service quotas\. You can configure alarms that alert you when your usage approaches a service quota\. For more information about CloudWatch integration with service quotas, see [Service Quotas Integration and Usage Metrics](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-Service-Quota-Integration.html)\.
Amazon EC2 publishes the following metrics in the `AWS/Usage` namespace\.
| Metric | Description |
| --- | --- |
| `ResourceCount` | The number of the specified resources running in your account\. The resources are defined by the dimensions associated with the metric\. The most useful statistic for this metric is `MAXIMUM`, which represents the maximum number of resources used during the 1\-minute period\. |
The following dimensions are used to refine the usage metrics that are published by Amazon EC2\.
| Dimension | Description |
| --- | --- |
| Service | The name of the AWS service containing the resource\. For Amazon EC2 usage metrics, the value for this dimension is `EC2`\. |
| Type | The type of entity that is being reported\. Currently, the only valid value for Amazon EC2 usage metrics is `Resource`\. | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/viewing_metrics_with_cloudwatch.md |
497767f03969-1 | | Type | The type of entity that is being reported\. Currently, the only valid value for Amazon EC2 usage metrics is `Resource`\. |
| Resource | The type of resource that is running\. Currently, the only valid value for Amazon EC2 usage metrics is `vCPU`, which returns information on instances that are running\. |
| Class | The class of resource being tracked\. For Amazon EC2 usage metrics with `vCPU` as the value of the `Resource` dimension, the valid values are `Standard/OnDemand`, `F/OnDemand`, `G/OnDemand`, `Inf/OnDemand`, `P/OnDemand`, and `X/OnDemand`\. The values for this dimension define the first letter of the instance types that are reported by the metric\. For example, `Standard/OnDemand` returns information about all running instances with types that start with A, C, D, H, I, M, R, T, and Z, and `G/OnDemand` returns information about all running instances with types that start with G\. | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/viewing_metrics_with_cloudwatch.md |
a6f4d5e6416f-0 | Metrics are grouped first by namespace, and then by the various dimension combinations within each namespace\. For example, you can view all metrics provided by Amazon EC2, or metrics grouped by instance ID, instance type, image \(AMI\) ID, or Auto Scaling group\.
**To view available metrics by category \(console\)**
1. Open the CloudWatch console at [https://console\.aws\.amazon\.com/cloudwatch/](https://console.aws.amazon.com/cloudwatch/)\.
1. In the navigation pane, choose **Metrics**\.
1. Choose the **EC2** metric namespace\.
![\[Choose the EC2 metrics namespace\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/metric_view_categories.png)
1. Select a metric dimension \(for example, **Per\-Instance Metrics**\)\.
![\[View the metric dimensions for Amazon EC2\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/metric_view_metric_category.png)
1. To sort the metrics, use the column heading\. To graph a metric, select the check box next to the metric\. To filter by resource, choose the resource ID and then choose **Add to search**\. To filter by metric, choose the metric name and then choose **Add to search**\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/viewing_metrics_with_cloudwatch.md |
a6f4d5e6416f-1 | ![\[View the metrics for Amazon EC2\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/metric_view_metrics.png) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/viewing_metrics_with_cloudwatch.md |
9f273fe4764e-0 | Use the [list\-metrics](https://docs.aws.amazon.com/cli/latest/reference/cloudwatch/list-metrics.html) command to list the CloudWatch metrics for your instances\.
**To list all the available metrics for Amazon EC2 \(AWS CLI\)**
The following example specifies the `AWS/EC2` namespace to view all the metrics for Amazon EC2\.
```
aws cloudwatch list-metrics --namespace AWS/EC2
```
The following is example output:
```
{
"Metrics": [
{
"Namespace": "AWS/EC2",
"Dimensions": [
{
"Name": "InstanceId",
"Value": "i-1234567890abcdef0"
}
],
"MetricName": "NetworkOut"
},
{
"Namespace": "AWS/EC2",
"Dimensions": [
{
"Name": "InstanceId",
"Value": "i-1234567890abcdef0"
}
],
"MetricName": "CPUUtilization"
},
{ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/viewing_metrics_with_cloudwatch.md |
9f273fe4764e-1 | }
],
"MetricName": "CPUUtilization"
},
{
"Namespace": "AWS/EC2",
"Dimensions": [
{
"Name": "InstanceId",
"Value": "i-1234567890abcdef0"
}
],
"MetricName": "NetworkIn"
},
...
]
}
```
**To list all the available metrics for an instance \(AWS CLI\)**
The following example specifies the `AWS/EC2` namespace and the `InstanceId` dimension to view the results for the specified instance only\.
```
aws cloudwatch list-metrics --namespace AWS/EC2 --dimensions Name=InstanceId,Value=i-1234567890abcdef0
```
**To list a metric across all instances \(AWS CLI\)**
The following example specifies the `AWS/EC2` namespace and a metric name to view the results for the specified metric only\.
```
aws cloudwatch list-metrics --namespace AWS/EC2 --metric-name CPUUtilization
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/viewing_metrics_with_cloudwatch.md |
011cd5fc187a-0 | Some resources can be used in all regions \(global\), and some resources are specific to the region or Availability Zone in which they reside\.
| Resource | Type | Description |
| --- | --- | --- |
| AWS account | Global | You can use the same AWS account in all regions\. |
| Key pairs | Global or Regional | The key pairs that you create using Amazon EC2 are tied to the Region where you created them\. You can create your own RSA key pair and upload it to the region in which you want to use it; therefore, you can make your key pair globally available by uploading it to each Region\. For more information, see [Amazon EC2 key pairs and Linux instances](ec2-key-pairs.md)\. |
| Amazon EC2 resource identifiers | Regional | Each resource identifier, such as an AMI ID, instance ID, EBS volume ID, or EBS snapshot ID, is tied to its Region and can be used only in the Region where you created the resource\. |
| User\-supplied resource names | Regional | Each resource name, such as a security group name or key pair name, is tied to its region and can be used only in the Region where you created the resource\. Although you can create resources with the same name in multiple regions, they aren't related to each other\. |
| AMIs | Regional | An AMI is tied to the Region where its files are located within Amazon S3\. You can copy an AMI from one Region to another\. For more information, see [Copying an AMI](CopyingAMIs.md)\. | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/resources.md |
011cd5fc187a-1 | | Elastic IP addresses | Regional | An Elastic IP address is tied to a Region and can be associated only with an instance in the same Region\. |
| Security groups | Regional | A security group is tied to a Region and can be assigned only to instances in the same Region\. You can't enable an instance to communicate with an instance outside its Region using security group rules\. Traffic from an instance in another Region is seen as WAN bandwidth\. |
| EBS snapshots | Regional | An EBS snapshot is tied to its Region and can only be used to create volumes in the same Region\. You can copy a snapshot from one Region to another\. For more information, see [Copying an Amazon EBS snapshot](ebs-copy-snapshot.md)\. |
| EBS volumes | Availability Zone | An Amazon EBS volume is tied to its Availability Zone and can be attached only to instances in the same Availability Zone\. |
| Instances | Availability Zone | An instance is tied to the Availability Zones in which you launched it\. However, its instance ID is tied to the Region\. | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/resources.md |
7435e92c6987-0 | Several factors, including I/O characteristics and the configuration of your instances and volumes, can affect the performance of Amazon EBS\. Customers who follow the guidance on our Amazon EBS and Amazon EC2 product detail pages typically achieve good performance out of the box\. However, there are some cases where you may need to do some tuning in order to achieve peak performance on the platform\. This topic discusses general best practices as well as performance tuning that is specific to certain use cases\. We recommend that you tune performance with information from your actual workload, in addition to benchmarking, to determine your optimal configuration\. After you learn the basics of working with EBS volumes, it's a good idea to look at the I/O performance you require and at your options for increasing Amazon EBS performance to meet those requirements\.
AWS updates to the performance of EBS volume types might not immediately take effect on your existing volumes\. To see full performance on an older volume, you might first need to perform a `ModifyVolume` action on it\. For more information, see [Modifying the Size, IOPS, or Type of an EBS Volume on Linux](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-modify-volume.html)\.
**Topics**
+ [Amazon EBS performance tips](#tips)
+ [I/O characteristics and monitoring](ebs-io-characteristics.md)
+ [Initializing Amazon EBS volumes](ebs-initialize.md)
+ [RAID Configuration on Linux](raid-config.md)
+ [Benchmark EBS volumes](benchmark_procedures.md) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/EBSPerformance.md |
bdd1c7b97f57-0 | These tips represent best practices for getting optimal performance from your EBS volumes in a variety of user scenarios\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/EBSPerformance.md |
8110200365d1-0 | On instances without support for EBS\-optimized throughput, network traffic can contend with traffic between your instance and your EBS volumes; on EBS\-optimized instances, the two types of traffic are kept separate\. Some EBS\-optimized instance configurations incur an extra cost \(such as C3, R3, and M3\), while others are always EBS\-optimized at no extra cost \(such as M4, C4, C5, and D2\)\. For more information, see [Amazon EBS–optimized | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/EBSPerformance.md |
8110200365d1-1 | For more information, see [Amazon EBS–optimized instances](ebs-optimized.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/EBSPerformance.md |
fafe798fdd12-0 | When you measure the performance of your EBS volumes, it is important to understand the units of measure involved and how performance is calculated\. For more information, see [I/O characteristics and monitoring](ebs-io-characteristics.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/EBSPerformance.md |
Subsets and Splits