[Docs] Link to AWS SDK documentation for requests logging

[tlrx]

Co-authored-by: David Turner david.turner@elastic.co

[github-actions]

Documentation preview:

• ✨ Changed pages

[elasticsearchmachine]

Pinging @elastic/es-docs (Team:Docs)

[elasticsearchmachine]

Pinging @elastic/es-distributed (Team:Distributed)

[DaveCTurner]

I suspect that this will not completely redirect these questions away from the ES team. How about something a little more explicit like this?

Most storage systems can be configured to log the details of their interaction
with {es}. If you are investigating a suspected incompatibility with AWS S3, it
is usually simplest to collect these logs and provide them to the supplier of
your storage system for further analysis. If the incompatibility is not clear
from the logs emitted by the storage system, configure {es} to log every
request it makes to the S3 API by <<configuring-logging-levels,setting the
logging level>> of the `com.amazonaws.request` logger to `DEBUG`:

[source,console]
----
PUT /_cluster/settings
{
  "persistent": {
    "logger.com.amazonaws.request": "DEBUG"
  }
}
----
// TEST[skip:we don't really want to change this logger]

The supplier of your storage system will be able to analyse these logs to determine the problem. See
the https://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/java-dg-logging.html[AWS Java SDK]
documentation for further information.

[tlrx]

This is much better indeed, I stole your suggestion without any change.

[DaveCTurner]

LGTM

[elasticsearchmachine]

💚 Backport successful

Status	Branch	Result
✅	8.11
✅	8.10