Cloud-hosted virtual network lab for topology testing, automation development, and training at scale
Arista Cloud Test is a multi-tenant, cloud-hosted virtual lab environment that allows network engineers and automation developers to deploy full Arista network topologies using virtual instances of EOS, CloudEOS, and CloudVision Portal, without physical hardware. The environment runs each device as a separate virtual machine within a VxLAN Layer 2 overlay built on the cloud provider's underlying Layer 3 infrastructure, which means that the connectivity behaviour within the virtual topology mirrors what the same EOS configuration would produce on physical hardware, including L2 adjacencies, VLAN segmentation, and spanning-tree behaviour. Topologies are defined in YAML files, and the platform validates the topology before provisioning, preventing malformed configurations from consuming lab resources.
Access to deployed topologies is available through HTTPS directly in a browser or via an IPSec VPN tunnel for workflows that require direct IP connectivity to the in-topology management plane, for example Ansible playbooks that SSH into each virtual switch, or AVD pipelines that deploy full fabric configurations across dozens of virtual nodes simultaneously. A pre-built Tools Server node packages the tooling most commonly required for Arista automation development: GitLab for source control and CI/CD pipelines, Ansible and AVD for automated configuration deployment, and Wireshark for packet-level verification of dataplane behaviour within the topology. Third-party vendor devices can be included via Bring Your Own License arrangements, enabling interoperability testing between Arista EOS nodes and devices from other vendors within the same virtual fabric.
The VxLAN overlay architecture allows Cloud Test to present accurate Layer 2 topology behaviour to virtual EOS instances regardless of the actual Layer 3 infrastructure underneath, meaning that a virtual topology with dozens of L2 adjacencies, VLAN trunks, and spanning-tree configurations behaves identically to the equivalent physical topology. This accuracy is the prerequisite for using Cloud Test results to validate configurations that will subsequently be deployed on physical hardware, because any discrepancy between virtual and physical L2 behaviour would cause test results to be unreliable predictors of production behaviour.
Topology specifications written in YAML describe the nodes, connections, and initial configuration of the virtual lab, and the platform validates these files before provisioning any resources, catching referencing errors, unsupported node type combinations, and resource limit violations before they result in a partially provisioned environment that must be manually unwound. YAML topology files are version-controllable alongside the automation code they support, meaning that a specific network design and its associated automation tests can be reproduced from git history without manual reconstruction, and that topology changes follow the same review-and-merge process as application code.
The built-in Tools Server provides a pre-configured environment containing the full stack required for Arista automation development: GitLab for repository hosting and CI/CD pipeline execution, Ansible and Arista Validated Designs (AVD) for structured configuration deployment, and Wireshark for protocol-level packet inspection within the virtual topology. Having these tools pre-installed in the lab environment eliminates the setup overhead that would otherwise be required before a new team member could begin working with automation. The topology boots with the tools already available, and the team can begin developing or reviewing automation code against live virtual devices immediately.
The multi-user, multi-tenant architecture allows multiple individuals or teams to run simultaneous independent topologies within the same Cloud Test service without their environments interfering with each other. For training programmes that run instructor-led Arista EOS or AVD workshops, this means each student or student group gets their own isolated topology without the instructor needing to pre-provision separate physical lab infrastructure for each cohort. For engineering teams, simultaneous topologies allow separate development and QA environments to operate in parallel, with one team member developing and breaking a topology while another validates a working baseline against the same platform.
Full specifications for Arista Cloud Test
Download product documentation and resources
Explore other configurations and models that might suit your needs.
Recommended
#Arista-CLOUDVISION-CUE
Recommended
#Arista-DANZ-MONITORING-FABRIC
Recommended
#Arista-MULTI-DIRECTOR
Our team of experts is ready to help you find the perfect solution for your business needs. Get personalized advice and competitive quotes.
We're here to help with any questions