id
stringlengths 14
16
| text
stringlengths 1
2.43k
| source
stringlengths 99
229
|
|---|---|---|
61e30fe77203-0 | The following examples specify two launch configurations with different instance types, but the same AMI and Availability Zone or subnet\. The Spot Fleet launches the instances using the specified instance type with the lowest price\.
**Availability Zone**
```
{
"TargetCapacity": 20,
"IamFleetRole": "arn:aws:iam::123456789012:role/aws-ec2-spot-fleet-tagging-role",
"LaunchSpecifications": [
{
"ImageId": "ami-1a2b3c4d",
"SecurityGroups": [
{
"GroupId": "sg-1a2b3c4d"
}
],
"InstanceType": "cc2.8xlarge",
"Placement": {
"AvailabilityZone": "us-west-2b"
}
},
{
"ImageId": "ami-1a2b3c4d",
"SecurityGroups": [
{
"GroupId": "sg-1a2b3c4d"
}
],
"InstanceType": "r3.8xlarge",
"Placement": {
"AvailabilityZone": "us-west-2b"
}
} | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/spot-fleet-examples.md |
61e30fe77203-1 | "Placement": {
"AvailabilityZone": "us-west-2b"
}
}
]
}
```
**Subnet**
```
{
"TargetCapacity": 20,
"IamFleetRole": "arn:aws:iam::123456789012:role/aws-ec2-spot-fleet-tagging-role",
"LaunchSpecifications": [
{
"ImageId": "ami-1a2b3c4d",
"SecurityGroups": [
{
"GroupId": "sg-1a2b3c4d"
}
],
"InstanceType": "cc2.8xlarge",
"SubnetId": "subnet-1a2b3c4d"
},
{
"ImageId": "ami-1a2b3c4d",
"SecurityGroups": [
{
"GroupId": "sg-1a2b3c4d"
}
],
"InstanceType": "r3.8xlarge",
"SubnetId": "subnet-1a2b3c4d"
}
]
} | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/spot-fleet-examples.md |
61e30fe77203-2 | "SubnetId": "subnet-1a2b3c4d"
}
]
}
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/spot-fleet-examples.md |
f22e5b0c07e3-0 | We recommended that you use the default maximum price, which is the On\-Demand price\. If you prefer, you can specify a maximum price for the fleet request and maximum prices for individual launch specifications\.
The following examples specify a maximum price for the fleet request and maximum prices for two of the three launch specifications\. The maximum price for the fleet request is used for any launch specification that does not specify a maximum price\. The Spot Fleet launches the instances using the instance type with the lowest price\.
**Availability Zone**
```
{
"SpotPrice": "1.00",
"TargetCapacity": 30,
"IamFleetRole": "arn:aws:iam::123456789012:role/aws-ec2-spot-fleet-tagging-role",
"LaunchSpecifications": [
{
"ImageId": "ami-1a2b3c4d",
"InstanceType": "c3.2xlarge",
"Placement": {
"AvailabilityZone": "us-west-2b"
},
"SpotPrice": "0.10"
},
{
"ImageId": "ami-1a2b3c4d",
"InstanceType": "c3.4xlarge",
"Placement": {
"AvailabilityZone": "us-west-2b"
}, | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/spot-fleet-examples.md |
f22e5b0c07e3-1 | "Placement": {
"AvailabilityZone": "us-west-2b"
},
"SpotPrice": "0.20"
},
{
"ImageId": "ami-1a2b3c4d",
"InstanceType": "c3.8xlarge",
"Placement": {
"AvailabilityZone": "us-west-2b"
}
}
]
}
```
**Subnet**
```
{
"SpotPrice": "1.00",
"TargetCapacity": 30,
"IamFleetRole": "arn:aws:iam::123456789012:role/aws-ec2-spot-fleet-tagging-role",
"LaunchSpecifications": [
{
"ImageId": "ami-1a2b3c4d",
"InstanceType": "c3.2xlarge",
"SubnetId": "subnet-1a2b3c4d",
"SpotPrice": "0.10"
},
{
"ImageId": "ami-1a2b3c4d",
"InstanceType": "c3.4xlarge", | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/spot-fleet-examples.md |
f22e5b0c07e3-2 | "ImageId": "ami-1a2b3c4d",
"InstanceType": "c3.4xlarge",
"SubnetId": "subnet-1a2b3c4d",
"SpotPrice": "0.20"
},
{
"ImageId": "ami-1a2b3c4d",
"InstanceType": "c3.8xlarge",
"SubnetId": "subnet-1a2b3c4d"
}
]
}
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/spot-fleet-examples.md |
4b61aec222d6-0 | The following example uses the `diversified` allocation strategy\. The launch specifications have different instance types but the same AMI and Availability Zone or subnet\. The Spot Fleet distributes the 30 instances across the three launch specifications, such that there are 10 instances of each type\. For more information, see [Allocation strategy for Spot Instances](spot-fleet.md#spot-fleet-allocation-strategy)\.
**Availability Zone**
```
{
"SpotPrice": "0.70",
"TargetCapacity": 30,
"AllocationStrategy": "diversified",
"IamFleetRole": "arn:aws:iam::123456789012:role/aws-ec2-spot-fleet-tagging-role",
"LaunchSpecifications": [
{
"ImageId": "ami-1a2b3c4d",
"InstanceType": "c4.2xlarge",
"Placement": {
"AvailabilityZone": "us-west-2b"
}
},
{
"ImageId": "ami-1a2b3c4d",
"InstanceType": "m3.2xlarge",
"Placement": {
"AvailabilityZone": "us-west-2b"
}
},
{ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/spot-fleet-examples.md |
4b61aec222d6-1 | "Placement": {
"AvailabilityZone": "us-west-2b"
}
},
{
"ImageId": "ami-1a2b3c4d",
"InstanceType": "r3.2xlarge",
"Placement": {
"AvailabilityZone": "us-west-2b"
}
}
]
}
```
**Subnet**
```
{
"SpotPrice": "0.70",
"TargetCapacity": 30,
"AllocationStrategy": "diversified",
"IamFleetRole": "arn:aws:iam::123456789012:role/aws-ec2-spot-fleet-tagging-role",
"LaunchSpecifications": [
{
"ImageId": "ami-1a2b3c4d",
"InstanceType": "c4.2xlarge",
"SubnetId": "subnet-1a2b3c4d"
},
{
"ImageId": "ami-1a2b3c4d",
"InstanceType": "m3.2xlarge",
"SubnetId": "subnet-1a2b3c4d" | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/spot-fleet-examples.md |
4b61aec222d6-2 | "InstanceType": "m3.2xlarge",
"SubnetId": "subnet-1a2b3c4d"
},
{
"ImageId": "ami-1a2b3c4d",
"InstanceType": "r3.2xlarge",
"SubnetId": "subnet-1a2b3c4d"
}
]
}
```
A best practice to increase the chance that a spot request can be fulfilled by EC2 capacity in the event of an outage in one of the Availability Zones is to diversify across zones\. For this scenario, include each Availability Zone available to you in the launch specification\. And, instead of using the same subnet each time, use three unique subnets \(each mapping to a different zone\)\.
**Availability Zone**
```
{
"SpotPrice": "0.70",
"TargetCapacity": 30,
"AllocationStrategy": "diversified",
"IamFleetRole": "arn:aws:iam::123456789012:role/aws-ec2-spot-fleet-tagging-role",
"LaunchSpecifications": [
{
"ImageId": "ami-1a2b3c4d",
"InstanceType": "c4.2xlarge", | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/spot-fleet-examples.md |
4b61aec222d6-3 | "ImageId": "ami-1a2b3c4d",
"InstanceType": "c4.2xlarge",
"Placement": {
"AvailabilityZone": "us-west-2a"
}
},
{
"ImageId": "ami-1a2b3c4d",
"InstanceType": "m3.2xlarge",
"Placement": {
"AvailabilityZone": "us-west-2b"
}
},
{
"ImageId": "ami-1a2b3c4d",
"InstanceType": "r3.2xlarge",
"Placement": {
"AvailabilityZone": "us-west-2c"
}
}
]
}
```
**Subnet**
```
{
"SpotPrice": "0.70",
"TargetCapacity": 30,
"AllocationStrategy": "diversified",
"IamFleetRole": "arn:aws:iam::123456789012:role/aws-ec2-spot-fleet-tagging-role",
"LaunchSpecifications": [
{ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/spot-fleet-examples.md |
4b61aec222d6-4 | "LaunchSpecifications": [
{
"ImageId": "ami-1a2b3c4d",
"InstanceType": "c4.2xlarge",
"SubnetId": "subnet-1a2b3c4d"
},
{
"ImageId": "ami-1a2b3c4d",
"InstanceType": "m3.2xlarge",
"SubnetId": "subnet-2a2b3c4d"
},
{
"ImageId": "ami-1a2b3c4d",
"InstanceType": "r3.2xlarge",
"SubnetId": "subnet-3a2b3c4d"
}
]
}
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/spot-fleet-examples.md |
20217aa9982c-0 | The following examples use instance weighting, which means that the price is per unit hour instead of per instance hour\. Each launch configuration lists a different instance type and a different weight\. The Spot Fleet selects the instance type with the lowest price per unit hour\. The Spot Fleet calculates the number of Spot Instances to launch by dividing the target capacity by the instance weight\. If the result isn't an integer, the Spot Fleet rounds it up to the next integer, so that the size of your fleet is not below its target capacity\.
If the `r3.2xlarge` request is successful, Spot provisions 4 of these instances\. Divide 20 by 6 for a total of 3\.33 instances, then round up to 4 instances\.
If the `c3.xlarge` request is successful, Spot provisions 7 of these instances\. Divide 20 by 3 for a total of 6\.66 instances, then round up to 7 instances\.
For more information, see [Spot Fleet instance weighting](spot-fleet.md#spot-instance-weighting)\.
**Availability Zone**
```
{
"SpotPrice": "0.70",
"TargetCapacity": 20,
"IamFleetRole": "arn:aws:iam::123456789012:role/aws-ec2-spot-fleet-tagging-role",
"LaunchSpecifications": [
{
"ImageId": "ami-1a2b3c4d", | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/spot-fleet-examples.md |
20217aa9982c-1 | "LaunchSpecifications": [
{
"ImageId": "ami-1a2b3c4d",
"InstanceType": "r3.2xlarge",
"Placement": {
"AvailabilityZone": "us-west-2b"
},
"WeightedCapacity": 6
},
{
"ImageId": "ami-1a2b3c4d",
"InstanceType": "c3.xlarge",
"Placement": {
"AvailabilityZone": "us-west-2b"
},
"WeightedCapacity": 3
}
]
}
```
**Subnet**
```
{
"SpotPrice": "0.70",
"TargetCapacity": 20,
"IamFleetRole": "arn:aws:iam::123456789012:role/aws-ec2-spot-fleet-tagging-role",
"LaunchSpecifications": [
{
"ImageId": "ami-1a2b3c4d",
"InstanceType": "r3.2xlarge",
"SubnetId": "subnet-1a2b3c4d", | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/spot-fleet-examples.md |
20217aa9982c-2 | "InstanceType": "r3.2xlarge",
"SubnetId": "subnet-1a2b3c4d",
"WeightedCapacity": 6
},
{
"ImageId": "ami-1a2b3c4d",
"InstanceType": "c3.xlarge",
"SubnetId": "subnet-1a2b3c4d",
"WeightedCapacity": 3
}
]
}
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/spot-fleet-examples.md |
5d9f12cdc4ef-0 | To ensure that you always have instance capacity, you can include a request for On\-Demand capacity in your Spot Fleet request\. If there is capacity, the On\-Demand request is always fulfilled\. The balance of the target capacity is fulfilled as Spot if there is capacity and availability\.
The following example specifies the desired target capacity as 10, of which 5 must be On\-Demand capacity\. Spot capacity is not specified; it is implied in the balance of the target capacity minus the On\-Demand capacity\. Amazon EC2 launches 5 capacity units as On\-Demand, and 5 capacity units \(10\-5=5\) as Spot if there is available Amazon EC2 capacity and availability\.
For more information, see [On\-Demand in Spot Fleet](spot-fleet.md#on-demand-in-spot)\.
```
{
"IamFleetRole": "arn:aws:iam::781603563322:role/aws-ec2-spot-fleet-tagging-role",
"AllocationStrategy": "lowestPrice",
"TargetCapacity": 10,
"SpotPrice": null,
"ValidFrom": "2018-04-04T15:58:13Z",
"ValidUntil": "2019-04-04T15:58:13Z",
"TerminateInstancesWithExpiration": true,
"LaunchSpecifications": [],
"Type": "maintain", | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/spot-fleet-examples.md |
5d9f12cdc4ef-1 | "LaunchSpecifications": [],
"Type": "maintain",
"OnDemandTargetCapacity": 5,
"LaunchTemplateConfigs": [
{
"LaunchTemplateSpecification": {
"LaunchTemplateId": "lt-0dbb04d4a6cca5ad1",
"Version": "2"
},
"Overrides": [
{
"InstanceType": "t2.medium",
"WeightedCapacity": 1,
"SubnetId": "subnet-d0dc51fb"
}
]
}
]
}
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/spot-fleet-examples.md |
59f57f753453-0 | As a managed service, Amazon EC2 is protected by the AWS global network security procedures that are described in the [Amazon Web Services: Overview of Security Processes](https://d0.awsstatic.com/whitepapers/Security/AWS_Security_Whitepaper.pdf) whitepaper\.
You use AWS published API calls to access Amazon EC2 through the network\. Clients must support Transport Layer Security \(TLS\) 1\.0 or later\. We recommend TLS 1\.2 or later\. Clients must also support cipher suites with perfect forward secrecy \(PFS\) such as Ephemeral Diffie\-Hellman \(DHE\) or Elliptic Curve Ephemeral Diffie\-Hellman \(ECDHE\)\. Most modern systems such as Java 7 and later support these modes\.
Additionally, requests must be signed using an access key ID and a secret access key that is associated with an IAM principal\. Or you can use the [AWS Security Token Service](https://docs.aws.amazon.com/STS/latest/APIReference/Welcome.html) \(AWS STS\) to generate temporary security credentials to sign requests\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/infrastructure-security.md |
db9fae7f1caa-0 | A virtual private cloud \(VPC\) is a virtual network in your own logically isolated area in the AWS Cloud\. Use separate VPCs to isolate infrastructure by workload or organizational entity\.
A subnet is a range of IP addresses in a VPC\. When you launch an instance, you launch it into a subnet in your VPC\. Use subnets to isolate the tiers of your application \(for example, web, application, and database\) within a single VPC\. Use private subnets for your instances if they should not be accessed directly from the internet\.
To call the Amazon EC2 API from your VPC without sending traffic over the public internet, use AWS PrivateLink\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/infrastructure-security.md |
202e784f5e9c-0 | Different EC2 instances on the same physical host are isolated from each other as though they are on separate physical hosts\. The hypervisor isolates CPU and memory, and the instances are provided virtualized disks instead of access to the raw disk devices\.
When you stop or terminate an instance, the memory allocated to it is scrubbed \(set to zero\) by the hypervisor before it is allocated to a new instance, and every block of storage is reset\. This ensures that your data is not unintentionally exposed to another instance\.
Network MAC addresses are dynamically assigned to instances by the AWS network infrastructure\. IP addresses are either dynamically assigned to instances by the AWS network infrastructure, or assigned by an EC2 administrator through authenticated API requests\. The AWS network allows instances to send traffic only from the MAC and IP addresses assigned to them\. Otherwise, the traffic is dropped\.
By default, an instance cannot receive traffic that is not specifically addressed to it\. If you need to run network address translation \(NAT\), routing, or firewall services on your instance, you can disable source/destination checking for the network interface\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/infrastructure-security.md |
a25ba0a3ed67-0 | Consider the following options for controlling network traffic to your EC2 instances:
+ Restrict access to your instances using [security groups](ec2-security-groups.md)\. For example, you can allow traffic only from the address ranges for your corporate network\.
+ Use private subnets for your instances if they should not be accessed directly from the internet\. Use a bastion host or NAT gateway for internet access from an instance in a private subnet\.
+ Use AWS Virtual Private Network or AWS Direct Connect to establish private connections from your remote networks to your VPCs\. For more information, see [Network\-to\-Amazon VPC Connectivity Options](https://docs.aws.amazon.com/whitepapers/latest/aws-vpc-connectivity-options/network-to-amazon-vpc-connectivity-options.html)\.
+ Use [VPC Flow Logs](https://docs.aws.amazon.com/vpc/latest/userguide/flow-logs.html) to monitor the traffic that reaches your instances\.
+ Use [AWS Security Hub](http://aws.amazon.com/security-hub/) to check for unintended network accessibility from your instances\.
+ Use [EC2 Instance Connect](Connect-using-EC2-Instance-Connect.md) to connect to your instances using Secure Shell \(SSH\) without the need to share and manage SSH keys\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/infrastructure-security.md |
a25ba0a3ed67-1 | + Use [AWS Systems Manager Session Manager](https://docs.aws.amazon.com/systems-manager/latest/userguide/session-manager.html) to access your instances remotely instead of opening inbound SSH ports and managing SSH keys\.
+ Use [AWS Systems Manager Run Command](https://docs.aws.amazon.com/systems-manager/latest/userguide/execute-remote-commands.html) to automate common administrative tasks instead of opening inbound SSH ports and managing SSH keys\.
In addition to restricting network access to each Amazon EC2 instance, Amazon VPC supports implementing additional network security controls like in\-line gateways, proxy servers, and various network monitoring options\.
For more information, see the [AWS Security Best Practices](https://d1.awsstatic.com/whitepapers/Security/AWS_Security_Best_Practices.pdf) whitepaper\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/infrastructure-security.md |
06eddabe7edb-0 | We recommend that you regularly patch, update, and secure the operating system and applications on your EC2 instances\. You can use [AWS Systems Manager Patch Manager](https://docs.aws.amazon.com/systems-manager/latest/userguide/systems-manager-patch.html) to automate the process of installing security\-related updates for both the operating system and applications\. Alternatively, you can use any automatic update services or recommended processes for installing updates that are provided by the application vendor\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/update-management.md |
0ab0f1882db4-0 | Amazon Elastic Compute Cloud \(Amazon EC2\) provides scalable computing capacity in the Amazon Web Services \(AWS\) cloud\. Using Amazon EC2 eliminates your need to invest in hardware up front, so you can develop and deploy applications faster\. You can use Amazon EC2 to launch as many or as few virtual servers as you need, configure security and networking, and manage storage\. Amazon EC2 enables you to scale up or down to handle changes in requirements or spikes in popularity, reducing your need to forecast traffic\.
For more information about cloud computing, see [What is Cloud Computing?](https://aws.amazon.com/what-is-cloud-computing/) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/concepts.md |
f35621a38808-0 | Amazon EC2 provides the following features:
+ Virtual computing environments, known as *instances*
+ Preconfigured templates for your instances, known as *Amazon Machine Images \(AMIs\)*, that package the bits you need for your server \(including the operating system and additional software\)
+ Various configurations of CPU, memory, storage, and networking capacity for your instances, known as *instance types*
+ Secure login information for your instances using *key pairs* \(AWS stores the public key, and you store the private key in a secure place\)
+ Storage volumes for temporary data that's deleted when you stop or terminate your instance, known as *instance store volumes*
+ Persistent storage volumes for your data using Amazon Elastic Block Store \(Amazon EBS\), known as *Amazon EBS volumes*
+ Multiple physical locations for your resources, such as instances and Amazon EBS volumes, known as *Regions* and *Availability Zones*
+ A firewall that enables you to specify the protocols, ports, and source IP ranges that can reach your instances using *security groups*
+ Static IPv4 addresses for dynamic cloud computing, known as *Elastic IP addresses*
+ Metadata, known as *tags*, that you can create and assign to your Amazon EC2 resources
+ Virtual networks you can create that are logically isolated from the rest of the AWS cloud, and that you can optionally connect to your own network, known as *virtual private clouds* \(VPCs\)
For more information about the features of Amazon EC2, see the [Amazon EC2 product page](https://aws.amazon.com/ec2)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/concepts.md |
f35621a38808-1 | For more information about the features of Amazon EC2, see the [Amazon EC2 product page](https://aws.amazon.com/ec2)\.
For more information about running your website on AWS, see [Web Hosting](https://aws.amazon.com/websites/)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/concepts.md |
55165c409787-0 | First, you need to get set up to use Amazon EC2\. After you are set up, you are ready to complete the Getting Started tutorial for Amazon EC2\. Whenever you need more information about an Amazon EC2 feature, you can read the technical documentation\.
**Get up and running**
+ [Setting up with Amazon EC2](get-set-up-for-amazon-ec2.md)
+ [Tutorial: Getting started with Amazon EC2 Linux instances](EC2_GetStarted.md)
**Basics**
+ [Instances and AMIs](ec2-instances-and-amis.md)
+ [Regions and Availability Zones](using-regions-availability-zones.md)
+ [Instance types](instance-types.md)
+ [Tags](Using_Tags.md)
**Networking and security**
+ [Amazon EC2 key pairs and Linux instances](ec2-key-pairs.md)
+ [Security Groups](ec2-security-groups.md)
+ [Elastic IP addresses](elastic-ip-addresses-eip.md)
+ [Amazon EC2 and Amazon VPC](using-vpc.md)
**Storage**
+ [Amazon EBS](AmazonEBS.md)
+ [Instance Store](InstanceStorage.md)
**Working with Linux instances** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/concepts.md |
55165c409787-1 | + [Instance Store](InstanceStorage.md)
**Working with Linux instances**
+ [AWS Systems Manager Run Command](https://docs.aws.amazon.com/systems-manager/latest/userguide/execute-remote-commands.html) in the *AWS Systems Manager User Guide*
+ [Tutorial: Install a LAMP web server on Amazon Linux 2](ec2-lamp-amazon-linux-2.md)
+ [Tutorial: Configure SSL/TLS on Amazon Linux 2](SSL-on-amazon-linux-2.md)
+ [Getting Started with AWS: Hosting a Web App for Linux](https://docs.aws.amazon.com/gettingstarted/latest/wah-linux/)
If you have questions about whether AWS is right for you, [contact AWS Sales](https://aws.amazon.com/contact-us/)\. If you have technical questions about Amazon EC2, use the [Amazon EC2 forum](https://forums.aws.amazon.com/forum.jspa?forumID=30)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/concepts.md |
5ffdfec352c6-0 | You can provision Amazon EC2 resources, such as instances and volumes, directly using Amazon EC2\. You can also provision Amazon EC2 resources using other services in AWS\. For more information, see the following documentation:
+ [Amazon EC2 Auto Scaling User Guide](https://docs.aws.amazon.com/autoscaling/ec2/userguide/)
+ [AWS CloudFormation User Guide](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/)
+ [AWS Elastic Beanstalk Developer Guide](https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/)
+ [AWS OpsWorks User Guide](https://docs.aws.amazon.com/opsworks/latest/userguide/)
To automatically distribute incoming application traffic across multiple instances, use Elastic Load Balancing\. For more information, see the [Elastic Load Balancing User Guide](https://docs.aws.amazon.com/elasticloadbalancing/latest/userguide/)\.
To get a managed relational database in the cloud, use Amazon Relational Database Service \(Amazon RDS\) to launch a database instance\. Although you can set up a database on an EC2 instance, Amazon RDS offers the advantage of handling your database management tasks, such as patching the software, backing up, and storing the backups\. For more information, see the [Amazon Relational Database Service Developer Guide](https://docs.aws.amazon.com/AmazonRDS/latest/DeveloperGuide/)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/concepts.md |
5ffdfec352c6-1 | To make it easier to manage Docker containers on a cluster of EC2 instances, use Amazon Elastic Container Service \(Amazon ECS\)\. For more information, see the [Amazon Elastic Container Service Developer Guide](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/) or the [Amazon Elastic Container Service User Guide for AWS Fargate](https://docs.aws.amazon.com/AmazonECS/latest/userguide/)\.
To monitor basic statistics for your instances and Amazon EBS volumes, use Amazon CloudWatch\. For more information, see the [Amazon CloudWatch User Guide](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/)\. To detect potentially authorized or malicious use of your EC2 instances, use Amazon GuardDuty\. For more information see the [Amazon GuardDuty User Guide](https://docs.aws.amazon.com/guardduty/latest/ug/)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/concepts.md |
c9baa8af5a6f-0 | Amazon EC2 provides a web\-based user interface, the Amazon EC2 console\. If you've signed up for an AWS account, you can access the Amazon EC2 console by signing into the AWS Management Console and selecting **EC2** from the console home page\.
If you prefer to use a command line interface, you have the following options:
**AWS Command Line Interface \(CLI\)**
Provides commands for a broad set of AWS products, and is supported on Windows, Mac, and Linux\. To get started, see [AWS Command Line Interface User Guide](https://docs.aws.amazon.com/cli/latest/userguide/)\. For more information about the commands for Amazon EC2, see [ec2](https://docs.aws.amazon.com/cli/latest/reference/ec2/index.html) in the *AWS CLI Command Reference*\.
**AWS Tools for Windows PowerShell**
Provides commands for a broad set of AWS products for those who script in the PowerShell environment\. To get started, see the [AWS Tools for Windows PowerShell User Guide](https://docs.aws.amazon.com/powershell/latest/userguide/)\. For more information about the cmdlets for Amazon EC2, see the [AWS Tools for PowerShell Cmdlet Reference](https://docs.aws.amazon.com/powershell/latest/reference/Index.html)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/concepts.md |
c9baa8af5a6f-1 | Amazon EC2 provides a Query API\. These requests are HTTP or HTTPS requests that use the HTTP verbs GET or POST and a Query parameter named `Action`\. For more information about the API actions for Amazon EC2, see [Actions](https://docs.aws.amazon.com/AWSEC2/latest/APIReference/query-apis.html) in the *Amazon EC2 API Reference*\.
If you prefer to build applications using language\-specific APIs instead of submitting a request over HTTP or HTTPS, AWS provides libraries, sample code, tutorials, and other resources for software developers\. These libraries provide basic functions that automate tasks such as cryptographically signing your requests, retrying requests, and handling error responses, making it is easier for you to get started\. For more information, see [AWS SDKs and Tools](https://aws.amazon.com/tools/)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/concepts.md |
f3138b66da66-0 | When you sign up for AWS, you can get started with Amazon EC2 for free using the [AWS Free Tier](https://aws.amazon.com/free/)\.
Amazon EC2 provides the following purchasing options for instances:
**On\-Demand Instances**
Pay for the instances that you use by the second, with no long\-term commitments or upfront payments\.
**Savings Plans**
You can reduce your Amazon EC2 costs by making a commitment to a consistent amount of usage, in USD per hour, for a term of 1 or 3 years\.
**Reserved Instances**
You can reduce your Amazon EC2 costs by making a commitment to a specific instance configuration, including instance type and Region, for a term of 1 or 3 years\.
**Spot Instances**
Request unused EC2 instances, which can reduce your Amazon EC2 costs significantly\.
For a complete list of charges and prices for Amazon EC2, see [Amazon EC2 Pricing](https://aws.amazon.com/ec2/pricing)\.
To calculate the cost of a sample provisioned environment, see [Cloud Economics Center](https://aws.amazon.com/economics/)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/concepts.md |
f3138b66da66-1 | To calculate the cost of a sample provisioned environment, see [Cloud Economics Center](https://aws.amazon.com/economics/)\.
To see your bill, go to the **Billing and Cost Management Dashboard** in the [AWS Billing and Cost Management console](https://console.aws.amazon.com/billing/)\. Your bill contains links to usage reports that provide details about your bill\. To learn more about AWS account billing, see [AWS Account Billing](https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/)\.
If you have questions concerning AWS billing, accounts, and events, [contact AWS Support](https://aws.amazon.com/contact-us/)\.
For an overview of Trusted Advisor, a service that helps you optimize the costs, security, and performance of your AWS environment, see [AWS Trusted Advisor](https://aws.amazon.com/premiumsupport/trustedadvisor/)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/concepts.md |
3994b4d8f54b-0 | Amazon EC2 supports the processing, storage, and transmission of credit card data by a merchant or service provider, and has been validated as being compliant with Payment Card Industry \(PCI\) Data Security Standard \(DSS\)\. For more information about PCI DSS, including how to request a copy of the AWS PCI Compliance Package, see [PCI DSS Level 1](https://aws.amazon.com/compliance/pci-dss-level-1-faqs/)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/concepts.md |
cc4cc5466ca3-0 | Amazon EC2 provides enhanced networking capabilities through the Elastic Network Adapter \(ENA\)\. To use enhanced networking, you must install the required ENA module and enable ENA support\.
**Topics**
+ [Requirements](#ena-requirements)
+ [Enhanced networking performance](#ena-performance)
+ [Testing whether enhanced networking is enabled](#test-enhanced-networking-ena)
+ [Enabling enhanced networking on the Amazon Linux AMI](#enable-enhanced-networking-ena-AL)
+ [Enabling enhanced networking on Ubuntu](#enhanced-networking-ena-ubuntu)
+ [Enabling enhanced networking on Linux](#enhanced-networking-ena-linux)
+ [Enabling enhanced networking on Ubuntu with DKMS](#enhanced-networking-ena-ubuntu-dkms)
+ [Troubleshooting](#enhanced-networking-ena-troubleshooting)
+ [Operating system optimizations](enhanced-networking-os.md) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/enhanced-networking-ena.md |
bfb8ce48bdf4-0 | To prepare for enhanced networking using the ENA, set up your instance as follows:
+ Launch the instance using a [current generation](instance-types.md#current-gen-instances) instance type, other than an M4 instance smaller than `m4.16xlarge`\.
+ Launch the instance using a supported version of the Linux kernel and a supported distribution, so that ENA enhanced networking is enabled for your instance automatically\. For more information, see [ENA Linux Kernel Driver Release Notes](https://github.com/amzn/amzn-drivers/blob/master/kernel/linux/ena/RELEASENOTES.md)\.
+ 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/enhanced-networking-ena.md |
bfb8ce48bdf4-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 `enaSupport` 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/enhanced-networking-ena.md |
d793f8855b66-0 | The following documentation provides a summary of the network performance for the instance types that support ENA enhanced networking:
+ [Network Performance for Accelerated Computing Instances](accelerated-computing-instances.md#gpu-network-performance)
+ [Network Performance for Compute Optimized Instances](compute-optimized-instances.md#compute-network-performance)
+ [Network Performance for General Purpose Instances](general-purpose-instances.md#general-purpose-network-performance)
+ [Network Performance for Memory Optimized Instances](memory-optimized-instances.md#memory-network-perf)
+ [Network Performance for Storage Optimized Instances](storage-optimized-instances.md#storage-network-performance) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/enhanced-networking-ena.md |
14e83e04001c-0 | The following AMIs include the required ENA module and have ENA support enabled:
+ Amazon Linux 2
+ Amazon Linux AMI 2018\.03
+ Ubuntu 14\.04 \(with `linux-aws` kernel\) or later
+ Red Hat Enterprise Linux 7\.4 or later
+ SUSE Linux Enterprise Server 12 SP2 or later
+ CentOS 7\.4\.1708 or later
+ FreeBSD 11\.1 or later
+ Debian GNU/Linux 9 or later
To test whether enhanced networking is already enabled, verify that the `ena` module is installed on your instance and that the `enaSupport` attribute is set\. If your instance satisfies these two conditions, then the ethtool \-i eth*n* command should show that the module is in use on the network interface\.
**Kernel module \(ena\)**
To verify that the `ena` module is installed, use the modinfo command as shown in the following example\.
```
[ec2-user ~]$ modinfo ena
filename: /lib/modules/4.14.33-59.37.amzn2.x86_64/kernel/drivers/amazon/net/ena/ena.ko
version: 1.5.0g
license: GPL
description: Elastic Network Adapter (ENA)
author: Amazon.com, Inc. or its affiliates | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/enhanced-networking-ena.md |
14e83e04001c-1 | license: GPL
description: Elastic Network Adapter (ENA)
author: Amazon.com, Inc. or its affiliates
srcversion: 692C7C68B8A9001CB3F31D0
alias: pci:v00001D0Fd0000EC21sv*sd*bc*sc*i*
alias: pci:v00001D0Fd0000EC20sv*sd*bc*sc*i*
alias: pci:v00001D0Fd00001EC2sv*sd*bc*sc*i*
alias: pci:v00001D0Fd00000EC2sv*sd*bc*sc*i*
depends:
retpoline: Y
intree: Y
name: ena
...
```
In the above Amazon Linux case, the `ena` module is installed\.
```
ubuntu:~$ modinfo ena
ERROR: modinfo: could not find module ena
```
In the above Ubuntu instance, the module is not installed, so you must first install it\. For more information, see [Enabling enhanced networking on Ubuntu](#enhanced-networking-ena-ubuntu)\.
**Instance attribute \(enaSupport\)** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/enhanced-networking-ena.md |
14e83e04001c-2 | **Instance attribute \(enaSupport\)**
To check whether an instance has the enhanced networking `enaSupport` attribute set, use one of the following commands\. If the attribute is set, the response is true\.
+ [describe\-instances](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-instances.html) \(AWS CLI\)
```
aws ec2 describe-instances --instance-ids instance_id --query "Reservations[].Instances[].EnaSupport"
```
+ [Get\-EC2Instance](https://docs.aws.amazon.com/powershell/latest/reference/items/Get-EC2Instance.html) \(Tools for Windows PowerShell\)
```
(Get-EC2Instance -InstanceId instance-id).Instances.EnaSupport
```
**Image attribute \(enaSupport\)**
To check whether an AMI has the enhanced networking `enaSupport` attribute set, use one of the following commands\. If the attribute is set, the response is true\.
+ [describe\-images](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-images.html) \(AWS CLI\)
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/enhanced-networking-ena.md |
14e83e04001c-3 | ```
aws ec2 describe-images --image-id ami_id --query "Images[].EnaSupport"
```
+ [Get\-EC2Image](https://docs.aws.amazon.com/powershell/latest/reference/items/Get-EC2Image.html) \(Tools for Windows PowerShell\)
```
(Get-EC2Image -ImageId ami_id).EnaSupport
```
**Network interface driver**
Use the following command to verify that the `ena` 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\), it this is `eth0`\. If the operating system supports [predictable network names](#predictable-network-names-ena), this could be a name like `ens5`\.
In the following example, the `ena` 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
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/enhanced-networking-ena.md |
14e83e04001c-4 | supports-register-dump: no
supports-priv-flags: no
```
In this example, the `ena` module is loaded and at the minimum recommended version\. This instance has enhanced networking properly configured\.
```
[ec2-user ~]$ ethtool -i eth0
driver: ena
version: 1.5.0g
firmware-version:
expansion-rom-version:
bus-info: 0000:00:05.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: no
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/enhanced-networking-ena.md |
33e9f7dffbd5-0 | Amazon Linux 2 and the latest versions of the Amazon Linux AMI include the module required for enhanced networking with ENA installed and have ENA support enabled\. Therefore, if you launch an instance with an HVM version of Amazon Linux on a supported instance type, enhanced networking is already enabled for your instance\. For more information, see [Testing whether enhanced networking is enabled](#test-enhanced-networking-ena)\.
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\.
**To enable enhanced networking on Amazon Linux AMI**
1. <a name="amazon-linux-enhanced-networking-ena-start-step-AL"></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 `ena`:
```
[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/enhanced-networking-ena.md |
33e9f7dffbd5-1 | 1. <a name="amazon-linux-enhanced-networking-ena-stop-step-AL"></a>Connect to your instance again and verify that the `ena` module is installed and at the minimum recommended version using the modinfo ena command from [Testing whether enhanced networking is enabled](#test-enhanced-networking-ena)\.
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 on Amazon Linux AMI \(instance store\-backed instances\)](#enhanced-networking-ena-instance-store-AL)\.
1. From your local computer, enable the enhanced networking attribute using one of the following commands: | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/enhanced-networking-ena.md |
33e9f7dffbd5-2 | 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 --ena-support
```
+ [Edit\-EC2InstanceAttribute](https://docs.aws.amazon.com/powershell/latest/reference/items/Edit-EC2InstanceAttribute.html) \(Tools for Windows PowerShell\)
```
Edit-EC2InstanceAttribute -InstanceId instance-id -EnaSupport $true
```
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 `enaSupport` attribute from the instance\. Therefore, you can use this AMI to launch another instance with enhanced networking enabled by default\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/enhanced-networking-ena.md |
33e9f7dffbd5-3 | 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. Connect to your instance and verify that the `ena` 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-ena)\.
If you are unable to connect to your instance after enabling enhanced networking, see [Troubleshooting the Elastic Network Adapter \(ENA\)](troubleshooting-ena.md)\.<a name="enhanced-networking-ena-instance-store-AL"></a>
**To enable enhanced networking on Amazon Linux AMI \(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\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/enhanced-networking-ena.md |
33e9f7dffbd5-4 | + [register\-image](https://docs.aws.amazon.com/cli/latest/reference/ec2/register-image.html) \(AWS CLI\)
```
aws ec2 register-image --ena-support ...
```
+ [Register\-EC2Image](https://docs.aws.amazon.com/powershell/latest/reference/items/Register-EC2Image.html) \(AWS Tools for Windows PowerShell\)
```
Register-EC2Image -EnaSupport $true ...
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/enhanced-networking-ena.md |
dd9426dc2801-0 | The latest Ubuntu HVM AMIs include the module required for enhanced networking with ENA installed and have ENA support enabled\. Therefore, if you launch an instance with the latest Ubuntu HVM AMI on a supported instance type, enhanced networking is already enabled for your instance\. For more information, see [Testing whether enhanced networking is enabled](#test-enhanced-networking-ena)\.
If you launched your instance using an older AMI and it does not have enhanced networking enabled already, you can install the `linux-aws` kernel package to get the latest enhanced networking drivers and update the required attribute\.
**To install the linux\-aws kernel package \(Ubuntu 16\.04 or later\)**
Ubuntu 16\.04 and 18\.04 ship with the Ubuntu custom kernel \(linux\-aws kernel package\)\. To use a different kernel, contact [AWS Support](https://console.aws.amazon.com/support)\.<a name="ubuntu-enhanced-networking-ena-procedure"></a>
**To install the linux\-aws kernel package \(Ubuntu Trusty 14\.04\)**
1. <a name="ubuntu-enhanced-networking-ena-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
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/enhanced-networking-ena.md |
dd9426dc2801-1 | 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` onto, and then choose to keep the current version of `/boot/grub/menu.lst`\.
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 on Ubuntu \(instance store\-backed instances\)](#enhanced-networking-ena-instance-store-ubuntu)\.
1. From your local computer, enable the enhanced networking attribute using one of the following commands: | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/enhanced-networking-ena.md |
dd9426dc2801-2 | 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 --ena-support
```
+ [Edit\-EC2InstanceAttribute](https://docs.aws.amazon.com/powershell/latest/reference/items/Edit-EC2InstanceAttribute.html) \(Tools for Windows PowerShell\)
```
Edit-EC2InstanceAttribute -InstanceId instance-id -EnaSupport $true
```
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 `enaSupport` attribute from the instance\. Therefore, you can use this AMI to launch another instance with enhanced networking enabled by default\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/enhanced-networking-ena.md |
dd9426dc2801-3 | 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\.<a name="enhanced-networking-ena-instance-store-ubuntu"></a>
**To enable enhanced networking on Ubuntu \(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 --ena-support ...
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/enhanced-networking-ena.md |
dd9426dc2801-4 | ```
aws ec2 register-image --ena-support ...
```
+ [Register\-EC2Image](https://docs.aws.amazon.com/powershell/latest/reference/items/Register-EC2Image.html) \(AWS Tools for Windows PowerShell\)
```
Register-EC2Image -EnaSupport $true ...
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/enhanced-networking-ena.md |
f4079ad1b4e9-0 | The latest AMIs for Red Hat Enterprise Linux, SUSE Linux Enterprise Server, and CentOS include the module required for enhanced networking with ENA and have ENA support enabled\. Therefore, if you launch an instance with the latest AMI on a supported instance type, enhanced networking is already enabled for your instance\. For more information, see [Testing whether enhanced networking is enabled](#test-enhanced-networking-ena)\.
The following procedure provides the general steps for enabling enhanced networking on a Linux distribution other than Amazon Linux AMI or Ubuntu\. For more information, such as detailed syntax for commands, file locations, or package and tool support, see the documentation for your Linux distribution\.
**To enable enhanced networking on Linux**
1. <a name="other-linux-enhanced-networking-ena-start-step"></a>Connect to your instance\.
1. Clone the source code for the `ena` module on your instance from GitHub at [https://github.com/amzn/amzn-drivers](https://github.com/amzn/amzn-drivers)\. \(SUSE Linux Enterprise Server 12 SP2 and later include ENA 2\.02 by default, so you are not required to download and compile the ENA driver\. For SUSE Linux Enterprise Server 12 SP2 and later, you should file a request to add the driver version you want to the stock kernel\)\.
```
git clone https://github.com/amzn/amzn-drivers
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/enhanced-networking-ena.md |
f4079ad1b4e9-1 | ```
git clone https://github.com/amzn/amzn-drivers
```
1. Compile and install the `ena` module on your instance\. These steps depend on the Linux distribution\. For more information about compiling the module on Red Hat Enterprise Linux, see the [AWS Knowledge Center article](http://aws.amazon.com/premiumsupport/knowledge-center/install-ena-driver-rhel-ec2/)\.
1. Run the sudo depmod command to update module dependencies\.
1. <a name="other-linux-enhanced-networking-ena-stop-step"></a>Update `initramfs` on your instance to ensure that the new module loads at boot time\. For example, if your distribution supports dracut, you can use the following command\.
```
dracut -f -v
```
1. <a name="predictable-network-names-ena"></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\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/enhanced-networking-ena.md |
f4079ad1b4e9-2 | 1. You can check the systemd or udev versions on RPM\-based systems with the following command\.
```
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`\.
```
sudo sed -i '/^GRUB\_CMDLINE\_LINUX/s/\"$/\ net\.ifnames\=0\"/' /etc/default/grub
```
1. Rebuild the grub configuration file\.
```
sudo grub2-mkconfig -o /boot/grub2/grub.cfg
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/enhanced-networking-ena.md |
f4079ad1b4e9-3 | ```
sudo grub2-mkconfig -o /boot/grub2/grub.cfg
```
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 on Linux \(instance store–backed instances\)](#other-linux-enhanced-networking-ena-instance-store)\.
1. From your local computer, enable the enhanced networking `enaSupport` 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 --ena-support | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/enhanced-networking-ena.md |
f4079ad1b4e9-4 | ```
aws ec2 modify-instance-attribute --instance-id instance_id --ena-support
```
+ [Edit\-EC2InstanceAttribute](https://docs.aws.amazon.com/powershell/latest/reference/items/Edit-EC2InstanceAttribute.html) \(Tools for Windows PowerShell\)
```
Edit-EC2InstanceAttribute -InstanceId instance-id -EnaSupport $true
```
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 `enaSupport` 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/enhanced-networking-ena.md |
f4079ad1b4e9-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\.
If you are unable to connect to your instance after enabling enhanced networking, see [Troubleshooting the Elastic Network Adapter \(ENA\)](troubleshooting-ena.md)\.<a name="other-linux-enhanced-networking-ena-instance-store"></a>
**To enable enhanced networking on Linux \(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\)
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/enhanced-networking-ena.md |
f4079ad1b4e9-6 | ```
aws ec2 register-image --ena-support ...
```
+ [Register\-EC2Image](https://docs.aws.amazon.com/powershell/latest/reference/items/Register-EC2Image.html) \(AWS Tools for Windows PowerShell\)
```
Register-EC2Image -EnaSupport ...
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/enhanced-networking-ena.md |
2140563ff1e3-0 | This method is for testing and feedback purposes only\. It is not intended for use with production deployments\. For production deployments, see [Enabling enhanced networking on Ubuntu](#enhanced-networking-ena-ubuntu)\.
**Important**
Using DKMS voids the support agreement for your subscription\. It should not be used for production deployments\.
**To enable enhanced networking with ENA on Ubuntu \(EBS\-backed instances\)**
1. Follow steps 1 and 2 in [Enabling enhanced networking on Ubuntu](#enhanced-networking-ena-ubuntu)\.
1. Install the `build-essential` packages to compile the kernel module and the `dkms` package so that your `ena` module is rebuilt every time your kernel is updated\.
```
ubuntu:~$ sudo apt-get install -y build-essential dkms
```
1. Clone the source for the `ena` module on your instance from GitHub at [https://github.com/amzn/amzn-drivers](https://github.com/amzn/amzn-drivers)\.
```
ubuntu:~$ git clone https://github.com/amzn/amzn-drivers
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/enhanced-networking-ena.md |
2140563ff1e3-1 | ubuntu:~$ git clone https://github.com/amzn/amzn-drivers
```
1. Move the `amzn-drivers` package to the `/usr/src/` directory so DKMS can find it and build it for each kernel update\. Append the version number \(you can find the current version number in the release notes\) of the source code to the directory name\. For example, version `1.0.0` is shown in the following example\.
```
ubuntu:~$ sudo mv amzn-drivers /usr/src/amzn-drivers-1.0.0
```
1. Create the DKMS configuration file with the following values, substituting your version of `ena`\.
Create the file\.
```
ubuntu:~$ sudo touch /usr/src/amzn-drivers-1.0.0/dkms.conf
```
Edit the file and add the following values\.
```
ubuntu:~$ sudo vim /usr/src/amzn-drivers-1.0.0/dkms.conf
PACKAGE_NAME="ena"
PACKAGE_VERSION="1.0.0"
CLEAN="make -C kernel/linux/ena clean" | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/enhanced-networking-ena.md |
2140563ff1e3-2 | PACKAGE_VERSION="1.0.0"
CLEAN="make -C kernel/linux/ena clean"
MAKE="make -C kernel/linux/ena/ BUILD_KERNEL=${kernelver}"
BUILT_MODULE_NAME[0]="ena"
BUILT_MODULE_LOCATION="kernel/linux/ena"
DEST_MODULE_LOCATION[0]="/updates"
DEST_MODULE_NAME[0]="ena"
AUTOINSTALL="yes"
```
1. Add, build, and install the `ena` module on your instance using DKMS\.
Add the module to DKMS\.
```
ubuntu:~$ sudo dkms add -m amzn-drivers -v 1.0.0
```
Build the module using the dkms command\.
```
ubuntu:~$ sudo dkms build -m amzn-drivers -v 1.0.0
```
Install the module using dkms\.
```
ubuntu:~$ sudo dkms install -m amzn-drivers -v 1.0.0
```
1. Rebuild `initramfs` so the correct module is loaded at boot time\.
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/enhanced-networking-ena.md |
2140563ff1e3-3 | ```
1. Rebuild `initramfs` so the correct module is loaded at boot time\.
```
ubuntu:~$ sudo update-initramfs -u -k all
```
1. Verify that the `ena` module is installed using the modinfo ena command from [Testing whether enhanced networking is enabled](#test-enhanced-networking-ena)\.
```
ubuntu:~$ modinfo ena
filename: /lib/modules/3.13.0-74-generic/updates/dkms/ena.ko
version: 1.0.0
license: GPL
description: Elastic Network Adapter (ENA)
author: Amazon.com, Inc. or its affiliates
srcversion: 9693C876C54CA64AE48F0CA
alias: pci:v00001D0Fd0000EC21sv*sd*bc*sc*i*
alias: pci:v00001D0Fd0000EC20sv*sd*bc*sc*i*
alias: pci:v00001D0Fd00001EC2sv*sd*bc*sc*i*
alias: pci:v00001D0Fd00000EC2sv*sd*bc*sc*i*
depends: | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/enhanced-networking-ena.md |
2140563ff1e3-4 | alias: pci:v00001D0Fd00000EC2sv*sd*bc*sc*i*
depends:
vermagic: 3.13.0-74-generic SMP mod_unload modversions
parm: debug:Debug level (0=none,...,16=all) (int)
parm: push_mode:Descriptor / header push mode (0=automatic,1=disable,3=enable)
0 - Automatically choose according to device capability (default)
1 - Don't push anything to device memory
3 - Push descriptors and header buffer to device memory (int)
parm: enable_wd:Enable keepalive watchdog (0=disable,1=enable,default=1) (int)
parm: enable_missing_tx_detection:Enable missing Tx completions. (default=1) (int)
parm: numa_node_override_array:Numa node override map
(array of int)
parm: numa_node_override:Enable/Disable numa node override (0=disable)
(int)
```
1. Continue with Step 3 in [Enabling enhanced networking on Ubuntu](#enhanced-networking-ena-ubuntu)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/enhanced-networking-ena.md |
9b30736d36a7-0 | For additional information about troubleshooting your ENA adapter, see [Troubleshooting the Elastic Network Adapter \(ENA\)](troubleshooting-ena.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/enhanced-networking-ena.md |
b4b6fd885543-0 | It is important to keep software up\-to\-date\. Many packages in a Linux distribution are updated frequently to fix bugs, add features, and protect against security exploits\. When you first launch and connect to an Amazon Linux instance, you may see a message asking you to update software packages for security purposes\. This section shows how to update an entire system, or just a single package\.
**Important**
This information applies to Amazon Linux\. For information about other distributions, see their specific documentation\.
**To update all packages on an Amazon Linux instance**
1. \(Optional\) Start a screen session in your shell window\. Sometimes you may experience a network interruption that can disconnect the SSH connection to your instance\. If this happens during a long software update, it can leave the instance in a recoverable, although confused state\. A screen session allows you to continue running the update even if your connection is interrupted, and you can reconnect to the session later without problems\.
1. Execute the screen command to begin the session\.
```
[ec2-user ~]$ screen
```
1. If your session is disconnected, log back into your instance and list the available screens\.
```
[ec2-user ~]$ screen -ls
There is a screen on:
17793.pts-0.ip-12-34-56-78 (Detached)
1 Socket in /var/run/screen/S-ec2-user.
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/install-updates.md |
b4b6fd885543-1 | 1 Socket in /var/run/screen/S-ec2-user.
```
1. Reconnect to the screen using the screen \-r command and the process ID from the previous command\.
```
[ec2-user ~]$ screen -r 17793
```
1. When you are finished using screen, use the exit command to close the session\.
```
[ec2-user ~]$ exit
[screen is terminating]
```
1. Run the yum update command\. Optionally, you can add the `--security` flag to apply only security updates\.
```
[ec2-user ~]$ sudo yum update
```
1. Review the packages listed, type **y**, and press Enter to accept the updates\. Updating all of the packages on a system can take several minutes\. The yum output shows the status of the update while it is running\.
1. \(Optional\) Reboot your instance to ensure that you are using the latest packages and libraries from your update; kernel updates are not loaded until a reboot occurs\. Updates to any `glibc` libraries should also be followed by a reboot\. For updates to packages that control services, it may be sufficient to restart the services to pick up the updates, but a system reboot ensures that all previous package and library updates are complete\.
**To update a single package on an Amazon Linux instance** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/install-updates.md |
b4b6fd885543-2 | **To update a single package on an Amazon Linux instance**
Use this procedure to update a single package \(and its dependencies\) and not the entire system\.
1. Run the yum update command with the name of the package you would like to update\.
```
[ec2-user ~]$ sudo yum update openssl
```
1. Review the package information listed, type **y**, and press Enter to accept the update or updates\. Sometimes there will be more than one package listed if there are package dependencies that must be resolved\. The yum output shows the status of the update while it is running\.
1. \(Optional\) Reboot your instance to ensure that you are using the latest packages and libraries from your update; kernel updates are not loaded until a reboot occurs\. Updates to any `glibc` libraries should also be followed by a reboot\. For updates to packages that control services, it may be sufficient to restart the services to pick up the updates, but a system reboot ensures that all previous package and library updates are complete\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/install-updates.md |
28387828547c-0 | EBS volumes are exposed as NVMe block devices on instances built on the [Nitro System](instance-types.md#ec2-nitro-instances)\. The device names are `/dev/nvme0n1`, `/dev/nvme1n1`, and so on\. The device names that you specify in a block device mapping are renamed using NVMe device names \(`/dev/nvme[0-26]n1`\)\. The block device driver can assign NVMe device names in a different order than you specified for the volumes in the block device mapping\.
The EBS performance guarantees stated in [Amazon EBS Product Details](http://aws.amazon.com/ebs/details/) are valid regardless of the block\-device interface\.
**Topics**
+ [Install or upgrade the NVMe driver](#install-nvme-driver)
+ [Identifying the EBS device](#identify-nvme-ebs-device)
+ [Working with NVMe EBS volumes](#using-nvme-ebs-volumes)
+ [I/O operation timeout](#timeout-nvme-ebs-volumes) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/nvme-ebs-volumes.md |
9aae45bae43e-0 | To access NVMe volumes, the NVMe drivers must be installed\. Instances can support NVMe EBS volumes, NVMe instance store volumes, both types of NVMe volumes, or no NVMe volumes\. For more information, see [Summary of networking and storage features](instance-types.md#instance-type-summary-table)\.
The following AMIs include the required NVMe drivers:
+ Amazon Linux 2
+ Amazon Linux AMI 2018\.03
+ Ubuntu 14\.04 \(with `linux-aws` kernel\) or later
+ Red Hat Enterprise Linux 7\.4 or later
+ SUSE Linux Enterprise Server 12 SP2 or later
+ CentOS 7\.4\.1708 or later
+ FreeBSD 11\.1 or later
+ Debian GNU/Linux 9 or later
For more information about NVMe drivers on Windows instances, see [Amazon EBS and NVMe on Windows Instances](https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/nvme-ebs-volumes.html) in the *Amazon EC2 User Guide for Windows Instances*\.
**To confirm that your instance has the NVMe driver**
You can confirm that your instance has the NVMe driver and check the driver version using the following command\. If the instance has the NVMe driver, the command returns information about the driver\.
```
$ modinfo nvme
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/nvme-ebs-volumes.md |
9aae45bae43e-1 | ```
$ modinfo nvme
```
**To update the NVMe driver**
If your instance has the NVMe driver, you can update the driver to the latest version using the following procedure\.
1. Connect to your instance\.
1. Update your package cache to get necessary package updates as follows\.
+ For Amazon Linux 2, Amazon Linux, CentOS, and Red Hat Enterprise Linux:
```
[ec2-user ~]$ sudo yum update -y
```
+ For Ubuntu and Debian:
```
[ec2-user ~]$ sudo apt-get update -y
```
1. Ubuntu 16\.04 and later include the `linux-aws` package, which contains the NVMe and ENA drivers required by Nitro\-based instances\. Upgrade the `linux-aws` package to receive the latest version as follows:
```
[ec2-user ~]$ sudo apt-get install --only-upgrade -y linux-aws
```
For Ubuntu 14\.04, you can install the latest `linux-aws` package as follows:
```
[ec2-user ~]$ sudo apt-get install linux-aws
```
1. Reboot your instance to load the latest kernel version\.
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/nvme-ebs-volumes.md |
9aae45bae43e-2 | ```
1. Reboot your instance to load the latest kernel version\.
```
sudo reboot
```
1. Reconnect to your instance after it has rebooted\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/nvme-ebs-volumes.md |
3931ff0f6fb9-0 | EBS uses single\-root I/O virtualization \(SR\-IOV\) to provide volume attachments on Nitro\-based instances using the NVMe specification\. These devices rely on standard NVMe drivers on the operating system\. These drivers typically discover attached devices by scanning the PCI bus during instance boot, and create device nodes based on the order in which the devices respond, not on how the devices are specified in the block device mapping\. In Linux, NVMe device names follow the pattern `/dev/nvme<x>n<y>`, where <x> is the enumeration order, and, for EBS, <y> is 1\. Occasionally, devices can respond to discovery in a different order in subsequent instance starts, which causes the device name to change\.
We recommend that you use stable identifiers for your EBS volumes within your instance, such as one of the following:
+ For Nitro\-based instances, the block device mappings that are specified in the Amazon EC2 console when you are attaching an EBS volume or during `AttachVolume` or `RunInstances` API calls are captured in the vendor\-specific data field of the NVMe controller identification\. With Amazon Linux AMIs later than version 2017\.09\.01, we provide a `udev` rule that reads this data and creates a symbolic link to the block\-device mapping\.
+ NVMe EBS volumes have the EBS volume ID set as the serial number in the device identification\. Use the `lsblk -o +SERIAL` command to list the serial number\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/nvme-ebs-volumes.md |
3931ff0f6fb9-1 | + When a device is formatted, a UUID is generated that persists for the life of the filesystem\. A device label can be specified at the same time\. For more information, see [Making an Amazon EBS volume available for use on Linux](ebs-using-volumes.md) and [Booting from the wrong volume](instance-booting-from-wrong-volume.md)\.
**Amazon Linux AMIs**
With Amazon Linux AMI 2017\.09\.01 or later \(including Amazon Linux 2\), you can run the ebsnvme\-id command as follows to map the NVMe device name to a volume ID and device name:
```
[ec2-user ~]$ sudo /sbin/ebsnvme-id /dev/nvme1n1
Volume ID: vol-01324f611e2463981
/dev/sdf
```
Amazon Linux also creates a symbolic link from the device name in the block device mapping \(for example, `/dev/sdf`\), to the NVMe device name\.
**FreeBSD AMIs** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/nvme-ebs-volumes.md |
3931ff0f6fb9-2 | **FreeBSD AMIs**
Starting with FreeBSD 12\.2\-RELEASE, you can run the ebsnvme\-id command as shown above\. Pass either the name of the NVMe device \(for example, `nvme0`\) or the disk device \(for example, `nvd0` or `nda0`\)\. FreeBSD also creates symbolic links to the disk devices \(for example, `/dev/aws/disk/ebs/`*volume\_id*\)\.
**Other Linux AMIs**
With a kernel version of 4\.2 or later, you can run the nvme id\-ctrl command as follows to map an NVMe device to a volume ID\. First, install the NVMe command line package, `nvme-cli`, using the package management tools for your Linux distribution\. For download and installation instructions for other distributions, refer to the documentation specific to your distribution\.
The following example gets the volume ID and device name\. The device name is available through the NVMe controller vendor\-specific extension \(bytes 384:4095 of the controller identification\):
```
[ec2-user ~]$ sudo nvme id-ctrl -v /dev/nvme1n1
NVME Identify Controller:
vid : 0x1d0f
ssvid : 0x1d0f
sn : vol01234567890abcdef
mn : Amazon Elastic Block Store
... | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/nvme-ebs-volumes.md |
3931ff0f6fb9-3 | sn : vol01234567890abcdef
mn : Amazon Elastic Block Store
...
0000: 2f 64 65 76 2f 73 64 6a 20 20 20 20 20 20 20 20 "/dev/sdf..."
```
The lsblk command lists available devices and their mount points \(if applicable\)\. This helps you determine the correct device name to use\. In this example, `/dev/nvme0n1p1` is mounted as the root device and `/dev/nvme1n1` is attached but not mounted\.
```
[ec2-user ~]$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
nvme1n1 259:3 0 100G 0 disk
nvme0n1 259:0 0 8G 0 disk
nvme0n1p1 259:1 0 8G 0 part /
nvme0n1p128 259:2 0 1M 0 part
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/nvme-ebs-volumes.md |
d55b56005307-0 | To format and mount an NVMe EBS volume, see [Making an Amazon EBS volume available for use on Linux](ebs-using-volumes.md)\.
If you are using Linux kernel 4\.2 or later, any change you make to the volume size of an NVMe EBS volume is automatically reflected in the instance\. For older Linux kernels, you might need to detach and attach the EBS volume or reboot the instance for the size change to be reflected\. With Linux kernel 3\.19 or later, you can use the hdparm command as follows to force a rescan of the NVMe device:
```
[ec2-user ~]$ sudo hdparm -z /dev/nvme1n1
```
When you detach an NVMe EBS volume, the instance does not have an opportunity to flush the file system caches or metadata before detaching the volume\. Therefore, before you detach an NVMe EBS volume, you should first sync and unmount it\. If the volume fails to detach, you can attempt a `force-detach` command as described in [Detaching an Amazon EBS volume from a Linux instance](ebs-detaching-volume.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/nvme-ebs-volumes.md |
1a1c7d6165a6-0 | EBS volumes attached to Nitro\-based instances use the default NVMe driver provided by the operating system\. Most operating systems specify a timeout for I/O operations submitted to NVMe devices\. The default timeout is 30 seconds and can be changed using the `nvme_core.io_timeout` boot parameter\. For most Linux kernels earlier than version 4\.6, this parameter is `nvme.io_timeout`\.
If I/O latency exceeds the value of this timeout parameter, the Linux NVMe driver fails the I/O and returns an error to the filesystem or application\. Depending on the I/O operation, your filesystem or application can retry the error\. In some cases, your filesystem might be remounted as read\-only\.
For an experience similar to EBS volumes attached to Xen instances, we recommend setting `nvme_core.io_timeout` to the highest value possible\. For current kernels, the maximum is 4294967295, while for earlier kernels the maximum is 255\. Depending on the version of Linux, the timeout might already be set to the supported maximum value\. For example, the timeout is set to 4294967295 by default for Amazon Linux AMI 2017\.09\.01 and later\.
You can verify the maximum value for your Linux distribution by writing a value higher than the suggested maximum to `/sys/module/nvme_core/parameters/io_timeout` and checking for the Numerical result out of range error when attempting to save the file\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/nvme-ebs-volumes.md |
582c53b0cbb5-0 | An Amazon EBS–optimized instance uses an optimized configuration stack and provides additional, dedicated capacity for Amazon EBS I/O\. This optimization provides the best performance for your EBS volumes by minimizing contention between Amazon EBS I/O and other traffic from your instance\.
EBS–optimized instances deliver dedicated bandwidth to Amazon EBS\. When attached to an EBS–optimized instance, General Purpose SSD \(`gp2`\) volumes are designed to deliver their baseline and burst performance 99% of the time, and Provisioned IOPS SSD \(`io1` and `io2`\) volumes are designed to deliver their provisioned performance 99\.9% of the time\. Both Throughput Optimized HDD \(`st1`\) and Cold HDD \(`sc1`\) guarantee performance consistency of 90% of burst throughput 99% of the time\. Non\-compliant periods are approximately uniformly distributed, targeting 99% of expected total throughput each hour\. For more information, see [Amazon EBS volume types](ebs-volume-types.md)\.
**Topics**
+ [Supported instance types](#ebs-optimization-support)
+ [Getting maximum performance](#ebs-optimization-performance)
+ [Enabling EBS optimization at launch](#enable-ebs-optimization)
+ [Enable EBS optimization for an existing instance](#modify-ebs-optimized-attribute) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-optimized.md |
49c196091a17-0 | The following tables show which instance types support EBS optimization\. They include the dedicated bandwidth to Amazon EBS, the typical maximum aggregate throughput that can be achieved on that connection with a streaming read workload and 128 KiB I/O size, and the maximum IOPS the instance can support if you are using a 16 KiB I/O size\. Choose an EBS–optimized instance that provides more dedicated Amazon EBS throughput than your application needs; otherwise, the connection | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-optimized.md |
49c196091a17-1 | than your application needs; otherwise, the connection between Amazon EBS and Amazon EC2 can become a performance bottleneck\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-optimized.md |
d8f15a7d348d-0 | The following table lists the instance types that support EBS optimization and EBS optimization is enabled by default\. There is no need to enable EBS optimization and no effect if you disable EBS optimization\.
| Instance size | Maximum bandwidth \(Mbps\) | Maximum throughput \(MB/s, 128 KiB I/O\) | Maximum IOPS \(16 KiB I/O\) |
| --- | --- | --- | --- |
| a1\.medium \* | 3,500 | 437\.5 | 20,000 |
| a1\.large \* | 3,500 | 437\.5 | 20,000 |
| a1\.xlarge \* | 3,500 | 437\.5 | 20,000 |
| a1\.2xlarge \* | 3,500 | 437\.5 | 20,000 |
| a1\.4xlarge | 3,500 | 437\.5 | 20,000 |
| a1\.metal | 3,500 | 437\.5 | 20,000 |
| c4\.large | 500 | 62\.5 | 4,000 |
| c4\.xlarge | 750 | 93\.75 | 6,000 |
| c4\.2xlarge | 1,000 | 125 | 8,000 |
| c4\.4xlarge | 2,000 | 250 | 16,000 |
| c4\.8xlarge | 4,000 | 500 | 32,000 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-optimized.md |
d8f15a7d348d-1 | | c4\.8xlarge | 4,000 | 500 | 32,000 |
| c5\.large \* | 4,750 | 593\.75 | 20,000 |
| c5\.xlarge \* | 4,750 | 593\.75 | 20,000 |
| c5\.2xlarge \* | 4,750 | 593\.75 | 20,000 |
| c5\.4xlarge | 4,750 | 593\.75 | 20,000 |
| c5\.9xlarge | 9,500 | 1,187\.5 | 40,000 |
| c5\.12xlarge | 9,500 | 1,187\.5 | 40,000 |
| c5\.18xlarge | 19,000 | 2,375 | 80,000 |
| c5\.24xlarge | 19,000 | 2,375 | 80,000 |
| c5\.metal | 19,000 | 2,375 | 80,000 |
| c5a\.large \* | 3,170 | 396 | 13,300 |
| c5a\.xlarge \* | 3,170 | 396 | 13,300 |
| c5a\.2xlarge \* | 3,170 | 396 | 13,300 |
| c5a\.4xlarge \* | 3,170 | 396 | 13,300 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-optimized.md |
d8f15a7d348d-2 | | c5a\.4xlarge \* | 3,170 | 396 | 13,300 |
| c5a\.8xlarge | 3,170 | 396 | 13,300 |
| c5a\.12xlarge | 4,750 | 594 | 20,000 |
| c5a\.16xlarge | 6,300 | 788 | 26,700 |
| c5a\.24xlarge | 9,500 | 1,188 | 40,000 |
| c5ad\.large \* | 3,170 | 396 | 13,300 |
| c5ad\.xlarge \* | 3,170 | 396 | 13,300 |
| c5ad\.2xlarge \* | 3,170 | 396 | 13,300 |
| c5ad\.4xlarge \* | 3,170 | 396 | 13,300 |
| c5ad\.8xlarge | 3,170 | 396 | 13,300 |
| c5ad\.12xlarge | 4,750 | 594 | 20,000 |
| c5ad\.16xlarge | 6,300 | 788 | 26,700 |
| c5ad\.24xlarge | 9,500 | 1,188 | 40,000 |
| c5d\.large \* | 4,750 | 593\.75 | 20,000 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-optimized.md |
d8f15a7d348d-3 | | c5d\.large \* | 4,750 | 593\.75 | 20,000 |
| c5d\.xlarge \* | 4,750 | 593\.75 | 20,000 |
| c5d\.2xlarge \* | 4,750 | 593\.75 | 20,000 |
| c5d\.4xlarge | 4,750 | 593\.75 | 20,000 |
| c5d\.9xlarge | 9,500 | 1,187\.5 | 40,000 |
| c5d\.12xlarge | 9,500 | 1,187\.5 | 40,000 |
| c5d\.18xlarge | 19,000 | 2,375 | 80,000 |
| c5d\.24xlarge | 19,000 | 2,375 | 80,000 |
| c5d\.metal | 19,000 | 2,375 | 80,000 |
| c5n\.large \* | 4,750 | 593\.75 | 20,000 |
| c5n\.xlarge \* | 4,750 | 593\.75 | 20,000 |
| c5n\.2xlarge \* | 4,750 | 593\.75 | 20,000 |
| c5n\.4xlarge | 4,750 | 593\.75 | 20,000 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-optimized.md |
d8f15a7d348d-4 | | c5n\.4xlarge | 4,750 | 593\.75 | 20,000 |
| c5n\.9xlarge | 9,500 | 1,187\.5 | 40,000 |
| c5n\.18xlarge | 19,000 | 2,375 | 80,000 |
| c5n\.metal | 19,000 | 2,375 | 80,000 |
| c6g\.medium \* | 4,750 | 593\.75 | 20,000 |
| c6g\.large \* | 4,750 | 593\.75 | 20,000 |
| c6g\.xlarge \* | 4,750 | 593\.75 | 20,000 |
| c6g\.2xlarge \* | 4,750 | 593\.75 | 20,000 |
| c6g\.4xlarge | 4,750 | 593\.75 | 20,000 |
| c6g\.8xlarge | 9,500 | 1,187\.5 | 40,000 |
| c6g\.12xlarge | 14,250 | 1,781\.25 | 50,000 |
| c6g\.16xlarge | 19,000 | 2,375 | 80,000 |
| c6g\.metal | 19,000 | 2,375 | 80,000 |
| c6gd\.medium \* | 4,750 | 593\.75 | 20,000 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-optimized.md |
d8f15a7d348d-5 | | c6gd\.medium \* | 4,750 | 593\.75 | 20,000 |
| c6gd\.large \* | 4,750 | 593\.75 | 20,000 |
| c6gd\.xlarge \* | 4,750 | 593\.75 | 20,000 |
| c6gd\.2xlarge \* | 4,750 | 593\.75 | 20,000 |
| c6gd\.4xlarge | 4,750 | 593\.75 | 20,000 |
| c6gd\.8xlarge | 9,500 | 1,187\.5 | 40,000 |
| c6gd\.12xlarge | 14,250 | 1,781\.25 | 50,000 |
| c6gd\.16xlarge | 19,000 | 2,375 | 80,000 |
| c6gd\.metal | 19,000 | 2,375 | 80,000 |
| d2\.xlarge | 750 | 93\.75 | 6,000 |
| d2\.2xlarge | 1,000 | 125 | 8,000 |
| d2\.4xlarge | 2,000 | 250 | 16,000 |
| d2\.8xlarge | 4,000 | 500 | 32,000 |
| f1\.2xlarge | 1,700 | 212\.5 | 12,000 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-optimized.md |
d8f15a7d348d-6 | | f1\.2xlarge | 1,700 | 212\.5 | 12,000 |
| f1\.4xlarge | 3,500 | 437\.5 | 44,000 |
| f1\.16xlarge | 14,000 | 1,750 | 75,000 |
| g3s\.xlarge | 850 | 106\.25 | 5,000 |
| g3\.4xlarge | 3,500 | 437\.5 | 20,000 |
| g3\.8xlarge | 7,000 | 875 | 40,000 |
| g3\.16xlarge | 14,000 | 1,750 | 80,000 |
| g4dn\.xlarge \* | 3,500 | 437\.5 | 20,000 |
| g4dn\.2xlarge \* | 3,500 | 437\.5 | 20,000 |
| g4dn\.4xlarge | 4,750 | 593\.75 | 20,000 |
| g4dn\.8xlarge | 9,500 | 1,187\.5 | 40,000 |
| g4dn\.12xlarge | 9,500 | 1,187\.5 | 40,000 |
| g4dn\.16xlarge | 9,500 | 1,187\.5 | 40,000 |
| g4dn\.metal | 19,000 | 2,375 | 80,000 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-optimized.md |
d8f15a7d348d-7 | | g4dn\.metal | 19,000 | 2,375 | 80,000 |
| h1\.2xlarge | 1,750 | 218\.75 | 12,000 |
| h1\.4xlarge | 3,500 | 437\.5 | 20,000 |
| h1\.8xlarge | 7,000 | 875 | 40,000 |
| h1\.16xlarge | 14,000 | 1,750 | 80,000 |
| i3\.large | 425 | 53\.13 | 3000 |
| i3\.xlarge | 850 | 106\.25 | 6000 |
| i3\.2xlarge | 1,700 | 212\.5 | 12,000 |
| i3\.4xlarge | 3,500 | 437\.5 | 16,000 |
| i3\.8xlarge | 7,000 | 875 | 32,500 |
| i3\.16xlarge | 14,000 | 1,750 | 65,000 |
| i3\.metal | 19,000 | 2,375 | 80,000 |
| i3en\.large \* | 4,750 | 593\.75 | 20,000 |
| i3en\.xlarge \* | 4,750 | 593\.75 | 20,000 |
| i3en\.2xlarge \* | 4,750 | 593\.75 | 20,000 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-optimized.md |
d8f15a7d348d-8 | | i3en\.2xlarge \* | 4,750 | 593\.75 | 20,000 |
| i3en\.3xlarge \* | 4,750 | 593\.75 | 20,000 |
| i3en\.6xlarge | 4,750 | 593\.75 | 20,000 |
| i3en\.12xlarge | 9,500 | 1,187\.5 | 40,000 |
| i3en\.24xlarge | 19,000 | 2,375 | 80,000 |
| i3en\.metal | 19,000 | 2,375 | 80,000 |
| inf1\.xlarge \* | 4,750 | 593\.75 | 20,000 |
| inf1\.2xlarge \* | 4,750 | 593\.75 | 20,000 |
| inf1\.6xlarge | 4,750 | 593\.75 | 20,000 |
| inf1\.24xlarge | 19,000 | 2,375 | 80,000 |
| m4\.large | 450 | 56\.25 | 3,600 |
| m4\.xlarge | 750 | 93\.75 | 6,000 |
| m4\.2xlarge | 1,000 | 125 | 8,000 |
| m4\.4xlarge | 2,000 | 250 | 16,000 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-optimized.md |
d8f15a7d348d-9 | | m4\.4xlarge | 2,000 | 250 | 16,000 |
| m4\.10xlarge | 4,000 | 500 | 32,000 |
| m4\.16xlarge | 10,000 | 1,250 | 65,000 |
| m5\.large \* | 4,750 | 593\.75 | 18,750 |
| m5\.xlarge \* | 4,750 | 593\.75 | 18,750 |
| m5\.2xlarge \* | 4,750 | 593\.75 | 18,750 |
| m5\.4xlarge | 4,750 | 593\.75 | 18,750 |
| m5\.8xlarge | 6,800 | 850 | 30,000 |
| m5\.12xlarge | 9,500 | 1,187\.5 | 40,000 |
| m5\.16xlarge | 13,600 | 1,700 | 60,000 |
| m5\.24xlarge | 19,000 | 2,375 | 80,000 |
| m5\.metal | 19,000 | 2,375 | 80,000 |
| m5a\.large \* | 2,880 | 360 | 16,000 |
| m5a\.xlarge \* | 2,880 | 360 | 16,000 |
| m5a\.2xlarge \* | 2,880 | 360 | 16,000 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-optimized.md |
d8f15a7d348d-10 | | m5a\.2xlarge \* | 2,880 | 360 | 16,000 |
| m5a\.4xlarge | 2,880 | 360 | 16,000 |
| m5a\.8xlarge | 4,750 | 593\.75 | 20,000 |
| m5a\.12xlarge | 6,780 | 847\.5 | 30,000 |
| m5a\.16xlarge | 9,500 | 1,187\.50 | 40,000 |
| m5a\.24xlarge | 13,570 | 1,696\.25 | 60,000 |
| m5ad\.large \* | 2,880 | 360 | 16,000 |
| m5ad\.xlarge \* | 2,880 | 360 | 16,000 |
| m5ad\.2xlarge \* | 2,880 | 360 | 16,000 |
| m5ad\.4xlarge | 2,880 | 360 | 16,000 |
| m5ad\.8xlarge | 4,750 | 593\.75 | 20,000 |
| m5ad\.12xlarge | 6,780 | 847\.5 | 30,000 |
| m5ad\.16xlarge | 9,500 | 1,187\.5 | 40,000 |
| m5ad\.24xlarge | 13,570 | 1,696\.25 | 60,000 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-optimized.md |
d8f15a7d348d-11 | | m5ad\.24xlarge | 13,570 | 1,696\.25 | 60,000 |
| m5d\.large \* | 4,750 | 593\.75 | 18,750 |
| m5d\.xlarge \* | 4,750 | 593\.75 | 18,750 |
| m5d\.2xlarge \* | 4,750 | 593\.75 | 18,750 |
| m5d\.4xlarge | 4,750 | 593\.75 | 18,750 |
| m5d\.8xlarge | 6,800 | 850 | 30,000 |
| m5d\.12xlarge | 9,500 | 1,187\.5 | 40,000 |
| m5d\.16xlarge | 13,600 | 1,700 | 60,000 |
| m5d\.24xlarge | 19,000 | 2,375 | 80,000 |
| m5d\.metal | 19,000 | 2,375 | 80,000 |
| m5dn\.large \* | 4,750 | 593\.75 | 18,750 |
| m5dn\.xlarge \* | 4,750 | 593\.75 | 18,750 |
| m5dn\.2xlarge \* | 4,750 | 593\.75 | 18,750 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-optimized.md |
d8f15a7d348d-12 | | m5dn\.2xlarge \* | 4,750 | 593\.75 | 18,750 |
| m5dn\.4xlarge | 4,750 | 593\.75 | 18,750 |
| m5dn\.8xlarge | 6,800 | 850 | 30,000 |
| m5dn\.12xlarge | 9,500 | 1,187\.5 | 40,000 |
| m5dn\.16xlarge | 13,600 | 1,700 | 60,000 |
| m5dn\.24xlarge | 19,000 | 2,375 | 80,000 |
| m5n\.large \* | 4,750 | 593\.75 | 18,750 |
| m5n\.xlarge \* | 4,750 | 593\.75 | 18,750 |
| m5n\.2xlarge \* | 4,750 | 593\.75 | 18,750 |
| m5n\.4xlarge | 4,750 | 593\.75 | 18,750 |
| m5n\.8xlarge | 6,800 | 850 | 30,000 |
| m5n\.12xlarge | 9,500 | 1,187\.5 | 40,000 |
| m5n\.16xlarge | 13,600 | 1,700 | 60,000 |
| m5n\.24xlarge | 19,000 | 2,375 | 80,000 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-optimized.md |
d8f15a7d348d-13 | | m5n\.24xlarge | 19,000 | 2,375 | 80,000 |
| m6g\.medium \* | 4,750 | 593\.75 | 20,000 |
| m6g\.large \* | 4,750 | 593\.75 | 20,000 |
| m6g\.xlarge \* | 4,750 | 593\.75 | 20,000 |
| m6g\.2xlarge \* | 4,750 | 593\.75 | 20,000 |
| m6g\.4xlarge | 4,750 | 593\.75 | 20,000 |
| m6g\.8xlarge | 9,500 | 1,187\.5 | 40,000 |
| m6g\.12xlarge | 14,250 | 1,781\.25 | 50,000 |
| m6g\.16xlarge | 19,000 | 2,375 | 80,000 |
| m6g\.metal | 19,000 | 2,375 | 80,000 |
| m6gd\.medium \* | 4,750 | 593\.75 | 20,000 |
| m6gd\.large \* | 4,750 | 593\.75 | 20,000 |
| m6gd\.xlarge \* | 4,750 | 593\.75 | 20,000 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-optimized.md |
d8f15a7d348d-14 | | m6gd\.xlarge \* | 4,750 | 593\.75 | 20,000 |
| m6gd\.2xlarge \* | 4,750 | 593\.75 | 20,000 |
| m6gd\.4xlarge | 4,750 | 593\.75 | 20,000 |
| m6gd\.8xlarge | 9,500 | 1,187\.5 | 40,000 |
| m6gd\.12xlarge | 14,250 | 1,781\.25 | 50,000 |
| m6gd\.16xlarge | 19,000 | 2,375 | 80,000 |
| m6gd\.metal | 19,000 | 2,375 | 80,000 |
| p2\.xlarge | 750 | 93\.75 | 6,000 |
| p2\.8xlarge | 5,000 | 625 | 32,500 |
| p2\.16xlarge | 10,000 | 1,250 | 65,000 |
| p3\.2xlarge | 1,750 | 218\.75 | 10,000 |
| p3\.8xlarge | 7,000 | 875 | 40,000 |
| p3\.16xlarge | 14,000 | 1,750 | 80,000 |
| p3dn\.24xlarge | 19,000 | 2,375 | 80,000 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-optimized.md |
d8f15a7d348d-15 | | p3dn\.24xlarge | 19,000 | 2,375 | 80,000 |
| r4\.large | 425 | 53\.13 | 3,000 |
| r4\.xlarge | 850 | 106\.25 | 6,000 |
| r4\.2xlarge | 1,700 | 212\.5 | 12,000 |
| r4\.4xlarge | 3,500 | 437\.5 | 18,750 |
| r4\.8xlarge | 7,000 | 875 | 37,500 |
| r4\.16xlarge | 14,000 | 1,750 | 75,000 |
| r5\.large \* | 4,750 | 593\.75 | 18,750 |
| r5\.xlarge \* | 4,750 | 593\.75 | 18,750 |
| r5\.2xlarge \* | 4,750 | 593\.75 | 18,750 |
| r5\.4xlarge | 4,750 | 593\.75 | 18,750 |
| r5\.8xlarge | 6,800 | 850 | 30,000 |
| r5\.12xlarge | 9,500 | 1,187\.5 | 40,000 |
| r5\.16xlarge | 13,600 | 1,700 | 60,000 |
| r5\.24xlarge | 19,000 | 2,375 | 80,000 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-optimized.md |
d8f15a7d348d-16 | | r5\.24xlarge | 19,000 | 2,375 | 80,000 |
| r5\.metal | 19,000 | 2,375 | 80,000 |
| r5a\.large \* | 2,880 | 360 | 16,000 |
| r5a\.xlarge \* | 2,880 | 360 | 16,000 |
| r5a\.2xlarge \* | 2,880 | 360 | 16,000 |
| r5a\.4xlarge | 2,880 | 360 | 16,000 |
| r5a\.8xlarge | 4,750 | 593\.75 | 20,000 |
| r5a\.12xlarge | 6,780 | 847\.5 | 30,000 |
| r5a\.16xlarge | 9,500 | 1,187\.5 | 40,000 |
| r5a\.24xlarge | 13,570 | 1,696\.25 | 60,000 |
| r5ad\.large \* | 2,880 | 360 | 16,000 |
| r5ad\.xlarge \* | 2,880 | 360 | 16,000 |
| r5ad\.2xlarge \* | 2,880 | 360 | 16,000 |
| r5ad\.4xlarge | 2,880 | 360 | 16,000 |
| r5ad\.8xlarge | 4,750 | 593\.75 | 20,000 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-optimized.md |
d8f15a7d348d-17 | | r5ad\.8xlarge | 4,750 | 593\.75 | 20,000 |
| r5ad\.12xlarge | 6,780 | 847\.5 | 30,000 |
| r5ad\.16xlarge | 9,500 | 1,187\.5 | 40,000 |
| r5ad\.24xlarge | 13,570 | 1,696\.25 | 60,000 |
| r5d\.large \* | 4,750 | 593\.75 | 18,750 |
| r5d\.xlarge \* | 4,750 | 593\.75 | 18,750 |
| r5d\.2xlarge \* | 4,750 | 593\.75 | 18,750 |
| r5d\.4xlarge | 4,750 | 593\.75 | 18,750 |
| r5d\.8xlarge | 6,800 | 850 | 30,000 |
| r5d\.12xlarge | 9,500 | 1,187\.5 | 40,000 |
| r5d\.16xlarge | 13,600 | 1,700 | 60,000 |
| r5d\.24xlarge | 19,000 | 2,375 | 80,000 |
| r5d\.metal | 19,000 | 2,375 | 80,000 |
| r5dn\.large \* | 4,750 | 593\.75 | 18,750 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-optimized.md |
Subsets and Splits