Edge BYOC S3 upload fails with 403 despite valid IAM policy

Context:
We are migrating our recording storage to a customer-hosted S3 bucket using the Edge/BYOC feature. The environment is Genesys Cloud EU-West-1. The goal is to export WhatsApp transcript metadata and associated media for legal discovery requests. The IAM user attached to the integration has s3:PutObject and s3:GetObject permissions on the target bucket. Network connectivity between the Genesys Edge location and the S3 bucket endpoint is verified and open on port 443. The bulk export job is triggered via the Data Action API.

Question:
Does anyone know why the initial test upload succeeds, but subsequent bulk export jobs fail with a 403 Forbidden error specifically when writing the chain of custody JSON files? The voice recordings upload fine. The error response body indicates AccessDenied but only for the metadata objects. The timestamps in the logs suggest the request is reaching the S3 endpoint. Is there a specific header or content-type requirement for the metadata files that the Edge agent might be missing? The recording API works correctly for standard voice channels. We are using the latest Edge agent version deployed in the private VPC. Any insights on debugging this permission mismatch would be appreciated.