[Website]: Generalize the output API key section to consider other outputs #1605
Description
Type of issue
None
What documentation page is affected
https://www.elastic.co/docs/reference/fleet/fleet-enrollment-tokens
What happened?
The page https://www.elastic.co/docs/reference/fleet/fleet-enrollment-tokens is correct when one uses ES outputs in the policy.
We got report of users getting confused Elastic Agent would still "generate" an ES API Key for the output even if one uses purely Logstash or Kafka output in the policy (both the data and monitoring outputs) are not Elasticsearch.
If the output is:
- ES Output: an API Key for ES will be generated by Fleet at Elastic Agent enroll time and will be updated over time with the EA Policy. The permissions will grant write permissions to data streams associated to the integration in the policy
- Remote ES Output: not 100% certain of the whole flow, we need to ask Fleet team
- LS Ouptut: no API key will be deployed on the Elastic Agent as the API Key must be generated at LS Output creation time and it is not needed on the Elastic Agent
- Kafka Output: auth parameters to connect to Kafka from EA will be deployed to the Elastic Agent
Additional info
No response