[BZ-1399388] Explicitly state logging directly to AWS ES is not supported

[jcantrill]

cc @ewolinetz

[ewolinetz]

I think we should simply state to use Fluentd Secure Forward in conjunction with a Fluentd instance that is configured with an AWS-ES plugin instead of "to understand how this may be accomplished"

[jcantrill]

@ewolinetz @richm updated

[ewolinetz]

LGTM

[richm]

LGTM

[ahardin-rh]

Thanks!

[ahardin-rh]

[rev_history]
|xref:../install_config/aggregate_logging.adoc#install-config-aggregate-logging[Aggregating Container Logs]
|Added Note boxes explicitly stating that sending logs directly to an AWS Elasticsearch instance is not supported.
%

[adellape]

@jcantrill This PR and its follow-up (#3340) reference and link to the "Configuring Fluentd to Send Logs to an External Log Aggregator" section, but that isn't being added until 3.4 (via #2969 + #3067). It's not clear from https://bugzilla.redhat.com/show_bug.cgi?id=1399388 whether this should go into 3.3 docs now or not, so I'm moving the milestone on this to "Future Release" until confirmed.

Reason I'm doing this is because it was about to published in this week's 3.3 doc update.

cc @ahardin-rh @richm

[richm]

@adellape IMO, it should go into the 3.3 docs, since

• we support secure_forward in 3.3 and
• the 3.3 docs say you can configure fluentd to send logs to any Elasticsearch

[adellape]

@richm OK, thanks. Confirmed on IRC w/ @ewolinetz that this was backported to the 3.3 fluentd image, so I'm gonna let this + the 3 other PRs mentioned above through into 3.3 docs.