All checks
Medium EC2 · regional

EC2 paravirtual instance types should not be used

Detects EC2 instances using paravirtual (PV) virtualization, a legacy type with fewer features and security controls than HVM.

service
EC2
severity
Medium
scope
evaluated in every region

How to fix it

Set at creation: fixing it means replacing the resource.

Launch a replacement instance from an HVM AMI and move the workload onto it. Virtualization type comes from the AMI rather than from any setting on the instance, so there is nothing to modify and changing the instance type will not do it either. Plan it as a rebuild: a paravirtual root volume will not boot on an HVM instance, so move the data volumes across or restore them from snapshots. The replacement gets a new instance ID and new addresses.

In the console

EC2 → Instances → Launch instances → Application and OS Images (Amazon Machine Image)

With Terraform

resource "aws_instance" "this" {
  ami           = var.hvm_ami_id
  instance_type = "m5.large"
}

See which of your accounts this check is failing on.

Book a demo