Unable to map prod production s3 repo on test cluster

Hello Team,

We have an AWS S3 repository configured on our production Elasticsearch cluster for backup snapshots, and this repository is successfully mapped to our PERF environment to restore snapshots without any issues.

However, when attempting to map the same repository to our test cluster, we are encountering the following error:

Environment Details:

  • The production cluster is in a different AWS account, and the S3 bucket is also in the same account.
  • Our PERF and test clusters are in a same AWS account. We have configured cross-account permissions for the S3 bucket with GET, PUT, and LIST permissions.
  • Elasticsearch version on Production and PERF: 7.17.0
  • Elasticsearch version on Test Cluster: 7.5.1

Given this configuration, we are experiencing the issue only on the test cluster. We need assistance in resolving this problem.

Error:

{
"error": {
"root_cause": [
{
"type": "repository_verification_exception",
"reason": "[es-prd-va-7-17-repo] path [snapshots/prd_es_7_17] is not accessible on master node"
}
],
"type": "repository_verification_exception",
"reason": "[es-prd-va-7-17-repo] path [snapshots/prd_es_7_17] is not accessible on master node",
"caused_by": {
"type": "i_o_exception",
"reason": "Unable to upload object [snapshots/prd_es_7_17/tests-iR8klPHPQd2M1xA6-ZDF6g/master.dat] using a single upload",
"caused_by": {
"type": "amazon_service_exception",
"reason": "Unauthorized (Service: null; Status Code: 401; Error Code: null; Request ID: null)"
}
}
},
"status": 500
}