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

# Onboard VPCs or VNets

> Aviatrix PaaS VPC or VNet onboarding

After onboarding your cloud account in Aviatrix, the VPCs or VNets associated
with the account display as unmanaged resources in the Aviatrix PaaS console.
You can see a list of VPCs and VNets, and associated VM resources, on the Cloud
Assets page.

To bring the resources under Aviatrix management, you must onboard the VPCs or
VNets. The recommended (default) performance size for VPCs and VNets is Medium.

It is recommended that you deploy each VPC or VNet with at least two subnets in
two different zones to provide high availability. You can select one subnet per
availability zone.

<Note>
  For information about Kubernetes clusters, see [Onboard Kubernetes
  Clusters](/docs/cloud/platform-administration/kubernetes/kubernetes-onboard).
</Note>

During onboarding, an Aviatrix Spoke Gateway is created on each subnet in the
managed VPC or VNet. This gateway is displayed on the Topology map, along with
other network resources.

<Tip>
  The Aviatrix PaaS console will onboard only one VPC or VNet at a time, but you
  can begin the onboarding process for multiple VPCs or VNets at the same time.
  You do not have to wait until a VPC or VNet finishes onboarding to start the
  onboarding process for another one.
</Tip>

You can also onboard, monitor, and protect VPCs and VNets from Security >
Egress > Protected VPC/VNets.

To view the status of individual subnets, expand the VPC or VNet listing.

To display related route tables, click the Name of a VPC or VNet.

To onboard your VPCs or VNets, do the following.

1. Go to *Cloud Resources > Cloud Assets > VPC/VNets & Subnets*.
2. Click the *Onboard* link for a VPC or VNet you want Aviatrix to manage. You
   can only onboard resources that have public IPs. By default, the 10.0.0.0/16
   CIDRs are private.
3. On *Onboard a VPC/VNet* you can do the following:
   1. From *Performance Size*, select the instance size for your VPC or VNet.
      The recommended default size is Medium.
   2. Remove a subnet from the onboarding list by clicking the "*x*" next to the
      subnet IP address. This action only removes the subnet from being managed,
      it does not remove the subnet from the VPC or VNet.
   3. Add a subnet to the list by clicking the down arrow and selecting the
      subnet IP address.
   4. Click *Onboard*. The *Aviatrix Managed* column changes status to *In
      Progress*. When onboarding of all subnets for the VPC or VNet is complete,
      status changes to *Yes*.
4. Expand the VPC or VNet listing to see the status of individual subnets in the
   VPC or VNet.
5. Click the Name of the VPC or VNet to display related route tables.

As subnets are onboarded, they also appear in the
[Cloud Fabric > Topology map](/docs/cloud/monitoring/topology-working-with) as
managed resources.

You can monitor and protect onboarded VPCs and VNets from Security > Egress >
Protected VPC/VNets.

<Tip>
  You can [offboard a VPC or
  VNet](/docs/cloud/platform-administration/onboard-offboard/vpc-vnet-offboard)
  from the Aviatrix console by using the Manage menu.
</Tip>

## Next Step

After onboarding your VPCs or VNets, you can secure them. Use either the
Distributed Cloud Firewall (DCF) or Egress Security workflow.

* [Protect Your Traffic with Distributed Cloud Firewall](/docs/cloud/security/dcf/about-dcf-security)
  DCF provides granular network security rules for distributed applications in
  the cloud.

* [Protect Your Traffic with Egress Security](/docs/cloud/security/egress-nat/about-egress-security)
  Egress Security involves monitoring network traffic to the Internet and
  protecting the traffic using DCF Rules, SmartGroups, and WebGroups.

## Related Topics


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.