Amazon EC2 Dedicated Hosts
An Amazon EC2 Dedicated Host is a physical server that is fully dedicated for your use. You can optionally choose to share the instance capacity with other AWS accounts. For more information, see Cross-account Amazon EC2 Dedicated Host sharing.
Dedicated Hosts provide visibility and control over instance placement and they support host affinity. This means that you can launch and run instances on specific hosts, and you can ensure that instances run only on specific hosts. For more information, see Amazon EC2 Dedicated Host auto-placement and host affinity.
Dedicated Hosts provide comprehensive Bring Your Own License (BYOL) support. They allow you to use your existing per-socket, per-core, or per-VM software licenses, including Windows Server, SQL Server, SUSE Linux Enterprise Server, Red Hat Enterprise Linux, or other software licenses that are bound to VMs, sockets, or physical cores, subject to your license terms.
If you require your instances to run on dedicated hardware, but you do not need visibility or control over instance placement, and you do not need to use per-socket or per-core software licenses, you can consider using Dedicated Instances instead. Dedicated Instances and Dedicated Hosts can both be used to launch Amazon EC2 instances onto dedicated physical servers. There are no performance, security, or physical differences between Dedicated Instances and instances on Dedicated Hosts. However, there are some key differences between them. The following table highlights some of the key differences between Dedicated Instances and Dedicated Hosts:
Dedicated Host | Dedicated Instance | |
---|---|---|
Dedicated physical server |
Physical server with instance capacity fully dedicated to your use. |
Physical server that's dedicated to a single customer account. |
Instance capacity sharing |
Can share instance capacity with other accounts. |
Not supported |
Billing |
Per-host billing |
Per-instance billing |
Visibility of sockets, cores, and host ID |
Provides visibility of the number of sockets and physical cores |
No visibility |
Host and instance affinity |
Allows you to consistently deploy your instances to the same physical server over time |
Not supported |
Targeted instance placement |
Provides additional visibility and control over how instances are placed on a physical server |
Not supported |
Automatic instance recovery |
Supported. For more information, see Amazon EC2 Dedicated Host recovery. |
Supported |
Bring Your Own License (BYOL) | Supported |
Partial support * |
Capacity Reservations | Not supported |
Supported |
* Microsoft SQL Server with License Mobility through Software Assurance, and Windows Virtual Desktop Access (VDA) licenses can be used with Dedicated Instance.
For more information about Dedicated Instances, see Amazon EC2 Dedicated Instances.
Dedicated Hosts restrictions
Before you allocate Dedicated Hosts, take note of the following limitations and restrictions:
-
To run RHEL, SUSE Linux, and SQL Server on Dedicated Hosts, you must bring your own AMIs. RHEL, SUSE Linux, and SQL Server AMIs that are offered by AWS or that are available on AWS Marketplace can't be used with Dedicated Hosts. For more information on how to create your own AMI, see Bring your own software licenses to Amazon EC2 Dedicated Hosts.
This restriction does not apply to hosts allocated for high memory instances (
u-6tb1.metal
,u-9tb1.metal
,u-12tb1.metal
,u-18tb1.metal
, andu-24tb1.metal
). RHEL and SUSE Linux AMIs that are offered by AWS or that are available on AWS Marketplace can be used with these hosts. -
There is a limit on the number of running Dedicated Hosts per instance family per AWS account per Region. Quotas apply to running instances only. If your instance is pending, stopping, or stopped, it does not count towards your quota. To view the quotas for your account, or to request a quota increase, use the Service Quotas console
. -
The instances that run on a Dedicated Host can only be launched in a VPC.
-
Auto Scaling groups are supported when using a launch template that specifies a host resource group. For more information, see Create a launch template using advanced settings in the Amazon EC2 Auto Scaling User Guide.
-
Amazon RDS instances are not supported.
-
The AWS Free Usage tier is not available for Dedicated Hosts.
-
Instance placement control refers to managing instance launches onto Dedicated Hosts. You cannot launch Dedicated Hosts into placement groups.
-
If you allocate a host for a virtualized instance type, you can't modify the instance type to a
.metal
instance type after the host is allocated. For example, if you allocate a host for them5.large
instance type, you can't modify the instance type tom5.metal
.Similarly, if you allocate a host for a
.metal
instance type, you can't modify the instance type to a virtualized instance type after the host is allocated. For example, if you allocate a host for them5.metal
instance type, you can't modify the instance type tom5.large
.
Contents
- Pricing and billing
- Instance capacity configurations
- Burstable instances on Dedicated Hosts
- Bring your own licenses
- Auto-placement and affinity
- Allocate a Dedicated Host
- Launch instances on a Dedicated Host
- Launch instances into a host resource group
- Modify Dedicated Host auto-placement
- Modify supported instance types
- Modify tenancy and affinity for an instance
- Release Dedicated Host
- Purchase a Dedicated Host Reservation
- Cross-account sharing
- Dedicated Hosts on Outposts
- Host recovery
- Host maintenance
- Monitor Dedicated Hosts
- Track configuration changes
Purchase Dedicated Host Reservations for Dedicated Host billing discounts
Dedicated Host Reservations provide you with a discount of up to 70 percent compared to On-Demand Dedicated Host pricing. You must have active Dedicated Hosts allocated in your account before you can purchase Dedicated Host Reservations. For more information, see Dedicated Host Reservations.
You can purchase Dedicated Host Reservations using the following methods: