Amazon Web Services (AWS) has announced a significant advance for its flagship cloud computing platform: Amazon EC2 now supports nested virtualization on selected virtual instances. This long-anticipated feature—unveiled on February 16, 2026—marks a pivotal change in how enterprises, developers, and researchers can leverage EC2, unlocking advanced use cases previously tethered to on-premises or bare-metal cloud hardware. With the addition of nested virtualization, customers can now deploy secondary hypervisors—namely KVM and Hyper-V—inside EC2 virtual machines, creating sophisticated virtualized environments with unprecedented flexibility.
A New Layer of Virtualization: What Nested Support Means
In traditional cloud environments, accessing a single virtual machine (VM) is the default. Nested virtualization, however, enables customers to run a hypervisor inside an EC2 instance, allowing further guest VMs to be hosted atop that layer. The paradigm resembles Russian nesting dolls—one virtual environment contained within another—allowing intricate emulation, simulation, and testing setups otherwise impossible on standard virtual machines.
This capability, already available on AWS bare metal instances, is now accessible on a select group of virtual instance types: C8i (compute-optimized), M8i (general-purpose), and R8i (memory-optimized) families. All feature the latest Intel Xeon 6 processors and the AWS Nitro abstraction layer, which exposes critical processor extensions like Intel VT-x to the guest VM, making nested virtualization possible even without direct access to underlying hardware.
Who Benefits—and How?
The introduction of nested virtualization multiplies the functional possibilities for several key user groups:
- Developers and Test Engineers: Now able to spin up emulators for mobile applications, run multi-VM test environments, or simulate complex IT deployments in a single EC2 instance, saving costs and time previously spent orchestrating fleets of separate machines.
- Hardware Simulation and Automotive: Teams can simulate in-vehicle hardware for development of automotive systems, running multiple virtual devices atop a controlled environment, a capability crucial for industries that demand rigorous virtual hardware-in-the-loop testing.
- Windows Workstation Users: Support for running Windows Subsystem for Linux (WSL) on Windows-based virtual desktops enables seamless cross-platform development, previously challenging or impossible in cloud-only environments.
- Container and Platform Engineers: Nested environments allow orchestration platforms (such as Kubernetes clusters) to isolate and manage complex production-like scenarios within a single, easily managed cloud instance.
According to AWS, customers can now utilize these nested environments for “emulators for mobile applications, simulating in-vehicle hardware for automobiles, and running Windows Subsystem for Linux on Windows workstations.” For more, see the official AWS announcement.
Technical Underpinnings: How It Works
At the core, nested virtualization involves three layers:
- L0: The AWS Nitro hypervisor layer, managing the physical server.
- L1: The virtual EC2 instance, which now gains the ability to act as a hypervisor itself.
- L2: Guest VMs running inside the L1 instance, managed by KVM or Hyper-V.
Enabling this hierarchy previously required the raw hardware access afforded by bare metal instances—an expensive and resource-intensive constraint. With advances in Intel Xeon 6 processors and AWS’s Nitro system, processor extensions like VT-x (crucial for virtualization) can now be passed through to select virtual instances, maintaining high levels of security and performance thanks to Trust Domain Extensions (TDX).
For those seeking hands-on guidance, AWS has updated its nested virtualization documentation with setup instructions.
Supported Setups and Current Limitations
The first phase of this rollout focuses on:
- Hypervisors: KVM (open source, widely used in Linux systems) and Microsoft Hyper-V (the foundation for many Windows-based virtualization initiatives). VMware ESXi is not supported at this time, but AWS has hinted at possible future expansion.
- Instance Types: The C8i, M8i, and R8i families feature Intel Xeon 6 processors with built-in isolation enhancements. The release is active across all commercial AWS regions, according to industry reports.
Before deploying, users should consult the latest EC2 instance types guide to confirm supported hardware and capabilities.
Industry Implications: AWS Moves to Close the Feature Gap
With this upgrade, AWS brings its service in closer alignment with cloud competitors like Microsoft Azure and Google Cloud Platform, both of which have provided forms of nested virtualization for select workloads. However, Azure and Google have maintained restrictions—such as limited hypervisor support or higher pricing for nested features—that AWS will likely seek to outpace as it enhances this offering.
For enterprises, this means cloud-native strategies requiring sophisticated, multi-layered virtualization (think enterprise IT simulation, DevOps sandboxes, or cloud lab environments) are increasingly viable at scale, without prohibitive costs. Unlike on-site clusters or bare metal cloud resources, virtual nested EC2 instances allow rapid on-demand provisioning, managed security, and fine-grained scalability, which can fit tightly into cost-management strategies.
New Horizons for Research and Development
One of the most impactful use cases revolves around research, hardware development, and education. Engineering and computer science teams can now run advanced hypervisor training, build custom simulation platforms, or create repeatable lab environments—all while harnessing AWS’s ecosystem for automation, storage, and networking.
In addition, integration with Windows Subsystem for Linux (WSL) enables streamlined cross-platform toolchains. For example, developers can code, test, and deploy both Linux and Windows applications without switching contexts or dealing with dual-boot setups—vital in hybrid research and prototyping work.
Security and Isolation: Trust Domain Extensions (TDX)
Security remains center stage in multi-tenant clouds. By leveraging Intel’s Trust Domain Extensions (TDX), AWS ensures critical isolation between nested guest VMs and the host, limiting the risk of escape attacks or cross-VM data leaks. TDX hardware creates cryptographically isolated domains, wrapping VM state and memory in protected enclaves. The result: organizations can confidently host sensitive workloads—even in a layered virtual topology—without relinquishing security baselines.
Early Feedback and Potential Challenges
The initial industry response has praised the move, with users highlighting the freedom from hardware procurement cycles and the ability to simulate complex production environments for a fraction of the effort. But challenges remain. Firstly, only a subset of instances is eligible for nested virtualization, meaning legacy workloads—or those on GPU or ARM hardware—may not benefit immediately. Migrating to compatible C8i, M8i, or R8i resources may involve some operational overhead.
Additionally, at launch, VMware’s popular ESXi hypervisor is absent from the support matrix, and there may be performance overhead associated with sustaining multi-level virtualization for high-IO or latency-sensitive applications. Nevertheless, for most development and test workloads, performance should remain within acceptable bounds—particularly if customers size their EC2 instances appropriately.
Practical Steps: Getting Started
To leverage nested virtualization, AWS customers can follow the updated documentation for prerequisites and deployment instructions. In essence, users will:
- Select a supported instance type from the C8i, M8i, or R8i families.
- Launch an EC2 instance running a compatible OS (for example, Amazon Linux, Ubuntu, or Windows Server with Hyper-V).
- Install or activate the desired hypervisor (KVM or Hyper-V) inside that instance.
- Begin provisioning and managing guest VMs atop the internal hypervisor, treating the EC2 instance as a fully functional virtual lab machine.
This process is now as seamless as spinning up any EC2 instance, albeit with performance and capacity guidelines to avoid resource bottlenecks on densely nested environments.
Looking Ahead: Democratizing Advanced Virtualization
Nesting virtualization support on Amazon EC2 marks a landmark step toward making the public cloud a true superset of the datacenter. By offering multilayered environments atop virtual infrastructure—without the need for costly bare-metal nodes—AWS recasts itself as an ideal platform for next-generation development, rigorous simulation, and versatile IT automation.
While limited initially to a few instance families, the foundation is in place for broader support. Coupled with the promise of deeper integrations, improved performance optimizations, and the potential addition of other hypervisors (such as VMware ESXi), the cloud starts to deliver on the promise of running “anything, anywhere, in any abstraction layer” with unprecedented security and reliability.
For those eager to test the future, the official AWS announcement page offers a comprehensive entry point.
