Repository-gcs plugin 5.2.2 and Google Global HTTP batch endpoint

[MMH]

Hi,
Google is deprecating Global HTTP batch endpoint on Aug 12th: https://www.google.com/url?q=https://developers.googleblog.com/2018/03/discontinuing-support-for-json-rpc-and.html
On the ES 5.2 cluster, the repository-gcs plugin is still using this endpoint for Google Cloud Storage communication.
I saw an issue created for this: https://github.com/elastic/elasticsearch/issues/29259
And a commit, that resolved the issue for ES 6.4 and never: https://github.com/elastic/elasticsearch/commit/873d380f455811c6f3002ad3436f310e3e3dfb78

I do not want to lose repository-gcs plugin functionality on my cluster.
Is there a way to get around this issue without upgrading cluster to a newer version?

[Armin_Braun]

Hi @MMH

Is there a way to get around this issue without upgrading cluster to a newer version?

I'm afraid the answer here is mostly no. Elasticsearch 5.x is past its EOL date and we won't be releasing a fix for it going forward.

The best workaround I can think of if you absolutely cannot upgrade might be to use the S3 compatibility layer in GCS and use the S3 repository plugin instead of the GCS plugin. That might work going forward but I don't want to make any guarantees since I haven't tested it.