@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.
@elkninja Been following along your part one blog and noticed you have specific cert parameters in your metricbeat service within docker-compose.yml. Specifically,
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.