Installation layout
Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability This functionality is generally available and ready for production usage. Serverless interfaces and procedures might differ from classic Elastic Stack deployments. The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability This functionality is generally available and ready for production usage. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
Serverless
Generally available
Stack
Generally available
Elastic Agent files are installed in the following locations.
/Library/Elastic/Agent/*- Elastic Agent program files
/Library/Elastic/Agent/elastic-agent.yml- Main Elastic Agent configuration
/Library/Elastic/Agent/fleet.enc- Main Elastic Agent Fleet encrypted configuration
/Library/Elastic/Agent/data/elastic-agent-*/logs/elastic-agent.ndjson- Log files for Elastic Agent and Beats shippers1
/usr/local/bin/elastic-agent- Shell wrapper installed into PATH
You can install Elastic Agent in a custom base path other than /Library. When installing Elastic Agent with the ./elastic-agent install command, use the --base-path CLI option to specify the custom base path.
/opt/Elastic/Agent/*- Elastic Agent program files
/opt/Elastic/Agent/elastic-agent.yml- Main Elastic Agent configuration
/opt/Elastic/Agent/fleet.enc- Main Elastic Agent Fleet encrypted configuration
/opt/Elastic/Agent/data/elastic-agent-*/logs/elastic-agent.ndjson- Log files for Elastic Agent and Beats shippers1
/usr/bin/elastic-agent- Shell wrapper installed into PATH
You can install Elastic Agent in a custom base path other than /opt. When installing Elastic Agent with the ./elastic-agent install command, use the --base-path CLI option to specify the custom base path.
C:\Program Files\Elastic\Agent*- Elastic Agent program files
C:\Program Files\Elastic\Agent\elastic-agent.yml- Main Elastic Agent configuration
C:\Program Files\Elastic\Agent\fleet.enc- Main Elastic Agent Fleet encrypted configuration
C:\Program Files\Elastic\Agent\data\elastic-agent-*\logs\elastic-agent.ndjson- Log files for Elastic Agent and Beats shippers1
You can install Elastic Agent in a custom base path other than C:\Program Files. When installing Elastic Agent with the .\elastic-agent.exe install command, use the --base-path CLI option to specify the custom base path.
/usr/share/elastic-agent/*- Elastic Agent program files
/etc/elastic-agent/elastic-agent.yml- Main Elastic Agent configuration
/etc/elastic-agent/fleet.enc- Main Elastic Agent Fleet encrypted configuration
/var/lib/elastic-agent/data/elastic-agent-*/logs/elastic-agent.ndjson- Log files for Elastic Agent and Beats shippers1
/usr/bin/elastic-agent- Shell wrapper installed into PATH
/usr/share/elastic-agent/*- Elastic Agent program files
/etc/elastic-agent/elastic-agent.yml- Main Elastic Agent configuration
/etc/elastic-agent/fleet.enc- Main Elastic Agent Fleet encrypted configuration
/var/lib/elastic-agent/data/elastic-agent-*/logs/elastic-agent.ndjson- Log files for Elastic Agent and Beats shippers1
/usr/bin/elastic-agent- Shell wrapper installed into PATH
1 Logs file names end with a date (YYYYMMDD) and optional number: elastic-agent-YYYYMMDD.ndjson, elastic-agent-YYYYMMDD-1.ndjson, and so on as new files are created during rotation.