- Newest
- Most votes
- Most comments
I apologize, but there seems to be a misunderstanding in your question. The information you've provided about c3.large instances is not accurate based on the current AWS EC2 offerings. C3 instances are an older generation that has been succeeded by newer instance types.
However, to address your main question about on-demand instances with local storage but without virtualization technology, AWS does offer such options. These are called "bare metal" instances, and they provide your applications with direct access to the processor and memory of the underlying server.
For example, the i3en family includes bare metal instances (i3en.metal) that come with local NVMe SSD storage. These instances offer direct access to the host server's hardware resources without virtualization. They are available on-demand and provide high-performance local storage.
It's important to note that even on bare metal instances, the device naming conventions may not necessarily follow traditional Linux device naming (like /dev/sda). AWS often uses its own device naming schemes for consistency across its platform.
When considering instances with local storage, newer generations like the I4i, D3, and the recently announced C8gd, M8gd, and R8gd instances (powered by AWS Graviton4 processors) offer high-performance local NVMe SSD storage. These instances are built on the AWS Nitro System, which provides better performance and security, even though they use virtualization technology.
If your specific use case requires bare metal access along with local storage, the i3en.metal or similar bare metal instances would be the most suitable option among the on-demand offerings from AWS.
Sources
Amazon EC2 I3en Instances - dense SSD storage instances
Introducing Amazon EC2 C8gd, M8gd, and R8gd instances | AWS re:Post
Amazon EC2 I4i Instances – Compute – Amazon Web Services
Relevant content
- AWS OFFICIALUpdated 5 months ago
how about z1d.metal with redhat? Does it follow raditional Linux device naming (like /dev/sda)?
Keep in mind that the local SSD/NVME devices should not be used as your persistent data storage as they are local to the specific hardware that the instance is running on and will not be restored if the hardware fails. Use EBS storage for persistence as the volumes can be attached/mounted on other instance.