id
stringlengths 14
16
| text
stringlengths 1
2.43k
| source
stringlengths 99
229
|
|---|---|---|
4dfbac92a1cc-0 | One strategy is to maintain a minimum level of guaranteed compute resources for your applications by launching a core group of On\-Demand Instances, and supplementing them with Spot Instances when the opportunity arises\.
![\[Compare On-Demand and Spot Instances\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/images/spot_introduction.png)
Another strategy is to launch Spot Instances with a specified duration \(also known as Spot blocks\), which are designed not to be interrupted and will run continuously for the duration you select\. In rare situations, Spot blocks may be interrupted due to Amazon EC2 capacity needs\. In these cases, we provide a two\-minute warning before we terminate an instance, and you are not charged for the terminated instances even if you used them\. For more information, see [Defining a duration for your Spot Instances](spot-requests.md#fixed-duration-spot-instances)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-spot-instances.md |
8472b8d523ff-0 | The first thing you need to do is get set up to use Amazon EC2\. It can also be helpful to have experience launching On\-Demand Instances before launching Spot Instances\.
**Get up and running**
+ [Setting up with Amazon EC2](get-set-up-for-amazon-ec2.md)
+ [Tutorial: Getting started with Amazon EC2 Linux instances](EC2_GetStarted.md)
**Spot basics**
+ [How Spot Instances work](how-spot-instances-work.md)
+ [How Spot Fleet works](spot-fleet.md)
**Working with Spot Instances**
+ [Preparing for interruptions](spot-interruptions.md#using-spot-instances-managing-interruptions)
+ [Creating a Spot Instance request](spot-requests.md#using-spot-instances-request)
+ [Getting request status information](spot-request-status.md#get-spot-instance-request-status)
**Working with Spot Fleets**
+ [Spot Fleet permissions](spot-fleet-requests.md#spot-fleet-prerequisites)
+ [Creating a Spot Fleet request](spot-fleet-requests.md#create-spot-fleet) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-spot-instances.md |
6e91a4c3cf66-0 | You can provision Spot Instances directly using Amazon EC2\. You can also provision Spot Instances using other services in AWS\. For more information, see the following documentation\.
Amazon EC2 Auto Scaling and Spot Instances
You can create launch templates or configurations with the maximum price that you are willing to pay, so that Amazon EC2 Auto Scaling can launch Spot Instances\. For more information, see [Launching Spot Instances in Your Auto Scaling Group](https://docs.aws.amazon.com/autoscaling/latest/userguide/asg-launch-spot-instances.html) and [Using Multiple Instance Types and Purchase Options](https://docs.aws.amazon.com/autoscaling/latest/userguide/AutoScalingGroup.html#asg-purchase-options) in the *Amazon EC2 Auto Scaling User Guide*\.
Amazon EMR and Spot Instances
There are scenarios where it can be useful to run Spot Instances in an Amazon EMR cluster\. For more information, see [Spot Instances](https://docs.aws.amazon.com/emr/latest/ManagementGuide/emr-instance-purchasing-options.html#emr-spot-instances) and [When Should You Use Spot Instances](https://docs.aws.amazon.com/emr/latest/ManagementGuide/emr-plan-instances-guidelines.html#emr-plan-spot-instances) in the *Amazon EMR Management Guide*\.
AWS CloudFormation templates | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-spot-instances.md |
6e91a4c3cf66-1 | AWS CloudFormation templates
AWS CloudFormation enables you to create and manage a collection of AWS resources using a template in JSON format\. AWS CloudFormation templates can include the maximum price you are willing to pay\. For more information, see [EC2 Spot Instance Updates \- Auto Scaling and CloudFormation Integration](https://aws.amazon.com/blogs/aws/ec2-spot-instance-updates-auto-scaling-and-cloudformation-integration-new-sample-app-1/)\.
AWS SDK for Java
You can use the Java programming language to manage your Spot Instances\. For more information, see [Tutorial: Amazon EC2 Spot Instances](https://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/tutorial-spot-instances-java.html) and [Tutorial: Advanced Amazon EC2 Spot Request Management](https://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/tutorial-spot-adv-java.html)\.
AWS SDK for \.NET
You can use the \.NET programming environment to manage your Spot Instances\. For more information, see [Tutorial: Amazon EC2 Spot Instances](https://docs.aws.amazon.com/sdk-for-net/v3/developer-guide/tutorial-spot-instances-net.html)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-spot-instances.md |
b74471a60adf-0 | You pay the Spot price for Spot Instances, which is set by Amazon EC2 and adjusted gradually based on the long\-term supply of and demand for Spot Instances\. If the maximum price for your request exceeds the current Spot price, Amazon EC2 fulfills your request if capacity is available\. Your Spot Instances run until you terminate them, capacity is no longer available, the Spot price exceeds your maximum price, or your Amazon EC2 Auto Scaling group terminates them during [scale in](https://docs.aws.amazon.com/autoscaling/latest/userguide/AutoScalingGroupLifecycle.html#as-lifecycle-scale-in)\.
Spot Instances with a predefined duration use a fixed hourly price that remains in effect for the Spot Instance while it runs\.
If you or Amazon EC2 interrupts a running Spot Instance, you are charged for the seconds used or the full hour, or you receive no charge, depending on the operating system used and who interrupted the Spot Instance\. For more information, see [Billing for interrupted Spot Instances](spot-interruptions.md#billing-for-interrupted-spot-instances)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-spot-instances.md |
bcbb550fd35a-0 | To view the current \(updated every five minutes\) lowest Spot price per AWS Region and instance type, see the [Spot Instances Pricing](https://aws.amazon.com/ec2/spot/pricing/) page\.
To view the Spot price history for the past three months, use the Amazon EC2 console or the [describe\-spot\-price\-history](https://docs.aws.amazon.com/cli/latest/reference/ec2/describe-spot-price-history.html) command \(AWS CLI\)\. For more information, see [Spot Instance pricing history](using-spot-instances-history.md)\.
We independently map Availability Zones to codes for each AWS account\. Therefore, you can get different results for the same Availability Zone code \(for example, `us-west-2a`\) between different accounts\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-spot-instances.md |
8a92eb426c5a-0 | You can view the savings made from using Spot Instances for a single Spot Fleet or for all Spot Instances\. You can view the savings made in the last hour or the last three days, and you can view the average cost per vCPU hour and per memory \(GiB\) hour\. Savings are estimated and may differ from actual savings because they do not include the billing adjustments for your usage\. For more information about viewing savings information, | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-spot-instances.md |
8a92eb426c5a-1 | For more information about viewing savings information, see [Savings from purchasing Spot Instances](spot-savings.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-spot-instances.md |
d349b3ec9333-0 | To review your bill, go to your [AWS Account Activity page](https://aws.amazon.com/account-activity)\. Your bill contains links to usage reports that provide details about your bill\. For more information, see [AWS Account Billing](https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/)\.
If you have questions concerning AWS billing, accounts, and events, [contact AWS Support](https://aws.amazon.com/contact-us/)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/using-spot-instances.md |
8c460c8839f9-0 | The following information can help you troubleshoot issues if your instance fails a status check\. First determine whether your applications are exhibiting any problems\. If you verify that the instance is not running your applications as expected, review the status check information and the system logs\.
**Topics**
+ [Review status check information](#InitialSteps)
+ [Retrieve the system logs](#troubleshooting-retrieve-system-logs)
+ [Troubleshooting system log errors for Linux\-based instances](#system-log-errors-linux)
+ [Out of memory: kill process](#MemoryOOM)
+ [ERROR: mmu\_update failed \(Memory management update failed\)](#MemoryMMU)
+ [I/O error \(block device failure\)](#DeviceBlock)
+ [I/O ERROR: neither local nor remote disk \(Broken distributed block device\)](#DeviceDistributed)
+ [request\_module: runaway loop modprobe \(Looping legacy kernel modprobe on older Linux versions\)](#KernelLoop)
+ ["FATAL: kernel too old" and "fsck: No such file or directory while trying to open /dev" \(Kernel and AMI mismatch\)](#KernelOld)
+ ["FATAL: Could not load /lib/modules" or "BusyBox" \(Missing kernel modules\)](#KernelMissing)
+ [ERROR Invalid kernel \(EC2 incompatible kernel\)](#KernelInvalid) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
8c460c8839f9-1 | + [ERROR Invalid kernel \(EC2 incompatible kernel\)](#KernelInvalid)
+ [fsck: No such file or directory while trying to open\.\.\. \(File system not found\)](#FilesystemFschk)
+ [General error mounting filesystems \(failed mount\)](#FilesystemGeneral)
+ [VFS: Unable to mount root fs on unknown\-block \(Root filesystem mismatch\)](#FilesystemKernel)
+ [Error: Unable to determine major/minor number of root device\.\.\. \(Root file system/device mismatch\)](#FilesystemError)
+ [XENBUS: Device with no driver\.\.\.](#FilesystemXenbus)
+ [\.\.\. days without being checked, check forced \(File system check required\)](#FilesystemCheck)
+ [fsck died with exit status\.\.\. \(Missing device\)](#FilesystemFschkDied)
+ [GRUB prompt \(grubdom>\)](#OpSystemGrub)
+ [Bringing up interface eth0: Device eth0 has different MAC address than expected, ignoring\. \(Hard\-coded MAC address\)](#OpSystemBringing) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
8c460c8839f9-2 | + [Unable to load SELinux Policy\. Machine is in enforcing mode\. Halting now\. \(SELinux misconfiguration\)](#OpSystemUnable)
+ [XENBUS: Timeout connecting to devices \(Xenbus timeout\)](#OpSystemXenbus) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
3910b5f301d9-0 | **To investigate impaired instances 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 then select your instance\.
1. In the details pane, choose **Status Checks** to see the individual results for all **System Status Checks** and **Instance Status Checks**\.
If a system status check has failed, you can try one of the following options:
+ Create an instance recovery alarm\. For more information, see [Create alarms that stop, terminate, reboot, or recover an instance](UsingAlarmActions.md)\.
+ If you changed the instance type to an instance built on the [Nitro System](instance-types.md#ec2-nitro-instances), status checks fail if you migrated from an instance that does not have the required ENA and NVMe drivers\. For more information, see [Compatibility for resizing instances](ec2-instance-resize.md#resize-limitations)\.
+ For an instance using an Amazon EBS\-backed AMI, stop and restart the instance\.
+ For an instance using an instance\-store backed AMI, terminate the instance and launch a replacement\.
+ Wait for Amazon EC2 to resolve the issue\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
3910b5f301d9-1 | + For an instance using an instance\-store backed AMI, terminate the instance and launch a replacement\.
+ Wait for Amazon EC2 to resolve the issue\.
+ Post your issue to the [Amazon EC2 forum](https://forums.aws.amazon.com/forum.jspa?forumID=30)\.
+ If your instance is in an Auto Scaling group, the Amazon EC2 Auto Scaling service automatically launches a replacement instance\. For more information, see [Health Checks for Auto Scaling Instances](https://docs.aws.amazon.com/autoscaling/ec2/userguide/healthcheck.html) in the *Amazon EC2 Auto Scaling User Guide*\.
+ Retrieve the system log and look for errors\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
ca160c8afdd0-0 | If an instance status check fails, you can reboot the instance and retrieve the system logs\. The logs may reveal an error that can help you troubleshoot the issue\. Rebooting clears unnecessary information from the logs\.
**To reboot an instance and retrieve the system log**
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 your instance\.
1. Choose **Actions**, **Instance State**, **Reboot**\. It may take a few minutes for your instance to reboot\.
1. Verify that the problem still exists; in some cases, rebooting may resolve the problem\.
1. When the instance is in the `running` state, choose **Actions**, **Instance Settings**, **Get System Log**\.
1. Review the log that appears on the screen, and use the list of known system log error statements below to troubleshoot your issue\.
1. If your experience differs from our check results, or if you are having an issue with your instance that our checks did not detect, choose **Submit feedback** on the **Status Checks** tab to help us improve our detection tests\.
1. If your issue is not resolved, you can post your issue to the [Amazon EC2 forum](https://forums.aws.amazon.com/forum.jspa?forumID=30)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
66bdfb0eed18-0 | For Linux\-based instances that have failed an instance status check, such as the instance reachability check, verify that you followed the steps above to retrieve the system log\. The following list contains some common system log errors and suggested actions you can take to resolve the issue for each error\.
**Memory Errors**
+ [Out of memory: kill process](#MemoryOOM)
+ [ERROR: mmu\_update failed \(Memory management update failed\)](#MemoryMMU)
**Device Errors**
+ [I/O error \(block device failure\)](#DeviceBlock)
+ [I/O ERROR: neither local nor remote disk \(Broken distributed block device\)](#DeviceDistributed)
**Kernel Errors**
+ [request\_module: runaway loop modprobe \(Looping legacy kernel modprobe on older Linux versions\)](#KernelLoop)
+ ["FATAL: kernel too old" and "fsck: No such file or directory while trying to open /dev" \(Kernel and AMI mismatch\) ](#KernelOld)
+ ["FATAL: Could not load /lib/modules" or "BusyBox" \(Missing kernel modules\)](#KernelMissing)
+ [ERROR Invalid kernel \(EC2 incompatible kernel\)](#KernelInvalid)
**File System Errors**
+ [fsck: No such file or directory while trying to open\.\.\. \(File system not found\)](#FilesystemFschk) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
66bdfb0eed18-1 | + [General error mounting filesystems \(failed mount\)](#FilesystemGeneral)
+ [VFS: Unable to mount root fs on unknown\-block \(Root filesystem mismatch\)](#FilesystemKernel)
+ [Error: Unable to determine major/minor number of root device\.\.\. \(Root file system/device mismatch\)](#FilesystemError)
+ [XENBUS: Device with no driver\.\.\.](#FilesystemXenbus)
+ [\.\.\. days without being checked, check forced \(File system check required\)](#FilesystemCheck)
+ [fsck died with exit status\.\.\. \(Missing device\)](#FilesystemFschkDied)
**Operating System Errors**
+ [GRUB prompt \(grubdom>\)](#OpSystemGrub)
+ [Bringing up interface eth0: Device eth0 has different MAC address than expected, ignoring\. \(Hard\-coded MAC address\) ](#OpSystemBringing)
+ [Unable to load SELinux Policy\. Machine is in enforcing mode\. Halting now\. \(SELinux misconfiguration\)](#OpSystemUnable)
+ [XENBUS: Timeout connecting to devices \(Xenbus timeout\)](#OpSystemXenbus) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
4eb74dedf7e1-0 | An out\-of\-memory error is indicated by a system log entry similar to the one shown below\.
```
[115879.769795] Out of memory: kill process 20273 (httpd) score 1285879
or a child
[115879.769795] Killed process 1917 (php-cgi) vsz:467184kB, anon-
rss:101196kB, file-rss:204kB
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
83695ca2f042-0 | Exhausted memory | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
44aa2f17dad8-0 | | For this instance type | Do this |
| --- | --- |
| Amazon EBS\-backed | Do one of the following: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstances.html) |
| Instance store\-backed | Do one of the following: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstances.html) | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
e8aa48432c7f-0 | Memory management update failures are indicated by a system log entry similar to the following:
```
...
Press `ESC' to enter the menu... 0 [H[J Booting 'Amazon Linux 2011.09 (2.6.35.14-95.38.amzn1.i686)'
root (hd0)
Filesystem type is ext2fs, using whole disk
kernel /boot/vmlinuz-2.6.35.14-95.38.amzn1.i686 root=LABEL=/ console=hvc0 LANG=
en_US.UTF-8 KEYTABLE=us
initrd /boot/initramfs-2.6.35.14-95.38.amzn1.i686.img
ERROR: mmu_update failed with rc=-22
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
5f27d982ec10-0 | Issue with Amazon Linux | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
1acfed30fcef-0 | Post your issue to the [Developer Forums](https://forums.aws.amazon.com/) or contact [AWS Support](https://aws.amazon.com/premiumsupport/)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
500364c75951-0 | An input/output error is indicated by a system log entry similar to the following example:
```
[9943662.053217] end_request: I/O error, dev sde, sector 52428288
[9943664.191262] end_request: I/O error, dev sde, sector 52428168
[9943664.191285] Buffer I/O error on device md0, logical block 209713024
[9943664.191297] Buffer I/O error on device md0, logical block 209713025
[9943664.191304] Buffer I/O error on device md0, logical block 209713026
[9943664.191310] Buffer I/O error on device md0, logical block 209713027
[9943664.191317] Buffer I/O error on device md0, logical block 209713028
[9943664.191324] Buffer I/O error on device md0, logical block 209713029
[9943664.191332] Buffer I/O error on device md0, logical block 209713030
[9943664.191339] Buffer I/O error on device md0, logical block 209713031
[9943664.191581] end_request: I/O error, dev sde, sector 52428280
[9943664.191590] Buffer I/O error on device md0, logical block 209713136 | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
500364c75951-1 | [9943664.191590] Buffer I/O error on device md0, logical block 209713136
[9943664.191597] Buffer I/O error on device md0, logical block 209713137
[9943664.191767] end_request: I/O error, dev sde, sector 52428288
[9943664.191970] end_request: I/O error, dev sde, sector 52428288
[9943664.192143] end_request: I/O error, dev sde, sector 52428288
[9943664.192949] end_request: I/O error, dev sde, sector 52428288
[9943664.193112] end_request: I/O error, dev sde, sector 52428288
[9943664.193266] end_request: I/O error, dev sde, sector 52428288
...
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
f11ea52c6942-0 | | Instance type | Potential cause |
| --- | --- |
| Amazon EBS\-backed | A failed Amazon EBS volume |
| Instance store\-backed | A failed physical drive | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
3b2402f7797f-0 | | For this instance type | Do this |
| --- | --- |
| Amazon EBS\-backed | Use the following procedure: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstances.html) |
| Instance store\-backed | Terminate the instance and launch a new instance\. Data cannot be recovered\. Recover from backups\. It's a good practice to use either Amazon S3 or Amazon EBS for backups\. Instance store volumes are directly tied to single host and single disk failures\. | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
1a3e9f814b91-0 | An input/output error on the device is indicated by a system log entry similar to the following example:
```
...
block drbd1: Local IO failed in request_timer_fn. Detaching...
Aborting journal on device drbd1-8.
block drbd1: IO ERROR: neither local nor remote disk
Buffer I/O error on device drbd1, logical block 557056
lost page write due to I/O error on drbd1
JBD2: I/O error detected when updating journal superblock for drbd1-8.
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
e283eec1258a-0 | | Instance type | Potential cause |
| --- | --- |
| Amazon EBS\-backed | A failed Amazon EBS volume |
| Instance store\-backed | A failed physical drive | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
816c15f84cb7-0 | Terminate the instance and launch a new instance\.
For an Amazon EBS\-backed instance you can recover data from a recent snapshot by creating an image from it\. Any data added after the snapshot cannot be recovered\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
c86f7579e7ba-0 | This condition is indicated by a system log similar to the one shown below\. Using an unstable or old Linux kernel \(for example, 2\.6\.16\-xenU\) can cause an interminable loop condition at startup\.
```
Linux version 2.6.16-xenU ([email protected]) (gcc version 4.0.1
20050727 (Red Hat 4.0.1-5)) #1 SMP Mon May 28 03:41:49 SAST 2007
BIOS-provided physical RAM map:
Xen: 0000000000000000 - 0000000026700000 (usable)
0MB HIGHMEM available.
...
request_module: runaway loop modprobe binfmt-464c
request_module: runaway loop modprobe binfmt-464c
request_module: runaway loop modprobe binfmt-464c
request_module: runaway loop modprobe binfmt-464c
request_module: runaway loop modprobe binfmt-464c
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
73d8c1542ce4-0 | | For this instance type | Do this |
| --- | --- |
| Amazon EBS\-backed | Use a newer kernel, either GRUB\-based or static, using one of the following options: Option 1: Terminate the instance and launch a new instance, specifying the `–kernel` and `–ramdisk` parameters\. Option 2: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstances.html) |
| Instance store\-backed | Terminate the instance and launch a new instance, specifying the `–kernel` and `–ramdisk` parameters\. | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
6e7d963bb39a-0 | This condition is indicated by a system log similar to the one shown below\.
```
Linux version 2.6.16.33-xenU ([email protected])
(gcc version 4.1.1 20070105 (Red Hat 4.1.1-52)) #2 SMP Wed Aug 15 17:27:36 SAST 2007
...
FATAL: kernel too old
Kernel panic - not syncing: Attempted to kill init!
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
e1ea2c109dfd-0 | Incompatible kernel and userland | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
29cdf7de5ed4-0 | | For this instance type | Do this |
| --- | --- |
| Amazon EBS\-backed | Use the following procedure: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstances.html) |
| Instance store\-backed | Use the following procedure: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstances.html) | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
559d6aa20c1a-0 | This condition is indicated by a system log similar to the one shown below\.
```
[ 0.370415] Freeing unused kernel memory: 1716k freed
Loading, please wait...
WARNING: Couldn't open directory /lib/modules/2.6.34-4-virtual: No such file or directory
FATAL: Could not open /lib/modules/2.6.34-4-virtual/modules.dep.temp for writing: No such file or directory
FATAL: Could not load /lib/modules/2.6.34-4-virtual/modules.dep: No such file or directory
Couldn't get a file descriptor referring to the console
Begin: Loading essential drivers... ...
FATAL: Could not load /lib/modules/2.6.34-4-virtual/modules.dep: No such file or directory
FATAL: Could not load /lib/modules/2.6.34-4-virtual/modules.dep: No such file or directory
Done.
Begin: Running /scripts/init-premount ...
Done.
Begin: Mounting root file system... ...
Begin: Running /scripts/local-top ...
Done.
Begin: Waiting for root file system... ...
Done.
Gave up waiting for root device. Common problems:
- Boot args (cat /proc/cmdline) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
559d6aa20c1a-1 | Done.
Gave up waiting for root device. Common problems:
- Boot args (cat /proc/cmdline)
- Check rootdelay= (did the system wait long enough?)
- Check root= (did the system wait for the right device?)
- Missing modules (cat /proc/modules; ls /dev)
FATAL: Could not load /lib/modules/2.6.34-4-virtual/modules.dep: No such file or directory
FATAL: Could not load /lib/modules/2.6.34-4-virtual/modules.dep: No such file or directory
ALERT! /dev/sda1 does not exist. Dropping to a shell!
BusyBox v1.13.3 (Ubuntu 1:1.13.3-1ubuntu5) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs)
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
2cae1d6dd1b7-0 | One or more of the following conditions can cause this problem:
+ Missing ramdisk
+ Missing correct modules from ramdisk
+ Amazon EBS root volume not correctly attached as `/dev/sda1` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
1a23d7ffa35a-0 | | For this instance type | Do this |
| --- | --- |
| Amazon EBS\-backed | Use the following procedure: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstances.html) |
| Instance store\-backed | Use the following procedure: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstances.html) | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
ed010694d7c3-0 | This condition is indicated by a system log similar to the one shown below\.
```
...
root (hd0)
Filesystem type is ext2fs, using whole disk
kernel /vmlinuz root=/dev/sda1 ro
initrd /initrd.img
ERROR Invalid kernel: elf_xen_note_check: ERROR: Will only load images
built for the generic loader or Linux images
xc_dom_parse_image returned -1
Error 9: Unknown boot failure
Booting 'Fallback'
root (hd0)
Filesystem type is ext2fs, using whole disk
kernel /vmlinuz.old root=/dev/sda1 ro
Error 15: File not found
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
b89961887671-0 | One or both of the following conditions can cause this problem:
+ Supplied kernel is not supported by GRUB
+ Fallback kernel does not exist | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
a051b3e389a5-0 | | For this instance type | Do this |
| --- | --- |
| Amazon EBS\-backed | Use the following procedure: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstances.html) |
| Instance store\-backed | Use the following procedure: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstances.html) | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
0e7e7d095d01-0 | This condition is indicated by a system log similar to the one shown below\.
```
Welcome to Fedora
Press 'I' to enter interactive startup.
Setting clock : Wed Oct 26 05:52:05 EDT 2011 [ OK ]
Starting udev: [ OK ]
Setting hostname localhost: [ OK ]
No devices found
Setting up Logical Volume Management: File descriptor 7 left open
No volume groups found
[ OK ]
Checking filesystems
Checking all file systems.
[/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/sda1
/dev/sda1: clean, 82081/1310720 files, 2141116/2621440 blocks
[/sbin/fsck.ext3 (1) -- /mnt/dbbackups] fsck.ext3 -a /dev/sdh
fsck.ext3: No such file or directory while trying to open /dev/sdh
/dev/sdh:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device> | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
0e7e7d095d01-1 | is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
[FAILED]
*** An error occurred during the file system check.
*** Dropping you to a shell; the system will reboot
*** when you leave the shell.
Give root password for maintenance
(or type Control-D to continue):
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
c8427cc0d416-0 | + A bug exists in ramdisk filesystem definitions /etc/fstab
+ Misconfigured filesystem definitions in /etc/fstab
+ Missing/failed drive | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
2f305f243898-0 | | For this instance type | Do this |
| --- | --- |
| Amazon EBS\-backed | Use the following procedure: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstances.html) The sixth field in the fstab defines availability requirements of the mount – a nonzero value implies that an fsck will be done on that volume and *must* succeed\. Using this field can be problematic in Amazon EC2 because a failure typically results in an interactive console prompt that is not currently available in Amazon EC2\. Use care with this feature and read the Linux man page for fstab\. |
| Instance store\-backed | Use the following procedure: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstances.html) | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
d141a4858662-0 | This condition is indicated by a system log similar to the one shown below\.
```
Loading xenblk.ko module
xen-vbd: registered block device major 8
Loading ehci-hcd.ko module
Loading ohci-hcd.ko module
Loading uhci-hcd.ko module
USB Universal Host Controller Interface driver v3.0
Loading mbcache.ko module
Loading jbd.ko module
Loading ext3.ko module
Creating root device.
Mounting root filesystem.
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
Setting up other filesystems.
Setting up new root fs
no fstab.sys, mounting internal defaults
Switching to new root and running init.
unmounting old /dev
unmounting old /proc
unmounting old /sys
mountall:/proc: unable to mount: Device or resource busy
mountall:/proc/self/mountinfo: No such file or directory
mountall: root filesystem isn't mounted
init: mountall main process (221) terminated with status 1
General error mounting filesystems.
A maintenance shell will now be started.
CONTROL-D will terminate this shell and re-try.
Press enter for maintenance | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
d141a4858662-1 | A maintenance shell will now be started.
CONTROL-D will terminate this shell and re-try.
Press enter for maintenance
(or type Control-D to continue):
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
509bb7661ae7-0 | | Instance type | Potential cause |
| --- | --- |
| Amazon EBS\-backed | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstances.html) |
| Instance store\-backed | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstances.html) | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
d1c7322f79f8-0 | | For this instance type | Do this |
| --- | --- |
| Amazon EBS\-backed | Use the following procedure: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstances.html) |
| Instance store\-backed | Try one of the following: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstances.html) | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
c6f539e4f37a-0 | This condition is indicated by a system log similar to the one shown below\.
```
Linux version 2.6.16-xenU ([email protected]) (gcc version 4.0.1
20050727 (Red Hat 4.0.1-5)) #1 SMP Mon May 28 03:41:49 SAST 2007
...
Kernel command line: root=/dev/sda1 ro 4
...
Registering block device major 8
...
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,1)
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
4415979daa42-0 | | Instance type | Potential cause |
| --- | --- |
| Amazon EBS\-backed | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstances.html) |
| Instance store\-backed | Hardware device failure\. | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
d963353c8257-0 | | For this instance type | Do this |
| --- | --- |
| Amazon EBS\-backed | Do one of the following: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstances.html) |
| Instance store\-backed | Terminate the instance and launch a new instance using a modern kernel\. | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
22fc8ae135b0-0 | This condition is indicated by a system log similar to the one shown below\.
```
...
XENBUS: Device with no driver: device/vif/0
XENBUS: Device with no driver: device/vbd/2048
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
Initializing network drop monitor service
Freeing unused kernel memory: 508k freed
:: Starting udevd...
done.
:: Running Hook [udev]
:: Triggering uevents...<30>udevd[65]: starting version 173
done.
Waiting 10 seconds for device /dev/xvda1 ...
Root device '/dev/xvda1' doesn't exist. Attempting to create it.
ERROR: Unable to determine major/minor number of root device '/dev/xvda1'.
You are being dropped to a recovery shell
Type 'exit' to try and continue booting
sh: can't access tty; job control turned off
[ramfs /]#
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
c513f5897d74-0 | + Missing or incorrectly configured virtual block device driver
+ Device enumeration clash \(sda versus xvda or sda instead of sda1\)
+ Incorrect choice of instance kernel | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
94ccd25493ce-0 | | For this instance type | Do this |
| --- | --- |
| Amazon EBS\-backed | Use the following procedure: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstances.html) |
| Instance store\-backed | Use the following procedure: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstances.html) | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
b406cb50fe4b-0 | This condition is indicated by a system log similar to the one shown below\.
```
XENBUS: Device with no driver: device/vbd/2048
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
Initalizing network drop monitor service
Freeing unused kernel memory: 508k freed
:: Starting udevd...
done.
:: Running Hook [udev]
:: Triggering uevents...<30>udevd[65]: starting version 173
done.
Waiting 10 seconds for device /dev/xvda1 ...
Root device '/dev/xvda1' doesn't exist. Attempting to create it.
ERROR: Unable to determine major/minor number of root device '/dev/xvda1'.
You are being dropped to a recovery shell
Type 'exit' to try and continue booting
sh: can't access tty; job control turned off
[ramfs /]#
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
5ab447df20a0-0 | + Missing or incorrectly configured virtual block device driver
+ Device enumeration clash \(sda versus xvda\)
+ Incorrect choice of instance kernel | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
5629a87040a0-0 | | For this instance type | Do this |
| --- | --- |
| Amazon EBS\-backed | Use the following procedure: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstances.html) |
| Instance store\-backed | Use the following procedure: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstances.html) | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
ed244c60d960-0 | This condition is indicated by a system log similar to the one shown below\.
```
...
Checking filesystems
Checking all file systems.
[/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/sda1
/dev/sda1 has gone 361 days without being checked, check forced
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
11034e7a10bd-0 | Filesystem check time passed; a filesystem check is being forced\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
fb978e7e4776-0 | + Wait until the filesystem check completes\. A filesystem check can take a long time depending on the size of the root filesystem\.
+ Modify your filesystems to remove the filesystem check \(fsck\) enforcement using tune2fs or tools appropriate for your filesystem\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
86e605bb8f01-0 | This condition is indicated by a system log similar to the one shown below\.
```
Cleaning up ifupdown....
Loading kernel modules...done.
...
Activating lvm and md swap...done.
Checking file systems...fsck from util-linux-ng 2.16.2
/sbin/fsck.xfs: /dev/sdh does not exist
fsck died with exit status 8
[31mfailed (code 8).[39;49m
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
88e9b1631306-0 | + Ramdisk looking for missing drive
+ Filesystem consistency check forced
+ Drive failed or detached | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
7d118a2a79d5-0 | | For this instance type | Do this |
| --- | --- |
| Amazon EBS\-backed | Try one or more of the following to resolve the issue: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstances.html) |
| Instance store\-backed | Try one or more of the following to resolve the issue: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstances.html) | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
39ab2904dd0a-0 | This condition is indicated by a system log similar to the one shown below\.
```
GNU GRUB version 0.97 (629760K lower / 0K upper memory)
[ Minimal BASH-like line editing is supported. For
the first word, TAB lists possible command
completions. Anywhere else TAB lists the possible
completions of a device/filename. ]
grubdom>
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
186d4629b0f2-0 | | Instance type | Potential causes |
| --- | --- |
| Amazon EBS\-backed | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstances.html) |
| Instance store\-backed | [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstances.html) | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
37733c840b7f-0 | | For this instance type | Do this |
| --- | --- |
| Amazon EBS\-backed | Option 1: Modify the AMI and relaunch the instance: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstances.html) Option 2: Fix the existing instance: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstances.html) |
| Instance store\-backed | Option 1: Modify the AMI and relaunch the instance: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstances.html) Option 2: Terminate the instance and launch a new instance, specifying the correct kernel\. To recover data from the existing instance, contact [AWS Support](https://aws.amazon.com/premiumsupport/)\. | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
94f95eaf3d07-0 | This condition is indicated by a system log similar to the one shown below\.
```
...
Bringing up loopback interface: [ OK ]
Bringing up interface eth0: Device eth0 has different MAC address than expected, ignoring.
[FAILED]
Starting auditd: [ OK ]
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
5eecb90c7d59-0 | There is a hardcoded interface MAC in the AMI configuration | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
f98a28dad08a-0 | | For this instance type | Do this |
| --- | --- |
| Amazon EBS\-backed | Do one of the following: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstances.html) OR Use the following procedure: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstances.html) |
| Instance store\-backed | Do one of the following: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstances.html) | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
615c0aac894c-0 | This condition is indicated by a system log similar to the one shown below\.
```
audit(1313445102.626:2): enforcing=1 old_enforcing=0 auid=4294967295
Unable to load SELinux Policy. Machine is in enforcing mode. Halting now.
Kernel panic - not syncing: Attempted to kill init!
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
6b771a7f9ffb-0 | SELinux has been enabled in error:
+ Supplied kernel is not supported by GRUB
+ Fallback kernel does not exist | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
a7a0846964f5-0 | | For this instance type | Do this |
| --- | --- |
| Amazon EBS\-backed | Use the following procedure: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstances.html) |
| Instance store\-backed | Use the following procedure: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstances.html) | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
4b35da8abf69-0 | This condition is indicated by a system log similar to the one shown below\.
```
Linux version 2.6.16-xenU ([email protected]) (gcc version 4.0.1
20050727 (Red Hat 4.0.1-5)) #1 SMP Mon May 28 03:41:49 SAST 2007
...
XENBUS: Timeout connecting to devices!
...
Kernel panic - not syncing: No init found. Try passing init= option to kernel.
``` | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
0d7c80415485-0 | + The block device is not connected to the instance
+ This instance is using an old instance kernel | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
966bab2975a8-0 | | For this instance type | Do this |
| --- | --- |
| Amazon EBS\-backed | Do one of the following: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstances.html) |
| Instance store\-backed | Do one of the following: [\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstances.html) | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/TroubleshootingInstances.md |
9742f3f6af55-0 | Third\-party auditors assess the security and compliance of Amazon EC2 as part of multiple AWS compliance programs\. These include SOC, PCI, FedRAMP, HIPAA, and others\.
For a list of AWS services in scope of specific compliance programs, see [AWS Services in Scope by Compliance Program](http://aws.amazon.com/compliance/services-in-scope/)\. For general information, see [AWS Compliance Programs](http://aws.amazon.com/compliance/programs/)\.
You can download third\-party audit reports using AWS Artifact\. For more information, see [Downloading Reports in AWS Artifact](https://docs.aws.amazon.com/artifact/latest/ug/downloading-documents.html)\.
Your compliance responsibility when using Amazon EC2 is determined by the sensitivity of your data, your company's compliance objectives, and applicable laws and regulations\. AWS provides the following resources to help with compliance:
+ [Security and Compliance Quick Start Guides](http://aws.amazon.com/quickstart/?awsf.quickstart-homepage-filter=categories%23security-identity-compliance) – These deployment guides discuss architectural considerations and provide steps for deploying security\- and compliance\-focused baseline environments on AWS\.
+ [Architecting for HIPAA Security and Compliance Whitepaper ](https://d0.awsstatic.com/whitepapers/compliance/AWS_HIPAA_Compliance_Whitepaper.pdf) – This whitepaper describes how companies can use AWS to create HIPAA\-compliant applications\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/compliance-validation.md |
9742f3f6af55-1 | + [AWS Compliance Resources](http://aws.amazon.com/compliance/resources/) – This collection of workbooks and guides might apply to your industry and location\.
+ [Evaluating Resources with Rules](https://docs.aws.amazon.com/config/latest/developerguide/evaluate-config.html) in the *AWS Config Developer Guide* – AWS Config; assesses how well your resource configurations comply with internal practices, industry guidelines, and regulations\.
+ [AWS Security Hub](https://docs.aws.amazon.com/securityhub/latest/userguide/what-is-securityhub.html) – This AWS service provides a comprehensive view of your security state within AWS that helps you check your compliance with security industry standards and best practices\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/compliance-validation.md |
33313fc58f64-0 | Amazon Elastic Inference \(EI\) is a resource you can attach to your Amazon EC2 CPU instances to accelerate your deep learning \(DL\) inference workloads\. Amazon EI accelerators come in multiple sizes and are a cost\-effective method to build intelligent capabilities into applications running on Amazon EC2 instances\.
Amazon EI distributes model operations defined by TensorFlow, Apache MXNet, and the Open Neural Network Exchange \(ONNX\) format through MXNet between low\-cost, DL inference accelerators and the CPU of the instance\.
For more information about Amazon Elastic Inference, see the [Amazon EI Developer Guide](https://docs.aws.amazon.com/elastic-inference/latest/developerguide/what-is-ei.html)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/elastic-inference.md |
fa4a4ecac58b-0 | Memory optimized instances are designed to deliver fast performance for workloads that process large data sets in memory\.
**R5, R5a, and R5n instances**
These instances are well suited for the following:
+ High\-performance, relational \(MySQL\) and NoSQL \(MongoDB, Cassandra\) databases\.
+ Distributed web scale cache stores that provide in\-memory caching of key\-value type data \(Memcached and Redis\)\.
+ In\-memory databases using optimized data storage formats and analytics for business intelligence \(for example, SAP HANA\)\.
+ Applications performing real\-time processing of big unstructured data \(financial services, Hadoop/Spark clusters\)\.
+ High\-performance computing \(HPC\) and Electronic Design Automation \(EDA\) applications\.
Bare metal instances, such as `r5.metal`, provide your applications with direct access to physical resources of the host server, such as processors and memory\. These instances are well suited for the following:
+ Workloads that require access to low\-level hardware features \(for example, Intel VT\) that are not available or fully supported in virtualized environments
+ Applications that require a non\-virtualized environment for licensing or support
For more information, see [Amazon EC2 R5 Instances](https://aws.amazon.com/ec2/instance-types/r5)\.
**R6g and R6gd instances** | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/memory-optimized-instances.md |
fa4a4ecac58b-1 | **R6g and R6gd instances**
These instances are powered by AWS Graviton2 processors and are ideal for running memory\-intensive workloads, such as the following:
+ Open\-source databases \(for example, MySQL, MariaDB, and PostgreSQL\)
+ In\-memory caches \(for example, Memcached, Redis, and KeyDB\)
Bare metal instances, such as `r6g.metal`, provide your applications with direct access to physical resources of the host server, such as processors and memory\.
For more information, see [Amazon EC2 R6g Instances](https://aws.amazon.com/ec2/instance-types/r6)\.
**High memory instances**
High memory instances \(`u-6tb1.metal`, `u-9tb1.metal`, `u-12tb1.metal`, `u-18tb1.metal`, and `u-24tb1.metal`\) offer 6 TiB, 9 TiB, 12 TiB, 18 TiB, and 24 TiB of memory per instance\. These instances are designed to run large in\-memory databases, including production deployments of the SAP HANA in\-memory database, in the cloud\. They offer bare metal performance with direct access to host hardware\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/memory-optimized-instances.md |
fa4a4ecac58b-2 | For more information, see [Amazon EC2 High Memory Instances](http://aws.amazon.com/ec2/instance-types/high-memory/) and [Storage Configuration for SAP HANA](https://docs.aws.amazon.com/quickstart/latest/sap-hana/storage.html)\.
**X1 instances**
These instances are well suited for the following:
+ In\-memory databases such as SAP HANA, including SAP\-certified support for Business Suite S/4HANA, Business Suite on HANA \(SoH\), Business Warehouse on HANA \(BW\), and Data Mart Solutions on HANA\. For more information, see [SAP HANA on the AWS Cloud](https://aws.amazon.com/sap/solutions/saphana/)\.
+ Big\-data processing engines such as Apache Spark or Presto\.
+ High\-performance computing \(HPC\) applications\.
For more information, see [Amazon EC2 X1 Instances](https://aws.amazon.com/ec2/instance-types/x1)\.
**X1e instances**
These instances are well suited for the following:
+ High\-performance databases\.
+ In\-memory databases such as SAP HANA\. For more information, see [SAP HANA on the AWS Cloud](https://aws.amazon.com/sap/solutions/saphana/)\.
+ Memory\-intensive enterprise applications\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/memory-optimized-instances.md |
fa4a4ecac58b-3 | + Memory\-intensive enterprise applications\.
For more information, see [Amazon EC2 X1e Instances](https://aws.amazon.com/ec2/instance-types/x1e)\.
**z1d instances**
These instances deliver both high compute and high memory and are well\-suited for the following:
+ Electronic Design Automation \(EDA\)
+ Relational database workloads
`z1d.metal` instances provide your applications with direct access to physical resources of the host server, such as processors and memory\. These instances are well suited for the following:
+ Workloads that require access to low\-level hardware features \(for example, Intel VT\) that are not available or fully supported in virtualized environments
+ Applications that require a non\-virtualized environment for licensing or support
For more information, see [Amazon EC2 z1d Instances](https://aws.amazon.com/ec2/instance-types/z1d)\.
**Topics**
+ [Hardware specifications](#memory-instances-hardware)
+ [Memory performance](#memory-perf)
+ [Instance performance](#memory-compute-perf)
+ [Network performance](#memory-network-perf)
+ [SSD I/O performance](#instances-ssd-perf)
+ [Instance features](#memory-instances-features)
+ [Support for vCPUs](#high-cpu-support) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/memory-optimized-instances.md |
fa4a4ecac58b-4 | + [Instance features](#memory-instances-features)
+ [Support for vCPUs](#high-cpu-support)
+ [Release notes](#memory-instance-limits) | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/memory-optimized-instances.md |
95067997477e-0 | The following is a summary of the hardware specifications for memory optimized instances\.
| Instance type | Default vCPUs | Memory \(GiB\) |
| --- | --- | --- |
| r4\.large | 2 | 15\.25 |
| r4\.xlarge | 4 | 30\.5 |
| r4\.2xlarge | 8 | 61 |
| r4\.4xlarge | 16 | 122 |
| r4\.8xlarge | 32 | 244 |
| r4\.16xlarge | 64 | 488 |
| r5\.large | 2 | 16 |
| r5\.xlarge | 4 | 32 |
| r5\.2xlarge | 8 | 64 |
| r5\.4xlarge | 16 | 128 |
| r5\.8xlarge | 32 | 256 |
| r5\.12xlarge | 48 | 384 |
| r5\.16xlarge | 64 | 512 |
| r5\.24xlarge | 96 | 768 |
| r5\.metal | 96 | 768 |
| r5a\.large | 2 | 16 |
| r5a\.xlarge | 4 | 32 |
| r5a\.2xlarge | 8 | 64 |
| r5a\.4xlarge | 16 | 128 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/memory-optimized-instances.md |
95067997477e-1 | | r5a\.2xlarge | 8 | 64 |
| r5a\.4xlarge | 16 | 128 |
| r5a\.8xlarge | 32 | 256 |
| r5a\.12xlarge | 48 | 384 |
| r5a\.16xlarge | 64 | 512 |
| r5a\.24xlarge | 96 | 768 |
| r5ad\.large | 2 | 16 |
| r5ad\.xlarge | 4 | 32 |
| r5ad\.2xlarge | 8 | 64 |
| r5ad\.4xlarge | 16 | 128 |
| r5ad\.8xlarge | 32 | 256 |
| r5ad\.12xlarge | 48 | 384 |
| r5ad\.16xlarge | 64 | 512 |
| r5ad\.24xlarge | 96 | 768 |
| r5d\.large | 2 | 16 |
| r5d\.xlarge | 4 | 32 |
| r5d\.2xlarge | 8 | 64 |
| r5d\.4xlarge | 16 | 128 |
| r5d\.8xlarge | 32 | 256 |
| r5d\.12xlarge | 48 | 384 |
| r5d\.16xlarge | 64 | 512 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/memory-optimized-instances.md |
95067997477e-2 | | r5d\.12xlarge | 48 | 384 |
| r5d\.16xlarge | 64 | 512 |
| r5d\.24xlarge | 96 | 768 |
| r5d\.metal | 96 | 768 |
| r5dn\.large | 2 | 16 |
| r5dn\.xlarge | 4 | 32 |
| r5dn\.2xlarge | 8 | 64 |
| r5dn\.4xlarge | 16 | 128 |
| r5dn\.8xlarge | 32 | 256 |
| r5dn\.12xlarge | 48 | 384 |
| r5dn\.16xlarge | 64 | 512 |
| r5dn\.24xlarge | 96 | 768 |
| r5n\.large | 2 | 16 |
| r5n\.xlarge | 4 | 32 |
| r5n\.2xlarge | 8 | 64 |
| r5n\.4xlarge | 16 | 128 |
| r5n\.8xlarge | 32 | 256 |
| r5n\.12xlarge | 48 | 384 |
| r5n\.16xlarge | 64 | 512 |
| r5n\.24xlarge | 96 | 768 |
| r6g\.medium | 1 | 8 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/memory-optimized-instances.md |
95067997477e-3 | | r5n\.24xlarge | 96 | 768 |
| r6g\.medium | 1 | 8 |
| r6g\.large | 2 | 16 |
| r6g\.xlarge | 4 | 32 |
| r6g\.2xlarge | 8 | 64 |
| r6g\.4xlarge | 16 | 128 |
| r6g\.8xlarge | 32 | 256 |
| r6g\.12xlarge | 48 | 384 |
| r6g\.16xlarge | 64 | 512 |
| r6gd\.medium | 1 | 8 |
| r6gd\.large | 2 | 16 |
| r6gd\.xlarge | 4 | 32 |
| r6gd\.2xlarge | 8 | 64 |
| r6gd\.4xlarge | 16 | 128 |
| r6gd\.8xlarge | 32 | 256 |
| r6gd\.12xlarge | 48 | 384 |
| r6gd\.16xlarge | 64 | 512 |
| u\-6tb1\.metal | 448 \* | 6,144 |
| u\-9tb1\.metal | 448 \* | 9,216 |
| u\-12tb1\.metal | 448 \* | 12,288 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/memory-optimized-instances.md |
95067997477e-4 | | u\-12tb1\.metal | 448 \* | 12,288 |
| u\-18tb1\.metal | 448 \* | 18,432 |
| u\-24tb1\.metal | 448 \* | 24,576 |
| x1\.16xlarge | 64 | 976 |
| x1\.32xlarge | 128 | 1,952 |
| x1e\.xlarge | 4 | 122 |
| x1e\.2xlarge | 8 | 244 |
| x1e\.4xlarge | 16 | 488 |
| x1e\.8xlarge | 32 | 976 |
| x1e\.16xlarge | 64 | 1,952 |
| x1e\.32xlarge | 128 | 3,904 |
| z1d\.large | 2 | 16 |
| z1d\.xlarge | 4 | 32 |
| z1d\.2xlarge | 8 | 64 |
| z1d\.3xlarge | 12 | 96 |
| z1d\.6xlarge | 24 | 192 |
| z1d\.12xlarge | 48 | 384 |
| z1d\.metal | 48 | 384 |
\* Each logical processor is a hyperthread on 224 cores\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/memory-optimized-instances.md |
95067997477e-5 | | z1d\.metal | 48 | 384 |
\* Each logical processor is a hyperthread on 224 cores\.
For more information about the hardware specifications for each Amazon EC2 instance type, see [Amazon EC2 Instance Types](https://aws.amazon.com/ec2/instance-types/)\.
For more information about specifying CPU options, see [Optimizing CPU options](instance-optimize-cpu.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/memory-optimized-instances.md |
27d4864a4aa6-0 | X1 instances include Intel Scalable Memory Buffers, providing 300 GiB/s of sustainable memory\-read bandwidth and 140 GiB/s of sustainable memory\-write bandwidth\.
For more information about how much RAM can be enabled for memory optimized instances, see [Hardware specifications](#memory-instances-hardware)\.
Memory optimized instances have high memory and require 64\-bit HVM AMIs to take advantage of that capacity\. HVM AMIs provide superior performance in comparison to paravirtual \(PV\) AMIs on memory optimized instances\. For more information, see [Linux AMI virtualization types](virtualization_types.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/memory-optimized-instances.md |
f4828e576588-0 | Memory optimized instances enable increased cryptographic performance through the latest Intel AES\-NI feature, support Intel Transactional Synchronization Extensions \(TSX\) to boost the performance of in\-memory transactional data processing, and support Advanced Vector Extensions 2 \(Intel AVX2\) processor instructions to expand most integer commands to 256 bits\.
Some memory optimized instances provide the ability to control processor C\-states and P\-states on Linux\. C\-states control the sleep levels that a core can enter when it is inactive, while P\-states control the desired performance \(measured by CPU frequency\) from a core\. For more information, see [Processor state control for your EC2 instance](processor_state_control.md)\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/memory-optimized-instances.md |
86337afed7af-0 | You can enable enhanced networking on supported instance types to provide lower latencies, lower network jitter, and higher packet\-per\-second \(PPS\) performance\. Most applications do not consistently need a high level of network performance, but can benefit from access to increased bandwidth when they send or receive data\. For more information, see [Enhanced networking on Linux](enhanced-networking.md)\.
The following is a summary of network performance for memory optimized instances that support enhanced networking\.
| Instance type | Network performance | Enhanced networking |
| --- | --- | --- |
| r4\.4xlarge and smaller \| r5\.4xlarge and smaller \| r5a\.8xlarge and smaller \| r5ad\.8xlarge and smaller \| r5d\.4xlarge and smaller \| r6g\.4xlarge and smaller \| r6gd\.4xlarge and smaller \| x1e\.8large and smaller \| z1d\.3xlarge and smaller | Up to 10 Gbps † | [ENA](enhanced-networking-ena.md) | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/memory-optimized-instances.md |
86337afed7af-1 | | r4\.8xlarge \| r5\.8xlarge \| r5\.12xlarge \| r5a\.12xlarge \| r5ad\.12xlarge \| r5d\.8xlarge \| r5d\.12xlarge \| x1\.16xlarge \| x1e\.16xlarge \| z1d\.6xlarge | 10 Gbps | [ENA](enhanced-networking-ena.md) |
| r5a\.16xlarge \| r5ad\.16xlarge \| r6g\.8xlarge \| r6gd\.8xlarge | 12 Gbps | [ENA](enhanced-networking-ena.md) |
| r5\.16xlarge \| r5a\.24xlarge \| r5ad\.24xlarge \| r5d\.16xlarge \| r6g\.12xlarge \| r6gd\.12xlarge | 20 Gbps | [ENA](enhanced-networking-ena.md) |
| r5dn\.4xlarge and smaller \| r5n\.4xlarge and smaller | Up to 25 Gbps † | [ENA](enhanced-networking-ena.md) | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/memory-optimized-instances.md |
86337afed7af-2 | | r4\.16xlarge \| r5\.24xlarge \| r5\.metal \| r5d\.24xlarge \| r5d\.metal \| r5dn\.8xlarge \| r5n\.8xlarge \| r6g\.16xlarge \| r6g\.metal \| r6gd\.16xlarge \| r6gd\.metal \| x1\.32xlarge \| x1e\.32xlarge \| z1d\.12xlarge \| z1d\.metal | 25 Gbps | [ENA](enhanced-networking-ena.md) |
| r5dn\.12xlarge \| r5n\.12xlarge | 50 Gbps | [ENA](enhanced-networking-ena.md) |
| r5dn\.16xlarge \| r5n\.16xlarge | 75 Gbps | [ENA](enhanced-networking-ena.md) |
| r5dn\.24xlarge \| r5n\.24xlarge \| u\-6tb1\.metal \* \| u\-9tb1\.metal \* \| u\-12tb1\.metal \* \| u\-18tb1\.metal \| u\-24tb1\.metal | 100 Gbps | [ENA](enhanced-networking-ena.md) | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/memory-optimized-instances.md |
86337afed7af-3 | \* Instances of this type launched after March 12, 2020 provide network performance of 100 Gbps\. Instances of this type launched before March 12, 2020 might only provide network performance of 25 Gbps\. To ensure that instances launched before March 12, 2020 have a network performance of 100 Gbps, contact your account team to upgrade your instance at no additional cost\.
† These instances use a network I/O credit mechanism to allocate network bandwidth to instances based on average bandwidth utilization\. They accrue credits when their bandwidth is below their baseline bandwidth, and can use these credits when they perform network data transfers\. For more information, open a support case and ask about baseline bandwidth for the specific instance types that you are interested in\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/memory-optimized-instances.md |
d6a89d8a8611-0 | If you use a Linux AMI with kernel version 4\.4 or later and use all the SSD\-based instance store volumes available to your instance, you get the IOPS \(4,096 byte block size\) performance listed in the following table \(at queue depth saturation\)\. Otherwise, you get lower IOPS performance\.
| Instance Size | 100% Random Read IOPS | Write IOPS |
| --- | --- | --- |
| r5ad\.large \* | 30,000 | 15,000 |
| r5ad\.xlarge \* | 59,000 | 29,000 |
| r5ad\.2xlarge \* | 117,000 | 57,000 |
| r5ad\.4xlarge \* | 234,000 | 114,000 |
| r5ad\.8xlarge | 466,666 | 233,333 |
| r5ad\.12xlarge | 700,000 | 340,000 |
| r5ad\.16xlarge | 933,333 | 466,666 |
| r5ad\.24xlarge | 1,400,000 | 680,000 |
| r5d\.large \* | 30,000 | 15,000 |
| r5d\.xlarge \* | 59,000 | 29,000 |
| r5d\.2xlarge \* | 117,000 | 57,000 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/memory-optimized-instances.md |
d6a89d8a8611-1 | | r5d\.2xlarge \* | 117,000 | 57,000 |
| r5d\.4xlarge \* | 234,000 | 114,000 |
| r5d\.8xlarge | 466,666 | 233,333 |
| r5d\.12xlarge | 700,000 | 340,000 |
| r5d\.16xlarge | 933,333 | 466,666 |
| r5d\.24xlarge | 1,400,000 | 680,000 |
| r5d\.metal | 1,400,000 | 680,000 |
| r5dn\.large \* | 30,000 | 15,000 |
| r5dn\.xlarge \* | 59,000 | 29,000 |
| r5dn\.2xlarge \* | 117,000 | 57,000 |
| r5dn\.4xlarge \* | 234,000 | 114,000 |
| r5dn\.8xlarge | 466,666 | 233,333 |
| r5dn\.12xlarge | 700,000 | 340,000 |
| r5dn\.16xlarge | 933,333 | 466,666 |
| r5dn\.24xlarge | 1,400,000 | 680,000 |
| r6gd\.medium | 13,438 | 5,625 | | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/memory-optimized-instances.md |
d6a89d8a8611-2 | | r6gd\.medium | 13,438 | 5,625 |
| r6gd\.large | 26,875 | 11,250 |
| r6gd\.xlarge | 53,750 | 22,500 |
| r6gd\.2xlarge | 107,500 | 45,000 |
| r6gd\.4xlarge | 215,000 | 90,000 |
| r6gd\.8xlarge | 430,000 | 180,000 |
| r6gd\.12xlarge | 645,000 | 270,000 |
| r6gd\.16xlarge | 860,000 | 360,000 |
| r6gd\.metal | 860,000 | 360,000 |
| z1d\.large \* | 30,000 | 15,000 |
| z1d\.xlarge \* | 59,000 | 29,000 |
| z1d\.2xlarge \* | 117,000 | 57,000 |
| z1d\.3xlarge \* | 175,000 | 75,000 |
| z1d\.6xlarge | 350,000 | 170,000 |
| z1d\.12xlarge | 700,000 | 340,000 |
| z1d\.metal | 700,000 | 340,000 |
\* For these instances, you can get up to the specified performance\. | https://github.com/siagholami/aws-documentation/tree/main/documents/amazon-ec2-user-guide/doc_source/memory-optimized-instances.md |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.