S3 Analytics Export Job Fails with 403 Access Denied Despite Correct IAM Policy

General Discussion
1

Having some issues getting my configuration to work… I am attempting to automate a daily analytics export to S3 using a Python script that leverages the Genesys Cloud Reporting API v2 and boto3. The objective is to query historical interaction data and push the resulting CSV directly to a bucket in us-west-2.

  1. I obtain a bearer token using client credentials via genesyscloud.platform.login_client_credentials.
  2. I construct the OData query body with specific metrics and date ranges, targeting /api/v2/analytics/reporting/query.
  3. I initiate the export job and poll for completion status.
  4. Upon completion, I use boto3.client('s3').put_object to upload the file URL content to my designated bucket.

The script successfully retrieves the data file URL from Genesys, but the final upload step fails. The HTTP response from AWS returns a 403 Forbidden error with the message Access Denied. I have verified that the IAM user associated with my boto3 credentials has the s3:PutObject permission on the target bucket. The code snippet for the upload is standard:

s3_client.put_object(Bucket='my-analytics-bucket', Key='export.csv', Body=content)

Is there a specific header or content-type requirement when transferring data from the Genesys reporting endpoint to S3 that I am missing? The file content appears valid when saved locally, but the pipeline breaks during the S3 put operation.