- Fleet and Elastic Agent Guide: other versions:
- Fleet and Elastic Agent overview
- Beats and Elastic Agent capabilities
- Quick start: Get logs, metrics, and uptime data into the Elastic Stack
- Quick start: Get application traces into the Elastic Stack
- Integrations
- Elastic Agents
- Install Elastic Agents
- Uninstall Elastic Agent
- Run Elastic Agent standalone (advanced users)
- Run Elastic Agent in a container
- Run Elastic Agent on Kubernetes managed by Fleet
- Run Elastic Agent standalone on Kubernetes
- Upgrade Elastic Agent
- Start Elastic Agent
- Stop Elastic Agent
- Unenroll Elastic Agent
- View status of Elastic Agents
- Variables and conditions in input configurations
- Environment variables
- Configure logging for Fleet-managed Elastic Agents
- Policies
- Elastic Agent standalone configuration
- Fleet UI settings
- Fleet Server
- Fleet enrollment tokens
- Encrypt traffic in clusters with a self-managed Fleet Server
- Data streams
- Command reference
- Troubleshoot common problems
- Frequently asked questions
- Release notes
- Fleet APIs
IMPORTANT: No additional bug fixes or documentation updates
will be released for this version. For the latest information, see the
current release documentation.
Unenroll Elastic Agent
editUnenroll Elastic Agent
editYou can unenroll an agent to invalidate the API key used to connect to Elasticsearch.
- In Fleet, select Agents.
- Under Agents, choose Unenroll agent from the Actions menu next to the agent you want to unenroll.
-
Click Unenroll agent.
The agent will continue to run, but will not be able to send data. It will show this error instead:
invalid api key to authenticate with fleet
.
If unenrollment hangs, select Force unenroll to invalidate all API
keys related to the agent and change the status to inactive
so that the agent
no longer appears in Fleet.
Was this helpful?
Thank you for your feedback.