Skip to main content
For AWS and Microsoft Azure deployments, use the Aviatrix launch experience at launch.aviatrix.com. For more information, see the AWS Getting Started Guide and Azure Getting Started Guide.
IPv4 VPC/VNet for Controller and CoPilot: Deploy the Aviatrix Controller and Aviatrix CoPilot into IPv4-only VPCs/VNets. Do not associate IPv6 address space or enable IPv6-only addressing on the VPC/VNet or subnets used for Controller or CoPilot instances.
You can deploy Aviatrix CoPilot directly from Google Cloud (GCP) or Oracle Cloud Infrastructure (OCI) marketplaces, by using Terraform scripts.

​
General Recommendation for Choosing Which Deployment Method

General recommendations for which deployment method to use are as follows:
  • For AWS and Azure, the recommended method is to subscribe to Controller and CoPilot by using the Launch Aviatrix experience. You can also deploy by using Terraform scripts or the Aviatrix Controller user interface (AWS only).
  • For Google Cloud or OCI, use Terraform scripts.

​
Deploy from the CSP Marketplace

Deploying from the CSP marketplace takes only a few clicks to provision and launch the instance. You must subscribe to a CoPilot offer in the marketplace as a first step for all deployment methods. See Deploy CoPilot from the Marketplace .

​
Deploy by using Terraform Scripts

If you are knowledgeable in deploying infrastructure-as-code using Terraform, it is convenient to launch CoPilot by using Terraform scripts. You can launch a single-instance deployment using Terraform scripts. A summary of steps for launching a single instance using Terraform is provided at Deploy CoPilot Using Terraform . Please refer to the Aviatrix Terraform Module for CoPilot for the most current instructions and samples on GitHub here: https://github.com/AviatrixSystems/terraform-modules-copilot.

​
Deploy from Aviatrix Controller User Interface

If your Controller is in AWS, you can launch a CoPilot simple (single) deployment from the Aviatrix Controller user interface. This deployment method has its advantages because the associated auto-deploy process configures security group rules that are required for CoPilot and Controller and gateway interconnectivity. See Deploy CoPilot from Your Controller UI (AWS Only) .