# Amazon EC2 Dedicated Hosts on AWS Outposts AWS Outposts is a fully managed service that extends AWS infrastructure, services, APIs, and tools to your premises. By providing local access to AWS managed infrastructure, AWS Outposts enables you to build and run applications on premises using the same programming interfaces as in AWS Regions, while using local compute and storage resources for lower latency and local data processing needs. An Outpost is a pool of AWS compute and storage capacity deployed at a customer site. AWS operates, monitors, and manages this capacity as part of an AWS Region. You can allocate Dedicated Hosts on Outposts that you own in your account. This makes it easier for you to bring your existing software licenses and workloads that require a dedicated physical server to AWS Outposts. You can also target specific hardware assets on an Outpost to help minimize latency between your workloads. Dedicated Hosts allow you to use your eligible software licenses on Amazon EC2, so that you get the flexibility and cost effectiveness of using your own licenses. Other software licenses that are bound to virtual machines, sockets, or physical cores, can also be used on Dedicated Hosts, subject to their license terms. While Outposts have always been a single-tenant environments that are eligible for BYOL workloads, Dedicated Hosts allows you to limit the needed licenses to a single host as opposed to the entire Outpost deployment. Additionally, using Dedicated Hosts on an Outpost gives you greater flexibility in instance type deployment, and more granular control over instance placement. You can target a specific host for instance launches and use host affinity to ensure that the instance always runs on that host, or you can use auto-placement to launch an instance onto any available host that has matching configurations and available capacity. **Contents** + [Prerequisites](#dh-outpost-prereqs) + [Supported features](#dh-outpost-features) + [Considerations](#dh-outpost-considerations) + [Allocate an Amazon EC2 Dedicated Host on AWS Outposts](dh-outpost-allocate.md) ## Prerequisites You must have an Outpost installed at your site. For more information, see [ Create an Outpost and order Outpost capacity](https://docs.aws.amazon.com/outposts/latest/userguide/order-outpost-capacity.html) in the *AWS Outposts User Guide*. ## Supported features + The following instance families are supported: + **General purpose:** M5 \$1 M5d \$1 M7i \$1 M8i + **Compute optimized:** C5 \$1 C5d \$1 C7i \$1 C8i + **Memory optimized:** R5 \$1 R5d \$1 R7i \$1 R8i + **Storage optimized:** I3en + **Accelerated computing:** G4dn + Dedicated Hosts on Outposts can be configured to support multiple instance sizes. Support for multiple instance sizes is available for the following instance families. + **General purpose:** M5 \$1 M5d \$1 M7i + **Compute optimized:** C5 \$1 C5d \$1 C7i + **Memory optimized:** R5 \$1 R5d \$1 R7i For more information, see [Amazon EC2 Dedicated Host instance capacity configurations](dedicated-hosts-limits.md). + Dedicated Hosts on Outposts support auto-placement and targeted instance launches. For more information, see [Amazon EC2 Dedicated Host auto-placement and host affinity](dedicated-hosts-understanding.md). + Dedicated Hosts on Outposts support host affinity. For more information, see [Amazon EC2 Dedicated Host auto-placement and host affinity](dedicated-hosts-understanding.md). + Dedicated Hosts on Outposts support sharing with AWS RAM. For more information, see [Cross-account Amazon EC2 Dedicated Host sharing](dh-sharing.md). ## Considerations + Dedicated Host Reservations are not supported on Outposts. + Host resource groups and AWS License Manager are not supported on Outposts. + Dedicated Hosts on Outposts do not support burstable T3 instances. + Dedicated Hosts on Outposts do not support host recovery. + Simplified automatic recovery is not supported for instances with Dedicated Host tenancy on Outposts. # Allocate an Amazon EC2 Dedicated Host on AWS Outposts You allocate and use Dedicated Hosts on Outposts in the same way that would with Dedicated Hosts in an AWS Region. **Prerequisites** Create a subnet on the Outpost. For more information, see [Create a subnet](https://docs.aws.amazon.com/outposts/latest/userguide/launch-instance.html#create-subnet) in the *AWS Outposts User Guide*. **To allocate a Dedicated Host on an Outpost, use one of the following methods:** ------ #### [ Console ] **To allocate a Dedicated Host on an Outpost using the AWS Outposts console** 1. Open the AWS Outposts console at [https://console.aws.amazon.com/outposts/](https://console.aws.amazon.com/outposts/home). 1. In the navigation pane, choose **Outposts**. Select the Outpost and then choose **Actions**, **Allocate Dedicated Host**. 1. Configure the Dedicated Host as needed. For more information, see [Allocate an Amazon EC2 Dedicated Host for use in your account](dedicated-hosts-allocating.md). **Note** **Availability Zone** and **Outpost ARN** should be pre-populated with the Availability Zone and ARN of the selected Outpost. 1. Choose **Allocate**. **To allocate a Dedicated Host on an Outpost using the Amazon EC2 console** 1. Open the Amazon EC2 console at [https://console.aws.amazon.com/ec2/](https://console.aws.amazon.com/ec2/). 1. In the navigation pane, choose **Dedicated Hosts**, and then choose **Allocate Dedicated Host**. 1. For **Availability Zone**, select the Availability Zone associated with the Outpost. 1. For **Outpost ARN**, enter the ARN of the Outpost. 1. To target specific hardware assets on the Outpost, for **Target specific hardware assets on Outpost**, select **Enable**. For each hardware asset to target, choose **Add asset ID**, and then enter the ID of the hardware asset. **Note** The value that you specify for **Quantity** must be equal to the number of asset IDs that you specify. For example, if you specify 3 asset IDs, then Quantity must also be 3. 1. Configure the remaining Dedicated Host settings as needed. For more information, see [Allocate an Amazon EC2 Dedicated Host for use in your account](dedicated-hosts-allocating.md). 1. Choose **Allocate**. ------ #### [ AWS CLI ] **To allocate a Dedicated Host on an Outpost** Use the [allocate-hosts](https://docs.aws.amazon.com/cli/latest/reference/ec2/allocate-hosts.html) command. For `--availability-zone`, specify the Availability Zone associated with the Outpost. For `--outpost-arn`, specify the ARN of the Outpost. Optionally, for `--asset-ids`, specify the IDs of the Outpost hardware assets to target. ``` aws ec2 allocate-hosts \ --availability-zone "us-east-1a" \ --outpost-arn "arn:aws:outposts:us-east-1a:111122223333:outpost/op-4fe3dc21baEXAMPLE" \ --asset-ids asset_id \ --instance-family "m5" \ --auto-placement "off" \ --quantity 1 ``` ------ #### [ PowerShell ] **To allocate a Dedicated Host on an Outpost** Use the [New-EC2Host](https://docs.aws.amazon.com/powershell/latest/reference/items/New-EC2Host.html) cmdlet. Specify the Availability Zone associated with the Outpost. Optionally, for `-AssetId`, specify the IDs of the Outpost hardware assets to target. ``` New-EC2Host ` -AvailabilityZone "us-east-1a" ` -OutpostArn "arn:aws:outposts:us-east-1a:111122223333:outpost/op-4fe3dc21baEXAMPLE" ` -AssetId asset_id ` -InstanceFamily "m5" ` -AutoPlacement "off" ` -Quantity 1 ``` ------ **To launch an instance onto a Dedicated Host on an Outpost** 1. Open the Amazon EC2 console at [https://console.aws.amazon.com/ec2/](https://console.aws.amazon.com/ec2/). 1. In the navigation pane, choose **Dedicated Hosts**. Select the Dedicated Host that you allocated in the previous step and choose **Actions**, **Launch instance onto host**. 1. Configure the instance as needed and then launch the instance. For more information, see [Launch Amazon EC2 instances on an Amazon EC2 Dedicated Host](launching-dedicated-hosts-instances.md).