id
stringlengths 14
16
| text
stringlengths 1
2.43k
| source
stringlengths 99
229
|
|---|---|---|
51f625d0f4d6-2 | ```
**Example: Create a volume and apply a tag**
The following [create\-volume](https://docs.aws.amazon.com/cli/latest/reference/ec2/create-volume.html) command creates a volume and applies two tags: **purpose=production** and **cost\-center=cc123**\.
```
aws ec2 create-volume \
--availability-zone us-east-1a \
--volume-type gp2 \
--size 80 \
--tag-specifications 'ResourceType=volume,Tags=[{Key=purpose,Value=production},{Key=cost-center,Value=cc123}]'
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/Using_Tags.md |
a688f5ad81b9-0 | The following examples demonstrate how to add tags to an existing resource using the [create\-tags](https://docs.aws.amazon.com/cli/latest/reference/ec2/create-tags.html) command\.
**Example: Add a tag to a resource**
The following command adds the tag **Stack=production** to the specified image, or overwrites an existing tag for the AMI where the tag key is **Stack**\. If the command succeeds, no output is returned\.
```
aws ec2 create-tags \
--resources ami-78a54011 \
--tags Key=Stack,Value=production
```
**Example: Add tags to multiple resources**
This example adds \(or overwrites\) two tags for an AMI and an instance\. One of the tags contains just a key \(**webserver**\), with no value \(we set the value to an empty string\)\. The other tag consists of a key \(**stack**\) and value \(**Production**\)\. If the command succeeds, no output is returned\.
```
aws ec2 create-tags \
--resources ami-1a2b3c4d i-1234567890abcdef0 \
--tags Key=webserver,Value= Key=stack,Value=Production
```
**Example: Add tags with special characters** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/Using_Tags.md |
a688f5ad81b9-1 | ```
**Example: Add tags with special characters**
This example adds the tag **\[Group\]=test** to an instance\. The square brackets \(**\[** and **\]**\) are special characters, which must be escaped\.
If you are using Linux or OS X, to escape the special characters, enclose the element with the special character with double quotes \(**"**\), and then enclose the entire key and value structure with single quotes \(**'**\)\.
```
aws ec2 create-tags \
--resources i-1234567890abcdef0 \
--tags 'Key="[Group]",Value=test'
```
If you are using Windows, to escape the special characters, enclose the element that has special characters with double quotes \("\), and then precede each double quote character with a backslash \(**\\**\) as follows:
```
aws ec2 create-tags ^
--resources i-1234567890abcdef0 ^
--tags Key=\"[Group]\",Value=test
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/Using_Tags.md |
a688f5ad81b9-2 | --tags Key=\"[Group]\",Value=test
```
If you are using Windows PowerShell, to escape the special characters, enclose the value that has special characters with double quotes \(**"**\), precede each double quote character with a backslash \(**\\**\), and then enclose the entire key and value structure with single quotes \(**'**\) as follows:
```
aws ec2 create-tags `
--resources i-1234567890abcdef0 `
--tags 'Key=\"[Group]\",Value=test'
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/Using_Tags.md |
e1a448cacf2a-0 | The following examples show you how to use filters with the [describe\-instances](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-instances.html) to view instances with specific tags\. All EC2 describe commands use this syntax to filter by tag across a single resource type\. Alternatively, you can use the [describe\-tags](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-tags.html) command to filter by tag across EC2 resource types\.
**Example: Describe instances with the specified tag key**
The following command describes the instances with a **Stack** tag, regardless of the value of the tag\.
```
aws ec2 describe-instances \
--filters Name=tag-key,Values=Stack
```
**Example: Describe instances with the specified tag**
The following command describes the instances with the tag **Stack=production**\.
```
aws ec2 describe-instances \
--filters Name=tag:Stack,Values=production
```
**Example: Describe instances with the specified tag value**
The following command describes the instances with a tag with the value **production**, regardless of the tag key\.
```
aws ec2 describe-instances \
--filters Name=tag-value,Values=production
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/Using_Tags.md |
e1a448cacf2a-1 | ```
aws ec2 describe-instances \
--filters Name=tag-value,Values=production
```
**Example: Describe all EC2 resources with the specified tag**
The following command describes all EC2 resources with the tag **Stack=Test**\.
```
aws ec2 describe-tags \
--filters Name=key,Values=Stack Name=value,Values=Test
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/Using_Tags.md |
9286e1527ac4-0 | The following examples add the tag **Stack=Production** to the [AWS::EC2::Instance](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ec2-instance.html) resource\.
**Example: YAML**
```
TagSpecifications:
- ResourceType: "instance"
Tags:
- Key: "Stack"
Value: "Production"
```
**Example: JSON**
```
"TagSpecifications": [
{
"ResourceType": "instance",
"Tags": [
{
"Key": "Stack",
"Value": "Production"
}
]
}
]
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/Using_Tags.md |
ad6dca49046e-0 | To launch a Spot Instance, either you create a *Spot Instance request*, or Amazon EC2 creates a Spot Instance request on your behalf\. The Spot Instance launches when the Spot Instance request is fulfilled\.
You can launch a Spot Instance in the following ways:
+ You can create a Spot Instance request\. For more information, see [Creating a Spot Instance request](spot-requests.md#using-spot-instances-request)\.
+ You can create a Spot Fleet request, in which you specify the desired number of Spot Instances\. Amazon EC2 creates a Spot Instance request on your behalf for every Spot Instance that is specified in the Spot Fleet request\. For more information, see [Creating a Spot Fleet request](spot-fleet-requests.md#create-spot-fleet)\.
+ You can create an EC2 Fleet, in which you specify the desired number of Spot Instances\. Amazon EC2 creates a Spot Instance request on your behalf for every Spot Instance that is specified in the EC2 Fleet\. For more information, see [Creating an EC2 Fleet](manage-ec2-fleet.md#create-ec2-fleet)\.
The Spot Instance request must include the maximum price that you're willing to pay per hour per instance\. If you don't specify a price, the price defaults to the On\-Demand price\. The request can include other constraints such as the instance type and Availability Zone\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/how-spot-instances-work.md |
ad6dca49046e-1 | Your Spot Instance launches if the maximum price that you're willing to pay exceeds the Spot price, and if there is available capacity\. If the maximum price you're willing to pay is lower than the Spot price, then your instance does not launch\. However, because Amazon EC2 gradually adjusts the Spot price based on the long\-term supply of and demand for Spot Instances, the maximum price you're willing to pay might eventually exceed the Spot price, in which case your instance will launch\.
Your Spot Instance runs until you stop or terminate it, or until Amazon EC2 interrupts it \(known as a *Spot Instance interruption*\)\.
When you use Spot Instances, you must be prepared for interruptions\. Amazon EC2 can interrupt your Spot Instance when the Spot price exceeds your maximum price, when the demand for Spot Instances rises, or when the supply of Spot Instances decreases\. When Amazon EC2 interrupts a Spot Instance, it provides a Spot Instance interruption notice, which gives the instance a two\-minute warning before Amazon EC2 interrupts it\. You can't enable termination protection for Spot Instances\. For more information, see [Spot Instance interruptions](spot-interruptions.md)\.
You can stop, start, reboot, or terminate an Amazon EBS\-backed Spot Instance\. The Spot service can stop, terminate, or hibernate a Spot Instance when it interrupts it\.
**Topics**
+ [Launching Spot Instances in a launch group](#spot-launch-group)
+ [Launching Spot Instances in an Availability Zone group](#spot-az-group)
+ [Launching Spot Instances in a VPC](#concepts-spot-instances-vpcs) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/how-spot-instances-work.md |
f4bde39ea44a-0 | Specify a launch group in your Spot Instance request to tell Amazon EC2 to launch a set of Spot Instances only if it can launch them all\. In addition, if the Spot service must terminate one of the instances in a launch group \(for example, if the Spot price exceeds your maximum price\), it must terminate them all\. However, if you terminate one or more of the instances in a launch group, Amazon EC2 does not terminate the remaining instances in the launch group\.
Although this option can be useful, adding this constraint can decrease the chances that your Spot Instance request is fulfilled and increase the chances that your Spot Instances are terminated\. For example, your launch group includes instances in multiple Availability Zones\. If capacity in one of these Availability Zones decreases and is no longer available, then Amazon EC2 terminates all instances for the launch group\.
If you create another successful Spot Instance request that specifies the same \(existing\) launch group as an earlier successful request, then the new instances are added to the launch group\. Subsequently, if an instance in this launch group is terminated, all instances in the launch group are terminated, which includes instances launched by the first and second requests\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/how-spot-instances-work.md |
b9a1d455d1c3-0 | Specify an Availability Zone group in your Spot Instance request to tell the Spot service to launch a set of Spot Instances in the same Availability Zone\. Amazon EC2 need not interrupt all instances in an Availability Zone group at the same time\. If Amazon EC2 must interrupt one of the instances in an Availability Zone group, the others remain running\.
Although this option can be useful, adding this constraint can lower the chances that your Spot Instance request is fulfilled\.
If you specify an Availability Zone group but don't specify an Availability Zone in the Spot Instance request, the result depends on the network you specified\.
**Default VPC**
Amazon EC2 uses the Availability Zone for the specified subnet\. If you don't specify a subnet, it selects an Availability Zone and its default subnet, but not necessarily the lowest\-priced zone\. If you deleted the default subnet for an Availability Zone, then you must specify a different subnet\.
**Nondefault VPC**
Amazon EC2 uses the Availability Zone for the specified subnet\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/how-spot-instances-work.md |
60ff54837752-0 | You specify a subnet for your Spot Instances the same way that you specify a subnet for your On\-Demand Instances\.
+ You should use the default maximum price \(the On\-Demand price\), or base your maximum price on the Spot price history of Spot Instances in a VPC\.
+ \[Default VPC\] If you want your Spot Instance launched in a specific low\-priced Availability Zone, you must specify the corresponding subnet in your Spot Instance request\. If you do not specify a subnet, Amazon EC2 selects one for you, and the Availability Zone for this subnet might not have the lowest Spot price\.
+ \[Nondefault VPC\] You must specify the subnet for your Spot Instance\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/how-spot-instances-work.md |
4b285f20150f-0 | Dedicated Host sharing enables Dedicated Host owners to share their Dedicated Hosts with other AWS accounts or within an AWS organization\. This enables you to create and manage Dedicated Hosts centrally, and share the Dedicated Host across multiple AWS accounts or within your AWS organization\.
In this model, the AWS account that owns the Dedicated Host \(*owner*\) shares it with other AWS accounts \(*consumers*\)\. Consumers can launch instances onto Dedicated Hosts that are shared with them in the same way that they would launch instances onto Dedicated Hosts that they allocate in their own account\. The owner is responsible for managing the Dedicated Host and the instances that they launch onto it\. Owners can't modify instances that consumers launch onto shared Dedicated Hosts\. Consumers are responsible for managing the instances that they launch onto Dedicated Hosts shared with them\. Consumers can't view or modify instances owned by other consumers or by the Dedicated Host owner, and they can't modify Dedicated Hosts that are shared with them\.
A Dedicated Host owner can share a Dedicated Host with:
+ Specific AWS accounts inside or outside of its AWS organization
+ An organizational unit inside its AWS organization
+ Its entire AWS organization
**Topics**
+ [Prerequisites for sharing Dedicated Hosts](#dh-sharing-prereq)
+ [Limitations for sharing Dedicated Hosts](#dh-sharing-limitation)
+ [Related services](#dh-sharing-related)
+ [Sharing across Availability Zones](#dh-sharing-azs)
+ [Sharing a Dedicated Host](#sharing-dh) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dh-sharing.md |
4b285f20150f-1 | + [Sharing across Availability Zones](#dh-sharing-azs)
+ [Sharing a Dedicated Host](#sharing-dh)
+ [Unsharing a shared Dedicated Host](#unsharing-dh)
+ [Identifying a shared Dedicated Host](#identifying-shared-dh)
+ [Viewing instances running on a shared Dedicated Host](#shared-dh-usage)
+ [Shared Dedicated Host permissions](#shared-dh-perms)
+ [Billing and metering](#shared-dh-billing)
+ [Dedicated Host limits](#shared-dh-limits)
+ [Host recovery and Dedicated Host sharing](#dh-sharing-retirement) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dh-sharing.md |
68fff26f409b-0 | + To share a Dedicated Host, you must own it in your AWS account\. You can't share a Dedicated Host that has been shared with you\.
+ To share a Dedicated Host with your AWS organization or an organizational unit in your AWS organization, you must enable sharing with AWS Organizations\. For more information, see [Enable Sharing with AWS Organizations](https://docs.aws.amazon.com/ram/latest/userguide/getting-started-sharing.html) in the *AWS RAM User Guide*\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dh-sharing.md |
2ed5be0bf1f0-0 | You can't share Dedicated Hosts that have been allocated for the following instance types: `u-6tb1.metal`, `u-9tb1.metal`, `u-12tb1.metal`, `u-18tb1.metal`, and `u-24tb1.metal`\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dh-sharing.md |
f4fb6bdab3e3-0 | Dedicated Host sharing integrates with AWS Resource Access Manager \(AWS RAM\)\. AWS RAM is a service that enables you to share your AWS resources with any AWS account or through AWS Organizations\. With AWS RAM, you share resources that you own by creating a *resource share*\. A resource share specifies the resources to share, and the consumers with whom to share them\. Consumers can be individual AWS accounts, or organizational units or an entire organization from AWS Organizations\.
For more information about AWS RAM, see the *[AWS RAM User Guide](https://docs.aws.amazon.com/ram/latest/userguide/)*\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dh-sharing.md |
6f304c132fe6-0 | To ensure that resources are distributed across the Availability Zones for a Region, we independently map Availability Zones to names for each account\. This could lead to Availability Zone naming differences across accounts\. For example, the Availability Zone `us-east-1a` for your AWS account might not have the same location as `us-east-1a` for another AWS account\.
To identify the location of your Dedicated Hosts relative to your accounts, you must use the *Availability Zone ID* \(AZ ID\)\. The Availability Zone ID is a unique and consistent identifier for an Availability Zone across all AWS accounts\. For example, `use1-az1` is an Availability Zone ID for the `us-east-1` Region and it is the same location in every AWS account\.
**To view the Availability Zone IDs for the Availability Zones in your account**
1. Open the AWS RAM console at [https://console\.aws\.amazon\.com/ram](https://console.aws.amazon.com/ram/)\.
1. The Availability Zone IDs for the current Region are displayed in the **Your AZ ID** panel on the right\-hand side of the screen\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dh-sharing.md |
66678110eade-0 | When an owner shares a Dedicated Host, it enables consumers to launch instances on the host\. Consumers can launch as many instances onto the shared host as its available capacity allows\.
**Important**
Note that you are responsible for ensuring that you have appropriate license rights to share any BYOL licenses on your Dedicated Hosts\.
If you share a Dedicated Host with auto\-placement enabled, keep the following in mind as it could lead to unintended Dedicated Host usage:
+ If consumers launch instances with Dedicated Host tenancy and they do not have capacity on a Dedicated Host that they own in their account, the instance is automatically launched onto the shared Dedicated Host\.
To share a Dedicated Host, you must add it to a resource share\. A resource share is an AWS RAM resource that lets you share your resources across AWS accounts\. A resource share specifies the resources to share, and the consumers with whom they are shared\. You can add the Dedicated Host to an existing resource, or you can add it to a new resource share\.
If you are part of an organization in AWS Organizations and sharing within your organization is enabled, consumers in your organization are automatically granted access to the shared Dedicated Host\. Otherwise, consumers receive an invitation to join the resource share and are granted access to the shared Dedicated Host after accepting the invitation\.
**Note**
After you share a Dedicated Host, it could take a few minutes for consumers to have access to it\.
You can share a Dedicated Host that you own by using one of the following methods\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dh-sharing.md |
54ebc154ec16-0 | **To share a Dedicated Host that you own using the Amazon EC2 console**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the navigation pane, choose **Dedicated Hosts**\.
1. Choose the Dedicated Host to share and choose **Actions**, **Share host**\.
1. Select the resource share to which to add the Dedicated Host and choose **Share host**\.
It could take a few minutes for consumers to get access to the shared host\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dh-sharing.md |
fb0b23d1fa30-0 | **To share a Dedicated Host that you own using the AWS RAM console**
See [Creating a Resource Share](https://docs.aws.amazon.com/ram/latest/userguide/working-with-sharing.html#working-with-sharing-create) in the *AWS RAM User Guide*\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dh-sharing.md |
7b29778dc850-0 | **To share a Dedicated Host that you own using the AWS CLI**
Use the [create\-resource\-share](https://docs.aws.amazon.com/cli/latest/reference/ram/create-resource-share.html) command\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dh-sharing.md |
c41080b55ab8-0 | The Dedicated Host owner can unshare a shared Dedicated Host at any time\. When you unshare a shared Dedicated Host, the following rules apply:
+ Consumers with whom the Dedicated Host was shared can no longer launch new instances onto it\.
+ Instances owned by consumers that were running on the Dedicated Host at the time of unsharing continue to run but are scheduled for [ retirement](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/monitoring-instances-status-check_sched.html#schedevents_actions_retire)\. Consumers receive retirement notifications for the instances and they have two weeks to take action on the notifications\. However, if the Dedicated Host is reshared with the consumer within the retirement notice period, the instance retirements are cancelled\.
To unshare a shared Dedicated Host that you own, you must remove it from the resource share\. You can do this by using one of the following methods\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dh-sharing.md |
bfafd418a176-0 | **To unshare a shared Dedicated Host that you own using the Amazon EC2 console**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the navigation pane, choose **Dedicated Hosts**\.
1. Choose the Dedicated Host to unshare and choose the **Sharing** tab\.
1. The **Sharing** tab lists the resource shares to which the Dedicated Host has been added\. Select the resource share from which to remove the Dedicated Host and choose **Remove host from resource share**\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dh-sharing.md |
4d3e81d15698-0 | **To unshare a shared Dedicated Host that you own using the AWS RAM console**
See [Updating a Resource Share](https://docs.aws.amazon.com/ram/latest/userguide/working-with-sharing.html#working-with-sharing-update) in the *AWS RAM User Guide*\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dh-sharing.md |
37a2ea0429b4-0 | **To unshare a shared Dedicated Host that you own using the AWS CLI**
Use the [ disassociate\-resource\-share](https://docs.aws.amazon.com/cli/latest/reference/ram/disassociate-resource-share.html) command\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dh-sharing.md |
f072c0b404ca-0 | Owners and consumers can identify shared Dedicated Hosts using one of the following methods\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dh-sharing.md |
dffea58f9604-0 | **To identify a shared Dedicated Host using the Amazon EC2 console**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the navigation pane, choose **Dedicated Hosts**\. The screen lists Dedicated Hosts that you own and Dedicated Hosts that are shared with you\. The **Owner** column shows the AWS account ID of the Dedicated Host owner\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dh-sharing.md |
a65969f8652c-0 | **To identify a shared Dedicated Host using the AWS CLI**
Use the [ describe\-hosts](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-hosts.html) command\. The command returns the Dedicated Hosts that you own and Dedicated Hosts that are shared with you\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dh-sharing.md |
76b01f6ae2eb-0 | Owners and consumers can view the instances running on a shared Dedicated Host at any time using one of the following methods\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dh-sharing.md |
b66081fa98df-0 | **To view the instances running on a shared Dedicated Host using the Amazon EC2 console**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the navigation pane, choose **Dedicated Hosts**\.
1. Select the Dedicated Host for which to view the instances and choose **Instances**\. The tab lists the instances that are running on the host\. Owners see all of the instances running on the host, including instances launched by consumers\. Consumers only see running instances that they launched onto the host\. The **Owner** column shows the AWS account ID of the account that launched the instance\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dh-sharing.md |
04232904f051-0 | **To view the instances running on a shared Dedicated Host using the AWS CLI**
Use the [describe\-hosts](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-hosts.html) command\. The command returns the instances running on each Dedicated Host\. Owners see all of the instances running on the host\. Consumers only see running instances that they launched on the shared hosts\. `InstanceOwnerId` shows the AWS account ID of the instance owner\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dh-sharing.md |
8e9eb1158f39-0 | Owners are responsible for managing their shared Dedicated Hosts and the instances that they launch onto them\. Owners can view all instances running on the shared Dedicated Host, including those launched by consumers\. However, owners can't take any action on running instances that were launched by consumers\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dh-sharing.md |
44c753185435-0 | Consumers are responsible for managing the instances that they launch onto a shared Dedicated Host\. Consumers can't modify the shared Dedicated Host in any way, and they can't view or modify instances that were launched by other consumers or the Dedicated Host owner\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dh-sharing.md |
3fdce5e7e6a4-0 | There are no additional charges for sharing Dedicated Hosts\.
Owners are billed for Dedicated Hosts that they share\. Consumers are not billed for instances that they launch onto shared Dedicated Hosts\.
Dedicated Host Reservations continue to provide billing discounts for shared Dedicated Hosts\. Only Dedicated Host owners can purchase Dedicated Host Reservations for shared Dedicated Hosts that they own\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dh-sharing.md |
0422dd094f5e-0 | Shared Dedicated Hosts count towards the owner's Dedicated Hosts limits only\. Consumer's Dedicated Hosts limits are not affected by Dedicated Hosts that have been shared with them\. Similarly, instances that consumers launch onto shared Dedicated Hosts do not count towards their instance limits\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dh-sharing.md |
09c8ade761db-0 | Host recovery recovers instances launched by the Dedicated Host owner and the consumers with whom it has been shared\. The replacement Dedicated Host is allocated to the owner's account\. It is added to the same resource shares as the original Dedicated Host, and it is shared with the same consumers\.
For more information, see [Host recovery](dedicated-hosts-recovery.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/dh-sharing.md |
2074c45267a8-0 | Amazon EC2 provides different *resources* that you can create and use\. Some of these resources include images, instances, volumes, and snapshots\. When you create a resource, we assign the resource a unique resource ID\.
Some resources can be tagged with values that you define, to help you organize and identify them\.
The following topics describe resources and tags, and how you can work with them\.
**Topics**
+ [Resource locations](resources.md)
+ [Resource IDs](resource-ids.md)
+ [Listing and filtering your resources](Using_Filtering.md)
+ [Tagging your Amazon EC2 resources](Using_Tags.md)
+ [Amazon EC2 service quotas](ec2-resource-limits.md)
+ [Amazon EC2 usage reports](usage-reports.md) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/EC2_Resources.md |
d46209c80cac-0 | The following examples explain credit use for instances that are configured as `unlimited`\.
**Topics**
+ [Example 1: Explaining credit use with T3 Unlimited](#t3_unlimited_example)
+ [Example 2: Explaining credit use with T2 Unlimited](#t2_unlimited_example) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/unlimited-mode-examples.md |
62b61370a0a5-0 | In this example, you see the CPU utilization of a `t3.nano` instance launched as `unlimited`, and how it spends *earned* and *surplus* credits to sustain CPU utilization\.
A `t3.nano` instance earns 144 CPU credits over a rolling 24\-hour period, which it can redeem for 144 minutes of vCPU use\. When it depletes its CPU credit balance \(represented by the CloudWatch metric `CPUCreditBalance`\), it can spend *surplus* CPU credits—that it has *not yet earned*—to burst for as long as it needs\. Because a `t3.nano` instance earns a maximum of 144 credits in a 24\-hour period, it can spend surplus credits up to that maximum without being charged immediately\. If it spends more than 144 CPU credits, it is charged for the difference at the end of the hour\.
The intent of the example, illustrated by the following graph, is to show how an instance can burst using surplus credits even after it depletes its `CPUCreditBalance`\. The following workflow references the numbered points on the graph:
**P1** – At 0 hours on the graph, the instance is launched as `unlimited` and immediately begins to earn credits\. The instance remains idle from the time it is launched—CPU utilization is 0%—and no credits are spent\. All unspent credits are accrued in the credit balance\. For the first 24 hours, `CPUCreditUsage` is at 0, and the `CPUCreditBalance` value reaches its maximum of 144\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/unlimited-mode-examples.md |
62b61370a0a5-1 | **P2** – For the next 12 hours, CPU utilization is at 2\.5%, which is below the 5% baseline\. The instance earns more credits than it spends, but the `CPUCreditBalance` value cannot exceed its maximum of 144 credits\.
**P3** – For the next 24 hours, CPU utilization is at 7% \(above the baseline\), which requires a spend of 57\.6 credits\. The instance spends more credits than it earns, and the `CPUCreditBalance` value reduces to 86\.4 credits\.
**P4** – For the next 12 hours, CPU utilization decreases to 2\.5% \(below the baseline\), which requires a spend of 36 credits\. In the same time, the instance earns 72 credits\. The instance earns more credits than it spends, and the `CPUCreditBalance` value increases to 122 credits\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/unlimited-mode-examples.md |
62b61370a0a5-2 | **P5** – For the next 5 hours, the instance bursts at 100% CPU utilization, and spends a total of 570 credits to sustain the burst\. About an hour into this period, the instance depletes its entire `CPUCreditBalance` of 122 credits, and starts to spend surplus credits to sustain the high CPU utilization, totaling 448 surplus credits in this period \(570\-122=448\)\. When the `CPUSurplusCreditBalance` value reaches 144 CPU credits \(the maximum a `t3.nano` instance can earn in a 24\-hour period\), any surplus credits spent thereafter cannot be offset by earned credits\. The surplus credits spent thereafter amounts to 304 credits \(448\-144=304\), which results in a small additional charge at the end of the hour for 304 credits\.
**P6** – For the next 13 hours, CPU utilization is at 5% \(the baseline\)\. The instance earns as many credits as it spends, with no excess to pay down the `CPUSurplusCreditBalance`\. The `CPUSurplusCreditBalance` value remains at 144 credits\.
**P7** – For the last 24 hours in this example, the instance is idle and CPU utilization is 0%\. During this time, the instance earns 144 credits, which it uses to pay down the `CPUSurplusCreditBalance`\.
![\[Image NOT FOUND\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/t3_unlimited_graph.png) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/unlimited-mode-examples.md |
5860b12711c5-0 | In this example, you see the CPU utilization of a `t2.nano` instance launched as `unlimited`, and how it spends *earned* and *surplus* credits to sustain CPU utilization\.
A `t2.nano` instance earns 72 CPU credits over a rolling 24\-hour period, which it can redeem for 72 minutes of vCPU use\. When it depletes its CPU credit balance \(represented by the CloudWatch metric `CPUCreditBalance`\), it can spend *surplus* CPU credits—that it has *not yet earned*—to burst for as long as it needs\. Because a `t2.nano` instance earns a maximum of 72 credits in a 24\-hour period, it can spend surplus credits up to that maximum without being charged immediately\. If it spends more than 72 CPU credits, it is charged for the difference at the end of the hour\.
The intent of the example, illustrated by the following graph, is to show how an instance can burst using surplus credits even after it depletes its `CPUCreditBalance`\. You can assume that, at the start of the time line in the graph, the instance has an accrued credit balance equal to the maximum number of credits it can earn in 24 hours\. The following workflow references the numbered points on the graph:
**1** – In the first 10 minutes, `CPUCreditUsage` is at 0, and the `CPUCreditBalance` value remains at its maximum of 72\.
**2** – At 23:40, as CPU utilization increases, the instance spends CPU credits and the `CPUCreditBalance` value decreases\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/unlimited-mode-examples.md |
5860b12711c5-1 | **2** – At 23:40, as CPU utilization increases, the instance spends CPU credits and the `CPUCreditBalance` value decreases\.
**3** – At around 00:47, the instance depletes its entire `CPUCreditBalance`, and starts to spend surplus credits to sustain high CPU utilization\.
**4** – Surplus credits are spent until 01:55, when the `CPUSurplusCreditBalance` value reaches 72 CPU credits\. This is equal to the maximum a `t2.nano` instance can earn in a 24\-hour period\. Any surplus credits spent thereafter cannot be offset by earned credits within the 24\-hour period, which results in a small additional charge at the end of the hour\.
**5** – The instance continues to spend surplus credits until around 02:20\. At this time, CPU utilization falls below the baseline, and the instance starts to earn credits at 3 credits per hour \(or 0\.25 credits every 5 minutes\), which it uses to pay down the `CPUSurplusCreditBalance`\. After the `CPUSurplusCreditBalance` value reduces to 0, the instance starts to accrue earned credits in its `CPUCreditBalance` at 0\.25 credits every 5 minutes\.
![\[Image NOT FOUND\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/t2_unlimited_graph.png)
**Calculating the bill** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/unlimited-mode-examples.md |
5860b12711c5-2 | **Calculating the bill**
Surplus credits cost $0\.05 per vCPU\-hour\. The instance spent approximately 25 surplus credits between 01:55 and 02:20, which is equivalent to 0\.42 vCPU\-hours\.
Additional charges for this instance are 0\.42 vCPU\-hours x $0\.05/vCPU\-hour = $0\.021, rounded to $0\.02\.
Here is the month\-end bill for this T2 Unlimited instance:
![\[Example bill for a T2 Unlimited instance\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/t2_unlimited_bill_linux.png)
You can set billing alerts to be notified every hour of any accruing charges, and take action if required\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/unlimited-mode-examples.md |
f6a76e7fa6bc-0 | This topic explains how to verify the instance identity document using the base64\-encoded signature and the AWS RSA public certificate\.
**Important**
To validate the instance identity document using the base64\-encoded signature, you must request the AWS RSA public certificate from [AWS Support](https://console.aws.amazon.com/support/home#/)\.
**To validate the instance identity document using the base64\-encoded signature and the AWS RSA public certificate**
1. Connect to the instance\.
1. Retrieve the base64\-encoded signature from the instance metadata, convert it to binary, and add it to a file named `signature`\. Use one of the following commands depending on the IMDS version used by the instance\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/verify-signature.md |
9c2131eb35c6-0 | ```
$ 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/dynamic/instance-identity/signature | base64 -d > signature
```
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/verify-signature.md |
19a50e2a1477-0 | ```
$ curl -s http://169.254.169.254/latest/dynamic/instance-identity/signature | base64 -d > signature
```
------
1. Retrieve the plaintext instance identity document from the instance metadata and add it to a file named `document`\. Use one of the following commands depending on the IMDS version used by the instance\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/verify-signature.md |
301e0a843c3a-0 | ```
$ 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/dynamic/instance-identity/document > document
```
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/verify-signature.md |
7a278fcf8a14-0 | ```
$ curl -s http://169.254.169.254/latest/dynamic/instance-identity/document > document
```
------
1. Add the AWS RSA public certificate that you received from AWS Support to a file named `certificate`\.
1. Extract the public key from the certificate that you received from AWS Support and save it to a file named `key`\.
```
$ openssl x509 -pubkey -noout -in certificate > key
```
1. Use **OpenSSL dgst** command to verify the instance identity document\.
```
$ openssl dgst -sha256 -verify key -signature signature document
```
If the signature is valid, the `Verified OK` message appears\. If the signature cannot be verified, contact AWS Support\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/verify-signature.md |
667963d1103c-0 | After you launch your instance, you can connect to it and use it the way that you'd use a computer sitting in front of you\.
The following instructions explain how to connect to your instance using a Linux distribution on the Windows Subsystem for Linux \(WSL\)\. WSL is a free download and enables you to run native Linux command line tools directly on Windows, alongside your traditional Windows desktop, without the overhead of a virtual machine\.
By installing WSL, you can use a native Linux environment to connect to your Linux EC2 instances instead of using PuTTY or PuTTYgen\. The Linux environment makes it easier to connect to your Linux instances because it comes with a native SSH client that you can use to connect to your Linux instances and change the permissions of the \.pem key file\. The Amazon EC2 console provides the SSH command for connecting to the Linux instance, and you can get verbose output from the SSH command for troubleshooting\. For more information, see the [Windows Subsystem for Linux Documentation](https://docs.microsoft.com/en-us/windows/wsl/about)\.
**Note**
After you've installed the WSL, all the prerequisites and steps are the same as those described in [Connecting to your Linux instance using SSH](AccessingInstancesLinux.md), and the experience is just like using native Linux\.
If you receive an error while attempting to connect to your instance, see [Troubleshooting Connecting to Your Instance](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstancesConnecting.html)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/WSL.md |
667963d1103c-1 | **Contents**
+ [Prerequisites](#ssh-prereqs)
+ [Connect to your Linux instance using WSL](#Connect-Linux-WSL)
+ [Transferring files to Linux instances from Linux using SCP](#Connect-Linux-WSL-SCP)
+ [Uninstalling WSL](#uninstall-WSL) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/WSL.md |
2698489e78a8-0 | Before you connect to your Linux instance, complete the following prerequisites\.
**Verify that the instance is ready**
After you launch an instance, it can take a few minutes for the instance to be ready so that you can connect to it\. Check that your instance has passed its status checks\. You can view this information in the **Status Checks** column on the **Instances** page\.
**Verify the general prerequisites for connecting to your instance**
To find the public DNS name or IP address of your instance and the user name that you should use to connect to your instance, see [General prerequisites for connecting to your instance](connection-prereqs.md)\.
**Install the Windows Subsystem for Linux \(WSL\) and a Linux distribution on your local computer**
Install the WSL and a Linux distribution using the instructions in the [Windows 10 Installation Guide](https://docs.microsoft.com/en-us/windows/wsl/install-win10)\. The example in the instructions installs the Ubuntu distribution of Linux, but you can install any distribution\. You are prompted to restart your computer for the changes to take effect\.
**Copy the private key from Windows to WSL** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/WSL.md |
2698489e78a8-1 | **Copy the private key from Windows to WSL**
In a WSL terminal window, copy the `.pem` file \(for the key pair that you specified when you launched the instance\) from Windows to WSL\. Note the fully\-qualified path to the `.pem` file on WSL to use when connecting to your instance\. For information about how to specify the path to your Windows hard drive, see [How do I access my C drive?](https://docs.microsoft.com/en-us/windows/wsl/faq#how-do-i-access-my-c-drive)\. For more information about key pairs and Windows instances, see [Amazon EC2 key pairs and Windows instances](https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/ec2-key-pairs.html)\.
```
cp /mnt/<Windows drive letter>/path/my-key-pair.pem ~/WSL-path/my-key-pair.pem
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/WSL.md |
9d035e067769-0 | Use the following procedure to connect to your Linux instance using the Windows Subsystem for Linux \(WSL\)\. If you receive an error while attempting to connect to your instance, see [Troubleshooting Connecting to Your Instance](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstancesConnecting.html)\.
**To connect to your instance using SSH**
1. In a terminal window, use the ssh command to connect to the instance\. You specify the path and file name of the private key \(`.pem`\), the user name for your instance, and the public DNS name or IPv6 address for your instance\. For more information about how to find the private key, the user name for your instance, and the DNS name or IPv6 address for an instance, see [Locate the private key](connection-prereqs.md#connection-prereqs-private-key) and [Get information about your instance](connection-prereqs.md#connection-prereqs-get-info-about-instance)\. To connect to your instance, use one of the following commands\.
+ \(Public DNS\) To connect using your instance's public DNS name, enter the following command\.
```
sudo ssh -i /path/my-key-pair.pem my-instance-user-name@my-instance-public-dns-name
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/WSL.md |
9d035e067769-1 | ```
+ \(IPv6\) Alternatively, if your instance has an IPv6 address, you can connect to the instance using its IPv6 address\. Specify the ssh command with the path to the private key \(\.pem\) file, the appropriate user name, and the IPv6 address\.
```
sudo ssh -i /path/my-key-pair.pem my-instance-user-name@my-instance-IPv6-address
```
You see a response like the following:
```
The authenticity of host 'ec2-198-51-100-1.compute-1.amazonaws.com (10.254.142.33)'
can't be established.
RSA key fingerprint is 1f:51:ae:28:bf:89:e9:d8:1f:25:5d:37:2d:7d:b8:ca:9f:f5:f1:6f.
Are you sure you want to continue connecting (yes/no)?
```
1. \(Optional\) Verify that the fingerprint in the security alert matches the fingerprint that you previously obtained in [\(Optional\) Get the instance fingerprint](connection-prereqs.md#connection-prereqs-fingerprint)\. If these fingerprints don't match, someone might be attempting a "man\-in\-the\-middle" attack\. If they match, continue to the next step\.
1. Enter `yes`\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/WSL.md |
9d035e067769-2 | 1. Enter `yes`\.
You see a response like the following:
```
Warning: Permanently added 'ec2-198-51-100-1.compute-1.amazonaws.com' (RSA)
to the list of known hosts.
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/WSL.md |
077dbd882a9b-0 | One way to transfer files between your local computer and a Linux instance is to use the secure copy protocol \(SCP\)\. This section describes how to transfer files with SCP\. The procedure is similar to the procedure for connecting to an instance with SSH\.
**Prerequisites**
+ **Verify the general prerequisites for transferring files to your instance\.**
The general prerequisites for transferring files to an instance are the same as the general prerequisites for connecting to an instance\. For more information, see [General prerequisites for connecting to your instance](connection-prereqs.md)\.
+ **Install an SCP client**
Most Linux, Unix, and Apple computers include an SCP client by default\. If yours doesn't, the OpenSSH project provides a free implementation of the full suite of SSH tools, including an SCP client\. For more information, see [http://www\.openssh\.org](http://www.openssh.org/)\.
The following procedure steps you through using SCP to transfer a file\. If you've already connected to the instance with SSH and have verified its fingerprints, you can start with the step that contains the SCP command \(step 4\)\.
**To use SCP to transfer a file** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/WSL.md |
077dbd882a9b-1 | **To use SCP to transfer a file**
1. Transfer a file to your instance using the instance's public DNS name\. For example, if the name of the private key file is `my-key-pair`, the file to transfer is `SampleFile.txt`, the user name is `my-instance-user-name`, and the public DNS name of the instance is `my-instance-public-dns-name` or the IPv6 address is `my-instance-IPv6-address`, use one the following commands to copy the file to the `my-instance-user-name` home directory\.
+ \(Public DNS\) To transfer a file using your instance's public DNS name, enter the following command\.
```
scp -i /path/my-key-pair.pem /path/SampleFile.txt my-instance-user-name@my-instance-public-dns-name:~
```
+ \(IPv6\) Alternatively, if your instance has an IPv6 address, you can transfer a file using the instance's IPv6 address\. The IPv6 address must be enclosed in square brackets \(`[ ]`\), which must be escaped \(`\`\)\.
```
scp -i /path/my-key-pair.pem /path/SampleFile.txt my-instance-user-name@\[my-instance-IPv6-address\]:~
```
You see a response like the following: | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/WSL.md |
077dbd882a9b-2 | ```
You see a response like the following:
```
The authenticity of host 'ec2-198-51-100-1.compute-1.amazonaws.com (10.254.142.33)'
can't be established.
RSA key fingerprint is 1f:51:ae:28:bf:89:e9:d8:1f:25:5d:37:2d:7d:b8:ca:9f:f5:f1:6f.
Are you sure you want to continue connecting (yes/no)?
```
1. \(Optional\) Verify that the fingerprint in the security alert matches the fingerprint that you previously obtained in [\(Optional\) Get the instance fingerprint](connection-prereqs.md#connection-prereqs-fingerprint)\. If these fingerprints don't match, someone might be attempting a "man\-in\-the\-middle" attack\. If they match, continue to the next step\.
1. Enter **yes**\.
You see a response like the following:
```
Warning: Permanently added 'ec2-198-51-100-1.compute-1.amazonaws.com' (RSA)
to the list of known hosts.
Sending file modes: C0644 20 SampleFile.txt
Sink: C0644 20 SampleFile.txt
SampleFile.txt 100% 20 0.0KB/s 00:00 | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/WSL.md |
077dbd882a9b-3 | Sink: C0644 20 SampleFile.txt
SampleFile.txt 100% 20 0.0KB/s 00:00
```
If you receive a "bash: scp: command not found" error, you must first install scp on your Linux instance\. For some operating systems, this is located in the `openssh-clients` package\. For Amazon Linux variants, such as the Amazon ECS\-optimized AMI, use the following command to install scp:
```
[ec2-user ~]$ sudo yum install -y openssh-clients
```
1. To transfer files in the other direction \(from your Amazon EC2 instance to your local computer\), reverse the order of the host parameters\. For example, to transfer the `SampleFile.txt` file from your EC2 instance back to the home directory on your local computer as `SampleFile2.txt`, use one of the following commands on your local computer\.
+ \(Public DNS\) To transfer a file using your instance's public DNS name, enter the following command\.
```
scp -i /path/my-key-pair.pem [email protected]:~/SampleFile.txt ~/SampleFile2.txt
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/WSL.md |
077dbd882a9b-4 | ```
+ \(IPv6\) Alternatively, if your instance has an IPv6 address, to transfer files in the other direction using the instance's IPv6 address, enter the following command\.
```
scp -i /path/my-key-pair.pem my-instance-user-name@\[2001:db8:1234:1a00:9691:9503:25ad:1761\]:~/SampleFile.txt ~/SampleFile2.txt
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/WSL.md |
efce31178280-0 | For information about uninstalling Windows Subsystem for Linux, see [How do I uninstall a WSL Distribution?](https://docs.microsoft.com/en-us/windows/wsl/faq#how-do-i-uninstall-a-wsl-distribution)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/WSL.md |
44434071f65a-0 | To retrieve dynamic data from within a running instance, use the following URI\.
```
http://169.254.169.254/latest/dynamic/
```
This example shows how to retrieve the high\-level instance identity categories\.
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instancedata-dynamic-data-retrieval.md |
9d79f36c504a-0 | ```
[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/dynamic/instance-identity/
rsa2048
pkcs7
document
signature
dsa2048
```
------ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instancedata-dynamic-data-retrieval.md |
ca3f816fe86e-0 | ```
[ec2-user ~]$ curl http://169.254.169.254/latest/dynamic/instance-identity/
rsa2048
pkcs7
document
signature
dsa2048
```
------
For more information about dynamic data and examples of how to retrieve it, see [Instance identity documents](instance-identity-documents.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instancedata-dynamic-data-retrieval.md |
d1d87a851d3c-0 | When you launch an instance, the *instance type* that you specify determines the hardware of the host computer used for your instance\. Each instance type offers different compute, memory, and storage capabilities and are grouped in instance families based on these capabilities\. Select an instance type based on the requirements of the application or software that you plan to run on your instance\.
Amazon EC2 provides each instance with a consistent and predictable amount of CPU capacity, regardless of its underlying hardware\.
Amazon EC2 dedicates some resources of the host computer, such as CPU, memory, and instance storage, to a particular instance\. Amazon EC2 shares other resources of the host computer, such as the network and the disk subsystem, among instances\. If each instance on a host computer tries to use as much of one of these shared resources as possible, each receives an equal share of that resource\. However, when a resource is underused, an instance can consume a higher share of that resource while it's available\.
Each instance type provides higher or lower minimum performance from a shared resource\. For example, instance types with high I/O performance have a larger allocation of shared resources\. Allocating a larger share of shared resources also reduces the variance of I/O performance\. For most applications, moderate I/O performance is more than enough\. However, for applications that require greater or more consistent I/O performance, consider an instance type with higher I/O performance\.
**Topics**
+ [Available instance types](#AvailableInstanceTypes)
+ [Hardware specifications](#instance-hardware-specs)
+ [AMI virtualization types](#instance-virtualization-type) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-types.md |
d1d87a851d3c-1 | + [Hardware specifications](#instance-hardware-specs)
+ [AMI virtualization types](#instance-virtualization-type)
+ [Instances built on the Nitro System](#ec2-nitro-instances)
+ [Networking and storage features](#instance-networking-storage)
+ [Instance limits](#instance-type-limits)
+ [General purpose instances](general-purpose-instances.md)
+ [Compute optimized instances](compute-optimized-instances.md)
+ [Memory optimized instances](memory-optimized-instances.md)
+ [Storage optimized instances](storage-optimized-instances.md)
+ [Linux accelerated computing instances](accelerated-computing-instances.md)
+ [Finding an Amazon EC2 instance type](instance-discovery.md)
+ [Changing the instance type](ec2-instance-resize.md)
+ [Getting recommendations for an instance type](ec2-instance-recommendations.md) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-types.md |
7530b3dfcbe0-0 | Amazon EC2 provides a wide selection of instance types optimized for different use cases\. To determine which instance types meet your requirements, such as supported Regions, compute resources, or storage resources, see [Finding an Amazon EC2 instance type](instance-discovery.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-types.md |
60a43fdda24a-0 | For the best performance, we recommend that you use the following instance types when you launch new instances\. For more information, see [Amazon EC2 Instance Types](http://aws.amazon.com/ec2/instance-types/)\.
| Type | Sizes | Use case |
| --- | --- | --- |
| A1 | a1\.medium \| a1\.large \| a1\.xlarge \| a1\.2xlarge \| a1\.4xlarge \| a1\.metal | [General purpose](general-purpose-instances.md) |
| C4 | c4\.large \| c4\.xlarge \| c4\.2xlarge \| c4\.4xlarge \| c4\.8xlarge | [Compute optimized](compute-optimized-instances.md) |
| C5 | c5\.large \| c5\.xlarge \| c5\.2xlarge \| c5\.4xlarge \| c5\.9xlarge \| c5\.12xlarge \| c5\.18xlarge \| c5\.24xlarge \| c5\.metal | [Compute optimized](compute-optimized-instances.md) | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-types.md |
60a43fdda24a-1 | | C5a | c5a\.large \| c5a\.xlarge \| c5a\.2xlarge \| c5a\.4xlarge \| c5a\.8xlarge \| c5a\.12xlarge \| c5a\.16xlarge \| c5a\.24xlarge | [Compute optimized](compute-optimized-instances.md) |
| C5ad | c5ad\.large \| c5ad\.xlarge \| c5ad\.2xlarge \| c5ad\.4xlarge \| c5ad\.8xlarge \| c5ad\.12xlarge \| c5ad\.16xlarge \| c5ad\.24xlarge | [Compute optimized](compute-optimized-instances.md) |
| C5d | c5d\.large \| c5d\.xlarge \| c5d\.2xlarge \| c5d\.4xlarge \| c5d\.9xlarge \| c5d\.12xlarge \| c5d\.18xlarge \| c5d\.24xlarge \| c5d\.metal | [Compute optimized](compute-optimized-instances.md) | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-types.md |
60a43fdda24a-2 | | C5n | c5n\.large \| c5n\.xlarge \| c5n\.2xlarge \| c5n\.4xlarge \| c5n\.9xlarge \| c5n\.18xlarge \| c5n\.metal | [Compute optimized](compute-optimized-instances.md) |
| C6g | c6g\.medium \| c6g\.large \| c6g\.xlarge \| c6g\.2xlarge \| c6g\.4xlarge \| c6g\.8xlarge \| c6g\.12xlarge \| c6g\.16xlarge \| c6g\.metal | [Compute optimized](compute-optimized-instances.md) |
| C6gd | c6gd\.medium \| c6gd\.large \| c6gd\.xlarge \| c6gd\.2xlarge \| c6gd\.4xlarge \| c6gd\.8xlarge \| c6gd\.12xlarge \| c6gd\.16xlarge \| c6gd\.metal | [Compute optimized](compute-optimized-instances.md) |
| D2 | d2\.xlarge \| d2\.2xlarge \| d2\.4xlarge \| d2\.8xlarge | [Storage optimized](storage-optimized-instances.md) | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-types.md |
60a43fdda24a-3 | | F1 | f1\.2xlarge \| f1\.4xlarge \| f1\.16xlarge | [Accelerated computing](accelerated-computing-instances.md) |
| G3 | g3s\.xlarge \| g3\.4xlarge \| g3\.8xlarge \| g3\.16xlarge | [Accelerated computing](accelerated-computing-instances.md) |
| G4 | g4dn\.xlarge \| g4dn\.2xlarge \| g4dn\.4xlarge \| g4dn\.8xlarge \| g4dn\.12xlarge \| g4dn\.16xlarge \| g4dn\.metal | [Accelerated computing](accelerated-computing-instances.md) |
| H1 | h1\.2xlarge \| h1\.4xlarge \| h1\.8xlarge \| h1\.16xlarge | [Storage optimized](storage-optimized-instances.md) |
| I3 | i3\.large \| i3\.xlarge \| i3\.2xlarge \| i3\.4xlarge \| i3\.8xlarge \| i3\.16xlarge \| i3\.metal | [Storage optimized](storage-optimized-instances.md) | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-types.md |
60a43fdda24a-4 | | I3en | i3en\.large \| i3en\.xlarge \| i3en\.2xlarge \| i3en\.3xlarge \| i3en\.6xlarge \| i3en\.12xlarge \| i3en\.24xlarge \| i3en\.metal | [Storage optimized](storage-optimized-instances.md) |
| Inf1 | inf1\.xlarge \| inf1\.2xlarge \| inf1\.6xlarge \| inf1\.24xlarge | [Accelerated computing](accelerated-computing-instances.md) |
| M4 | m4\.large \| m4\.xlarge \| m4\.2xlarge \| m4\.4xlarge \| m4\.10xlarge \| m4\.16xlarge | [General purpose](general-purpose-instances.md) |
| M5 | m5\.large \| m5\.xlarge \| m5\.2xlarge \| m5\.4xlarge \| m5\.8xlarge \| m5\.12xlarge \| m5\.16xlarge \| m5\.24xlarge \| m5\.metal | [General purpose](general-purpose-instances.md) | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-types.md |
60a43fdda24a-5 | | M5a | m5a\.large \| m5a\.xlarge \| m5a\.2xlarge \| m5a\.4xlarge \| m5a\.8xlarge \| m5a\.12xlarge \| m5a\.16xlarge \| m5a\.24xlarge | [General purpose](general-purpose-instances.md) |
| M5ad | m5ad\.large \| m5ad\.xlarge \| m5ad\.2xlarge \| m5ad\.4xlarge \| m5ad\.8xlarge \| m5ad\.12xlarge \| m5ad\.16xlarge \| m5ad\.24xlarge | [General purpose](general-purpose-instances.md) |
| M5d | m5d\.large \| m5d\.xlarge \| m5d\.2xlarge \| m5d\.4xlarge \| m5d\.8xlarge \| m5d\.12xlarge \| m5d\.16xlarge \| m5d\.24xlarge \| m5d\.metal | [General purpose](general-purpose-instances.md) | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-types.md |
60a43fdda24a-6 | | M5dn | m5dn\.large \| m5dn\.xlarge \| m5dn\.2xlarge \| m5dn\.4xlarge \| m5dn\.8xlarge \| m5dn\.12xlarge \| m5dn\.16xlarge \| m5dn\.24xlarge | [General purpose](general-purpose-instances.md) |
| M5n | m5n\.large \| m5n\.xlarge \| m5n\.2xlarge \| m5n\.4xlarge \| m5n\.8xlarge \| m5n\.12xlarge \| m5n\.16xlarge \| m5n\.24xlarge | [General purpose](general-purpose-instances.md) |
| M6g | m6g\.medium \| m6g\.large \| m6g\.xlarge \| m6g\.2xlarge \| m6g\.4xlarge \| m6g\.8xlarge \| m6g\.12xlarge \| m6g\.16xlarge \| m6g\.metal | [General purpose](general-purpose-instances.md) | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-types.md |
60a43fdda24a-7 | | M6gd | m6gd\.medium \| m6gd\.large \| m6gd\.xlarge \| m6gd\.2xlarge \| m6gd\.4xlarge \| m6gd\.8xlarge \| m6gd\.12xlarge \| m6gd\.16xlarge \| m6gd\.metal | [General purpose](general-purpose-instances.md) |
| P2 | p2\.xlarge \| p2\.8xlarge \| p2\.16xlarge | [Accelerated computing](accelerated-computing-instances.md) |
| P3 | p3\.2xlarge \| p3\.8xlarge \| p3\.16xlarge | [Accelerated computing](accelerated-computing-instances.md) |
| P3dn | p3dn\.24xlarge | [Accelerated computing](accelerated-computing-instances.md) |
| R4 | r4\.large \| r4\.xlarge \| r4\.2xlarge \| r4\.4xlarge \| r4\.8xlarge \| r4\.16xlarge | [Memory optimized](memory-optimized-instances.md) | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-types.md |
60a43fdda24a-8 | | R5 | r5\.large \| r5\.xlarge \| r5\.2xlarge \| r5\.4xlarge \| r5\.8xlarge \| r5\.12xlarge \| r5\.16xlarge \| r5\.24xlarge \| r5\.metal | [Memory optimized](memory-optimized-instances.md) |
| R5a | r5a\.large \| r5a\.xlarge \| r5a\.2xlarge \| r5a\.4xlarge \| r5a\.8xlarge \| r5a\.12xlarge \| r5a\.16xlarge \| r5a\.24xlarge | [Memory optimized](memory-optimized-instances.md) |
| R5ad | r5ad\.large \| r5ad\.xlarge \| r5ad\.2xlarge \| r5ad\.4xlarge \| r5ad\.8xlarge \| r5ad\.12xlarge \| r5ad\.16xlarge \| r5ad\.24xlarge | [Memory optimized](memory-optimized-instances.md) | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-types.md |
60a43fdda24a-9 | | R5d | r5d\.large \| r5d\.xlarge \| r5d\.2xlarge \| r5d\.4xlarge \| r5d\.8xlarge \| r5d\.12xlarge \| r5d\.16xlarge \| r5d\.24xlarge \| r5d\.metal | [Memory optimized](memory-optimized-instances.md) |
| R5dn | r5dn\.large \| r5dn\.xlarge \| r5dn\.2xlarge \| r5dn\.4xlarge \| r5dn\.8xlarge \| r5dn\.12xlarge \| r5dn\.16xlarge \| r5dn\.24xlarge | [Memory optimized](memory-optimized-instances.md) |
| R5n | r5n\.large \| r5n\.xlarge \| r5n\.2xlarge \| r5n\.4xlarge \| r5n\.8xlarge \| r5n\.12xlarge \| r5n\.16xlarge \| r5n\.24xlarge | [Memory optimized](memory-optimized-instances.md) | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-types.md |
60a43fdda24a-10 | | R6g | r6g\.medium \| r6g\.large \| r6g\.xlarge \| r6g\.2xlarge \| r6g\.4xlarge \| r6g\.8xlarge \| r6g\.12xlarge \| r6g\.16xlarge \| r6g\.metal | [Memory optimized](memory-optimized-instances.md) |
| R6gd | r6gd\.medium \| r6gd\.large \| r6gd\.xlarge \| r6gd\.2xlarge \| r6gd\.4xlarge \| r6gd\.8xlarge \| r6gd\.12xlarge \| r6gd\.16xlarge \| r6gd\.metal | [Memory optimized](memory-optimized-instances.md) |
| T2 | t2\.nano \| t2\.micro \| t2\.small \| t2\.medium \| t2\.large \| t2\.xlarge \| t2\.2xlarge | [General purpose](general-purpose-instances.md) |
| T3 | t3\.nano \| t3\.micro \| t3\.small \| t3\.medium \| t3\.large \| t3\.xlarge \| t3\.2xlarge | [General purpose](general-purpose-instances.md) | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-types.md |
60a43fdda24a-11 | | T3a | t3a\.nano \| t3a\.micro \| t3a\.small \| t3a\.medium \| t3a\.large \| t3a\.xlarge \| t3a\.2xlarge | [General purpose](general-purpose-instances.md) |
| T4g | t4g\.nano \| t4g\.micro \| t4g\.small \| t4g\.medium \| t4g\.large \| t4g\.xlarge \| t4g\.2xlarge | [General purpose](general-purpose-instances.md) |
| u\-xtb1 | u\-6tb1\.metal \| u\-9tb1\.metal \| u\-12tb1\.metal \| u\-18tb1\.metal \| u\-24tb1\.metal | [Memory optimized](memory-optimized-instances.md) |
| X1 | x1\.16xlarge \| x1\.32xlarge | [Memory optimized](memory-optimized-instances.md) |
| X1e | x1e\.xlarge \| x1e\.2xlarge \| x1e\.4xlarge \| x1e\.8xlarge \| x1e\.16xlarge \| x1e\.32xlarge | [Memory optimized](memory-optimized-instances.md) | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-types.md |
60a43fdda24a-12 | | z1d | z1d\.large \| z1d\.xlarge \| z1d\.2xlarge \| z1d\.3xlarge \| z1d\.6xlarge \| z1d\.12xlarge \| z1d\.metal | [Memory optimized](memory-optimized-instances.md) | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-types.md |
258ae99aef9f-0 | Amazon Web Services offers previous generation instance types for users who have optimized their applications around them and have yet to upgrade\. We encourage you to use current generation instance types to get the best performance, but we continue to support the following previous generation instance types\. For more information about which current generation instance type would be a suitable upgrade, see [Previous Generation Instances](https://aws.amazon.com/ec2/previous-generation/)\.
| Type | Sizes |
| --- | --- |
| C1 | c1\.medium \| c1\.xlarge |
| C3 | c3\.large \| c3\.xlarge \| c3\.2xlarge \| c3\.4xlarge \| c3\.8xlarge |
| G2 | g2\.2xlarge \| g2\.8xlarge |
| I2 | i2\.xlarge \| i2\.2xlarge \| i2\.4xlarge \| i2\.8xlarge |
| M1 | m1\.small \| m1\.medium \| m1\.large \| m1\.xlarge |
| M2 | m2\.xlarge \| m2\.2xlarge \| m2\.4xlarge |
| M3 | m3\.medium \| m3\.large \| m3\.xlarge \| m3\.2xlarge | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-types.md |
258ae99aef9f-1 | | M3 | m3\.medium \| m3\.large \| m3\.xlarge \| m3\.2xlarge |
| R3 | r3\.large \| r3\.xlarge \| r3\.2xlarge \| r3\.4xlarge \| r3\.8xlarge |
| T1 | t1\.micro | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-types.md |
f9b547ed9942-0 | For more information about the hardware specifications for each Amazon EC2 instance type, see [Amazon EC2 Instance Types](https://aws.amazon.com/ec2/instance-types/)\.
To determine which instance type best meets your needs, we recommend that you launch an instance and use your own benchmark application\. Because you pay by the instance second, it's convenient and inexpensive to test multiple instance types before making a decision\.
If your needs change, even after you make a decision, you can resize your instance later\. For more information, see [Changing the instance type](ec2-instance-resize.md)\.
**Note**
Amazon EC2 instances typically run on 64\-bit virtual Intel processors as specified in the instance type product pages\. For more information about the hardware specifications for each Amazon EC2 instance type, see [Amazon EC2 Instance Types](https://aws.amazon.com/ec2/instance-types/)\. However, confusion may result from industry naming conventions for 64\-bit CPUs\. Chip manufacturer Advanced Micro Devices \(AMD\) introduced the first commercially successful 64\-bit architecture based on the Intel x86 instruction set\. Consequently, the architecture is widely referred to as AMD64 regardless of the chip manufacturer\. Windows and several Linux distributions follow this practice\. This explains why the internal system information on an Ubuntu or Windows EC2 instance displays the CPU architecture as AMD64 even though the instances are running on Intel hardware\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-types.md |
b0c23953d968-0 | <a name="virtualization"></a>The virtualization type of your instance is determined by the AMI that you use to launch it\. Current generation instance types support hardware virtual machine \(HVM\) only\. Some previous generation instance types support paravirtual \(PV\) and some AWS regions support PV instances\. For more information, see [Linux AMI virtualization types](virtualization_types.md)\.
For best performance, we recommend that you use an HVM AMI\. In addition, HVM AMIs are required to take advantage of enhanced networking\. HVM virtualization uses hardware\-assist technology provided by the AWS platform\. With HVM virtualization, the guest VM runs as if it were on a native hardware platform, except that it still uses PV network and storage drivers for improved performance\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-types.md |
6521ae8dc9ea-0 | The Nitro System is a collection of AWS\-built hardware and software components that enable high performance, high availability, and high security\. In addition, the Nitro System provides bare metal capabilities that eliminate virtualization overhead and support workloads that require full access to host hardware\. For more information, see [AWS Nitro System](http://aws.amazon.com/ec2/nitro/)\.
**Nitro components**
The following components are part of the Nitro System:
+ Nitro card
+ Local NVMe storage volumes
+ Networking hardware support
+ Management
+ Monitoring
+ Security
+ Nitro security chip, integrated into the motherboard
+ Nitro hypervisor \- A lightweight hypervisor that manages memory and CPU allocation and delivers performance that is indistinguishable from bare metal for most workloads\.
**Instance types**
The following instances are built on the Nitro System:
+ Virtualized: A1, C5, C5a, C5ad, C5d, C5n, C6g, C6gd, G4, I3en, Inf1, M5, M5a, M5ad, M5d, M5dn, M5n, M6g, M6gd, `p3dn.24xlarge`, R5, R5a, R5ad, R5d, R5dn, R5n, R6g, R6gd, T3, T3a, T4g, and z1d | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-types.md |
6521ae8dc9ea-1 | + Bare metal: `a1.metal`, `c5.metal`, `c5d.metal`, `c5n.metal`, `c6g.metal`, `c6gd.metal`, `i3.metal`, `i3en.metal`, `m5.metal`, `m5d.metal`, `m6g.metal`, `m6gd.metal`, `r5.metal`, `r5d.metal`, `r6g.metal`, `r6gd.metal`, `u-6tb1.metal`, `u-9tb1.metal`, `u-12tb1.metal`, `u-18tb1.metal`, `u-24tb1.metal`, and `z1d.metal`
**Learn more**
For more information, see the following videos:
+ [AWS re:Invent 2017: The Amazon EC2 Nitro System Architecture](https://www.youtube.com/watch?v=02EbskIXCOc)
+ [AWS re:Invent 2017: Amazon EC2 Bare Metal Instances](https://www.youtube.com/watch?v=o9_4uGvbvnk)
+ [AWS re:Invent 2019: Powering next\-gen Amazon EC2: Deep dive into the Nitro system](https://www.youtube.com/watch?v=rUY-00yFlE4) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-types.md |
6521ae8dc9ea-2 | + [AWS re:Inforce 2019: Security Benefits of the Nitro Architecture](https://www.youtube.com/watch?v=kN9XcFp5vUM) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-types.md |
bab4add2f153-0 | When you select an instance type, this determines the networking and storage features that are available\. To describe an instance type, use the [describe\-instance\-types](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-instance-types.html) command\.
**Networking features**
+ IPv6 is supported on all current generation instance types and the C3, R3, and I2 previous generation instance types\.
+ To maximize the networking and bandwidth performance of your instance type, you can do the following:
+ Launch supported instance types into a cluster placement group to optimize your instances for high performance computing \(HPC\) applications\. Instances in a common cluster placement group can benefit from high\-bandwidth, low\-latency networking\. For more information, see [Placement groups](placement-groups.md)\.
+ Enable enhanced networking for supported current generation instance types to get significantly higher packet per second \(PPS\) performance, lower network jitter, and lower latencies\. For more information, see [Enhanced networking on Linux](enhanced-networking.md)\.
+ Current generation instance types that are enabled for enhanced networking have the following networking performance attributes:
+ Traffic within the same Region over private IPv4 or IPv6 can support 5 Gbps for single\-flow traffic and up to 25 Gbps for multi\-flow traffic \(depending on the instance type\)\.
+ Traffic to and from Amazon S3 buckets within the same Region over the public IP address space or through a VPC endpoint can use all available instance aggregate bandwidth\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-types.md |
bab4add2f153-1 | + Traffic to and from Amazon S3 buckets within the same Region over the public IP address space or through a VPC endpoint can use all available instance aggregate bandwidth\.
+ The maximum transmission unit \(MTU\) supported varies across instance types\. All Amazon EC2 instance types support standard Ethernet V2 1500 MTU frames\. All current generation instances support 9001 MTU, or jumbo frames, and some previous generation instances support them as well\. For more information, see [Network maximum transmission unit \(MTU\) for your EC2 instance](network_mtu.md)\.
**Storage features**
+ Some instance types support EBS volumes and instance store volumes, while other instance types support only EBS volumes\. Some instance types that support instance store volumes use solid state drives \(SSD\) to deliver very high random I/O performance\. Some instance types support NVMe instance store volumes\. Some instance types support NVMe EBS volumes\. For more information, see [Amazon EBS and NVMe on Linux instances](nvme-ebs-volumes.md) and [NVMe SSD volumes](ssd-instance-store.md#nvme-ssd-volumes)\.
+ To obtain additional, dedicated capacity for Amazon EBS I/O, you can launch some instance types as EBS–optimized instances\. Some instance types are EBS–optimized by default\. 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/instance-types.md |
3792d54e1575-0 | The following table summarizes the networking and storage features supported by current generation instance types\.
| | EBS only | NVMe EBS | Instance store | Placement group | Enhanced networking |
| --- | --- | --- | --- | --- | --- |
| A1 | Yes | Yes | No | Yes | ENA |
| C4 | Yes | No | No | Yes | Intel 82599 VF |
| C5 | Yes | Yes | No | Yes | ENA |
| C5a | Yes | Yes | No | Yes | ENA |
| C5ad | No | Yes | NVMe \* | Yes | ENA |
| C5d | No | Yes | NVMe \* | Yes | ENA |
| C5n | Yes | Yes | No | Yes | ENA |
| C6g | Yes | Yes | No | Yes | ENA |
| C6gd | No | Yes | NVME \* | Yes | ENA |
| D2 | No | No | HDD | Yes | Intel 82599 VF |
| F1 | No | No | NVMe \* | Yes | ENA |
| G3 | Yes | No | No | Yes | ENA |
| G4 | No | Yes | NVMe \* | Yes | ENA |
| HS1 | No | No | HDD \* | Yes | ENA | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-types.md |
3792d54e1575-1 | | HS1 | No | No | HDD \* | Yes | ENA |
| I3 | No | No | NVMe \* | Yes | ENA |
| I3en | No | Yes | NVMe \* | Yes | ENA |
| Inf1 | Yes | Yes | No | Yes | ENA |
| M4 | Yes | No | No | Yes | m4\.16xlarge: ENA All other sizes: Intel 82599 VF |
| M5 | Yes | Yes | No | Yes | ENA |
| M5a | Yes | Yes | No | Yes | ENA |
| M5ad | No | Yes | NVMe \* | Yes | ENA |
| M5d | No | Yes | NVMe \* | Yes | ENA |
| M5dn | No | Yes | NVMe \* | Yes | ENA |
| M5n | Yes | Yes | No | Yes | ENA |
| M6g | Yes | Yes | No | Yes | ENA |
| M6gd | No | Yes | NVME \* | Yes | ENA |
| P2 | Yes | No | No | Yes | ENA |
| P3 | Yes | No | No | Yes | ENA |
| P3dn | No | Yes | NVMe \* | Yes | ENA |
| R4 | Yes | No | No | Yes | ENA | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-types.md |
3792d54e1575-2 | | R4 | Yes | No | No | Yes | ENA |
| R5 | Yes | Yes | No | Yes | ENA |
| R5a | Yes | Yes | No | Yes | ENA |
| R5ad | No | Yes | NVMe \* | Yes | ENA |
| R5d | No | Yes | NVMe \* | Yes | ENA |
| R5dn | No | Yes | NVMe \* | Yes | ENA |
| R5n | Yes | Yes | No | Yes | ENA |
| R6g | Yes | Yes | No | Yes | ENA |
| R6gd | No | Yes | NVME \* | Yes | ENA |
| T2 | Yes | No | No | No | No |
| T3 | Yes | Yes | No | No | ENA |
| T3a | Yes | Yes | No | No | ENA |
| T4g | Yes | Yes | No | No | ENA |
| u\-xtb1\.metal | Yes | Yes | No | No | ENA |
| X1 | No | No | SSD \* | Yes | ENA |
| X1e | No | No | SSD \* | Yes | ENA |
| z1d | No | Yes | NVMe \* | Yes | ENA |
\* The root device volume must be an Amazon EBS volume\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-types.md |
3792d54e1575-3 | \* The root device volume must be an Amazon EBS volume\.
The following table summarizes the networking and storage features supported by previous generation instance types\.
| | Instance store | Placement group | Enhanced networking |
| --- | --- | --- | --- |
| C3 | SSD | Yes | Intel 82599 VF |
| G2 | SSD | Yes | No |
| I2 | SSD | Yes | Intel 82599 VF |
| M3 | SSD | No | No |
| R3 | SSD | Yes | Intel 82599 VF | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-types.md |
41ca2e3b7689-0 | There is a limit on the total number of instances that you can launch in a region, and there are additional limits on some instance types\.
For more information about the default limits, see [How many instances can I run in Amazon EC2?](https://aws.amazon.com/ec2/faqs/#How_many_instances_can_I_run_in_Amazon_EC2)
For more information about viewing your current limits or requesting an increase in your current limits, see [Amazon EC2 service quotas](ec2-resource-limits.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-types.md |
c56c316693a7-0 | Amazon EBS provides the following volume types, which differ in performance characteristics and price, so that you can tailor your storage performance and cost to the needs of your applications\. The volumes types fall into two categories:
+ SSD\-backed volumes optimized for transactional workloads involving frequent read/write operations with small I/O size, where the dominant performance attribute is IOPS
+ HDD\-backed volumes optimized for large streaming workloads where throughput \(measured in MiB/s\) is a better performance measure than IOPS
There are several factors that can affect the performance of EBS volumes, such as instance configuration, I/O characteristics, and workload demand\. For more information about getting the most out of your EBS volumes, see [Amazon EBS volume performance on Linux instances](EBSPerformance.md)\.
For more information about pricing, see [Amazon EBS Pricing](http://aws.amazon.com/ebs/pricing/)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-volume-types.md |
8fde4b5a5db9-0 | The following table describes the use cases and performance characteristics for each volume type\. The default volume type is General Purpose SSD \(`gp2`\)\.
[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-volume-types.html)
\* The throughput limit is between 128 MiB/s and 250 MiB/s, depending on the volume size\. Volumes smaller than or equal to 170 GiB deliver a maximum throughput of 128 MiB/s\. Volumes larger than 170 GiB but smaller than 334 GiB deliver a maximum throughput of 250 MiB/s if burst credits are available\. Volumes larger than or equal to 334 GiB deliver 250 MiB/s regardless of burst credits\. Older `gp2` volumes might not reach full performance unless you modify the volume\. For more information, see [Amazon EBS Elastic Volumes](ebs-modify-volume.md)\.
† Maximum IOPS and throughput are guaranteed only on [Instances built on the Nitro System](instance-types.md#ec2-nitro-instances) provisioned with more than 32,000 IOPS\. Other instances guarantee up to 32,000 IOPS and 500 MiB/s\. Older `io1` volumes might not reach full performance unless you modify the volume\. For more information, see [Amazon EBS Elastic Volumes](ebs-modify-volume.md)\.
†† To achieve this throughput, you must have an instance that supports [EBS optimization](ebs-optimized.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-volume-types.md |
c0d467e0370b-0 | The following table describes previous\-generation EBS volume types\. If you need higher performance or performance consistency than previous\-generation volumes can provide, we recommend that you consider using General Purpose SSD \(`gp2`\) or other current volume types\. For more information, see [Previous Generation Volumes](https://aws.amazon.com/ebs/previous-generation/)\.
| Hard disk drives \(HDD\) |
| --- |
| Volume type | Magnetic |
| Use cases | Workloads where data is infrequently accessed |
| API name | standard |
| Volume size | 1 GiB\-1 TiB |
| Max IOPS per volume | 40–200 |
| Max throughput per volume | 40–90 MiB/s |
| Max IOPS per instance | 80,000 |
| Max throughput per instance | 1,750 MB/s |
| Dominant performance attribute | IOPS | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-volume-types.md |
54cd5b3bf948-0 | General Purpose SSD \(`gp2`\) volumes offer cost\-effective storage that is ideal for a broad range of workloads\. These volumes deliver single\-digit millisecond latencies and the ability to burst to 3,000 IOPS for extended periods of time\. Between a minimum of 100 IOPS \(at 33\.33 GiB and below\) and a maximum of 16,000 IOPS \(at 5,334 GiB and above\), baseline performance scales linearly at 3 IOPS per GiB of volume size\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-volume-types.md |
Subsets and Splits