> For the complete documentation index, see [llms.txt](https://docs.exavault.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.exavault.com/installing-and-upgrading-the-appliance/system-requirements.md). # System Requirements ExaVault is delivered as a virtual appliance. You are responsible for provisioning a physical environment and hypervisor in which to run the ExaVault appliance. ExaVault requires a 64-bit Intel processor. ARM environments, including AWS Graviton instances, are not supported. The ExaVault Virtual Appliance is tested and supported in the following virtual environments: * VMware ESXi 5.x, 6.x, 7.x, 8.x * Microsoft HyperV * Amazon AWS * Microsoft Azure * Linux KVM Within the hypervisor or cloud system of your choice, you will need to provision the following minimum resources: * **CPU:** 4 cores at 2.4 GHz or greater * **Memory:** 12 GB of memory (RAM) * **Primary Disk Drive:** 100 GB * **Data Disk Drive:** Sized at your discretion. All data on the appliance is saved to this drive, so make it as large as your environment can support. We recommend starting with at least 500 GB. The minimum supported instance sizes on AWS are `c5n.xlarge`, `m6i.xlarge`, or `m7i.xlarge`. You will also need a static (or rarely-changing) IP address because your installation's [license is associated with its IP address](/administration-tasks/license-keys.md#ip-address-changes). Frequent updates to the appliance's IP address will invalidate the license. Workloads vary widely across our customer base, so sizing guidance beyond these minima is hard to give in the abstract. Monitor RAM and CPU usage and upscale the instance when either resource is constrained. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.exavault.com/installing-and-upgrading-the-appliance/system-requirements.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.