- Newest
- Most votes
- Most comments
Resolved my issue. Had to add "transcribe.amazonaws.com" as a Trusted Entity (under "Trust relationships" tab in console Roles editor)
Hi jamalbernhard,
Make sure that you don't have policies on your source S3 bucket that would prevent other services like Amazon Transcribe from accessing it. Your testing that you can download your own file in your own S3 bucket only ensures that you have access. It doesn't confirm that other services can access.
I'm getting the same error
BadRequestException: The S3 URI that you provided can't be accessed. Make sure that you have read permission and try your request again
I set the bucket policy to allow public read, but still no luck
Have you been able to solve this?
Hello, do you have JobExecutionSettings set (queue)? This requires you to add another role that allows read and write access from input folder and output bucket. It may also require you to pass your role as well.
I'm experiencing the same issue (using the JobExecutionSettings deferred execution). I even tested after attaching the "AdministratorAccess" policy to both my API user (which performs the StartTranscriptionJob request), as well as the DataAccessRoleArn role, and still get the same error:
(The S3 URI that you provided can't be accessed. Make sure that you have read permission and try your request again.)
Works fine if I do not provide any JobExecutionSettings
Relevant content
- Accepted Answerasked 9 months ago
- asked 9 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 3 years ago