Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Fleet] Create additional API Keys for inputs #91704

Closed
simitt opened this issue Feb 17, 2021 · 3 comments
Closed

[Fleet] Create additional API Keys for inputs #91704

simitt opened this issue Feb 17, 2021 · 3 comments
Labels
Feature:Fleet Fleet team's agent central management project Team:Fleet Team label for Observability Data Collection Fleet team

Comments

@simitt
Copy link
Contributor

simitt commented Feb 17, 2021

Some inputs require access to Elasticsearch with additional privileges compared to the ones provided for the output.
An example for such a requirement is the new tail based sampling feature in APM Server, requiring read access to a specific data stream in Elasticsearch.

For such requirements an API Key should be generated and passed down to the Elastic Agent, which in turn will need to split up the configuration into inputs and forward the keys to the right inputs.

@simitt simitt added Feature:Fleet Fleet team's agent central management project Team:Fleet Team label for Observability Data Collection Fleet team labels Feb 17, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/fleet (Feature:Fleet)

@elasticmachine
Copy link
Contributor

Pinging @elastic/fleet (Team:Fleet)

@ph
Copy link
Contributor

ph commented Feb 23, 2021

@simitt Looking at elastic/fleet-server#101 we won't need to create additional api key for input but actually we will generate finer grained permission on the api keys.

@ph ph closed this as completed Feb 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Fleet Fleet team's agent central management project Team:Fleet Team label for Observability Data Collection Fleet team
Projects
None yet
Development

No branches or pull requests

3 participants