How Do EC2 Dedicated Hosts Show Physical Cores and Sockets?

An Amazon EC2 Dedicated Host is a physical server with EC2 instance capacity fully dedicated to your use, offering direct visibility into the underlying hardware topology, including the exact number of physical processor sockets and physical CPU cores. Unlike standard multi-tenant EC2 instances or Dedicated Instances that abstract hardware into virtual CPUs (vCPUs), Dedicated Hosts expose hardware-level specifications through the AWS Management Console, AWS CLI, and AWS APIs. This transparency allows organizations to bring their own socket-bound or core-bound enterprise software licenses, track instance placement at the physical server level, and satisfy strict regulatory compliance and auditing requirements.

Understanding the Hardware Abstraction Gap in Standard Cloud Environments

In a standard cloud computing environment, the hypervisor abstracts the physical hardware away from the user. When you launch a standard on-demand EC2 instance, AWS allocates a specific number of vCPUs to your virtual machine. Typically, each vCPU corresponds to a single hyperthread on an Intel or AMD processor core, though on AWS Graviton processors, each vCPU maps directly to a single physical core.

For a multi-threaded processor architecture, the relationship between vCPUs and physical hardware can be expressed as:

\[\text{Total vCPUs} = \text{Physical Sockets} \times \text{Cores per Socket} \times \text{Threads per Core}\]

While this abstraction is ideal for elastic workloads, it creates significant obstacles for enterprise software compliance. Legacy licensing models from vendors such as Microsoft, Oracle, and VMware often calculate costs based on the total number of physical sockets or physical cores present on the underlying host server, regardless of how many virtual machines are running or how few vCPUs are assigned to them. Without visibility into the physical server specifications and control over where instances are placed, organizations cannot prove to auditors that their workloads are restricted to a compliant number of physical sockets or cores.

How EC2 Dedicated Hosts Expose Physical Hardware Topology

Amazon EC2 Dedicated Hosts remove the hypervisor abstraction barrier for hardware inventory by allocating an entire physical server to a single AWS account. When you allocate a Dedicated Host, you select a specific instance family or instance type (such as m5, c6i, or r5.metal), and AWS provisions a physical machine with a fixed, transparent hardware configuration.

Direct Visibility via AWS Console and API

Once a Dedicated Host is allocated, AWS exposes its hardware properties directly in your account metadata. You can inspect these attributes using the AWS Management Console or programmatically via the DescribeHosts API call (aws ec2 describe-hosts).

The API response contains a HostProperties object that explicitly reports:

• Sockets: The exact number of physical CPU sockets installed on the server motherboard.
• Cores: The total number of physical processor cores across all sockets on the host (excluding hyperthreading).
• TotalVCpus: The total number of virtual CPUs available for instance allocation on the host.
• InstanceType or InstanceFamily: The supported compute configuration for the physical server.

For example, when querying an m5 Dedicated Host, the HostProperties output will explicitly show \(2\) physical sockets, \(48\) physical cores, and \(96\) total vCPUs. An auditor does not need to guess the underlying hardware architecture or rely on vCPU conversion ratios; the physical hardware metrics are documented directly in the resource configuration.

Core Mechanisms Supporting Compliance and Auditing

Visibility into physical sockets and cores is only the first step in achieving compliance. Auditors require proof that licenses are bound to specific physical servers, that hardware does not silently change over time, and that historical usage is tracked accurately. EC2 Dedicated Hosts provide several mechanisms to enforce and document these requirements.

Persistent Host IDs and Host Affinity

Every Dedicated Host is assigned a unique, persistent identifier (HostId). When you launch an EC2 instance onto a Dedicated Host, you can configure Host Affinity. Setting affinity to host establishes a strict binding between the instance and that specific physical server. If the instance is stopped and restarted, AWS guarantees it will only restart on that exact HostId.

This prevents license mobility violations. Many enterprise software agreements prohibit moving a licensed workload across different physical servers more than once every 90 days (to prevent "license multiplexing" across a cluster). By pinning an instance to a known HostId with a documented socket and core count, administrators can prove that the software remained on the same physical hardware for the required duration.

Automated License Tracking with AWS License Manager

To streamline compliance reporting, EC2 Dedicated Hosts integrate natively with AWS License Manager. Administrators can define custom licensing rules inside License Manager that mirror the terms of their enterprise agreements, such as:

• Specifying whether the license is measured by Physical Cores or Physical Sockets.
• Setting hard or soft limits on the total number of sockets or cores that can be consumed across the environment.
• Enforcing minimum host allocation periods to comply with vendor reassignment rules.

Whenever an instance is launched on a Dedicated Host, AWS License Manager automatically queries the host's physical socket and core counts, deducts the appropriate amount from the available license pool, and blocks non-compliant launches if a hard limit is reached.

Immutable Audit Trails with AWS Config and CloudTrail

For external compliance audits and regulatory frameworks (such as PCI-DSS, HIPAA, or FedRAMP), organizations must provide historical evidence of hardware isolation and license adherence. Dedicated Hosts integrate with AWS Config and AWS CloudTrail to generate a verifiable audit trail:

• AWS Config continuously records the configuration state of each Dedicated Host. It tracks exactly when a host was allocated, its physical socket and core properties, and a chronological timeline of every EC2 instance InstanceId that was placed on or removed from that host.
• AWS CloudTrail logs every API action related to host allocation, capacity modification, instance placement, and host release, providing timestamped proof of hardware lifecycle events.

Dedicated Hosts vs. Dedicated Instances

A common point of confusion in cloud compliance is the difference between EC2 Dedicated Instances and EC2 Dedicated Hosts. While both guarantee that your instances run on physical hardware dedicated to a single customer account, they differ fundamentally in hardware visibility:

Because Dedicated Instances abstract the underlying host and may migrate across different physical servers when stopped and started, they cannot be used to satisfy compliance requirements that demand visibility into physical sockets and cores. Dedicated Hosts are specifically engineered to bridge this gap, providing the exact hardware telemetry required for enterprise licensing and strict regulatory governance.