I want to know how i can provide my own API key in ELK version 8.0.0
I did try - "xpack.security.authc.api_key.enabled=true"
but no luck getting xpack.security.authc.api_key.key unknow setting in docker logs.
So wanted to know can we provide our own API key or not.
We want to implement this as we are monitoring a large number of machines and if ELK is completely destroyed, we can make it up from start and use the same old API key so that we do not need to rechange the API key in each beat's setup in machine for monitoring.
There is no such setting
Since you are using version 8.0, API key is enabled automatically. So you don't need to configure anything. In earlier versions, you need to enable it with
Thank you @Yang_Wang ,so do we have any other ways to setup a own API Key instead getting a random API Key ?
What do you mean by "a own API key"? If this is about reuse the same API key in a brand new cluster, it is not possible.
Yes I was thinking to use a old API key for a same cluster UID if we can do this it would help us a lot.
e.g if we have an ELK cluster running in docker, but we remove the entire container and recreated a container. so instead of creating a new API key we would love to use old API key so that we only do changes in ELK not in beats like changing API key in yml files. I hope this help
The only supported way to achieve what you are after is snapshot and restore the security feature state.
Thank You @Yang_Wang this really helps.
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.