# Get started with Outposts racks
<a name="get-started-outposts"></a>

Order an Outposts rack to get started. After installation of your Outpost equipment, launch an Amazon EC2 instance and configure connectivity to your on-premises network.

**Topics**
+ [

# Create an order for an Outposts rack
](order-outpost-capacity.md)
+ [

# Launch an instance on your Outposts rack
](launch-instance.md)
+ [

# Optimize Amazon EC2 for AWS Outposts
](outposts-optimizations.md)

# Create an order for an Outposts rack
<a name="order-outpost-capacity"></a>

To begin using AWS Outposts, you must create an Outpost and order Outpost capacity.

**Prerequisites**
+ Review the [available configurations](https://aws.amazon.com/outposts/rack/pricing/) for your Outposts racks.
+ An Outpost site is the physical location for your Outpost equipment. Before ordering capacity, verify that your site meets the requirements. For more information, see [Site requirements for Outposts racks](outposts-requirements.md).
+ You must have an [AWS Enterprise Support](https://aws.amazon.com/premiumsupport/plans/enterprise/) plan or an [AWS Unified Operations](https://aws.amazon.com/premiumsupport/plans/unified-operations/) plan.
+ Determine which AWS account you will use to create the Outposts site, create the Outpost, and place the order. Monitor the email associated with this account for information from AWS.

**Topics**
+ [

## Step 1: Create a site
](#create-site)
+ [

## Step 2: Create an Outpost
](#create-outpost)
+ [

## Step 3: Place the order
](#place-order)
+ [

## Step 4: Modify instance capacity
](#modify-instance-capacity)
+ [

## Next steps
](#order-fulfillment)

## Step 1: Create a site
<a name="create-site"></a>

Create a site to specify the operating address. The operating address is the physical location for your Outposts racks.

**Prerequisites**
+ Determine the operating address.

**To create a site**

1. Sign in to AWS.

1. Open the AWS Outposts console at [https://console.aws.amazon.com/outposts/](https://console.aws.amazon.com/outposts/home).

1. To select the parent AWS Region, use the Region selector in the upper-right corner of the page.

1. In the navigation pane, choose **Sites**.

1. Choose **Create site**.

1. For **Supported hardware type**, choose **Racks and servers**.

1. Enter a name, description, and operating address for your site.

1. For **Site details**, provide the requested information about the site.
   + **Max weight** – The maximum rack weight that this site can support, in lbs.
   + **Power draw** – The power draw available at the hardware placement position for the rack, in kVA.
   + **Power option** – The power option that you can provide for the hardware.
   + **Power connector** – The power connector that AWS should plan to provide for connections to the hardware.
   + **Power feed drop** – Indicate whether the power feed comes above or below the rack.
   + **Uplink speed** – The uplink speed the rack should support for the connection to the Region, in Gbps.
   + **Number of uplinks** – The number of uplinks for each Outpost networking device that you intend to use to connect the rack to your network.
   + **Fiber type** – The type of fiber that you will use to attach the rack to your network.
   + **Optical standard** – The type of optical standard that you will use to attach the rack to your network.

1. (Optional) For **Site notes**, enter any other information that might be useful for AWS to know about the site.

1. Read the facility requirements, and then select **I have read the facility requirements**.

1. Choose **Create site**.

## Step 2: Create an Outpost
<a name="create-outpost"></a>

Create an Outpost for your racks. Then, specify this Outpost when you place your order.

**Prerequisites**
+ Determine the AWS Availability Zone to associate with your site.

**To create an Outpost**

1. In the navigation pane, choose **Outposts**.

1. Choose **Create Outpost**.

1. Choose **Racks**.

1. Enter a name and description for your Outpost.

1. Choose an Availability Zone for your Outpost.

1. (Optional) To configure private connectivity, select **Use Private connectivity**. Choose a VPC and subnet in the same AWS account and Availability Zone as your Outpost. For more information, see [Prerequisites](private-connectivity.md#private-connectivity-prerequisites).
**Note**  
If you need to remove the private connectivity for your Outpost, you must contact [AWS Support Center](https://console.aws.amazon.com/support/home#/).

1. For **Site ID**, choose your site.

1. Choose **Create Outpost**.

**Note**  
You won't be able to modify the AZ anchor or physical location of your Outpost after you complete the order.

## Step 3: Place the order
<a name="place-order"></a>

Place an order for the Outposts racks that you need.

**Important**  
You can't edit an order after you submit it so review all details carefully before submission. If you need to change an order, contact your AWS Account Manager.

**Prerequisites**
+ Determine how you will pay for the order. You can pay all upfront, partially upfront, or nothing upfront. If you do not choose to pay all upfront, you'll pay monthly charges over the contract term.

  The pricing includes delivery, installation, infrastructure service maintenance, and software patches and upgrades.
+ Determine whether the delivery address is different than the operating address that you specified for the site.

**To place an order**

1. From the navigation pane, choose **Orders**.

1. Choose **Place order**.

1. For **Supported hardware type**, choose **Racks**.

1. For **Configurations**, specify the quantity for each resource that you need. If the available configurations do not meet your capacity needs, contact [AWS Support Center](https://console.aws.amazon.com/support/home#/) to request a custom capacity configuration.

1. For **Storage**:
   + Choose an Amazon EBS storage tier.
   + (Optional) Choose an Amazon S3 storage tier.

1. Choose **Next**.

1. Choose **Use an existing Outpost** and select your Outpost.

1. Choose **Next**.

1. Enter the name and number of the contact person at the operating site.

1. Specify the shipping address. You can specify a new address or select the site's operating address. If you select the operating address, be aware that any future change to the site's operating address will not propagate to existing orders. If you need to change the name and address of the shipping location on an existing order, contact your AWS Account Manager.

1. For **Site details**, specify your site information for each field.

1. Review the **Facility requirements**.

1. Select **I have read the facility requirements**.

1. Choose **Next**.

1. Select a contract term and payment option.

1. Choose **Next**.

1. On the **Review and order** page, verify that your information is correct and edit as needed. You will not be able to edit the order after you submit it.

1. Choose **Place order**.

## Step 4: Modify instance capacity
<a name="modify-instance-capacity"></a>

An Outpost provides a pool of AWS compute and storage capacity at your site as a private extension of an Availability Zone in an AWS Region. Because the compute and storage capacity available in the Outpost is finite and determined by the size and number of racks that AWS installs at your site, you get to decide how much Amazon EC2, Amazon EBS, and Amazon S3 on AWS Outposts capacity you need to run your initial workloads, accommodate future growth, and to provide extra capacity to mitigate server failures and maintenance events.

The capacity of each new Outpost order is configured with a default capacity configuration. You can convert the default configuration to create various instances to meet your business needs. To do so, you create a capacity task, specify the instance sizes and quantity, and run the capacity task to implement the changes.

**Note**  
You can change the quantity of instance sizes after you place the order for your Outposts.
Instances sizes and quantities are defined at the Outpost level.
Instances are placed automatically based on best practices.

**To modify instance capacity**

1. From the [AWS Outposts console's](https://console.aws.amazon.com/outposts/) left navigation pane, choose **Capacity tasks**.

1. On the **Capacity tasks** page, choose **Create capacity task**.

1. On the **Getting started** page, choose the order.

1. To modify capacity, you can use the steps in the console or upload a JSON file.

------
#### [ Console steps ]

1. Choose **Modify an Outpost capacity configuration**.

1. Choose **Next**.

1. On the **Configure instance capacity** page, each instance type shows one instance size with the maximum quantity preselected. To add more instance sizes, choose **Add instance size**.

1. Specify the instance quantity and note the capacity that is displayed for that instance size.

1. View the message at the end of each instance-type section that informs you if you are over or under capacity. Make adjustments at the instance size or quantity level to optimize your total available capacity.

1. You can also request AWS Outposts to optimize the instance quantity for a specific instance size. To do so: 

   1. Choose the instance size.

   1. Choose **Auto-balance** at the end of the related instance-type section.

1. For each instance type, ensure that the instance quantity is specified for at least one instance size.

1. Choose **Next**.

1. On the **Review and create** page, verify the updates that you are requesting.

1. Choose **Create**. AWS Outposts creates a capacity task.

1. On the capacity task page, monitor the status of the task.
**Note**  
AWS Outposts might request you to stop one or more running instances to enable running the capacity task. After you stop these instances, AWS Outposts will run the task.
If you need to change your capacity after you complete your order, contact [AWS Support Center](https://console.aws.amazon.com/support/home#/) to make the changes.

------
#### [ Upload a JSON file ]

1. Choose **Upload a capacity configuration**.

1. Choose **Next**.

1. On the **Upload capacity configuration plan** page, upload the JSON file that specifies the instance type, size, and quantity.  
**Example**  

   Example JSON file:

   ```
   {
       "InstancePools": [
           {
               "InstanceType": "c5.24xlarge",
               "Count": 1
           },
           {
               "InstanceType": "m5.24xlarge",
               "Count": 2
           }
       ]
   }
   ```

1. Review the contents of the JSON file in the **Capacity configuration plan** section.

1. Choose **Next**.

1. On the **Review and create** page, verify the updates that you are requesting.

1. Choose **Create**. AWS Outposts creates a capacity task.

1. On the capacity task page, monitor the status of the task.
**Note**  
AWS Outposts might request you to stop one or more running instances to enable running the capacity task. After you stop these instances, AWS Outposts will run the task.
If you need to change your capacity after you complete your order, contact [AWS Support Center](https://console.aws.amazon.com/support/home#/) to make the changes.
To troubleshoot issues, see [Troubleshooting capacity task issues](https://docs.aws.amazon.com/outposts/latest/userguide/order-troubleshooting.html).

------

## Next steps
<a name="order-fulfillment"></a>

You can view the status of your order using the AWS Outposts console. The initial status of your order is **Order received**. If you have any questions about your order, contact [AWS Support Center](https://console.aws.amazon.com/support/home#/).

To fulfill the order, AWS will schedule a date and time with you.

You will also receive a checklist of items to verify or provide before the installation. The AWS installation team will arrive at your site at the scheduled date and time. The team will roll the rack to the identified position and your electrician can power the rack. The team will establish network connectivity for the rack over the uplink that you provide, and will configure the rack's capacity. The installation is complete when you confirm that the Amazon EC2 and Amazon EBS capacity for your Outpost is available from your AWS account.

# Launch an instance on your Outposts rack
<a name="launch-instance"></a>

After your Outpost is installed and the compute and storage capacity is available for use, you can get started by creating resources. Launch Amazon EC2 instances and create Amazon EBS volumes on your Outpost using an Outpost subnet. You can also create snapshots of Amazon EBS volumes on your Outpost. For more information, see [Amazon EBS local snapshots on AWS Outposts](https://docs.aws.amazon.com/ebs/latest/userguide/snapshots-outposts.html) in the *Amazon EBS User Guide*.

**Prerequisite**  
You must have an Outpost installed at your site. For more information, see [Create an order for an Outposts rack](https://docs.aws.amazon.com/outposts/latest/userguide/launch-instance.html).

**Topics**
+ [

## Step 1: Create a VPC
](#create-vpc)
+ [

## Step 2: Create a subnet and custom route table
](#create-subnet)
+ [

## Step 3: Configure local gateway connectivity
](#configure-lgw-connectivity)
+ [

## Step 4: Configure the on-premises network
](#configure-on-prem)
+ [

## Step 5: Launch an instance on the Outpost
](#launch-instances)
+ [

## Step 6: Test the connectivity
](#test-connecitivity)

## Step 1: Create a VPC
<a name="create-vpc"></a>

You can extend any VPC in the AWS Region to your Outpost. Skip this step if you already have a VPC that you can use.

**To create a VPC for your Outpost**

1. Open the Amazon VPC console at [https://console.aws.amazon.com/vpc/](https://console.aws.amazon.com/vpc/).

1. Choose the same Region as the Outposts rack.

1. On the navigation pane, choose **Your VPCs** and then choose **Create VPC**.

1. Choose **VPC only**.

1. (Optional) for **Name tag** enter a name for the VPC.

1. For **IPv4 CIDR block**, choose **IPv4 CIDR manual input** and enter the IPv4 address range for the VPC in the **IPv4 CIDR** text box.
**Note**  
If you want to use Direct VPC routing, specify a CIDR range that does not overlap with the IP range that you use in your on-premises network.

1. For **IPv6 CIDR block**, choose **No IPv6 CIDR block**.

1. For **Tenancy**, choose **Default**.

1. (Optional) To add a tag to your VPC, choose **Add tag**, and enter a key and a value.

1. Choose **Create VPC**.

## Step 2: Create a subnet and custom route table
<a name="create-subnet"></a>

You can create and add an Outpost subnet to any VPC in the AWS Region that the Outpost is homed to. When you do so, the VPC includes the Outpost. For more information, see [Network components](https://docs.aws.amazon.com/outposts/latest/userguide/how-outposts-works.html#outposts-networking-components).

**Note**  
If you are launching an instance in an Outpost subnet that has been shared with you by another AWS account, skip to [Step 5: Launch an instance on the Outpost](https://docs.aws.amazon.com/outposts/latest/userguide/launch-instance.html#launch-instances).

**Topics**

### 2a: Create an Outpost subnet
<a name="create-outpost-subnet"></a>

**To create an Outpost subnet**

1. Open the AWS Outposts console at [https://console.aws.amazon.com/outposts/](https://console.aws.amazon.com/outposts/home).

1. On the navigation pane, choose **Outposts**.

1. Select the Outpost, and then choose **Actions**, **Create subnet**. You are redirected to create a subnet in the Amazon VPC console. We select the Outpost for you and the Availability Zone that the Outpost is homed to.

1. Select a VPC.

1. In **Subnet settings**, optionally name your subnet and specify an IP address range for the subnet.

1. Choose **Create subnet**.

1. (Optional) To make it easier to identify Outpost subnets, enable the **Outpost ID** column on the **Subnets** page. To enable the column, choose the **Preferences** icon, select **Outpost ID**, and choose **Confirm**.

### 2b: Create a custom route table
<a name="create-custom-routetable"></a>

Use the following procedure to create a custom route table with a route to the local gateway. You can't use the same route table as the Availability Zone subnets.

**To create a custom route table**

1. Open the Amazon VPC console at [https://console.aws.amazon.com/vpc/](https://console.aws.amazon.com/vpc/).

1. On the navigation pane, choose **Route tables**.

1. Choose **Create route table**.

1. (Optional) For **Name**, enter a name for your route table.

1. For **VPC**, choose your VPC.

1. (Optional) To add a tag, choose **Add new tag** and enter the tag key and tag value.

1. Choose **Create route table**.

### 2c: Associate the Outpost subnet and custom route table
<a name="associate-routetable-subnet"></a>

To apply route table routes to a particular subnet, you must associate the route table with the subnet. A route table can be associated with multiple subnets. However, a subnet can only be associated with one route table at a time. Any subnet not explicitly associated with a table is implicitly associated with the main route table by default.

**To associate the Outpost subnet and custom route table**

1. Open the Amazon VPC console at [https://console.aws.amazon.com/vpc/](https://console.aws.amazon.com/vpc/).

1. From the navigation pane, choose **Route tables**.

1. On the **Subnet associations** tab, choose **Edit subnet associations**.

1. Select the check box for the subnet to associate with the route table.

1. Choose **Save associations**.

## Step 3: Configure local gateway connectivity
<a name="configure-lgw-connectivity"></a>

The local gateway (LGW) enables connectivity between your Outpost subnets and your on-premises network.

For more information about the LGW, see [Local gateways](https://docs.aws.amazon.com/outposts/latest/userguide/outposts-local-gateways.html).

To provide connectivity between an instance in the Outposts subnet and your local network, you must complete the following tasks.

**Topics**

### 3a. Create a custom local gateway route table
<a name="create-lgw-routetable"></a>

Use the following procedure to create a custom route table for your local gateway.

**To create a custom local gateway route table**

1. Open the AWS Outposts console at [https://console.aws.amazon.com/outposts/](https://console.aws.amazon.com/outposts/home).

1. To change the AWS Region, use the Region selector in the upper-right corner of the page.

1. On the navigation pane, choose **Local gateway route table**.

1. Choose **Create local gateway route table**.

1. (Optional) For **Name**, enter a name for your route table.

1. For **Local gateway**, choose your local gateway.

1. For **Mode**, choose a mode for communication with your on-premises network.
   + Choose **Direct VPC routing** to use the private IP addresses of your instances.
   + Choose **CoIP** to use addresses from your customer-owned IP address pools. For more information, see [Create a CoIP pool](https://docs.aws.amazon.com/outposts/latest/userguide/coip-pools.html).

1. (Optional) To add a tag, choose **Add new tag** and enter a tag key and a tag value.

1. Choose **Create local gateway route table**.

### 3b: Associate the VPC with the custom route table
<a name="associate-vpc-with-route-table"></a>

Use the following procedure to associate a VPC with your local gateway route table. They are not associated by default.

**To associate a VPC with the custom local gateway route table**

1. Open the AWS Outposts console at [https://console.aws.amazon.com/outposts/](https://console.aws.amazon.com/outposts/home).

1. To change the AWS Region, use the Region selector in the upper-right corner of the page.

1. On the navigation pane, choose **Local gateway route tables**.

1. Select the route table, and then choose **Actions**, **Associate VPC**.

1. For **VPC ID**, select the VPC to associate with the local gateway route table.

1. (Optional) To add a tag, choose **Add new tag** and enter a tag key and a tag value.

1. Choose **Associate VPC**.

### 3c: Add a route entry in the Outpost subnet route table
<a name="add-route-entry"></a>

Add a route entry in the Outpost subnet route table to enable traffic between the Outpost subnets and the local gateway.

Outpost subnets within a VPC, which is associated with a local gateway route table, can have an additional target type of a Outpost Local gateway ID for their route tables. Consider the case where you want route traffic with a destination address of 172.16.100.0/24 to the customer network through the local gateway. To do this, edit the Outpost subnet route table and add the following route with the destination network and a target of the local gateway.


| Destination | Target | 
| --- | --- | 
|  172.16.100.0/24  |  `lgw-id`  | 

**To add a route entry with the local gateway as a target in the subnet route table**

1. Open the Amazon VPC console at [https://console.aws.amazon.com/vpc/](https://console.aws.amazon.com/vpc/).

1. In the navigation pane, choose **Route tables**, and select the route table you created in [2b: Create a custom route table](#create-custom-routetable).

1. Choose **Actions** and then **Edit routes**.

1. To add a route, choose **Add route**.

1. For **Destination** enter the destination CIDR block to the customer network.

1. For **Target**, choose **Outpost local gateway ID**.

1. Choose **Save changes**.

### 3d: Create a local gateway routing domain by associating the custom route table with the VIF groups
<a name="associate-route-table-vif-group"></a>

VIF groups are logical groupings of virtual interfaces (VIFs). Associate the local gateway route table with the VIF group to create a local gateway routing domain.

**To associate the custom route table with the VIF groups**

1. Open the AWS Outposts console at [https://console.aws.amazon.com/outposts/](https://console.aws.amazon.com/outposts/home).

1. To change the AWS Region, use the Region selector in the upper-right corner of the page.

1. On the navigation pane, choose **Networking** and then **LGW routing domain**.

1. Choose **Create LGW routing domain**. 

1. Enter a name for the local gateway routing domain.

1. Choose the local gateway, the local gateway VIF group, and the local gateway route table.

1. Choose **Create LGW routing domain**.

### 3e: Add a route entry in the route table
<a name="add-route-entry-lg-route-table"></a>

Edit the local gateway route table to add a static route that has the VIF Group as the target and your on-premise subnet CIDR range (or 0.0.0.0/0) as the destination.


| Destination | Target | 
| --- | --- | 
|  172.16.100.0/24  |  `VIF-Group-ID`  | 

**To add a route entry in the LGW route table**

1. Open the AWS Outposts console at [https://console.aws.amazon.com/outposts/](https://console.aws.amazon.com/outposts/home).

1. On the navigation pane, choose **Local gateway route table**.

1. Select the local gateway route table, and then choose **Actions**, **Edit routes**.

1. Choose **Add route**.

1. For **Destination**, enter the destination CIDR block, a single IP address, or the ID of a prefix list.

1. For **Target**, select the ID of the local gateway.

1. Choose **Save routes**.

### 3f: (Optional) Assign a customer-owned IP address to the instance
<a name="allocate-coip"></a>

If you configured your Outposts in the [3a. Create a custom local gateway route table](#create-lgw-routetable) to use a customer-owned IP (CoIP) address pool, you must allocate an Elastic IP address from the CoIP address pool and associate the Elastic IP address with the instance. For more information, see [Customer-owned IP addresses](https://docs.aws.amazon.com/outposts/latest/userguide/routing.html#ip-addressing).

If you configured your Outposts to use Direct VPC routing (DVR), skip this step.

**Shared customer-owned IP address pools**  
If you want to use a shared customer-owned IP address pool, the pool must be shared before you start the configuration. For information about how to share a customer-owned IPv4 address, see [Sharing an Outpost resource](sharing-outposts.md#sharing-share).

## Step 4: Configure the on-premises network
<a name="configure-on-prem"></a>

The Outpost establishes an external BGP peering from each Outpost Networking Device (OND) to a Customer Local Network Device (CND) to send and receive traffic from your on-premise network to the Outposts.

For more information, see [Local gateway BGP connectivity](https://docs.aws.amazon.com/outposts/latest/userguide/local-rack.html#local-gateway-bgp-connectivity).

To send and receive traffic from your on-premises network to the Outpost, ensure that:
+ On your customer network devices, the BGP session on the Local gateway VLAN is in an ACTIVE state from your network devices.
+ For traffic going from on-premises to Outposts, ensure that you are receiving in your CND the BGP advertisements from Outposts. These BGP advertisements contain the routes that your on-premises network must use to route traffic from the on-premises to Outpost. Hence, ensure that your network has the right routing between Outposts and the on-prem resources.
+ For traffic going from Outposts to on-premises network, ensure that your CNDs are sending the BGP route advertisements of on-premises network subnets to Outposts (or 0.0.0.0/0). As an alternative, you can advertise a default route (e.g. 0.0.0.0/0) to Outposts. The on-premises subnets advertised by the CNDs must have a CIDR range that is equal to or included in the CIDR range that you configured in [3e: Add a route entry in the route table](#add-route-entry-lg-route-table).

### Example: BGP advertisements in Direct VPC mode
<a name="example-bgp-direct-vpc"></a>

Consider the scenario where you have an Outpost, configured in Direct VPC mode, with two Outposts rack network devices connected by a local gateway VLAN to two customer local network devices. The following is configured:
+ A VPC with a CIDR block 10.0.0.0/16.
+ An Outpost subnet in the VPC with a CIDR block 10.0.3.0/24.
+ A subnet in the on-premises network with a CIDR block 172.16.100.0/24
+ Outposts uses the private IP address of the instances on the Outpost subnet, for example 10.0.3.0/24, to communicate with your on-premises network.

In this scenario, the route advertised by:
+ The local gateway to your customer devices is 10.0.3.0/24.
+ Your customer devices to the Outpost local gateway is 172.16.100.0/24.

As a result, the local gateway will send outbound traffic with destination network 172.16.100.0/24 to your customer devices. Ensure that your network has the correct routing configuration to deliver traffic to the destination host within your network.

For the specific commands and configuration required to check the state of the BGP sessions and the advertised routes within those sessions, see the documentation from your networking vendor.

For troubleshooting, see [AWS Outposts rack network troubleshooting checklist](https://docs.aws.amazon.com/outposts/latest/userguide/network-troubleshoot.html).

### Example: BGP advertisements in CoIP mode
<a name="example-bgp-coip"></a>

Consider the scenario where you have an Outpost with two Outposts rack network devices connected by a local gateway VLAN to two customer local network devices. The following is configured:
+ A VPC with a CIDR block 10.0.0.0/16.
+ A subnet in the VPC with a CIDR block 10.0.3.0/24.
+ A customer-owned IP pool (10.1.0.0/26).
+ An Elastic IP address association that associates 10.0.3.112 to 10.1.0.2.
+ A subnet in the on-premises network with a CIDR block 172.16.100.0/24 
+ Communication between your Outpost and on-premises network will use the CoIP Elastic IPs to address instances in the Outpost, the VPC CIDR range is not used.

In this scenario the route advertised by:
+ The local gateway to your customer devices is 10.1.0.0/26.
+ Your customer devices to the Outpost local gateway is 172.16.100.0/24.

As a result the local gateway will send outbound traffic with destination network 172.16.100.0/24 to your customer devices. Ensure that your network has the right routing configuration to deliver traffic to the destination host within your network.

For the specific commands and configuration required to check the state of the BGP sessions and the advertised routes within those sessions, see the documentation from your networking vendor.

For troubleshooting, see [AWS Outposts rack network troubleshooting checklist](https://docs.aws.amazon.com/outposts/latest/userguide/network-troubleshoot.html).

For troubleshooting, see [AWS Outposts rack network troubleshooting checklist](https://docs.aws.amazon.com/outposts/latest/network-userguide/network-troubleshoot.html).

## Step 5: Launch an instance on the Outpost
<a name="launch-instances"></a>

You can launch EC2 instances in the Outpost subnet that you created, or in an Outpost subnet that has been shared with you. Security groups control inbound and outbound VPC traffic for instances in an Outpost subnet, just as they do for instances in an Availability Zone subnet. To connect to an EC2 instance in an Outpost subnet, you can specify a key pair when you launch the instance, just as you do for instances in an Availability Zone subnet.

**Considerations**
+ To use block data or boot volumes backed by compatible third-party storage, you must provision and configure these volumes for use with EC2 instances on Outposts. For more information, see [Third-party block storage on Outposts racks](outpost-third-party-block-storage.md).
+ You can create a [placement group](https://docs.aws.amazon.com/outposts/latest/userguide/outposts-optimizations.html) to influence how Amazon EC2 should attempt to place groups of interdependent instances on the Outposts hardware. You can choose the placement group strategy that meets the needs of your workload.
+ If you add Amazon EBS volumes, you must use the gp2 volume type.
+ If your Outpost has been configured to use a customer-owned IP (CoIP) address pool, you must assign a customer-owned IP address to any instances that you launch.

**To launch instances in your Outpost subnet**

1. Open the AWS Outposts console at [https://console.aws.amazon.com/outposts/](https://console.aws.amazon.com/outposts/home).

1. On the navigation pane, choose **Outposts**.

1. Select the Outpost, and then choose **Actions, View details**.

1. On the **Outpost summary** page, choose **Launch instance**. You are redirected to the instance launch wizard in the Amazon EC2 console. We select the Outpost subnet for you, and show you only the instance types that are supported by your Outposts rack.

1. Choose an instance type that is supported by your Outposts rack. Note that instances that appear greyed out are not available.

1. (Optional) To launch the instances into a placement group, expand **Advanced details** and scroll to **Placement group**. You can either select an existing placement group or create a new placement group.

1. (Optional) You can add a [third-party data volume](outpost-third-party-block-storage.md).

   1. Expand **Configure storage**. Next to **External storage volume**, choose **Edit**.

   1. For **Storage Network Protocol**, choose **iSCSI**.

   1. Enter the Initiator IQN, then add the target IP address, the port, and the IQN of the external storage array.

1. Complete the wizard to launch the instance in your Outpost subnet. For more information, see [Launch an EC2 instance](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-launch-instance-wizard.html) in the *Amazon EC2 User Guide*:

## Step 6: Test the connectivity
<a name="test-connecitivity"></a>

You can test connectivity by using the appropriate use cases.

**Test connectivity from your local network to the Outpost**  
From a computer in your local network, run the `ping` command to the Outpost instance's private IP address.

```
ping 10.0.3.128
```

The following is example output.

```
Pinging 10.0.3.128

Reply from 10.0.3.128:  bytes=32 time=<1ms TTL=128
Reply from 10.0.3.128:  bytes=32 time=<1ms TTL=128
Reply from 10.0.3.128:  bytes=32 time=<1ms TTL=128
    
Ping statistics for 10.0.3.128
Packets:  Sent = 3,  Received = 3,  Lost = 0 (0% lost)

Approximate round trip time in milliseconds
Minimum = 0ms,  Maximum = 0ms,  Average = 0ms
```

**Test the connectivity from an Outpost instance to your local network**  
Depending on your operating system, use **ssh** or **rdp** to connect to the private IP address of your Outpost instance. For information about connecting to a Linux instance, see [Connect to your EC2 instance](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/connect.html) in the *Amazon EC2 User Guide*.

After the instance is running, run the `ping` command to an IP address of a computer in your local network. In the following example, the IP address is 172.16.0.130.

```
ping 172.16.0.130
```

The following is example output.

```
Pinging 172.16.0.130

Reply from 172.16.0.130:  bytes=32 time=<1ms TTL=128
Reply from 172.16.0.130:  bytes=32 time=<1ms TTL=128
Reply from 172.16.0.130:  bytes=32 time=<1ms TTL=128

Ping statistics for 172.16.0.130
Packets:  Sent = 3,  Received = 3,  Lost = 0 (0% lost)

Approximate round trip time in milliseconds
Minimum = 0ms,  Maximum = 0ms,  Average = 0ms
```

**Test connectivity between the AWS Region and the Outpost**  
Launch an instance in the subnet in the AWS Region. For example, use the [run-instances](https://docs.aws.amazon.com/cli/latest/reference/ec2/run-instances.html) command.

```
aws ec2 run-instances \
    --image-id ami-abcdefghi1234567898 \
    --instance-type c5.large \
    --key-name MyKeyPair \
    --security-group-ids sg-1a2b3c4d123456787 \
    --subnet-id subnet-6e7f829e123445678
```

After the instance is running, perform the following operations:

1. Get the private IP address of the instance in the AWS Region. This information is available in the Amazon EC2 console on the instance detail page.

1. Depending on your operating system, use **ssh** or **rdp** to connect to the private IP address of your Outpost instance.

1. Run the **ping** command from your Outpost instance, specifying the IP address of the instance in the AWS Region.

   ```
   ping 10.0.1.5
   ```

   The following is example output.

   ```
   Pinging 10.0.1.5
   
   Reply from 10.0.1.5:  bytes=32 time=<1ms TTL=128
   Reply from 10.0.1.5:  bytes=32 time=<1ms TTL=128
   Reply from 10.0.1.5:  bytes=32 time=<1ms TTL=128
   
   Ping statistics for 10.0.1.5
   Packets:  Sent = 3,  Received = 3,  Lost = 0 (0% lost)
   
   Approximate round trip time in milliseconds
   Minimum = 0ms,  Maximum = 0ms,  Average = 0ms
   ```

### Customer-owned IP address connectivity examples
<a name="test-connecitivity-coip"></a>

**Test the connectivity from your local network to the Outpost**  
From a computer in your local network, run the `ping` command to the Outpost instance's customer-owned IP address.

```
ping 172.16.0.128
```

The following is example output.

```
Pinging 172.16.0.128

Reply from 172.16.0.128:  bytes=32 time=<1ms TTL=128
Reply from 172.16.0.128:  bytes=32 time=<1ms TTL=128
Reply from 172.16.0.128:  bytes=32 time=<1ms TTL=128

Ping statistics for 172.16.0.128
Packets:  Sent = 3,  Received = 3,  Lost = 0 (0% lost)

Approximate round trip time in milliseconds
Minimum = 0ms,  Maximum = 0ms,  Average = 0ms
```

**Test the connectivity from an Outpost instance to your local network**  
Depending on your operating system, use **ssh** or **rdp** to connect to the private IP address of your Outpost instance. For information, see [Connect to your EC2 instance](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/connect.html) in the *Amazon EC2 User Guide*.

After the Outpost instance is running, run the `ping` command to an IP address of a computer in your local network.

```
ping 172.16.0.130
```

The following is example output.

```
Pinging 172.16.0.130

Reply from 172.16.0.130:  bytes=32 time=<1ms TTL=128
Reply from 172.16.0.130:  bytes=32 time=<1ms TTL=128
Reply from 172.16.0.130:  bytes=32 time=<1ms TTL=128

Ping statistics for 172.16.0.130
Packets:  Sent = 3,  Received = 3,  Lost = 0 (0% lost)

Approximate round trip time in milliseconds
Minimum = 0ms,  Maximum = 0ms,  Average = 0ms
```

**Test connectivity between the AWS Region and the Outpost**  
Launch an instance in the subnet in the AWS Region. For example, use the [run-instances](https://docs.aws.amazon.com/cli/latest/reference/ec2/run-instances.html) command.

```
aws ec2 run-instances \
    --image-id ami-abcdefghi1234567898 \
    --instance-type c5.large \
    --key-name MyKeyPair \
    --security-group-ids sg-1a2b3c4d123456787 \
    --subnet-id subnet-6e7f829e123445678
```

After the instance is running, perform the following operations:

1. Get the AWS Region instance private IP address, for example 10.0.0.5. This information is available in the Amazon EC2 console on the instance detail page.

1. Depending on your operating system, use **ssh** or **rdp** to connect to the private IP address of your Outpost instance. 

1. Run the `ping` command from your Outpost instance to the AWS Region instance IP address.

   ```
   ping 10.0.0.5
   ```

   The following is example output.

   ```
   Pinging 10.0.0.5
   
   Reply from 10.0.0.5:  bytes=32 time=<1ms TTL=128
   Reply from 10.0.0.5:  bytes=32 time=<1ms TTL=128
   Reply from 10.0.0.5:  bytes=32 time=<1ms TTL=128
   
   Ping statistics for 10.0.0.5
   Packets:  Sent = 3,  Received = 3,  Lost = 0 (0% lost)
   
   Approximate round trip time in milliseconds
   Minimum = 0ms,  Maximum = 0ms,  Average = 0ms
   ```

# Optimize Amazon EC2 for AWS Outposts
<a name="outposts-optimizations"></a>

In contrast to the AWS Region, Amazon Elastic Compute Cloud (Amazon EC2) capacity on an Outpost is finite. You are constrained by the total volume of compute capacity that you ordered. This topic offers best practices and optimization strategies to help you get the most out of your Amazon EC2 capacity in AWS Outposts. 

**Topics**
+ [

## Dedicated Hosts on Outposts
](#optimize-dedicated-hosts)
+ [

## Set up instance recovery
](#optimize-auto-recovery)
+ [

## Placement groups on Outposts
](#placement-groups-outpost)

## Dedicated Hosts on Outposts
<a name="optimize-dedicated-hosts"></a>

An Amazon EC2 Dedicated Host is a physical server with EC2 instance capacity fully dedicated to your use. Your Outpost already provides you with dedicated hardware, but Dedicated Hosts allows you to use existing software licenses with per-socket, per-core, or per-VM license restrictions against a single host. For more information, see [Dedicated Hosts on AWS Outposts](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/dh-outposts.html) in the *Amazon EC2 User Guide*.

Beyond licensing, Outpost owners can use Dedicated Hosts to optimize the servers in their Outpost deployments in two ways: 
+ Alter the capacity layout of a server
+ Control instance placement at the hardware level

**Alter the capacity layout of a server**  
Dedicated Hosts offers you the capability to alter the layout of servers in your Outpost deployment without contacting Support. When you purchase capacity for your Outpost, you specify an EC2 capacity layout that each server provides. Each server supports a single family of instance types. A layout can offer a single instance type or multiple instance types. Dedicated Hosts allows you to alter whatever you chose for that initial layout. If you allocate a host to support a single instance type for the entire capacity, you can only launch a single instance type from that host. The following illustration presents an m5.24xlarge server with a homogeneous layout:

![\[An illustration of homogeneous instance-type layout.\]](http://docs.aws.amazon.com/outposts/latest/userguide/images/dh-48xm5large.png)


You can allocate the same capacity for multiple instance types. When you allocate a host to support multiple instance types, you get a heterogeneous layout that doesn't require an explicit capacity layout. The following illustration presents an m5.24xlarge server with a heterogeneous layout at full capacity:

![\[An illustration of heterogeneous instance-type layout.\]](http://docs.aws.amazon.com/outposts/latest/userguide/images/dh-heterogeneous.png)


For more information, see [Allocate a Dedicated Host](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/dedicated-hosts-allocating.html) in the *Amazon EC2 User Guide*.

**Control instance placement at the hardware level**  
You can use Dedicated Hosts to control instance placement at the hardware level. Use auto-placement for Dedicated Hosts to manage whether instances you launch are launched onto a specific host, or onto any available host that has matching configurations. Use host affinity to establish a relationship between an instance and a Dedicated Host. If you have an Outposts rack, you can use these Dedicated Hosts features to minimize the impact of correlated hardware failures. For more information about instance recovery, see [Dedicated Host auto-placement and host affinity](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/dedicated-hosts-understanding.html) in the *Amazon EC2 User Guide*.

You can share Dedicated Hosts using AWS Resource Access Manager. Sharing Dedicated Hosts allows you to distribute hosts in an Outpost deployment across AWS accounts. For more information, see [Share your AWS Outposts resources](sharing-outposts.md).

## Set up instance recovery
<a name="optimize-auto-recovery"></a>

Instances on your Outpost that go into an unhealthy state because of hardware failure must be migrated to a healthy host. You can set up auto-recovery to have this migration done automatically based on instance status checks. For more information, see [Instance resiliency](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-recover.html).

## Placement groups on Outposts
<a name="placement-groups-outpost"></a>

AWS Outposts supports placement groups. Use placement groups to influence how Amazon EC2 should attempt to place groups of interdependent instances that you launch on the underlying hardware. You can use different strategies (cluster, partition, or spread) to meet the needs of different workloads. If you have a single-rack Outpost, you can use the spread strategy to place instances across hosts instead of racks.

### Spread placement groups
<a name="outpost-opt-spread-pg"></a>

Use a spread placement group to distribute a single instance across distinct hardware. Launching instances in a spread placement group reduces the risk of simultaneous failures that might occur when instances share the same equipment. Placement groups can spread instances across racks or hosts. You can use host level spread placement groups only with AWS Outposts. 

**Rack spread level placement groups**  
Your rack spread level placement group can hold as many instances as you have racks in your Outpost deployment. The following illustration shows a three-rack Outpost deployment running three instances in a rack spread level placement group. 

![\[An illustration of rack spread level placement group.\]](http://docs.aws.amazon.com/outposts/latest/userguide/images/placement-groups-spread.png)


**Host spread level placement groups**  
Your host spread level placement group can hold as many instances as you have hosts in your Outpost deployment. The following illustration shows a single-rack Outpost deployment running three instances in a host spread level placement group. 

![\[An illustration of host spread level placement group.\]](http://docs.aws.amazon.com/outposts/latest/userguide/images/placement-groups-host-spread.png)


### Partition placement groups
<a name="outpost-opt-parition-pg"></a>

Use a partition placement group to distribute multiple instances across racks with partitions. Each partition can hold multiple instances. You can use automatic distribution to spread instances across partitions or deploy instances to target partitions. The following illustration shows a partition placement group with automatic distribution. 

![\[An illustration of partition placement group using an automatic distribution.\]](http://docs.aws.amazon.com/outposts/latest/userguide/images/placement-groups-partition-auto.png)


You can also deploy instances to target partitions. The following illustration shows a partition placement group with targeted distribution.

![\[An illustration of partition placement group using a targeted distribution\]](http://docs.aws.amazon.com/outposts/latest/userguide/images/placement-groups-partition-targeted.png)


For more information about working with placement groups, see [Placement groups](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/placement-groups.html) and [Placement groups on AWS Outposts](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/placement-groups-outpost.html) in the *Amazon EC2 User Guide*.

For more information about AWS Outposts high availability, see [AWS Outposts High Availability Design and Architecture Considerations](https://docs.aws.amazon.com/whitepapers/latest/aws-outposts-high-availability-design/aws-outposts-high-availability-design.html).