--- title: Compatibility and requirements for the infrastructure agent source: https://docs.newrelic.com/docs/infrastructure/infrastructure-agent/requirements-infrastructure-agent --- Before [installing our infrastructure agent](https://docs.newrelic.com/docs/infrastructure/install-infrastructure-agent/get-started/install-infrastructure-agent-new-relic), make sure your system and any on-host integrations you configure meet the requirements. You also need a New Relic account. [Sign up for free](https://newrelic.com/signup). No credit card required. ## Processor architectures [#processors] The infrastructure agent supports these processor architectures: - **Linux**: 64-bit for x86 processor architectures (also requires 64-bit package manager and dependencies) - **Windows**: 64-bit for x86 processor architectures - **ARM**: arm64 architecture including [AWS Graviton 2 processor](https://aws.amazon.com/ec2/graviton/) is supported on compatible Linux operating sytems. On-host integrations are also supported (with the exception of the Oracle integration). - **macOS**: both 64-bit x86 and Apple silicon. ## Operating systems [#os] The infrastructure agent supports these operating systems up to their manufacturer's end-of-life. The agent might still be compatible with older versions, but please refer to the step-by-step instructions for each operating system if the guided installation is no longer available for a specific operating system version. | Operating system | Supported by the infrastructure agent | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ![amazon linux.png](https://docs.newrelic.com/images/os_icon_amazon-linux.webp "amazon linux")[Amazon Linux 2, Amazon Linux 2023](https://docs.newrelic.com/docs/infrastructure-install-amazon-linux-centos-debian-rhel-or-ubuntu) | All versions | | ![centos icon](https://docs.newrelic.com/images/os_icon_centos.webp "centos icon")[CentOS](https://docs.newrelic.com/docs/infrastructure-install-amazon-linux-centos-debian-rhel-or-ubuntu) | CentOS Stream 9 or higher ( CentOS 10 installs via tarball; package manager is work in progress ) | | ![almalinux icon](https://docs.newrelic.com/images/os_icon_almalinux.webp "AlmaLinux icon")[AlmaLinux](https://docs.newrelic.com/docs/infrastructure-install-amazon-linux-centos-debian-rhel-or-ubuntu) | AlmaLinux 8, 9 and 10 | | ![rockylinux icon](https://docs.newrelic.com/images/os_icon_rockylinux.webp "RockyLinux icon")[RockyLinux](https://docs.newrelic.com/docs/infrastructure-install-amazon-linux-centos-debian-rhel-or-ubuntu) | RockyLinux 8, 9 and 10 | | ![Debian.png](https://docs.newrelic.com/images/os_icon_debian.webp "Debian icon")[Debian](https://docs.newrelic.com/docs/infrastructure-install-amazon-linux-centos-debian-rhel-or-ubuntu) | Version 11 ("bullseye"), 12 ("bookworm") and 13 ("trixie") | | ![Docker icon](https://docs.newrelic.com/images/os_icon_docker.webp "Docker icon")[Docker](https://docs.newrelic.com/docs/infrastructure/install-configure-manage-infrastructure/docker-installation/docker-instrumentation-infrastructure) | See [container monitoring requirements](https://docs.newrelic.com/docs/infrastructure/install-infrastructure-agent/linux-installation/container-instrumentation-infrastructure-monitoring/#requirements) | | ![Kubernetes icon](https://docs.newrelic.com/images/os_icon_k8.webp "Kubernetes icon")[Kubernetes](https://docs.newrelic.com/docs/integrations/host-integrations/host-integrations-list/kubernetes-monitoring-integration) | See [Kubernetes integration requirements](https://docs.newrelic.com/docs/kubernetes-pixie/kubernetes-integration/get-started/kubernetes-integration-compatibility-requirements/#compatibility) | | ![redhat icon](https://docs.newrelic.com/images/os_icon_redhat.webp "redhat icon")[Red Hat Enterprise Linux (RHEL)](https://docs.newrelic.com/docs/infrastructure-install-amazon-linux-centos-debian-rhel-or-ubuntu) | Version 7.9 to 10 | | ![Oracle icon](https://docs.newrelic.com/images/os_icon_oracle.webp "oracle icon")[Oracle Linux](https://docs.newrelic.com/docs/infrastructure-install-amazon-linux-centos-debian-rhel-or-ubuntu) | Version 7.9 or higher | | ![suse icon](https://docs.newrelic.com/images/os_icon_suse.webp "suse icon")[SUSE Linux Enterprise Server (SLES)](https://docs.newrelic.com/docs/infrastructure-install-amazon-linux-centos-debian-rhel-or-ubuntu) | Versions 12.5, 15.3, 15.4, 15.5, 15.6, 15.7 | | ![ubuntu icon](https://docs.newrelic.com/images/os_icon_ubuntu.webp "ubuntu icon")[Ubuntu](https://docs.newrelic.com/docs/infrastructure-install-amazon-linux-centos-debian-rhel-or-ubuntu) | [LTS](https://wiki.ubuntu.com/LTS) versions 16.04.x, 18.04.x, 20.04.x, 22.04.x, 24.04.x | | ![Windows Server icon](https://docs.newrelic.com/images/os_icon_windows.webp "Windows Server")[Windows](https://docs.newrelic.com/docs/infrastructure-install-windows-server) | Windows Server 2016, 2019, 2022 and 2025. Windows 10 (Microsoft EOL date October 14th 2025), Windows 11. | | ![macOS icon](https://docs.newrelic.com/images/os_icon_mac.webp "macOS")[macOS](https://docs.newrelic.com/docs/infrastructure/install-infrastructure-agent/macos-installation/install-infrastructure-monitoring-agent-macos/) | 3 most recent major versions. Currently: 13 (Ventura), 14 (Sonoma), 15 (Sequoia) | You can also monitor Amazon BottleRocket workloads: - When running EC2 instances, use the [containerized agent](https://docs.newrelic.com/docs/infrastructure/install-infrastructure-agent/linux-installation/docker-container-infrastructure-monitoring). - On EKS, install the [Kubernetes integration](/install/kubernetes). - For ECS clusters, deploy the [ECS integration](https://docs.newrelic.com/docs/integrations/elastic-container-service-integration/installation/install-ecs-integration). ## Unique hostname [#hostname] The infrastructure agent uses the hostname to uniquely identify each server. To avoid inaccurate metrics from combining multiple servers under a single hostname, make sure that each monitored server has a unique hostname. - You can use the optional [`display_name`](https://docs.newrelic.com/docs/infrastructure/new-relic-infrastructure/configuration/configure-infrastructure-agent#display_name) setting to override the default hostname. - Servers named `localhost` are not reported because this is a default name and inherently non-unique. ## Permissions The infrastructure agent requires these permissions: - **Linux**: By default, [the agent runs and installs as root](https://docs.newrelic.com/docs/infrastructure/new-relic-infrastructure/installation/install-infrastructure-agent-linux#agent-mode-intro). You can also select [privileged](https://docs.newrelic.com/docs/infrastructure/new-relic-infrastructure/installation/install-infrastructure-agent-linux#install-privileged) or [unprivileged](https://docs.newrelic.com/docs/infrastructure/new-relic-infrastructure/installation/install-infrastructure-agent-linux#install-unprivileged) run modes. - **Windows**: The agent must be installed from an Administrator account, and by default it will run as a service with the `Local System` logon context. It can also run as a non-admin/user account (local, Active Directory, Microsoft Entra ID or Group Managed Service Account / gMSA). The included script `set-service-account.ps1` helps with the transition and sets the required privileges. - **macOS**: The agent can be installed from any user account. ## Libraries For [agent versions 1.1.19 or higher](https://docs.newrelic.com/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes), you need the `libcap` library in order to install. It's available in the official repositories of your distribution. ## Network access [#network] In order to report data to New Relic, our infrastructure agent must have outbound access to [certain domains and ports](https://docs.newrelic.com/docs/apm/new-relic-apm/getting-started/networks#infrastructure). If your system needs a proxy to connect to these domains, use the [`proxy`](https://docs.newrelic.com/docs/infrastructure/new-relic-infrastructure/configuration/configure-infrastructure-agent#proxy) setting. ## Data center region support [#region-support] To report data to the [JP region data center](https://docs.newrelic.com/docs/accounts/accounts-billing/account-setup/choose-your-data-center/), you need these minimum versions: - Infrastructure agent [1.76.0](https://docs.newrelic.com/docs/release-notes/infrastructure-release-notes/infrastructure-agent-release-notes) or higher - Infrastructure bundle [3.3.28](https://github.com/newrelic/infrastructure-bundle/releases) or higher - nri-ecs [1.14.3](https://github.com/newrelic/nri-ecs/releases) or higher - nri-statsd [2.15.0](https://github.com/newrelic/nri-statsd/releases/tag/v2.15.0) or higher ## Container software [#container] The infrastructure agent [instruments Docker containers](https://docs.newrelic.com/docs/infrastructure-docker-instrumentation) when installed on the host server. We support Docker versions 1.12 or higher. ## CPU, memory, and disk usage [#resources] The infrastructure agent is fairly lightweight. For typical CPU, memory, and disk usage, see our page on [agent performance overhead](https://docs.newrelic.com/docs/infrastructure/new-relic-infrastructure/getting-started/infrastructure-agent-performance-overhead). For more information on supported file systems, see [Storage sample attributes](https://docs.newrelic.com/docs/infrastructure/new-relic-infrastructure/data-instrumentation/default-infrastructure-attributes-events#storagesample-attributes). ## Configuration management tools [#config-mgmt] The infrastructure agent can be deployed programmatically using several config management and deploy tools: - ![Ansible](https://docs.newrelic.com/images/os_icon_ansible-red.webp "Ansible") [Ansible](https://docs.newrelic.com/docs/infrastructure/new-relic-infrastructure/config-management-tools/configure-new-relic-infrastructure-using-ansible) - ![Chef](https://docs.newrelic.com/images/os_icon_chef.webp "Chef") [Chef](https://docs.newrelic.com/docs/infrastructure/new-relic-infrastructure/config-management-tools/configure-new-relic-infrastructure-using-chef) - ![EBS](https://docs.newrelic.com/images/os_icon_ebs.webp "EBS")[Elastic Beanstalk](https://docs.newrelic.com/docs/infrastructure/install-infrastructure-agent/config-management-tools/install-infrastructure-agent-aws-elastic-beanstalk) - ![Puppet](https://docs.newrelic.com/images/os_icon_puppet.webp "Puppet") [Puppet](https://docs.newrelic.com/docs/infrastructure/new-relic-infrastructure/config-management-tools/configure-new-relic-infrastructure-puppet) ## Other integrations [#other-integrations] If you're installing the Kubernetes integration, make sure that you meet the [Kubernetes compatibility and requirements](https://docs.newrelic.com/docs/kubernetes-pixie/kubernetes-integration/get-started/kubernetes-integration-compatibility-requirements).