You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 17, 2024. It is now read-only.
Verify that agent started and enrolled to the Fleet
Overview
In cloud deployments and/or physical system deployments there is a case where you want an Elastic Agent to enroll into Fleet on first startup and not at installation time. Example being a prepared gold image for a cloud deployment, or a prepared sys-prepped Windows image for an organization.
Idea
The idea is to add an option to the install command to not have it actually start the service and to not actually enroll at that time.
This would proceed to install the Elastic Agent, write an enroll.yml (with the url and enrollment token) file next to the elastic-agent.yml file and not start the service.
Then on the first start of the service (which is normally on boot up of a fresh deployment) then the Elastic Agent would notice that a enroll.yml file is present, load that perform enrollment, re-exec into Fleet mode, and then delete the enroll.yml.
The text was updated successfully, but these errors were encountered:
Steps:
Overview
In cloud deployments and/or physical system deployments there is a case where you want an Elastic Agent to enroll into Fleet on first startup and not at installation time. Example being a prepared gold image for a cloud deployment, or a prepared sys-prepped Windows image for an organization.
Idea
The idea is to add an option to the install command to not have it actually start the service and to not actually enroll at that time.
.\elastic-agent install --delay-enroll --url https://my.fleet.server --enrollment-token ${token}
Implementation
This would proceed to install the Elastic Agent, write an enroll.yml (with the url and enrollment token) file next to the elastic-agent.yml file and not start the service.
Then on the first start of the service (which is normally on boot up of a fresh deployment) then the Elastic Agent would notice that a enroll.yml file is present, load that perform enrollment, re-exec into Fleet mode, and then delete the enroll.yml.
The text was updated successfully, but these errors were encountered: