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

Certificate parameters in metricbeat service #29

Open
jc0r3 opened this issue Sep 8, 2024 · 0 comments
Open

Certificate parameters in metricbeat service #29

jc0r3 opened this issue Sep 8, 2024 · 0 comments

Comments

@jc0r3
Copy link

jc0r3 commented Sep 8, 2024

@elkninja Been following along your part one blog and noticed you have specific cert parameters in your metricbeat service within docker-compose.yml. Specifically,

  - CA_CERT=certs/ca/ca.crt
  - ES_CERT=certs/es01/es01.crt
  - ES_KEY=certs/es01/es01.key
  - KB_CERT=certs/kibana/kibana.crt
  - KB_KEY=certs/kibana/kibana.key

command:
-strict.perms=false

Why do you specify cert and location within the metricbeat service? We create certs in the setup for metric beat and copy those to /usr/share/elasticsearch/config/certs for all containers (services) to access. I am trying to understand the certificate usage here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant