IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.

« Monitor a self-managed Fleet Server Install Fleet-managed Elastic Agents »

›

Install Elastic Agents

edit

Install Elastic Agents

edit

Restrictions

Note the following restrictions when installing Elastic Agent on your system:

You can install only a single Elastic Agent per host. Due to the fact that the Elastic Agent may read data sources that are only accessible by a superuser, Elastic Agent will therefore also need to be executed with superuser permissions.
You might need to log in as a root user (or Administrator on Windows) to run the commands described here. After the Elastic Agent service is installed and running, make sure you run these commands without prepending them with ./ to avoid invoking the wrong binary.
Running Elastic Agent commands using the Windows PowerShell ISE is not supported.

You have a few options for installing and managing an Elastic Agent:

Install a Fleet-managed Elastic Agent (recommended)

With this approach, you install Elastic Agent and use Fleet in Kibana to define, configure, and manage your agents in a central location.

We recommend using Fleet management because it makes the management and upgrade of your agents considerably easier.

Refer to Install Fleet-managed Elastic Agents.
Install Elastic Agent in standalone mode (advanced users)

With this approach, you install Elastic Agent and manually configure the agent locally on the system where it’s installed. You are responsible for managing and upgrading the agents. This approach is reserved for advanced users only.

Refer to Install standalone Elastic Agents (advanced users).
Install Elastic Agent in a containerized environment

You can run Elastic Agent inside of a container — either with Fleet Server or standalone. Docker images for all versions of Elastic Agent are available from the Elastic Docker registry, and we provide deployment manifests for running on Kubernetes.

Refer to:

Restrictions in Serverless

If you are using Elastic Agent with Elastic Cloud Serverless, note these differences from use with Elasticsearch Service and self-managed Elasticsearch:

The number of Elastic Agents that may be connected to an Elastic Cloud Serverless project is limited to 10 thousand.
The minimum supported version of Elastic Agent supported for use with Elastic Cloud Serverless is 8.11.0.

Minimum Requirements

edit

Minimum requirements have been determined by running the Elastic Agent on a GCP e2-micro instance (2vCPU/1GB). The Elastic Agent used the default policy, running the system integration and self-monitoring. During upgrades, double the disk space is required to store the new Elastic Agent binary. After the upgrade completes, the original Elastic Agent is removed from disk to free up the space.

CPU	Under 2% total, including all monitoring processes
Disk	1.7 GB
RSS Mem Size	400 MB

Adding integrations will increase the memory used by the agent and its processes.

« Monitor a self-managed Fleet Server Install Fleet-managed Elastic Agents »