anchor.diff:  
   [NOTE]
   ====
  -Sending logs directly to an AWS Elasticsearch instance is not supported.  Please
  -use xref:fluentd-external-log-aggregator[Fluentd Secure Forward] to direct logs to an instance of 
  -Fluentd that you control and is configured with the `fluent-plugin-aws-elasticsearch-service` plugin.
  +Sending logs directly to an AWS Elasticsearch instance is not supported. Use
  +xref:fluentd-external-log-aggregator[Fluentd Secure Forward] to direct logs to
  +an instance of Fluentd that you control and that is configured with the
  +`fluent-plugin-aws-elasticsearch-service` plug-in.
   ====
   
   To direct logs to a specific Elasticsearch instance, edit the deployment
  
positive.code: 
  [NOTE]
  ====
  Sending logs directly to an AWS Elasticsearch instance is not supported.  Please
  use xref:fluentd-external-log-aggregator[Fluentd Secure Forward] to direct logs to an instance of 
  Fluentd that you control and is configured with the `fluent-plugin-aws-elasticsearch-service` plugin.
  ====
  
  To set the parameters:
  
negative.code: ====
  As of {product-title} 3.3, Fluentd no longer reads historical log files when using the
  json-file log driver. This is to avoid delays pushing into Elasticsearch the most recent logs
  on clusters that have a large number of log files that are older then the EFK deployment, and to
  mitigate Curator deleting logs shortly after they are added to Elasticsearch.
  ====
  
  