Hello All, After configuring migration for a few indexes, the following errors is filling up the log on all cluster peers: 06-27-2019 07:43:11.914 +0200 ERROR S3Client - command=get transactionId=0x4053369110 rTxnId=0x4051be42d0 status=comple ted success=N localPath="D:\Program Files\Splunk\var\lib\splunk\db\db_1561365505_1561358169_598_A3573547-8422-44 29-B22D-4867A0A1B8E8.tmp" offset=0 error="can not open file" reason="Access is denied." 06-27-2019 07:43:11.915 +0200 ERROR RetryableClientTransaction - transactionDone(): groupId=0x4043b50ef0 rTxnId=0x4051b e42d0 transactionId=0x4053369110 success=N HTTP-statusCode=502 HTTP-statusDescription="network error" retries=429496729 5 retry=N no_retry_reason="transaction group had fatal error" remainingTxns=0 S3 bucket is populated with files and retrieving also works - it's just amount of errors is insane We're running EC2 instances, is there a way we can find why are we getting Bad Gateway errors in Splunk and how to solve them? Thx, Serge. ... View more