A standard NC2 deployment typically requires a management subnet and a public subnet for basic internet and console access. However, when moving to aFlow-based deployment(using Flow Virtual Networking), the architecture becomes more complex, requiringManagementandFlow Virtual Networksubnets specifically tailored for the overlay. TheManagement subnetis used for the bare-metal hosts and CVMs to communicate with the NC2 portal and Prism Central. TheFlow Virtual Network subnet(often the Transit VPC subnet) is required to host the distributed gateways that manage encapsulated Geneve traffic. These subnets are essential for segregating the management traffic from the virtualized workload traffic, ensuring that the software-defined overlay has a dedicated and secure path through the AWS VPC infrastructure.