[skip ci] Important note: Don't use keys/certi shipped in Prod

Author: Chris Wiechmann

README.md

@@ -645,17 +645,21 @@ To activate these changes the Filebeat service must be restarted.
 
 _If you are using an existing Elasticsearch cluster, you have to provide the required CA to the solution to allow certificate validation._
 
-The project is shipped with long running certificates/keys that should help you to get started with the solution. For a production environment these certificates and keys should be replaced with custom certificates.  
+The project is shipped with sample long running certificates/keys that should help you to get started with the solution. For a production environment these certificates and keys should be replaced with custom certificates, as the sample certificates & key are public available on GitHub.  
 
 After you have created the corresponding certificates and keys based on your CA, you must save them in the folder: `certificates`. 
 Afterwards these certificates must be configured in the `.env` file.  
 ```
 API_BUILDER_SSL_KEY=config/certificates/corporate-certificate.key
 API_BUILDER_SSL_CERT=config/certificates/corporate-certificate.crt
 API_BUILDER_SSL_KEY_PASSWORD=dfslkjaskljdklasjdlas
-ELASTICSEARCH_KEY=config/certificates/corporate-elasticsearch.key
-ELASTICSEARCH_CRT=config/certificates/corporate-elasticsearch.crt
 ELASTICSEARCH_CA=config/certificates/corp-ca.crt
+ELASTICSEARCH1_KEY=config/certificates/corporate-elasticsearch.key
+ELASTICSEARCH1_CRT=config/certificates/corporate-elasticsearch.crt
+ELASTICSEARCH2_KEY=config/certificates/corporate-elasticsearch.key
+ELASTICSEARCH2_CRT=config/certificates/corporate-elasticsearch.crt
+ELASTICSEARCH3_KEY=config/certificates/corporate-elasticsearch.key
+ELASTICSEARCH3_CRT=config/certificates/corporate-elasticsearch.crt
 KIBANA_KEY=config/certificates/corporate-kibana.key
 KIBANA_CRT=config/certificates/corporate-kibana.crt
 ```

config/certificates/README.md

@@ -1,6 +1,7 @@
-Certificates in this folder will be made available to the Docker-Containers by a mount 
-and configured in the .env file.  
-If you would to use your own certificates and keys, place them in this directory and 
-adjust the .env file accordingly.
-It's important that you are using different filenames, as the original files will be 
+# Sample certificates for testing only
+
+The sample certificates in this folder will be automatically made available to the Docker-Containers by a mount and are pre-configured in the .env file.  
+:point_right:  It's stringly recommended that you use your own certificates and keys as the __certificates & keys are public on GitHub__. 
+
+Place you own certificates and keys in this directory and adjust the .env file accordingly. It's important that you are using different filenames, as the original files will be 
 replaced with the next version.