id
stringlengths 14
16
| text
stringlengths 1
2.43k
| source
stringlengths 99
229
|
|---|---|---|
d6a89d8a8611-3 | | z1d\.metal | 700,000 | 340,000 |
\* For these instances, you can get up to the specified performance\.
As you fill the SSD\-based instance store volumes for your instance, the number of write IOPS that you can achieve decreases\. This is due to the extra work the SSD controller must do to find available space, rewrite existing data, and erase unused space so that it can be rewritten\. This process of garbage collection results in internal write amplification to the SSD, expressed as the ratio of SSD write operations to user write operations\. This decrease in performance is even larger if the write operations are not in multiples of 4,096 bytes or not aligned to a 4,096\-byte boundary\. If you write a smaller amount of bytes or bytes that are not aligned, the SSD controller must read the surrounding data and store the result in a new location\. This pattern results in significantly increased write amplification, increased latency, and dramatically reduced I/O performance\.
SSD controllers can use several strategies to reduce the impact of write amplification\. One such strategy is to reserve space in the SSD instance storage so that the controller can more efficiently manage the space available for write operations\. This is called *over\-provisioning*\. The SSD\-based instance store volumes provided to an instance don't have any space reserved for over\-provisioning\. To reduce write amplification, we recommend that you leave 10% of the volume unpartitioned so that the SSD controller can use it for over\-provisioning\. This decreases the storage that you can use, but increases performance even if the disk is close to full capacity\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/memory-optimized-instances.md |
d6a89d8a8611-4 | For instance store volumes that support TRIM, you can use the TRIM command to notify the SSD controller whenever you no longer need data that you've written\. This provides the controller with more free space, which can reduce write amplification and increase performance\. For more information, see [Instance store volume TRIM support](ssd-instance-store.md#InstanceStoreTrimSupport)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/memory-optimized-instances.md |
41c274be00a0-0 | The following is a summary of features for memory optimized instances\.
| | EBS only | NVMe EBS | Instance store | Placement group |
| --- | --- | --- | --- | --- |
| R4 | Yes | No | No | Yes |
| R5 | Yes | Yes | No | Yes |
| R5a | Yes | Yes | No | Yes |
| R5ad | No | Yes | NVME \* | Yes |
| R5d | No | Yes | NVME \* | Yes |
| R5dn | No | Yes | NVME \* | Yes |
| R5n | Yes | Yes | No | Yes |
| R6g | Yes | Yes | No | Yes |
| R6gd | No | Yes | NVMe \* | Yes |
| u\-6tb1\.metal | Yes | Yes | No | No |
| u\-9tb1\.metal | Yes | Yes | No | No |
| u\-12tb1\.metal | Yes | Yes | No | No |
| u\-18tb1\.metal | Yes | Yes | No | No |
| u\-24tb1\.metal | Yes | Yes | No | No |
| X1 | No | No | SSD | Yes |
| X1e | No | No | SSD \* | Yes | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/memory-optimized-instances.md |
41c274be00a0-1 | | X1 | No | No | SSD | Yes |
| X1e | No | No | SSD \* | Yes |
| z1d | No | Yes | NVME \* | Yes |
**\*** The root device volume must be an Amazon EBS volume\.
For more information, see the following:
+ [Amazon EBS and NVMe on Linux instances](nvme-ebs-volumes.md)
+ [Amazon EC2 instance store](InstanceStorage.md)
+ [Placement groups](placement-groups.md) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/memory-optimized-instances.md |
cd93c6de099a-0 | Memory optimized instances provide a high number of vCPUs, which can cause launch issues with operating systems that have a lower vCPU limit\. We strongly recommend that you use the latest AMIs when you launch memory optimized instances\.
The following AMIs support launching memory optimized instances:
+ Amazon Linux 2 \(HVM\)
+ Amazon Linux AMI 2016\.03 \(HVM\) or later
+ Ubuntu Server 14\.04 LTS \(HVM\)
+ Red Hat Enterprise Linux 7\.1 \(HVM\)
+ SUSE Linux Enterprise Server 12 SP1 \(HVM\)
+ Windows Server 2019
+ Windows Server 2016
+ Windows Server 2012 R2
+ Windows Server 2012
+ Windows Server 2008 R2 64\-bit
+ Windows Server 2008 SP2 64\-bit | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/memory-optimized-instances.md |
c0abd1b5c8a1-0 | + R4 instances feature up to 64 vCPUs and are powered by two AWS\-customized Intel XEON processors based on E5\-2686v4 that feature high\-memory bandwidth and larger L3 caches to boost the performance of in\-memory applications\.
+ R5 and R5d instances feature a 3\.1 GHz Intel Xeon Platinum 8000 series processor from either the first generation \(Skylake\-SP\) or second generation \(Cascade Lake\)\.
+ R5a and R5ad instances feature a 2\.5 GHz AMD EPYC 7000 series processor\.
+ R6g and R6gd instances feature an AWS Graviton2 processor based on 64\-bit Arm architecture\.
+ High memory instances \(`u-6tb1.metal`, `u-9tb1.metal`, and `u-12tb1.metal`\) are the first instances to be powered by an eight\-socket platform with the latest generation Intel Xeon Platinum 8176M \(Skylake\) processors that are optimized for mission\-critical enterprise workloads\. High Memory instances with 18 TB and 24 TB of memory \(`u-18tb1.metal` and `u-24tb1.metal`\) are the first instances powered by an 8\-socket platform with 2nd Generation Intel Xeon Scalable 8280L \(Cascade Lake\) processors\.
+ X1e and X1 instances feature up to 128 vCPUs and are powered by four Intel Xeon E7\-8880 v3 processors that feature high\-memory bandwidth and larger L3 caches to boost the performance of in\-memory applications\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/memory-optimized-instances.md |
c0abd1b5c8a1-1 | + Instances built on the Nitro System have the following requirements:
+ [NVMe drivers](nvme-ebs-volumes.md) must be installed
+ [Elastic Network Adapter \(ENA\) drivers](enhanced-networking-ena.md) must be installed
The following Linux AMIs meet these requirements:
+ 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
+ Instances with an AWS Graviton processors have the following requirements:
+ Use an AMI for the 64\-bit Arm architecture\.
+ Support booting through UEFI with ACPI tables and support ACPI hot\-plug of PCI devices\.
The following AMIs meet these requirements:
+ Amazon Linux 2 \(64\-bit Arm\)
+ Ubuntu 16\.04 or later \(64\-bit Arm\)
+ Red Hat Enterprise Linux 8\.0 or later \(64\-bit Arm\)
+ SUSE Linux Enterprise Server 15 or later \(64\-bit Arm\) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/memory-optimized-instances.md |
c0abd1b5c8a1-2 | + SUSE Linux Enterprise Server 15 or later \(64\-bit Arm\)
+ Instances built on the Nitro System instances support a maximum of 28 attachments, including network interfaces, EBS volumes, and NVMe instance store volumes\. For more information, see [Nitro System volume limits](volume_limits.md#instance-type-volume-limits)\.
+ Launching a bare metal instance boots the underlying server, which includes verifying all hardware and firmware components\. This means that it can take 20 minutes from the time the instance enters the running state until it becomes available over the network\.
+ To attach or detach EBS volumes or secondary network interfaces from a bare metal instance requires PCIe native hotplug support\. Amazon Linux 2 and the latest versions of the Amazon Linux AMI support PCIe native hotplug, but earlier versions do not\. You must enable the following Linux kernel configuration options:
```
CONFIG_HOTPLUG_PCI_PCIE=y
CONFIG_PCIEASPM=y
```
+ Bare metal instances use a PCI\-based serial device rather than an I/O port\-based serial device\. The upstream Linux kernel and the latest Amazon Linux AMIs support this device\. Bare metal instances also provide an ACPI SPCR table to enable the system to automatically use the PCI\-based serial device\. The latest Windows AMIs automatically use the PCI\-based serial device\.
+ You can't launch X1 instances using a Windows Server 2008 SP2 64\-bit AMI, except for `x1.16xlarge` instances\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/memory-optimized-instances.md |
c0abd1b5c8a1-3 | + You can't launch X1 instances using a Windows Server 2008 SP2 64\-bit AMI, except for `x1.16xlarge` instances\.
+ You can't launch X1e instances using a Windows Server 2008 SP2 64\-bit AMI\.
+ With earlier versions of the Windows Server 2008 R2 64\-bit AMI, you can't launch `r4.large` and `r4.4xlarge` instances\. If you experience this issue, update to the latest version of this AMI\.
+ There is a limit on the total number of instances that you can launch in a Region, and there are additional limits on some instance types\. For more information, see [How many instances can I run in Amazon EC2?](https://aws.amazon.com/ec2/faqs/#How_many_instances_can_I_run_in_Amazon_EC2) in the Amazon EC2 FAQ\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/memory-optimized-instances.md |
16900ef9e812-0 | You can bring part or all of your public IPv4 address range or IPv6 address range from your on\-premises network to your AWS account\. You continue to own the address range, but AWS advertises it on the internet by default\. After you bring the address range to AWS, it appears in your account as an address pool\.
BYOIP is not available in all Regions\. For a list of supported Regions, see the [FAQ for Bring Your Own IP](https://aws.amazon.com/vpc/faqs/#Bring_Your_Own_IP)\.
**Note**
The following steps describe how to bring your own IP address range for use in Amazon EC2 only\. For steps to bring your own IP address range for use in AWS Global Accelerator, see [Bring your own IP addresses \(BYOIP\)](https://docs.aws.amazon.com/global-accelerator/latest/dg/using-byoip.html) in the *AWS Global Accelerator Developer Guide*\.
**Topics**
+ [Requirements](#byoip-requirements)
+ [Prepare to bring your address range to your AWS account](#prepare-for-byoip)
+ [Provision the address range for use with AWS](#byoip-provision)
+ [Advertise the address range through AWS](#byoip-advertise)
+ [Work with your address range](#byoip-working-with)
+ [Deprovision the address range](#byoip-deprovision) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-byoip.md |
6d53cd75dc9e-0 | + The address range must be registered with your Regional internet registry \(RIR\), such as the American Registry for Internet Numbers \(ARIN\), Réseaux IP Européens Network Coordination Centre \(RIPE\), or Asia\-Pacific Network Information Centre \(APNIC\)\. It must be registered to a business or institutional entity and cannot be registered to an individual person\.
+ The most specific IPv4 address range that you can bring is /24\.
+ The most specific IPv6 address range that you can bring is /48 for CIDRs that are publicly advertised, and /56 for CIDRs that are [not publicly advertised](#byoip-provision-non-public)\.
+ You can bring each address range to one Region at a time\.
+ You can bring a total of five IPv4 and IPv6 address ranges per Region to your AWS account\.
+ The addresses in the IP address range must have a clean history\. We might investigate the reputation of the IP address range and reserve the right to reject an IP address range if it contains an IP address that has a poor reputation or is associated with malicious behavior\.
+ You must own the IP address that you use\. This means that only the following are supported:
+ ARIN \- "Direct Allocation" and "Direct Assignment" network types
+ RIPE \- "ALLOCATED PA", "LEGACY", "ASSIGNED PI", and "ALLOCATED\-BY\-RIR" allocation statuses
+ APNIC – "ALLOCATED PORTABLE" and "ASSIGNED PORTABLE" allocation statuses | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-byoip.md |
83aa9efa9fd8-0 | To ensure that only you can bring your address range to your AWS account, you must authorize Amazon to advertise the address range\. You must also provide proof that you own the address range through a signed authorization message\.
A Route Origin Authorization \(ROA\) is a cryptographic statement about your route announcements that you can create through your RIR\. It contains the address range, the Autonomous System numbers \(ASN\) that are allowed to advertise the address range, and an expiration date\. An ROA authorizes Amazon to advertise an address range under a specific AS number\. However, it does not authorize your AWS account to bring the address range to AWS\. To authorize your AWS account to bring an address range to AWS, you must publish a self\-signed X509 certificate in the Registry Data Access Protocol \(RDAP\) remarks for the address range\. The certificate contains a public key, which AWS uses to verify the authorization\-context signature that you provide\. Keep your private key secure and use it to sign the authorization\-context message\.
The commands in these tasks are supported on Linux\. On Windows, you can use the [Windows Subsystem for Linux](https://docs.microsoft.com/en-us/windows/wsl/about) to run Linux commands\.
**Topics**
+ [Create a ROA object](#byoip-create-roa-object)
+ [Create a self\-signed X509 certificate](#byoip-certificate)
+ [Create a signed authorization message](#byoip-signed-authorization-message) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-byoip.md |
196ff50f5598-0 | Create a ROA object to authorize Amazon ASNs 16509 and 14618 to advertise your address range, plus the ASNs that are currently authorized to advertise the address range\. You must set the maximum length to the size of the smallest prefix that you want to bring \(for example, /24\)\. It might take up to 24 hours for the ROA to become available to Amazon\. For more information, see the following:
+ ARIN — [ROA Requests](https://www.arin.net/resources/rpki/roarequest.html)
+ RIPE — [Managing ROAs](https://www.ripe.net/manage-ips-and-asns/resource-management/certification/resource-certification-roa-management)
+ APNIC — [Route Management](https://www.apnic.net/wp-content/uploads/2017/01/route-roa-management-guide.pdf) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-byoip.md |
62f5b55c8937-0 | Use the following procedure to create a self\-signed X509 certificate and add it to the RDAP record for your RIR\. The openssl commands require OpenSSL version 1\.0\.2 or later\.
Copy the commands below and replace only the placeholder values \(in colored italic text\)\.
**To create a self\-signed X509 certificate and add it to the RDAP record**
1. Generate an RSA 2048\-bit key pair as shown in the following\.
```
openssl genrsa -out private.key 2048
```
1. Create a public X509 certificate from the key pair using the following command\. In this example, the certificate expires in 365 days, after which time it cannot be trusted\. Be sure to set the expiration appropriately\. When prompted for information, you can accept the default values\.
```
openssl req -new -x509 -key private.key -days 365 | tr -d "\n" > publickey.cer
```
1. Update the RDAP record for your RIR with the X509 certificate\. Be sure to copy the `-----BEGIN CERTIFICATE-----` and `-----END CERTIFICATE-----` from the certificate\. Be sure that you have removed newline characters, if you haven't already done so using the tr \-d "\\n" commands in the previous steps\. To view your certificate, run the following command\.
```
cat publickey.cer | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-byoip.md |
62f5b55c8937-1 | ```
cat publickey.cer
```
For ARIN, add the certificate in the "Public Comments" section for your address range\. Do not add it to the comments section for your organization\.
For RIPE, add the certificate as a new "descr" field for your address range\. Do not add it to the comments section for your organization\.
For APNIC, email the public key to [helpdesk@apnic\.net](mailto:[email protected]) to manually add it to the "remarks" field for your address range\. Send the email using the APNIC authorized contact for the IP addresses\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-byoip.md |
e80b970d3abe-0 | The format of the signed authorization message is as follows, where the date is the expiry date of the message\.
```
1|aws|account|cidr|YYYYMMDD|SHA256|RSAPSS
```
**To create a signed authorization message**
1. Create a plaintext authorization message and store it in a variable named `text_message` as shown in the following example\. Copy the following example and replace only the example account number, address range, and expiry date with your own values\.
```
text_message="1|aws|123456789012|198.51.100.0/24|20191201|SHA256|RSAPSS"
```
1. Sign the authorization message in `text_message` using the key pair that you created, and store it in a variable named `signed_message`\.
```
signed_message=$(echo $text_message | tr -d "\n" | openssl dgst -sha256 -sigopt rsa_padding_mode:pss -sigopt rsa_pss_saltlen:-1 -sign private.key -keyform PEM | openssl base64 | tr -- '+=/' '-_~' | tr -d "\n")
```
**Important**
We recommend that you copy and paste this command\. Do not modify or replace any of the values\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-byoip.md |
11670e31d7ee-0 | When you provision an address range for use with AWS, you are confirming that you own the address range and are authorizing Amazon to advertise it\. We also verify that you own the address range through a signed authorization message\. This message is signed with the self\-signed X509 key pair that you used when updating the RDAP record with the X509 certificate\.
To provision the address range, use the following [provision\-byoip\-cidr](https://docs.aws.amazon.com/cli/latest/reference/ec2/provision-byoip-cidr.html) command\. Replace the example address range with your own address range\. The `--cidr-authorization-context` option uses the variables that you created previously, not the ROA message\.
```
aws ec2 provision-byoip-cidr --cidr address-range --cidr-authorization-context Message="$text_message",Signature="$signed_message"
```
Provisioning an address range is an asynchronous operation, so the call returns immediately, but the address range is not ready to use until its status changes from `pending-provision` to `provisioned`\. It can take up to three weeks to complete the provisioning process\. To monitor the status of the address ranges that you've provisioned, use the following [describe\-byoip\-cidrs](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-byoip-cidrs.html) command\.
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-byoip.md |
11670e31d7ee-1 | ```
aws ec2 describe-byoip-cidrs --max-results 5
```
If there are issues during provisioning and the status goes to `failed-provision`, you must run the `provision-byoip-cidr` command again after the issues have been resolved\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-byoip.md |
c2072e3a82fb-0 | By default, an address range is provisioned to be publicly advertised to the internet\. You can provision an IPv6 address range that will not be publicly advertised\. When you associate an IPv6 CIDR block from a non\-public address range with a VPC, the IPv6 CIDR can only be accessed through an AWS Direct Connect connection\.
An ROA is not required to provision a non\-public address range\.
To provision an IPv6 address range that will not be publicly advertised, use the following [provision\-byoip\-cidr](https://docs.aws.amazon.com/cli/latest/reference/ec2/provision-byoip-cidr.html) command\.
```
aws ec2 provision-byoip-cidr --cidr address-range --cidr-authorization-context Message="$text_message",Signature="$signed_message" --no-publicly-advertisable
```
**Important**
You can only set the `publicly-advertisable` or `no-publicly-advertisable` flag during provisioning\. You cannot change the advertisable status of an address range later\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-byoip.md |
22f958c52f2b-0 | After the address range is provisioned, it is ready to be advertised\. You must advertise the exact address range that you provisioned\. You can't advertise only a portion of the provisioned address range\.
If you provisioned an IPv6 address range that will not be publicly advertised, you do not need to complete this step\.
We recommend that you stop advertising the address range from other locations before you advertise it through AWS\. If you keep advertising your IP address range from other locations, we can't reliably support it or troubleshoot issues\. Specifically, we can't guarantee that traffic to the address range will enter our network\.
To minimize down time, you can configure your AWS resources to use an address from your address pool before it is advertised, and then simultaneously stop advertising it from the current location and start advertising it through AWS\. For more information about allocating an Elastic IP address from your address pool, see [Allocating an Elastic IP address](elastic-ip-addresses-eip.md#using-instance-addressing-eips-allocating)\.
To advertise the address range, use the following [advertise\-byoip\-cidr](https://docs.aws.amazon.com/cli/latest/reference/ec2/advertise-byoip-cidr.html) command\.
```
aws ec2 advertise-byoip-cidr --cidr address-range
```
**Important** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-byoip.md |
22f958c52f2b-1 | aws ec2 advertise-byoip-cidr --cidr address-range
```
**Important**
You can run the advertise\-byoip\-cidr command at most once every 10 seconds, even if you specify different address ranges each time\.
To stop advertising the address range, use the following [withdraw\-byoip\-cidr](https://docs.aws.amazon.com/cli/latest/reference/ec2/withdraw-byoip-cidr.html) command\.
```
aws ec2 withdraw-byoip-cidr --cidr address-range
```
**Important**
You can run the withdraw\-byoip\-cidr command at most once every 10 seconds, even if you specify different address ranges each time\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-byoip.md |
5a0731568638-0 | You can view and work with the IPv4 and IPv6 address ranges that you've provisioned in your account\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-byoip.md |
eb2ea4a3191a-0 | You can create an Elastic IP address from your IPv4 address pool and use it with your AWS resources, such as EC2 instances, NAT gateways, and Network Load Balancers\.
To view information about the IPv4 address pools that you've provisioned in your account, use the following [describe\-public\-ipv4\-pools](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-public-ipv4-pools.html) command\.
```
aws ec2 describe-public-ipv4-pools
```
To create an Elastic IP address from your IPv4 address pool, use the [allocate\-address](https://docs.aws.amazon.com/cli/latest/reference/ec2/allocate-address.html) command\. You can use the `--public-ipv4-pool` option to specify the ID of the address pool returned by `describe-byoip-cidrs`\. Or you can use the `--address` option to specify an address from the address range that you provisioned\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-byoip.md |
cf0186c7b143-0 | To view information about the IPv6 address pools that you've provisioned in your account, use the following [describe\-ipv6\-pools](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-ipv6-pools.html) command\.
```
aws ec2 describe-ipv6-pools
```
To create a VPC and specify an IPv6 CIDR from your IPv6 address pool, use the following [create\-vpc](https://docs.aws.amazon.com/cli/latest/reference/ec2/create-vpc.html) command\. To let Amazon choose the IPv6 CIDR from your IPv6 address pool, omit the `--ipv6-cidr-block` option\.
```
aws ec2 create-vpc --cidr-block 10.0.0.0/16 --ipv6-cidr-block ipv6-cidr --ipv6-pool pool-id
```
To associate an IPv6 CIDR block from your IPv6 address pool with a VPC, use the following [associate\-vpc\-cidr\-block](https://docs.aws.amazon.com/cli/latest/reference/ec2/associate-vpc-cidr-block.html) command\. To let Amazon choose the IPv6 CIDR from your IPv6 address pool, omit the `--ipv6-cidr-block` option\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-byoip.md |
cf0186c7b143-1 | ```
aws ec2 associate-vpc-cidr-block --vpc-id vpc-123456789abc123ab --ipv6-cidr-block ipv6-cidr --ipv6-pool pool-id
```
To view your VPCs and the associated IPv6 address pool information, use the [describe\-vpcs](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-vpcs.html) command\. To view information about associated IPv6 CIDR blocks from a specific IPv6 address pool, use the following [get\-associated\-ipv6\-pool\-cidrs](https://docs.aws.amazon.com/cli/latest/reference/ec2/get-associated-ipv6-pool-cidrs.html) command\.
```
aws ec2 get-associated-ipv6-pool-cidrs --pool-id pool-id
```
If you disassociate the IPv6 CIDR block from your VPC, it's released back into your IPv6 address pool\.
For more information about working with IPv6 CIDR blocks in the VPC console, see [Working with VPCs and Subnets](https://docs.aws.amazon.com/vpc/latest/userguide/working-with-vpcs.html) in the *Amazon VPC User Guide*\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-byoip.md |
81bb7d86ac43-0 | To stop using your address range with AWS, first release any Elastic IP addresses and disassociate any IPv6 CIDR blocks that are still allocated from the address pool\. Then stop advertising the address range, and finally, deprovision the address range\.
You cannot deprovision a portion of the address range\. If you want to use a more specific address range with AWS, deprovision the entire address range and provision a more specific address range\.
\(IPv4\) To release each Elastic IP address, use the following [release\-address](https://docs.aws.amazon.com/cli/latest/reference/ec2/release-address.html) command\.
```
aws ec2 release-address --allocation-id eipalloc-12345678abcabcabc
```
\(IPv6\) To disassociate an IPv6 CIDR block, use the following [disassociate\-vpc\-cidr\-block](https://docs.aws.amazon.com/cli/latest/reference/ec2/disassociate-vpc-cidr-block.html) command\.
```
aws ec2 disassociate-vpc-cidr-block --association-id vpc-cidr-assoc-12345abcd1234abc1
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-byoip.md |
81bb7d86ac43-1 | ```
To stop advertising the address range, use the following [withdraw\-byoip\-cidr](https://docs.aws.amazon.com/cli/latest/reference/ec2/withdraw-byoip-cidr.html) command\.
```
aws ec2 withdraw-byoip-cidr --cidr address-range
```
To deprovision the address range, use the following [deprovision\-byoip\-cidr](https://docs.aws.amazon.com/cli/latest/reference/ec2/deprovision-byoip-cidr.html) command\.
```
aws ec2 deprovision-byoip-cidr --cidr address-range
```
It can take up to a day to deprovision an address range\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ec2-byoip.md |
14851e44d8d4-0 | AWS provides various tools that you can use to monitor Amazon EC2\. You can configure some of these tools to do the monitoring for you, while some of the tools require manual intervention\.
**Topics**
+ [Automated monitoring tools](#monitoring_automated_tools)
+ [Manual monitoring tools](#monitoring_manual_tools) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring_automated_manual.md |
2de62c5e8b87-0 | You can use the following automated monitoring tools to watch Amazon EC2 and report back to you when something is wrong:
+ **System status checks** – monitor the AWS systems required to use your instance to ensure that they are working properly\. These checks detect problems with your instance that require AWS involvement to repair\. When a system status check fails, you can choose to wait for AWS to fix the issue or you can resolve it yourself \(for example, by stopping and restarting or terminating and replacing an instance\)\. Examples of problems that cause system status checks to fail include:
+ Loss of network connectivity
+ Loss of system power
+ Software issues on the physical host
+ Hardware issues on the physical host that impact network reachability
For more information, see [Status checks for your instances](monitoring-system-instance-status-check.md)\.
+ **Instance status checks** – monitor the software and network configuration of your individual instance\. These checks detect problems that require your involvement to repair\. When an instance status check fails, typically you will need to address the problem yourself \(for example, by rebooting the instance or by making modifications in your operating system\)\. Examples of problems that may cause instance status checks to fail include:
+ Failed system status checks
+ Misconfigured networking or startup configuration
+ Exhausted memory
+ Corrupted file system
+ Incompatible kernel
For more information, see [Status checks for your instances](monitoring-system-instance-status-check.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring_automated_manual.md |
2de62c5e8b87-1 | + Incompatible kernel
For more information, see [Status checks for your instances](monitoring-system-instance-status-check.md)\.
+ **Amazon CloudWatch alarms** – watch a single metric over a time period you specify, and perform one or more actions based on the value of the metric relative to a given threshold over a number of time periods\. The action is a notification sent to an Amazon Simple Notification Service \(Amazon SNS\) topic or Amazon EC2 Auto Scaling policy\. Alarms invoke actions for sustained state changes only\. CloudWatch alarms will not invoke actions simply because they are in a particular state; the state must have changed and been maintained for a specified number of periods\. For more information, see [Monitoring your instances using CloudWatch](using-cloudwatch.md)\.
+ **Amazon CloudWatch Events** – automate your AWS services and respond automatically to system events\. Events from AWS services are delivered to CloudWatch Events in near real time, and you can specify automated actions to take when an event matches a rule you write\. For more information, see [What is Amazon CloudWatch Events?](https://docs.aws.amazon.com/AmazonCloudWatch/latest/events/WhatIsCloudWatchEvents.html)\.
+ **Amazon CloudWatch Logs** – monitor, store, and access your log files from Amazon EC2 instances, AWS CloudTrail, or other sources\. For more information, see the [Amazon CloudWatch Logs User Guide](https://docs.aws.amazon.com/AmazonCloudWatch/latest/logs/)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring_automated_manual.md |
2de62c5e8b87-2 | + **CloudWatch agent** – collect logs and system\-level metrics from both hosts and guests on your EC2 instances and on\-premises servers\. For more information, see [Collecting Metrics and Logs from Amazon EC2 Instances and On\-Premises Servers with the CloudWatch Agent](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Install-CloudWatch-Agent.html) in the *Amazon CloudWatch User Guide*\.
+ **AWS Management Pack for Microsoft System Center Operations Manager** – links Amazon EC2 instances and the Windows or Linux operating systems running inside them\. The AWS Management Pack is an extension to Microsoft System Center Operations Manager\. It uses a designated computer in your datacenter \(called a watcher node\) and the Amazon Web Services APIs to remotely discover and collect information about your AWS resources\. For more information, see [AWS Management Pack for Microsoft System Center](https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/AWSManagementPack.html)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring_automated_manual.md |
479e093dafa6-0 | Another important part of monitoring Amazon EC2 involves manually monitoring those items that the monitoring scripts, status checks, and CloudWatch alarms don't cover\. The Amazon EC2 and CloudWatch console dashboards provide an at\-a\-glance view of the state of your Amazon EC2 environment\.
+ Amazon EC2 Dashboard shows:
+ Service Health and Scheduled Events by Region
+ Instance state
+ Status checks
+ Alarm status
+ Instance metric details \(In the navigation pane choose **Instances**, select an instance, and choose the **Monitoring** tab\)
+ Volume metric details \(In the navigation pane choose **Volumes**, select a volume, and choose the **Monitoring** tab\)
+ Amazon CloudWatch Dashboard shows:
+ Current alarms and status
+ Graphs of alarms and resources
+ Service health status
In addition, you can use CloudWatch to do the following:
+ Graph Amazon EC2 monitoring data to troubleshoot issues and discover trends
+ Search and browse all your AWS resource metrics
+ Create and edit alarms to be notified of problems
+ See at\-a\-glance overviews of your alarms and AWS resources | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/monitoring_automated_manual.md |
1f196cbb2665-0 | After you attach an Amazon EBS volume to your instance, it is exposed as a block device\. You can format the volume with any file system and then mount it\. After you make the EBS volume available for use, you can access it in the same ways that you access any other volume\. Any data written to this file system is written to the EBS volume and is transparent to applications using the device\.
You can take snapshots of your EBS volume for backup purposes or to use as a baseline when you create another volume\. For more information, see [Amazon EBS snapshots](EBSSnapshots.md)\.
You can get directions for volumes on a Windows instance from [Making a Volume Available for Use on Windows](https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/ebs-using-volumes.html) in the *Amazon EC2 User Guide for Windows Instances*\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-using-volumes.md |
d02bea7ab8df-0 | Suppose that you have an EC2 instance with an EBS volume for the root device, `/dev/xvda`, and that you have just attached an empty EBS volume to the instance using `/dev/sdf`\. Use the following procedure to make the newly attached volume available for use\.
**To format and mount an EBS volume on Linux**
1. Connect to your instance using SSH\. For more information, see [Connect to your Linux instance](AccessingInstances.md)\.
1. The device could be attached to the instance with a different device name than you specified in the block device mapping\. For more information, see [Device naming on Linux instances](device_naming.md)\. Use the lsblk command to view your available disk devices and their mount points \(if applicable\) to help you determine the correct device name to use\. The output of lsblk removes the `/dev/` prefix from full device paths\.
The following is example output for an instance built on the [Nitro System](instance-types.md#ec2-nitro-instances), which exposes EBS volumes as NVMe block devices\. The root device is `/dev/nvme0n1`\. The attached volume is `/dev/nvme1n1`, which is not yet mounted\.
```
[ec2-user ~]$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
nvme1n1 259:0 0 10G 0 disk
nvme0n1 259:1 0 8G 0 disk | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-using-volumes.md |
d02bea7ab8df-1 | nvme1n1 259:0 0 10G 0 disk
nvme0n1 259:1 0 8G 0 disk
-nvme0n1p1 259:2 0 8G 0 part /
-nvme0n1p128 259:3 0 1M 0 part
```
The following is example output for a T2 instance\. The root device is `/dev/xvda`\. The attached volume is `/dev/xvdf`, which is not yet mounted\.
```
[ec2-user ~]$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
xvda 202:0 0 8G 0 disk
-xvda1 202:1 0 8G 0 part /
xvdf 202:80 0 10G 0 disk
```
1. Determine whether there is a file system on the volume\. New volumes are raw block devices, and you must create a file system on them before you can mount and use them\. Volumes that were created from snapshots likely have a file system on them already; if you create a new file system on top of an existing file system, the operation overwrites your data\.
Use the file \-s command to get information about a device, such as its file system type\. If the output shows simply `data`, as in the following example output, there is no file system on the device and you must create one\.
```
[ec2-user ~]$ sudo file -s /dev/xvdf | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-using-volumes.md |
d02bea7ab8df-2 | ```
[ec2-user ~]$ sudo file -s /dev/xvdf
/dev/xvdf: data
```
If the device has a file system, the command shows information about the file system type\. For example, the following output shows a root device with the XFS file system\.
```
[ec2-user ~]$ sudo file -s /dev/xvda1
/dev/xvda1: SGI XFS filesystem data (blksz 4096, inosz 512, v2 dirs)
```
1. <a name="create_file_system_step"></a>\(Conditional\) If you discovered that there is a file system on the device in the previous step, skip this step\. If you have an empty volume, use the mkfs \-t command to create a file system on the volume\.
**Warning**
Do not use this command if you're mounting a volume that already has data on it \(for example, a volume that was created from a snapshot\)\. Otherwise, you'll format the volume and delete the existing data\.
```
[ec2-user ~]$ sudo mkfs -t xfs /dev/xvdf
```
If you get an error that `mkfs.xfs` is not found, use the following command to install the XFS tools and then repeat the previous command:
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-using-volumes.md |
d02bea7ab8df-3 | ```
[ec2-user ~]$ sudo yum install xfsprogs
```
1. Use the mkdir command to create a mount point directory for the volume\. The mount point is where the volume is located in the file system tree and where you read and write files to after you mount the volume\. The following example creates a directory named `/data`\.
```
[ec2-user ~]$ sudo mkdir /data
```
1. Use the following command to mount the volume at the directory you created in the previous step\.
```
[ec2-user ~]$ sudo mount /dev/xvdf /data
```
1. Review the file permissions of your new volume mount to make sure that your users and applications can write to the volume\. For more information about file permissions, see [File security](http://tldp.org/LDP/intro-linux/html/sect_03_04.html) at *The Linux Documentation Project*\.
1. The mount point is not automatically preserved after rebooting your instance\. To automatically mount this EBS volume after reboot, see [Automatically mount an attached volume after reboot](#ebs-mount-after-reboot)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-using-volumes.md |
93803e7328d0-0 | To mount an attached EBS volume on every system reboot, add an entry for the device to the `/etc/fstab` file\.
You can use the device name, such as `/dev/xvdf`, in `/etc/fstab`, but we recommend using the device's 128\-bit universally unique identifier \(UUID\) instead\. Device names can change, but the UUID persists throughout the life of the partition\. By using the UUID, you reduce the chances that the system becomes unbootable after a hardware reconfiguration\. For more information, see [Identifying the EBS device](nvme-ebs-volumes.md#identify-nvme-ebs-device)\.
**To mount an attached volume automatically after reboot**
1. \(Optional\) Create a backup of your `/etc/fstab` file that you can use if you accidentally destroy or delete this file while editing it\.
```
[ec2-user ~]$ sudo cp /etc/fstab /etc/fstab.orig
```
1. Use the blkid command to find the UUID of the device\.
```
[ec2-user ~]$ sudo blkid | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-using-volumes.md |
93803e7328d0-1 | ```
[ec2-user ~]$ sudo blkid
/dev/xvda1: LABEL="/" UUID="ca774df7-756d-4261-a3f1-76038323e572" TYPE="xfs" PARTLABEL="Linux" PARTUUID="02dcd367-e87c-4f2e-9a72-a3cf8f299c10"
/dev/xvdf: UUID="aebf131c-6957-451e-8d34-ec978d9581ae" TYPE="xfs"
```
For Ubuntu 18\.04 use the lsblk command\.
```
[ec2-user ~]$ sudo lsblk -o +UUID
```
1. Open the `/etc/fstab` file using any text editor, such as nano or vim\.
```
[ec2-user ~]$ sudo vim /etc/fstab
```
1. Add the following entry to `/etc/fstab` to mount the device at the specified mount point\. The fields are the UUID value returned by blkid \(or lsblk for Ubuntu 18\.04\), the mount point, the file system, and the recommended file system mount options\. For more information, see the manual page for fstab \(run man fstab\)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-using-volumes.md |
93803e7328d0-2 | ```
UUID=aebf131c-6957-451e-8d34-ec978d9581ae /data xfs defaults,nofail 0 2
```
**Note**
If you ever boot your instance without this volume attached \(for example, after moving the volume to another instance\), the `nofail` mount option enables the instance to boot even if there are errors mounting the volume\. Debian derivatives, including Ubuntu versions earlier than 16\.04, must also add the `nobootwait` mount option\.
1. To verify that your entry works, run the following commands to unmount the device and then mount all file systems in `/etc/fstab`\. If there are no errors, the `/etc/fstab` file is OK and your file system will mount automatically after it is rebooted\.
```
[ec2-user ~]$ sudo umount /data
[ec2-user ~]$ sudo mount -a
```
If you receive an error message, address the errors in the file\.
**Warning**
Errors in the `/etc/fstab` file can render a system unbootable\. Do not shut down a system that has errors in the `/etc/fstab` file\.
If you are unsure how to correct errors in `/etc/fstab` and you created a backup file in the first step of this procedure, you can restore from your backup file using the following command\.
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-using-volumes.md |
93803e7328d0-3 | ```
[ec2-user ~]$ sudo mv /etc/fstab.orig /etc/fstab
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/ebs-using-volumes.md |
8393aa3eed52-0 | The following issues prevent you from launching an instance\.
**Topics**
+ [Instance limit exceeded](#troubleshooting-launch-limit)
+ [Insufficient instance capacity](#troubleshooting-launch-capacity)
+ [Instance terminates immediately](#troubleshooting-launch-internal) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/troubleshooting-launch.md |
382841ac3c26-0 | You get the `InstanceLimitExceeded` error when you try to launch a new instance or restart a stopped instance\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/troubleshooting-launch.md |
8e6ffe3f98a6-0 | If you get an `InstanceLimitExceeded` error when you try to launch a new instance or restart a stopped instance, you have reached the limit on the number of instances that you can launch in a Region\. When you create your AWS account, we set default limits on the number of instances you can run on a per\-Region basis\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/troubleshooting-launch.md |
c943f5bae32f-0 | You can request an instance limit increase on a per\-region basis\. For more information, see [Amazon EC2 service quotas](ec2-resource-limits.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/troubleshooting-launch.md |
9c6cd70d63ef-0 | You get the `InsufficientInstanceCapacity` error when you try to launch a new instance or restart a stopped instance\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/troubleshooting-launch.md |
310a33b309c8-0 | If you get an `InsufficientInstanceCapacity` error when you try to launch an instance or restart a stopped instance, AWS does not currently have enough available On\-Demand capacity to service your request\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/troubleshooting-launch.md |
3504f707b2f6-0 | To resolve the issue, try the following:
+ Wait a few minutes and then submit your request again; capacity can shift frequently\.
+ Submit a new request with a reduced number of instances\. For example, if you're making a single request to launch 15 instances, try making 3 requests for 5 instances, or 15 requests for 1 instance instead\.
+ If you're launching an instance, submit a new request without specifying an Availability Zone\.
+ If you're launching an instance, submit a new request using a different instance type \(which you can resize at a later stage\)\. For more information, see [Changing the instance type](ec2-instance-resize.md)\.
+ If you are launching instances into a cluster placement group, you can get an insufficient capacity error\. For more information, see [Placement group rules and limitations](placement-groups.md#concepts-placement-groups)\.
+ Try creating an On\-Demand Capacity Reservation, which enables you to reserve Amazon EC2 capacity for any duration\. For more information, see [On\-Demand Capacity Reservations](ec2-capacity-reservations.md)\.
+ Try purchasing Reserved Instances, which are a long\-term capacity reservation\. For more information, see [Amazon EC2 Reserved Instances](https://aws.amazon.com/ec2/purchasing-options/reserved-instances/)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/troubleshooting-launch.md |
a5e882b3f683-0 | Your instance goes from the `pending` state to the `terminated` state immediately after restarting it\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/troubleshooting-launch.md |
634600f1d2a0-0 | The following are a few reasons why an instance might immediately terminate:
+ You've reached your EBS volume limit\.
+ An EBS snapshot is corrupt\.
+ The root EBS volume is encrypted and you do not have permissions to access the KMS key for decryption\.
+ The instance store\-backed AMI that you used to launch the instance is missing a required part \(an image\.part\.*xx* file\)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/troubleshooting-launch.md |
d10acfa941e5-0 | You can use the Amazon EC2 console or AWS Command Line Interface to get the termination reason\.
**To get the termination reason using the Amazon EC2 console**
1. Open the Amazon EC2 console at [https://console\.aws\.amazon\.com/ec2/](https://console.aws.amazon.com/ec2/)\.
1. In the navigation pane, choose **Instances**, and select the instance\.
1. In the **Description** tab, note the reason next to the **State transition reason** label\.
**To get the termination reason using the AWS Command Line Interface**
1. Use the [describe\-instances](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-instances.html) command and specify the instance ID\.
```
aws ec2 describe-instances --instance-id instance_id
```
1. Review the JSON response returned by the command and note the values in the `StateReason` response element\.
The following code block shows an example of a `StateReason` response element\.
```
"StateReason": {
"Message": "Client.VolumeLimitExceeded: Volume limit exceeded",
"Code": "Server.InternalError"
},
```
**To address the issue** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/troubleshooting-launch.md |
d10acfa941e5-1 | "Code": "Server.InternalError"
},
```
**To address the issue**
Take one of the following actions depending on the termination reason you noted:
+ If the reason is **`Client.VolumeLimitExceeded: Volume limit exceeded`**, you have reached your EBS volume limit\. For more information, see [Instance volume limits](volume_limits.md)\. To submit a request to increase your Amazon EBS volume limit, complete the AWS Support Center [Create Case](https://console.aws.amazon.com/support/home#/case/create?issueType=service-limit-increase&limitType=service-code-ebs) form\. For more information, see [Amazon EC2 service quotas](ec2-resource-limits.md)\.
+ If the reason is **`Client.InternalError: Client error on launch`**, that typically indicates that the root volume is encrypted and that you do not have permissions to access the KMS key for decryption\. To get permissions to access the required KMS key, add the appropriate KMS permissions to your IAM user\. For more information, see [Using Key Policies in AWS KMS](https://docs.aws.amazon.com/kms/latest/developerguide/key-policies.html) in the *AWS Key Management Service Developer Guide*\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/troubleshooting-launch.md |
a838b5ad7762-0 | When you attach a volume to your instance, you include a device name for the volume\. This device name is used by Amazon EC2\. The block device driver for the instance assigns the actual volume name when mounting the volume, and the name assigned can be different from the name that Amazon EC2 uses\.
The number of volumes that your instance can support is determined by the operating system\. For more information, see [Instance volume limits](volume_limits.md)\.
**Topics**
+ [Available device names](#available-ec2-device-names)
+ [Device name considerations](#device-name-limits)
For information about device names on Windows instances, see [Device naming on Windows instances](https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/device_naming.html) in the *Amazon EC2 User Guide for Windows Instances*\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/device_naming.md |
baa33f5e0d2a-0 | There are two types of virtualization available for Linux instances: paravirtual \(PV\) and hardware virtual machine \(HVM\)\. The virtualization type of an instance is determined by the AMI used to launch the instance\. All instance types support HVM AMIs\. Some previous generation instance types support PV AMIs\. Be sure to note the virtualization type of your AMI because the recommended and available device names that you can use depend on the virtualization type of your instance\. For more information, see [Linux AMI virtualization types](virtualization_types.md)\.
The following table lists the available device names that you can specify in a block device mapping or when attaching an EBS volume\.
| Virtualization type | Available | Reserved for root | Recommended for EBS volumes | Instance store volumes |
| --- | --- | --- | --- | --- |
| Paravirtual | /dev/sd\[a\-z\] /dev/sd\[a\-z\]\[1\-15\] /dev/hd\[a\-z\] /dev/hd\[a\-z\]\[1\-15\] | /dev/sda1 | /dev/sd\[f\-p\] /dev/sd\[f\-p\]\[1\-6\] | /dev/sd\[b\-e\] | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/device_naming.md |
baa33f5e0d2a-1 | | HVM | /dev/sd\[a\-z\] /dev/xvd\[b\-c\]\[a\-z\] | Differs by AMI /dev/sda1 or /dev/xvda | /dev/sd\[f\-p\] \* | /dev/sd\[b\-e\] /dev/sd\[b\-h\] \(h1\.16xlarge\) /dev/sd\[b\-y\] \(d2\.8xlarge\) /dev/sd\[b\-i\] \(i2\.8xlarge\) \*\* |
\* The device names that you specify for NVMe EBS volumes 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\.
\*\* NVMe instance store volumes are automatically enumerated and assigned an NVMe device name\.
For more information about instance store volumes, see [Amazon EC2 instance store](InstanceStorage.md)\. For more information about NVMe EBS volumes \(Nitro\-based instances\), including how to identify the EBS device, see [Amazon EBS and NVMe on Linux instances](nvme-ebs-volumes.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/device_naming.md |
41e0198cc71d-0 | Keep the following in mind when selecting a device name:
+ Although you can attach your EBS volumes using the device names used to attach instance store volumes, we strongly recommend that you don't because the behavior can be unpredictable\.
+ The number of NVMe instance store volumes for an instance depends on the size of the instance\. NVMe instance store volumes are automatically enumerated and assigned an NVMe device name \(`/dev/nvme[0-26]n1`\)\.
+ Depending on the block device driver of the kernel, the device could be attached with a different name than you specified\. For example, if you specify a device name of `/dev/sdh`, your device could be renamed `/dev/xvdh` or `/dev/hdh`\. In most cases, the trailing letter remains the same\. In some versions of Red Hat Enterprise Linux \(and its variants, such as CentOS\), the trailing letter could change \(`/dev/sda` could become `/dev/xvde`\)\. In these cases, the trailing letter of each device name is incremented the same number of times\. For example, if `/dev/sdb` is renamed `/dev/xvdf`, then `/dev/sdc` is renamed `/dev/xvdg`\. Amazon Linux creates a symbolic link for the name you specified to the renamed device\. Other operating systems could behave differently\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/device_naming.md |
41e0198cc71d-1 | + HVM AMIs do not support the use of trailing numbers on device names, except for `/dev/sda1`, which is reserved for the root device, and `/dev/sda2`\. While using `/dev/sda2` is possible, we do not recommend using this device mapping with HVM instances\.
+ When using PV AMIs, you cannot attach volumes that share the same device letters both with and without trailing digits\. For example, if you attach a volume as `/dev/sdc` and another volume as `/dev/sdc1`, only `/dev/sdc` is visible to the instance\. To use trailing digits in device names, you must use trailing digits on all device names that share the same base letters \(such as `/dev/sdc1`, `/dev/sdc2`, `/dev/sdc3`\)\.
+ Some custom kernels might have restrictions that limit use to `/dev/sd[f-p]` or `/dev/sd[f-p][1-6]`\. If you're having trouble using `/dev/sd[q-z]` or `/dev/sd[q-z][1-6]`, try switching to `/dev/sd[f-p]` or `/dev/sd[f-p][1-6]`\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/device_naming.md |
d1444fb2a2df-0 | An instance with an attached GPU, such as a P3 or G4 instance, must have the appropriate NVIDIA driver installed\. Depending on the instance type, you can either download a public NVIDIA driver, download a driver from Amazon S3 that is available only to AWS customers, or use an AMI with the driver pre\-installed\.
**Contents**
+ [Types of NVIDIA drivers](#nvidia-driver-types)
+ [Available drivers by instance type](#nvidia-driver-instance-type)
+ [Installation options](#nvidia-installation-options)
+ [Option 1: AMIs with the NVIDIA drivers installed](#preinstalled-nvidia-driver)
+ [Option 2: Public NVIDIA drivers](#public-nvidia-driver)
+ [Option 3: GRID drivers \(G3 and G4 instances\)](#nvidia-GRID-driver)
+ [Option 4: NVIDIA gaming drivers \(G4 instances\)](#nvidia-gaming-driver)
+ [Installing an additional version of CUDA](#gpu-instance-install-cuda) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/install-nvidia-driver.md |
1ae0c0f05c31-0 | The following are the main types of NVIDIA drivers that can be used with GPU\-based instances\.
Tesla drivers
These drivers are intended primarily for compute workloads, which use GPUs for computational tasks such as parallelized floating\-point calculations for machine learning and fast Fourier transforms for high performance computing applications\.
GRID drivers
These drivers are certified to provide optimal performance for professional visualization applications that render content such as 3D models or high\-resolution videos\. You can configure GRID drivers to support two modes\. Quadro Virtual Workstations provide access to four 4K displays per GPU\. GRID vApps provide RDSH App hosting capabilities\.
Gaming drivers
These drivers contain optimizations for gaming and are updated frequently to provide performance enhancements\. They support a single 4K display per GPU\.
**NVIDIA control panel**
The NVIDIA control panel is supported with GRID and Gaming drivers\. It is not supported with Tesla drivers\.
**Supported APIs for Tesla, GRID, and gaming drivers**
+ OpenCL, OpenGL, and Vulkan
+ NVIDIA CUDA and related libraries \(for example, cuDNN, TensorRT, nvJPEG, and cuBLAS\)
+ NVENC for video encoding and NVDEC for video decoding | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/install-nvidia-driver.md |
68cce3038857-0 | The following table summarizes the supported NVIDIA drivers for each GPU instance type\.
| Instance type | Tesla driver | GRID driver | Gaming driver |
| --- | --- | --- | --- |
| G2 | No | Yes | No |
| G3 | Yes | Yes | No |
| G4 | Yes | Yes | Yes |
| P2 | Yes | No | No |
| P3 | Yes | Yes † | No |
† Using Marketplace AMIs only | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/install-nvidia-driver.md |
3fe3ca622114-0 | Use one of the following options to get the NVIDIA drivers required for your GPU instance\.
**Topics**
+ [Option 1: AMIs with the NVIDIA drivers installed](#preinstalled-nvidia-driver)
+ [Option 2: Public NVIDIA drivers](#public-nvidia-driver)
+ [Option 3: GRID drivers \(G3 and G4 instances\)](#nvidia-GRID-driver)
+ [Option 4: NVIDIA gaming drivers \(G4 instances\)](#nvidia-gaming-driver) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/install-nvidia-driver.md |
2d64deb853ce-0 | AWS and NVIDIA offer different Amazon Machine Images \(AMI\) that come with the NVIDIA drivers installed\.
+ [Marketplace offerings with the Tesla driver](http://aws.amazon.com/marketplace/search/results?page=1&filters=VendorId&VendorId=e6a5002c-6dd0-4d1e-8196-0a1d1857229b%2Cc568fe05-e33b-411c-b0ab-047218431da9&searchTerms=tesla+driver)
+ [Marketplace offerings with the GRID driver](http://aws.amazon.com/marketplace/search/results?&searchTerms=NVIDIA+quadro)
+ [Marketplace offerings with the Gaming driver](http://aws.amazon.com/marketplace/search/results?searchTerms=NVIDIA+gaming)
To update the driver version installed using one of these AMIs, you must uninstall the NVIDIA packages from your instance to avoid version conflicts\. Use this command to uninstall the NVIDIA packages:
```
[ec2-user ~]$ sudo yum erase nvidia cuda
```
The CUDA toolkit package has dependencies on the NVIDIA drivers\. Uninstalling the NVIDIA packages erases the CUDA toolkit\. You must reinstall the CUDA toolkit after installing the NVIDIA driver\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/install-nvidia-driver.md |
4e43f129b2ea-0 | The options offered by AWS come with the necessary license for the driver\. Alternatively, you can install the public drivers and bring your own license\. To install a public driver, download it from the NVIDIA site as described here\.
Alternatively, you can use the options offered by AWS instead of the public drivers\. To use a GRID driver on a P3 instance, use the AWS Marketplace AMIs as described in [Option 1](#preinstalled-nvidia-driver)\. To use a GRID driver on a G3 or G4 instance, use the AWS Marketplace AMIs, as described in Option 1 or install the NVIDIA drivers provided by AWS as described in [Option 3](#nvidia-GRID-driver)\.
**To download a public NVIDIA driver**
Log on to your Linux instance and download the 64\-bit NVIDIA driver appropriate for the instance type from [http://www\.nvidia\.com/Download/Find\.aspx](http://www.nvidia.com/Download/Find.aspx)\. For **Product Type**, **Product Series**, and **Product**, use the options in the following table\.
| Instance | Product Type | Product Series | Product |
| --- | --- | --- | --- |
| G2 | GRID | GRID Series | GRID K520 |
| G3 | Tesla | M\-Class | M60 |
| G4 † | Tesla | T\-Series | T4 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/install-nvidia-driver.md |
4e43f129b2ea-1 | | G3 | Tesla | M\-Class | M60 |
| G4 † | Tesla | T\-Series | T4 |
| P2 | Tesla | K\-Series | K80 |
| P3 | Tesla | V\-Series | V100 |
† G4 instances require driver version 418\.87 or later\.
**To install the NVIDIA driver on Linux**
For more information about installing and configuring the driver, see the [NVIDIA Driver Installation Quickstart Guide](https://docs.nvidia.com/datacenter/tesla/tesla-installation-notes/index.html)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/install-nvidia-driver.md |
1348503896b7-0 | These downloads are available to AWS customers only\. By downloading, you agree to use the downloaded software only to develop AMIs for use with the NVIDIA Tesla T4 or NVIDIA Tesla M60 hardware\. Upon installation of the software, you are bound by the terms of the [NVIDIA GRID Cloud End User License Agreement](https://aws-nvidia-license-agreement.s3.amazonaws.com/NvidiaGridAWSUserLicenseAgreement.DOCX)\.
**Prerequisites**
+ Install the AWS CLI on your Linux instance and configure default credentials\. For more information, see [Installing the AWS CLI](https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-install.html) in the *AWS Command Line Interface User Guide*\.
+ IAM users must have the permissions granted by the **AmazonS3ReadOnlyAccess** policy\.
**To install the NVIDIA GRID driver on your Linux instance**
1. Connect to your Linux instance\. Install gcc and make, if they are not already installed\.
1. Update your package cache and get necessary package updates for your instance\.
+ For Amazon Linux, CentOS, and Red Hat Enterprise Linux:
```
[ec2-user ~]$ sudo yum update -y
```
+ For Ubuntu and Debian:
```
$ sudo apt-get update -y | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/install-nvidia-driver.md |
1348503896b7-1 | ```
+ For Ubuntu and Debian:
```
$ sudo apt-get update -y
```
1. \(Ubuntu 16\.04 and later, with the `linux-aws` package\) Upgrade the `linux-aws` package to receive the latest version\.
```
$ sudo apt-get upgrade -y linux-aws
```
1. Reboot your instance to load the latest kernel version\.
```
[ec2-user ~]$ sudo reboot
```
1. Reconnect to your instance after it has rebooted\.
1. Install the gcc compiler and the kernel headers package for the version of the kernel you are currently running\.
+ For Amazon Linux, CentOS, and Red Hat Enterprise Linux:
```
[ec2-user ~]$ sudo yum install -y gcc kernel-devel-$(uname -r)
```
+ For Ubuntu and Debian:
```
$ sudo apt-get install -y gcc make linux-headers-$(uname -r)
```
1. \[CentOS, Red Hat Enterprise Linux, Ubuntu, Debian\] Disable the `nouveau` open source driver for NVIDIA graphics cards\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/install-nvidia-driver.md |
1348503896b7-2 | 1. \[CentOS, Red Hat Enterprise Linux, Ubuntu, Debian\] Disable the `nouveau` open source driver for NVIDIA graphics cards\.
1. Add `nouveau` to the `/etc/modprobe.d/blacklist.conf` blacklist file\. Copy the following code block and paste it into a terminal\.
```
[ec2-user ~]$ cat << EOF | sudo tee --append /etc/modprobe.d/blacklist.conf
blacklist vga16fb
blacklist nouveau
blacklist rivafb
blacklist nvidiafb
blacklist rivatv
EOF
```
1. Edit the `/etc/default/grub` file and add the following line:
```
GRUB_CMDLINE_LINUX="rdblacklist=nouveau"
```
1. Rebuild the Grub configuration\.
+ For CentOS and Red Hat Enterprise Linux:
```
[ec2-user ~]$ sudo grub2-mkconfig -o /boot/grub2/grub.cfg
```
+ For Ubuntu and Debian:
```
$ sudo update-grub
```
1. Download the GRID driver installation utility using the following command:
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/install-nvidia-driver.md |
1348503896b7-3 | $ sudo update-grub
```
1. Download the GRID driver installation utility using the following command:
```
[ec2-user ~]$ aws s3 cp --recursive s3://ec2-linux-nvidia-drivers/latest/ .
```
Multiple versions of the GRID driver are stored in this bucket\. You can see all of the available versions using the following command\.
```
[ec2-user ~]$ aws s3 ls --recursive s3://ec2-linux-nvidia-drivers/
```
Starting with GRID version 11\.0, you can use the driver packages under `latest` for both G3 and G4 instances\. We will not add versions later than 11\.0 to `g4/latest`, but will keep version 11\.0 and the earlier versions specific to G4 under `g4/latest`\.
1. Add permissions to run the driver installation utility using the following command\.
```
[ec2-user ~]$ chmod +x NVIDIA-Linux-x86_64*.run
```
1. Run the self\-install script as follows to install the GRID driver that you downloaded\. For example:
```
[ec2-user ~]$ sudo /bin/sh ./NVIDIA-Linux-x86_64*.run
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/install-nvidia-driver.md |
1348503896b7-4 | [ec2-user ~]$ sudo /bin/sh ./NVIDIA-Linux-x86_64*.run
```
When prompted, accept the license agreement and specify the installation options as required \(you can accept the default options\)\.
1. Reboot the instance\.
```
[ec2-user ~]$ sudo reboot
```
1. Confirm that the driver is functional\. The response for the following command lists the installed version of the NVIDIA driver and details about the GPUs\.
```
[ec2-user ~]$ nvidia-smi -q | head
```
1. \(Optional\) Depending on your use case, you might complete the following optional steps\. If you do not require this functionality, do not complete these steps\.
1. To help take advantage of the four displays of up to 4K resolution, set up the high\-performance display protocol [NICE DCV](https://docs.aws.amazon.com/dcv)\.
1. NVIDIA Quadro Virtual Workstation mode is enabled by default\. To activate GRID Virtual Applications for RDSH Application hosting capabilities, complete the GRID Virtual Application activation steps in [Activate NVIDIA GRID Virtual Applications](activate_grid.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/install-nvidia-driver.md |
ad48a929f176-0 | These drivers are available to AWS customers only\. By downloading them, you agree to use the downloaded software only to develop AMIs for use with the NVIDIA Tesla T4 hardware\. Upon installation of the software, you are bound by the terms of the [NVIDIA GRID Cloud End User License Agreement](https://aws-nvidia-license-agreement.s3.amazonaws.com/NvidiaGridAWSUserLicenseAgreement.DOCX)\.
**Prerequisites**
+ Install the AWS CLI on your Linux instance and configure default credentials\. For more information, see [Installing the AWS CLI](https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-install.html) in the *AWS Command Line Interface User Guide*\.
+ IAM users must have the permissions granted by the **AmazonS3ReadOnlyAccess** policy\.
**To install the NVIDIA gaming driver on your Linux instance**
1. Connect to your Linux instance\. Install gcc and make, if they are not already installed\.
1. Update your package cache and get necessary package updates for your instance\.
+ For Amazon Linux, CentOS, and Red Hat Enterprise Linux:
```
[ec2-user ~]$ sudo yum update -y
```
+ For Ubuntu and Debian:
```
$ sudo apt-get update -y
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/install-nvidia-driver.md |
ad48a929f176-1 | + For Ubuntu and Debian:
```
$ sudo apt-get update -y
```
1. \(Ubuntu 16\.04 and later, with the `linux-aws` package\) Upgrade the `linux-aws` package to receive the latest version\.
```
$ sudo apt-get upgrade -y linux-aws
```
1. Reboot your instance to load the latest kernel version\.
```
[ec2-user ~]$ sudo reboot
```
1. Reconnect to your instance after it has rebooted\.
1. Install the gcc compiler and the kernel headers package for the version of the kernel you are currently running\.
+ For Amazon Linux, CentOS, and Red Hat Enterprise Linux:
```
[ec2-user ~]$ sudo yum install -y gcc kernel-devel-$(uname -r)
```
+ For Ubuntu and Debian:
```
$ sudo apt-get install -y gcc make linux-headers-$(uname -r)
```
1. \[CentOS, Red Hat Enterprise Linux, Ubuntu, Debian\] Disable the `nouveau` open source driver for NVIDIA graphics cards\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/install-nvidia-driver.md |
ad48a929f176-2 | 1. \[CentOS, Red Hat Enterprise Linux, Ubuntu, Debian\] Disable the `nouveau` open source driver for NVIDIA graphics cards\.
1. Add `nouveau` to the `/etc/modprobe.d/blacklist.conf` blacklist file\. Copy the following code block and paste it into a terminal\.
```
[ec2-user ~]$ cat << EOF | sudo tee --append /etc/modprobe.d/blacklist.conf
blacklist vga16fb
blacklist nouveau
blacklist rivafb
blacklist nvidiafb
blacklist rivatv
EOF
```
1. Edit the `/etc/default/grub` file and add the following line:
```
GRUB_CMDLINE_LINUX="rdblacklist=nouveau"
```
1. Rebuild the Grub configuration\.
+ For CentOS and Red Hat Enterprise Linux:
```
[ec2-user ~]$ sudo grub2-mkconfig -o /boot/grub2/grub.cfg
```
+ For Ubuntu and Debian:
```
$ sudo update-grub
```
1. Download the gaming driver installation utility using the following command:
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/install-nvidia-driver.md |
ad48a929f176-3 | $ sudo update-grub
```
1. Download the gaming driver installation utility using the following command:
```
[ec2-user ~]$ aws s3 cp --recursive s3://nvidia-gaming/linux/latest/ .
```
Multiple versions of the gaming driver are stored in this bucket\. You can see all of the available versions using the following command:
```
[ec2-user ~]$ aws s3 ls --recursive s3://nvidia-gaming/linux/
```
1. Add permissions to run the driver installation utility using the following command\.
```
[ec2-user ~]$ chmod +x NVIDIA-Linux-x86_64*.run
```
1. Run the installer using the following command:
```
[ec2-user ~]$ sudo ./NVIDIA-Linux-x86_64*.run
```
When prompted, accept the license agreement and specify the installation options as required \(you can accept the default options\)\.
1. Use the following command to create the required configuration file\.
```
[ec2-user ~]$ cat << EOF | sudo tee -a /etc/nvidia/gridd.conf
vGamingMarketplace=2
EOF | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/install-nvidia-driver.md |
ad48a929f176-4 | vGamingMarketplace=2
EOF
```
1. Use the following command to download and rename the certification file\.
+ For version 440\.68 or later:
```
[ec2-user ~]$ sudo curl -o /etc/nvidia/GridSwCert.txt "https://nvidia-gaming.s3.amazonaws.com/GridSwCert-Archive/GridSwCert-Linux_2020_04.cert"
```
+ For earlier versions:
```
[ec2-user ~]$ sudo curl -o /etc/nvidia/GridSwCert.txt "https://nvidia-gaming.s3.amazonaws.com/GridSwCert-Archive/GridSwCert-Linux_2019_09.cert"
```
1. Reboot the instance\.
```
[ec2-user ~]$ sudo reboot
```
1. \(Optional\) To help take advantage of a single display of up to 4K resolution, set up the high\-performance display protocol [NICE DCV](https://docs.aws.amazon.com/dcv)\. If you do not require this functionality, do not complete this step\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/install-nvidia-driver.md |
7a09f6e66bf0-0 | After you install an NVIDIA graphics driver on your instance, you can install a version of CUDA other than the version that is bundled with the graphics driver\. The following procedure demonstrates how to configure multiple versions of CUDA on the instance\.
**To install the CUDA toolkit**
1. Connect to your Linux instance\.
1. Open the [NVIDIA website](https://developer.nvidia.com/cuda-downloads?target_os=Linux) and select the version of CUDA that you need\.
1. Select the architecture, distribution, and version for the operating system on your instance\. For **Installer Type**, select **runfile \(local\)**\.
1. Follow the instructions to download the install script\.
1. Add run permissions to the install script that you downloaded using the following command\.
```
[ec2-user ~]$ chmod +x downloaded_installer_file
```
1. Run the install script as follows to install the CUDA toolkit and add the CUDA version number to the toolkit path\.
```
[ec2-user ~]$ sudo downloaded_installer_file --silent --override --toolkit --samples --toolkitpath=/usr/local/cuda-version --samplespath=/usr/local/cuda --no-opengl-lib
```
1. \(Optional\) Set the default CUDA version as follows\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/install-nvidia-driver.md |
7a09f6e66bf0-1 | ```
1. \(Optional\) Set the default CUDA version as follows\.
```
[ec2-user ~]$ ln -s /usr/local/cuda-version /usr/local/cuda
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/install-nvidia-driver.md |
3321250cbd66-0 | A burstable performance instance configured as `standard` is suited to workloads with an average CPU utilization that is consistently below the baseline CPU utilization of the instance\. To burst above the baseline, the instance spends credits that it has accrued in its CPU credit balance\. If the instance is running low on accrued credits, CPU utilization is gradually lowered to the baseline level, so that the instance does not experience a sharp performance drop\-off when its accrued CPU credit balance is depleted\. For more information, see [CPU credits and baseline utilization for burstable performance instances](burstable-credits-baseline-concepts.md)\.
**Contents**
+ [Standard mode concepts](burstable-performance-instances-standard-mode-concepts.md)
+ [How standard burstable performance instances work](burstable-performance-instances-standard-mode-concepts.md#how-burstable-performance-instances-standard-works)
+ [Launch credits](burstable-performance-instances-standard-mode-concepts.md#launch-credits)
+ [Launch credit limits](burstable-performance-instances-standard-mode-concepts.md#launch-credit-limits)
+ [Differences between launch credits and earned credits](burstable-performance-instances-standard-mode-concepts.md#burstable-performance-instances-diff-launch-earned-credits)
+ [Standard mode examples](standard-mode-examples.md)
+ [Example 1: Explaining credit use with T3 Standard](standard-mode-examples.md#t3_standard_example) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/burstable-performance-instances-standard-mode.md |
3321250cbd66-1 | + [Example 1: Explaining credit use with T3 Standard](standard-mode-examples.md#t3_standard_example)
+ [Example 2: Explaining credit use with T2 Standard](standard-mode-examples.md#t2-standard-example)
+ [Period 1: 1 – 24 hours](standard-mode-examples.md#period-1)
+ [Period 2: 25 – 36 hours](standard-mode-examples.md#period-2)
+ [Period 3: 37 – 61 hours](standard-mode-examples.md#period-3)
+ [Period 4: 62 – 72 hours](standard-mode-examples.md#period-4)
+ [Period 5: 73 – 75 hours](standard-mode-examples.md#period-5)
+ [Period 6: 76 – 90 hours](standard-mode-examples.md#period-6)
+ [Period 7: 91 – 96 hours](standard-mode-examples.md#period-7) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/burstable-performance-instances-standard-mode.md |
a5b92e1d278d-0 | The maximum number of volumes that your instance can have depends on the operating system and instance type\. When considering how many volumes to add to your instance, you should consider whether you need increased I/O bandwidth or increased storage capacity\.
**Topics**
+ [Nitro System volume limits](#instance-type-volume-limits)
+ [Linux\-specific volume limits](#linux-specific-volume-limits)
+ [Bandwidth versus capacity](#storage-bandwidth) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/volume_limits.md |
097ddd93500f-0 | Instances built on the [Nitro System](instance-types.md#ec2-nitro-instances) support a maximum number of attachments, which are shared between network interfaces, EBS volumes, and NVMe instance store volumes\. Every instance has at least one network interface attachment\. NVMe instance store volumes are automatically attached\. For more information, see [Elastic network interfaces](using-eni.md) and [Instance store volumes](InstanceStorage.md#instance-store-volumes)\.
Most of these instances support a maximum of 28 attachments\. For example, if you have no additional network interface attachments on an EBS\-only instance, you can attach up to 27 EBS volumes to it\. If you have one additional network interface on an instance with 2 NVMe instance store volumes, you can attach 24 EBS volumes to it\.
For other instances, the following limits apply:
+ `inf1.xlarge` and `inf1.2xlarge` instances support a maximum of 26 EBS volumes\.
+ `inf1.6xlarge` instances support a maximum of 23 volumes\.
+ `inf1.24xlarge` instances support a maximum of 11 EBS volumes\.
+ Most bare metal instances support a maximum of 31 EBS volumes\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/volume_limits.md |
097ddd93500f-1 | + Most bare metal instances support a maximum of 31 EBS volumes\.
+ `u-6tb1.metal`, `u-9tb1.metal`, and `u-12tb1.metal` instances support a maximum of 19 EBS volumes if launched after March 12, 2020 and a maximum of 14 EBS volumes otherwise\. To attach more than 14 EBS volumes to an instance launched before March 12, 2020, contact your account team to upgrade the instance at no additional cost\.
+ `u-18tb1.metal` and `u-24tb1.metal` instances support a maximum of 19 EBS volumes\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/volume_limits.md |
588fa227503c-0 | Attaching more than 40 volumes can cause boot failures\. This number includes the root volume, plus any attached instance store volumes and EBS volumes\. If you experience boot problems on an instance with a large number of volumes, stop the instance, detach any volumes that are not essential to the boot process, and then reattach the volumes after the instance is running\.
**Important**
Attaching more than 40 volumes to a Linux instance is supported on a best effort basis only and is not guaranteed\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/volume_limits.md |
6ca483e7e9de-0 | For consistent and predictable bandwidth use cases, use EBS\-optimized or 10 Gigabit network connectivity instances and General Purpose SSD or Provisioned IOPS SSD volumes\. Follow the guidance in [Amazon EBS–optimized instances](ebs-optimized.md) to match the IOPS you have provisioned for your volumes to the bandwidth available from your instances for maximum performance\. For RAID configurations, many administrators find that arrays larger than 8 volumes have diminished performance returns due to increased I/O overhead\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/volume_limits.md |
6ca483e7e9de-1 | performance returns due to increased I/O overhead\. Test your individual application performance and tune it as required\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/volume_limits.md |
b92f920c24d7-0 | The Nvidia Collective Communications Library \(NCCL\) is a library of standard collective communication routines for multiple GPUs across a single node or multiple nodes\. NCCL can be used together with EFA, Libfabric, and MPI to support various machine learning workloads\. For more information, see the [NCCL](https://developer.nvidia.com/nccl) website\.
**Note**
NCCL with EFA is supported with p3dn\.24xlarge instances only\.
Only NCCL 2\.4\.2 and later is supported with EFA\.
The following tutorials help you to launch an EFA and NCCL\-enabled instance cluster for machine learning workloads\.
+ [Using a base AMI](efa-start-nccl-base.md)
+ [Using an AWS Deep Learning AMI](efa-start-nccl-dlami.md) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/efa-start-nccl.md |
7c0a1beb486c-0 | An instance is scheduled to be retired when AWS detects irreparable failure of the underlying hardware that hosts the instance\. When an instance reaches its scheduled retirement date, it is stopped or terminated by AWS\.
+ If your instance root device is an Amazon EBS volume, the instance is stopped, and you can start it again at any time\. Starting the stopped instance migrates it to new hardware\.
+ If your instance root device is an instance store volume, the instance is terminated, and cannot be used again\.
For more information about the types of instance events, see [Scheduled events for your instances](monitoring-instances-status-check_sched.md)\.
**Topics**
+ [Identifying instances scheduled for retirement](#instance-retirement-identify)
+ [Actions to take for EBS\-backed instances scheduled for retirement](#instance-retirement-actions-EBS)
+ [Actions to take for instance\-store backed instances scheduled for retirement](#instance-retirement-actions-instance-store) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-retirement.md |
fc61340fca5b-0 | If your instance is scheduled for retirement, you receive an email prior to the event with the instance ID and retirement date\. You can also check for instances that are scheduled for retirement using the Amazon EC2 console or the command line\.
**Important**
If an instance is scheduled for retirement, we recommend that you take action as soon as possible because the instance might be unreachable\. \(The email notification you receive states the following: "Due to this degradation your instance could already be unreachable\."\) For more information about the recommended action you should take, see [Check if your instance is reachable](#check-instance)\.
**Topics**
+ [Email notification](#identify-by-email)
+ [Console identification](#identify-in-console-cli) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-retirement.md |
de07e7668cc9-0 | If your instance is scheduled for retirement, you receive an email prior to the event with the instance ID and retirement date\.
The email is sent to the address that's associated with your account\. It's the same email address that you use to log in to the AWS Management Console\. To update the contact information for your account, go to the [Account Settings](https://console.aws.amazon.com/billing/home?#/account) page\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-retirement.md |
805b6927e14c-0 | If you use an email account that you do not check regularly for instance retirement notifications, you can use the Amazon EC2 console or the command line to determine if any of your instances are scheduled for retirement\.<a name="identify-retiring-instances"></a>
**To identify instances scheduled for retirement using the console**
1. Open the Amazon EC2 console\.
1. In the navigation pane, choose **EC2 Dashboard**\. Under **Scheduled events**, you can see the events that are associated with your Amazon EC2 instances and volumes, organized by Region\.
![\[Scheduled events\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/dashboard-scheduled-events.png)
1. If you have an instance with a scheduled event listed, select its link below the Region name to go to the **Events** page\.
1. The **Events** page lists all resources that have events associated with them\. To view instances that are scheduled for retirement, select **Instance resources** from the first filter list, and then **Instance stop or retirement** from the second filter list\.
1. If the filter results show that an instance is scheduled for retirement, select it, and note the date and time in the **Start time** field in the details pane\. This is your instance retirement date\.
**To identify instances scheduled for retirement using the command line** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-retirement.md |
805b6927e14c-1 | **To identify instances scheduled for retirement using the command line**
You can use one of the following commands\. For more information about these command line interfaces, see [Accessing Amazon EC2](concepts.md#access-ec2)\.
+ [describe\-instance\-status](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-instance-status.html) \(AWS CLI\)
+ [Get\-EC2InstanceStatus](https://docs.aws.amazon.com/powershell/latest/reference/items/Get-EC2InstanceStatus.html) \(AWS Tools for Windows PowerShell\) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-retirement.md |
b294fb1423ad-0 | To preserve the data on your retiring instance, you can perform one of the following actions\. It's important that you take this action before the instance retirement date to prevent unforeseen downtime and data loss\.
If you are not sure whether your instance is backed by EBS or instance store, see [Determining the root device type of your instance](RootDeviceStorage.md#display-instance-root-device-type)\.
**Check if your instance is reachable**
When you are notified that your instance is scheduled for retirement, we recommend that you take the following action as soon as possible:
+ Check if your instance is reachable by either [connecting](AccessingInstances.md) to or pinging your instance\.
+ If your instance is reachable, you should plan to stop/start your instance at an appropriate time before the scheduled retirement date, when the impact is minimal\. For more information about stopping and starting your instance, and what to expect when your instance is stopped, such as the effect on public, private, and Elastic IP addresses that are associated with your instance, see [Stop and start your instance](Stop_Start.md)\. Note that data on instance store volumes is lost when you stop and start your instance\.
+ If your instance is unreachable, you should take immediate action and perform a [stop/start](Stop_Start.md) to recover your instance\.
+ Alternatively, if you want to [terminate](terminating-instances.md) your instance, plan to do so as soon as possible so that you stop incurring charges for the instance\.
**Create a backup of your instance** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-retirement.md |
b294fb1423ad-1 | **Create a backup of your instance**
Create an EBS\-backed AMI from your instance so that you have a backup\. To ensure data integrity, stop the instance before you create the AMI\. You can wait for the scheduled retirement date when the instance is stopped, or stop the instance yourself before the retirement date\. You can start the instance again at any time\. For more information, see [Creating an Amazon EBS\-backed Linux AMI](creating-an-ami-ebs.md)\.
**Launch a replacement instance**
After you create an AMI from your instance, you can use the AMI to launch a replacement instance\. From the Amazon EC2 console, select your new AMI and then choose **Actions**, **Launch**\. Follow the wizard to launch your instance\. For more information about each step in the wizard, see [Launching an instance using the Launch Instance Wizard](launching-instance.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-retirement.md |
7d297a633a31-0 | To preserve the data on your retiring instance, you can perform one of the following actions\. It's important that you take this action before the instance retirement date to prevent unforeseen downtime and data loss\.
**Warning**
If your instance store\-backed instance passes its retirement date, it is terminated and you cannot recover the instance or any data that was stored on it\. Regardless of the root device of your instance, the data on instance store volumes is lost when the instance is retired, even if the volumes are attached to an EBS\-backed instance\.
**Check if your instance is reachable**
When you are notified that your instance is scheduled for retirement, we recommend that you take the following action as soon as possible:
+ Check if your instance is reachable by either [connecting](AccessingInstances.md) to or pinging your instance\.
+ If your instance is unreachable, there is likely very little that can be done to recover your instance\. For more information, see [Troubleshooting an unreachable instance](instance-console.md)\. AWS will terminate your instance on the scheduled retirement date, so, for an unreachable instance, you can immediately [terminate](terminating-instances.md) the instance yourself\.
**Launch a replacement instance** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-retirement.md |
7d297a633a31-1 | **Launch a replacement instance**
Create an instance store\-backed AMI from your instance using the AMI tools, as described in [Creating an instance store\-backed Linux AMI](creating-an-ami-instance-store.md)\. From the Amazon EC2 console, select your new AMI and then choose **Actions**, **Launch**\. Follow the wizard to launch your instance\. For more information about each step in the wizard, see [Launching an instance using the Launch Instance Wizard](launching-instance.md)\.
**Convert your instance to an EBS\-backed instance**
Transfer your data to an EBS volume, take a snapshot of the volume, and then create AMI from the snapshot\. You can launch a replacement instance from your new AMI\. For more information, see [Converting your instance store\-backed AMI to an Amazon EBS\-backed AMI](Using_ConvertingS3toEBS.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/instance-retirement.md |
7146debb0cf0-0 | The following examples show you how to use the AWS Management Console or the AWS CLI to determine the maximum CPU utilization of a specific EC2 instance\.
**Requirements**
+ You must have the ID of the instance\. You can get the instance ID using the AWS Management Console or the [describe\-instances](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-instances.html) command\.
+ By default, basic monitoring is enabled, but you can enable detailed monitoring\. For more information, see [Enable or disable detailed monitoring for your instances](using-cloudwatch-new.md)\.
**To display the CPU utilization for a specific instance \(console\)**
1. Open the CloudWatch console at [https://console\.aws\.amazon\.com/cloudwatch/](https://console.aws.amazon.com/cloudwatch/)\.
1. In the navigation pane, choose **Metrics**\.
1. Choose the **EC2** metric namespace\.
![\[Choose the EC2 metrics namespace\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/metric_view_categories.png)
1. Choose the **Per\-Instance Metrics** dimension\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/US_SingleMetricPerInstance.md |
7146debb0cf0-1 | 1. Choose the **Per\-Instance Metrics** dimension\.
![\[View the metric dimensions for Amazon EC2\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/metric_view_metric_category.png)
1. In the search field, enter **CPUUtilization** and press Enter\. Choose the row for the specific instance, which displays a graph for the **CPUUtilization** metric for the instance\. To name the graph, choose the pencil icon\. To change the time range, select one of the predefined values or choose **custom**\.
![\[Graph a single metric\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/metric_statistics_ec2_instance.png)
1. To change the statistic or the period for the metric, choose the **Graphed metrics** tab\. Choose the column heading or an individual value, and then choose a different value\.
![\[Change the statistic or period for a metric\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/metric_statistics_ec2_instance_statistic_period.png)
**To get the CPU utilization for a specific instance \(AWS CLI\)** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/US_SingleMetricPerInstance.md |
7146debb0cf0-2 | **To get the CPU utilization for a specific instance \(AWS CLI\)**
Use the following [get\-metric\-statistics](https://docs.aws.amazon.com/cli/latest/reference/cloudwatch/get-metric-statistics.html) command to get the **CPUUtilization** metric for the specified instance, using the specified period and time interval:
```
aws cloudwatch get-metric-statistics --namespace AWS/EC2 --metric-name CPUUtilization --period 3600 \
--statistics Maximum --dimensions Name=InstanceId,Value=i-1234567890abcdef0 \
--start-time 2016-10-18T23:18:00 --end-time 2016-10-19T23:18:00
```
The following is example output\. Each value represents the maximum CPU utilization percentage for a single EC2 instance\.
```
{
"Datapoints": [
{
"Timestamp": "2016-10-19T00:18:00Z",
"Maximum": 0.33000000000000002,
"Unit": "Percent"
},
{
"Timestamp": "2016-10-19T03:18:00Z",
"Maximum": 99.670000000000002,
"Unit": "Percent"
}, | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/US_SingleMetricPerInstance.md |
7146debb0cf0-3 | "Maximum": 99.670000000000002,
"Unit": "Percent"
},
{
"Timestamp": "2016-10-19T07:18:00Z",
"Maximum": 0.34000000000000002,
"Unit": "Percent"
},
{
"Timestamp": "2016-10-19T12:18:00Z",
"Maximum": 0.34000000000000002,
"Unit": "Percent"
},
...
],
"Label": "CPUUtilization"
}
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/US_SingleMetricPerInstance.md |
2eed8bff68fe-0 | This example demonstrates how you can use both user data and instance metadata to configure your instances\.
Alice wants to launch four instances of her favorite database AMI, with the first acting as the original instance and the remaining three acting as replicas\. When she launches them, she wants to add user data about the replication strategy for each replica\. She is aware that this data will be available to all four instances, so she needs to structure the user data in a way that allows each instance to recognize which parts are applicable to it\. She can do this using the `ami-launch-index` instance metadata value, which will be unique for each instance\.
Here is the user data that Alice has constructed\.
```
replicate-every=1min | replicate-every=5min | replicate-every=10min
```
The `replicate-every=1min` data defines the first replica's configuration, `replicate-every=5min` defines the second replica's configuration, and so on\. Alice decides to provide this data as an ASCII string with a pipe symbol \(`|`\) delimiting the data for the separate instances\.
Alice launches four instances using the [run\-instances](https://docs.aws.amazon.com/cli/latest/reference/ec2/run-instances.html) command, specifying the user data\.
```
aws ec2 run-instances \
--image-id ami-0abcdef1234567890 \
--count 4 \
--instance-type t2.micro \ | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/AMI-launch-index-examples.md |
2eed8bff68fe-1 | --count 4 \
--instance-type t2.micro \
--user-data "replicate-every=1min | replicate-every=5min | replicate-every=10min"
```
After they're launched, all instances have a copy of the user data and the common metadata shown here:
+ AMI ID: ami\-0abcdef1234567890
+ Reservation ID: r\-1234567890abcabc0
+ Public keys: none
+ Security group name: default
+ Instance type: t2\.micro
However, each instance has certain unique metadata\.
**Instance 1**
| Metadata | Value |
| --- | --- |
| instance\-id | i\-1234567890abcdef0 |
| ami\-launch\-index | 0 |
| public\-hostname | ec2\-203\-0\-113\-25\.compute\-1\.amazonaws\.com |
| public\-ipv4 | 67\.202\.51\.223 |
| local\-hostname | ip\-10\-251\-50\-12\.ec2\.internal |
| local\-ipv4 | 10\.251\.50\.35 |
**Instance 2**
| Metadata | Value |
| --- | --- | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/AMI-launch-index-examples.md |
Subsets and Splits