anchor.diff:  do this when deploying only Kibana, to secure internal traffic
   between Kibana and Elasticsearch through the internal load balancer.
   
  -Configuring TLS for the HTTP layer requires xPackPlugins be set to `Yes`, and the following parameters can be used
  +Configuring TLS for the HTTP layer requires `xPackPlugins` be set to `Yes` for 5.x versions, 
  +6.x versions less than 6.8.0 and 7.x versions less than 7.1.0. With `xPackPlugins` set to `Yes`, a trial
  +license will be applied to the cluster, which allows TLS to be configured on these versions.
  +
  +The following parameters can be used
   
   `esHttpCertBlob`::
   A base 64 encoded string of the PKCS#12 archive containing the certificate and key with which to secure the HTTP layer. This certificate will be used by all nodes within the cluster.
  
positive.code: ==== Transport layer
  
  You can secure communication between nodes in the cluster with TLS on the Transport layer of Elasticsearch.
  Configuring TLS for the Transport layer requires `xPackPlugins` be set to `Yes`.
  The following parameters can be used
  
  `esTransportCaCertBlob`::
  
negative.code: the cluster. Each generated certificate contains a Subject Alternative Name DNS entry with
  the hostname and an ipAddress entry with the private IP address.
  
  `esTransportCaCertPassword`::
  Optional passphrase for the PKCS#12 archive encoded in `esTransportCaCertBlob`. Defaults
  to empty string as the archive may not be protected.
  
  `esTransportCertPassword`::
  Optional passphrase for each PKCS#12 archive generated by the CA certificate supplied in `esTransportCaCertBlob`.
  
  One way to generate a PKCS#12 archive containing a CA certificate and key is using
  {elasticdocs}/certutil.html[Elastic's certutil command utility].
  