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

# Planning AWS Deployment

> You can subscribe to the required Aviatrix Cloud Networking Platform license and subscriptions by using the Launch Aviatrix experience, accessible at launch.aviatrix.com.

You can subscribe to the required Aviatrix Cloud Networking Platform license and
subscriptions by using the Launch Aviatrix experience, accessible at
[launch.aviatrix.com](https://launch.aviatrix.com).

See the <a href={"/docs/enterprise/" + "10.1" +
"/guides/controlplane/getting-started-guide-aws"}>Getting Started Guide AWS</a>
for details about using the Aviatrix launch experience to deploy the Aviatrix
platform.

Before starting the Aviatrix deployment process, you should do the following:

* Ensure the AWS region you are deploying to has at least 1 VPC, 1 internet
  gateway, and 2 elastic IPs (EIPs) available prior to deployment.

  Deployment will fail if you do not have enough VPCs, gateways, and static
  public IP addresses (EIPs in AWS). If you need to increase your limits,
  contact AWS.

  <Note>
    If you use a shared VPC for Controller and CoPilot, different accounts are
    not allowed to see each other's instances. This is by design by AWS. In this
    case, put in a feature request with AWS to modify Resource Access Manager
    (RAM) permissions. All accounts in each shared subnet need the ability to
    see all the instances in the subnet. Otherwise, features like CoPilot AppIQ,
    SmartGroups, and others will not work properly in your account.
  </Note>

  <Warning>
    Make sure you choose the correct region before launching the Controller
    instance. After launching a Controller instance, you can only change that
    instance's region by stopping that Controller and deploying a new one.
  </Warning>

* If you already signed up for an Aviatrix license, have the license key
  available.

  The key was emailed to you when you signed up. It is not retained anywhere
  else. If you do not have the key, contact your account manager.

* Decide if you want to use an existing VPC for your deployment or create a new
  one.

  If you want to use an existing VPC, identify the VPC ID and a public subnet in
  that VPC. That information will be needed during deployment.

  If you want to use a new VPC, the VPC is automatically created for you as part
  of deployment.

* Determine which deployment method you will select from Launch Aviatrix.

  After registering for a license and subscribing to the Aviatrix platform, you
  complete the launch process by using one of the following.

  * The automated CloudFormation Quick Create Stack.

    *This is the recommended method.* It is fast and simple. No prerequisites
    required.

  * Terraform manually configured modules.

    You should be familiar with Terraform modules to use this method. If you
    choose to deploy with Terraform, you must meet the following prerequisites:

    * Install
      [Boto3](https://boto3.amazonaws.com/v1/documentation/api/latest/index.html).
    * Configure
      [authentication for AWS](https://docs.aws.amazon.com/cli/v1/userguide/cli-authentication-user.html).
    * Install a minimum version of [Terraform 0.13](https://www.terraform.io/)
      and [Python3](https://www.python.org/).

  <Check>
    As a general cloud security best practice, do not use the root user
    credentials of your AWS account to launch the Aviatrix Platform or any other
    AWS resources in your AWS account.
  </Check>