Metadata mismatch in WEM bulk export for legal discovery

403 Forbidden

What is the correct way to handle IAM policy restrictions when the bulk export job pushes data to our S3 bucket for legal hold? The job completes, but the manifest.json lacks the case_id custom attribute required for chain of custody. We use the EU-West-1 environment. Is this a limitation of the POST /api/v2/analytics/conversations/details/query endpoint, or do we need to modify the S3 data action configuration?