Deploy Envoy Proxy on Google Cloud C4A (Arm-based Axion VMs)
Introduction
Get started with Envoy Proxy on Google Axion C4A (Arm Neoverse V2)
Create a Google Axion C4A Arm virtual machine on GCP
Deploy Envoy on Google Axion C4A Arm virtual machines
Run baseline Envoy testing on a Google Axion C4A Arm VM
Benchmark Envoy on Google Cloud for Arm64 and x86_64 with Siege
Next Steps
Deploy Envoy Proxy on Google Cloud C4A (Arm-based Axion VMs)
Introduction
Get started with Envoy Proxy on Google Axion C4A (Arm Neoverse V2)
Create a Google Axion C4A Arm virtual machine on GCP
Deploy Envoy on Google Axion C4A Arm virtual machines
Run baseline Envoy testing on a Google Axion C4A Arm VM
Benchmark Envoy on Google Cloud for Arm64 and x86_64 with Siege
Next Steps
Review frequently asked questions
These FAQs were drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.
Use the C4A family with the
c4a-standard-4 machine type (four vCPUs, 16 GB memory).Follow the verification step after installing the official static Arm64 binary to confirm it’s present and executable. You should be able to start Envoy with the provided minimal configuration before continuing.
Requests to the listener on port
10000 should be proxied to httpbin.org and return HTTP 200 OK. The response confirms the listener is active and routing works as configured.Target the Envoy listener defined in your configuration, typically the VM’s address on port
10000 or localhost:10000. Keep the same target across runs to compare results consistently.Use the same Envoy version, configuration, and Siege workload on both instance types. Compare throughput, response time, availability, and failure rates reported by Siege.