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.

Prerequisites

You must have an Outpost installed at your site. For more information, see Create an Outpost and order Outpost capacity in the AWS Outposts User Guide.

Supported features

Considerations

Allocate and use a Dedicated Host on an Outpost

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 in the AWS Outposts User Guide.

To allocate a Dedicated Host on an Outpost, use one of the following methods:

AWS Outposts console

1. Open the AWS Outposts console at https://console.aws.amazon.com/outposts/.

2. In the navigation pane, choose Outposts. Select the Outpost and then choose Actions, Allocate Dedicated Host.

3. Configure the Dedicated Host as needed. For more information, see Allocate Dedicated Hosts.

   Note

   Availability Zone and Outpost ARN should be pre-populated with the Availability Zone and ARN of the selected Outpost.

4. Choose Allocate.

Amazon EC2 console

1. Open the Amazon EC2 console at https://console.aws.amazon.com/ec2/.

2. In the navigation pane, choose Dedicated Hosts, and then choose Allocate Dedicated Host.

3. For Availability Zone, select the Availability Zone associated with the Outpost.

4. For Outpost ARN, enter the ARN of the Outpost.

5. 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.

6. Configure the remaining Dedicated Host settings as needed. For more information, see Allocate Dedicated Hosts.

7. Choose Allocate.

AWS CLI

Use the allocate-hosts AWS CLI 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