Deploying Your CoPilot

About Deploying CoPilot

This section discusses how to deploy Aviatrix CoPilot.

Aviatrix CoPilot is available as an all-in-one virtual appliance that is hosted in your own IaaS cloud environment. It can be launched as an EC2 instance in AWS, a virtual machine in Azure, or a VM instance in GCP and OCI.

For information about the latest Aviatrix CoPilot base image releases, see Aviatrix Controller and Gateway Image Release Notes.

Aviatrix Controller and CoPilot are not required to be collocated. It is possible to run them in separate VPCs/VNets or separate cloud providers (in multicloud environments). Typically, Aviatrix Controller and Aviatrix CoPilot are run in the same VPC/VNet.

Before launching CoPilot:

  1. Ensure that you have reviewed all the topics under the Planning Your CoPilot Deployment.

  2. Choose a deployment method. See CoPilot Deployment Methods.

  3. After launching CoPilot, perform all the Post-Deployment Tasks for CoPilot.

If your CoPilot deployment is for the purpose of migrating CoPilot data from an existing (source) CoPilot to a newly launched (destination) CoPilot, see Migrating CoPilot Data.

CoPilot and Controller Interoperability

CoPilot is deployed as an all-in-one virtual appliance and is available on multiple clouds including AWS, Azure, GCP, and OCI MarketPlaces. CoPilot works in tandem with Aviatrix Controller; in order to use CoPilot, you must have an operational Aviatrix Controller. CoPilot works with all Controller versions that are not End of Life (EOL). If you need information about Aviatrix End of Engineering and End of Life (Support) policies or how to plan and update to the latest software, please contact Aviatrix Support.