> ## Documentation Index
> Fetch the complete documentation index at: https://docs.aviatrix.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Deploy CoPilot from Your Controller UI (AWS Only)

> You can deploy CoPilot from the Aviatrix Controller user interface with AWS. However, the recommended deployment method is by using the Launch Aviatrix setup assistant. See the AWS Getting Started Guide for more information.

You can deploy CoPilot from the Aviatrix Controller user interface with AWS.
However, **the recommended deployment method** is by using the
[Launch Aviatrix](https://launch.aviatrix.com) setup assistant. See the <a href={"/docs/enterprise/" + "10.1" +
"/guides/controlplane/getting-started-guide-aws"}>AWS Getting Started Guide</a>
for more information.

Before you
[Launch a CoPilot Instance from Controller UI (AWS Only)](#launch-a-copilot-instance-from-controller-ui-aws-only),
make sure you have reviewed all the planning topics.

<a id="uisingle" />

## Launch a CoPilot Instance from Controller UI (AWS Only)

<Note>
  You can only deploy a CoPilot Instance from the Controller UI with AWS. This
  option is not available for other CSPs. However, **the recommended deployment
  method** is by using the [Launch Aviatrix](https://launch.aviatrix.com) setup
  assistant. See the <a href={"/docs/enterprise/" + "10.1" +
  "/guides/controlplane/getting-started-guide-aws"}>AWS Getting Started Guide</a>
  for more information.
</Note>

This feature is available starting from Aviatrix Controller release
6.7.1185. If you deployed Aviatrix Controller in AWS and you want to
deploy Aviatrix CoPilot in AWS in the same region/AZ as the Controller,
you can deploy CoPilot directly from the Controller UI by following
these instructions.

The instance will be launched in the same AWS region/availability zone as your
Controller. If you want to deploy CoPilot in a different AWS region/availability
zone or in a different cloud, follow the instructions in the Aviatrix <a href={"/docs/enterprise/" + "10.1" +
"/concepts-architectures/overview/index"}>Getting Started Guide</a> for your
cloud provider.

Your Controller instance must have the `aviatrix-role-ec2` IAM role attached for
the deployment to succeed.

### Prerequisite Tasks for a Single CoPilot Instance Launch

Obtain the following information before you begin. You will need it for the
initial setup of CoPilot after instance launch:

* The login credentials of your Aviatrix Controller user account.
* The login credentials for the user account to be used as the CoPilot service
  account. See <a href={"/docs/enterprise/" + "10.1" +
  "/reference/controlplane/copilot-user-account-administration"}>CoPilot User
  Account Administration</a>.
* The CoPilot customer ID obtained from your Aviatrix Sales representative.
* Verify that your AWS account has been created in your Controller (you create
  your AWS account by navigating to Controller UI, from **ACCOUNTS > Access
  Accounts > +ADD NEW**).
* Verify that the IAM role `aviatrix-role-ec2` is attached to the Controller
  instance Access Account. The CoPilot deployment will fail if this role is not
  attached to your Controller. Make sure The `aviatrix-app-policy` policy is
  also added to the `aviatrix-role-ec2` role if you need to migrate your CoPilot
  data in the future.

If you are using private mode, note that CoPilot must have Internet access.

### Deploy CoPilot from the Controller UI

To deploy CoPilot from the Controller UI (AWS Only):

1. If you haven't already done so, subscribe to a CoPilot offer: a. Log in to
   your account at the Amazon Web Services (AWS) Marketplace. If your company
   has multiple AWS accounts, be sure to log in to the same AWS account that you
   registered (onboarded) in your Controller. b. Locate the Aviatrix CoPilot
   software offer you want to subscribe to and click **Subscribe**. c. When
   prompted, review the subscription pricing information and accept the terms
   and conditions.

<Note>
  You only need to subscribe, review the subscription pricing information, and
  accept the terms and conditions in the marketplace before proceeding to the next
  step. You would not move on to the configuration steps in the marketplace.
</Note>

2. Log into Aviatrix Controller UI, and perform one of the following to begin the
   deployment process:

* From the onboarding page, click the Aviatrix CoPilot tile.
* From the action bar, click the app icon and select **Deploy CoPilot**.

3. On the **Deploy CoPilot** dialog, perform the following:
   a. Select **Simple Deployment**.
   b. (Optional) If you have backed up CoPilot configuration in an old CoPilot instance and want to restore your CoPilot configuration for this new CoPilot deployment, select **Restore from CoPilot Backup**. Then you will not be able to choose **Customize Deployment**. See details in [Copilot Backup Configuration](https://legacy.docs.aviatrix.com/documentation/latest/platform-administration/copilot/copilot-backup-configuration.html).
   c. (Optional) If desired, click **Customize Deployment** to enable the editing of the configuration. Otherwise, click **Deploy** to use the default configurations for the CoPilot instance. By default, the deployment process will deploy the CoPilot instance in the same region and same VPC as your Controller.

d. (Optional) If desired, in **Region**, change the region in which to deploy
the instance. Deploying the instance in the same region as the Controller is
recommended to reduce latency. If you want to deploy the instance in a different
region than where the Controller is deployed, choose the desired region from the
drop-down box. e. (Optional) If desired, in **VPC**, change the VPC in which to
deploy the instance. By default, the deployment process will deploy the instance
in the same VPC as your Controller. If you want to deploy the instance in a
different VPC than where the Controller is deployed, select the VPC from the VPC
drop-down list. f. (Optional) In **Subnet**, specify the subnet (availability
zone) in which to deploy the instance.

<Note>
  Each CoPilot instance must be launched in a *subnet* that has outbound Internet
  access. If you are using private mode, you also must select a *subnet* with
  outbound Internet access in this step.
</Note>

g. (Optional) In **VM Size**, specify the VM size you want to provision for your
instance. The default is a recommended minimum VM size for a single
instance. See
<a href={"/docs/enterprise/" + "10.1" + "/reference/controlplane/copilot-platform-requirements"}>Minimum Instance (VM) System Requirements for CoPilot</a> for information about
instance sizing.
h. (Optional) In **Data Volume (GB)**, you can accept the default disk volume size or
specify the size you want. See
<a href={"/docs/enterprise/" + "10.1" + "/guides/controlplane/disk-management"}>CoPilot Disk (Volume) Management</a>.
i. Click **NEXT**.
j. Enter an CoPilot service account username and password. Then click **VERIFY**.
k. Click **Deploy**.
4\. Wait until the deployment progress indicator reads **Complete** and then
click **Close**.

<Note>
  During the deployment process, the status dialog shows the details of your
  CoPilot instance including the instance size, VPC name, region, and associated
  AWS account number. You can copy the information from the status dialog to take
  note of it.
</Note>

5. **Wait for approximately 15 minutes.** It takes about fifteen minutes
   for the CoPilot application to initialize and upgrade.

## Log into CoPilot

1. From the Controller action bar, click the app icon and select **CoPilot**.
2. When prompted, enter the login and password of your Aviatrix Controller user
   account.
3. When prompted for a **CoPilot Service Account**, enter the login credentials
   of the user account you created previously on the Controller to be the
   service account.

CoPilot opens to the Dashboard page.
