1 Answer
- Newest
- Most votes
- Most comments
1
This error can show up for several reasons:
- The bucket doesn't exist anymore
- The IAM role that the cluster is assuming does not have permissions to the bucket. For this please review the EMR documentation for IAM service roles: https://docs.aws.amazon.com/emr/latest/ManagementGuide/emr-iam-roles.html
- There could be a routing issue. Would need to know if you are trying to get to S3 via an access point, or end point. Either way, here is a blog post that goes into detail on both: https://aws.amazon.com/blogs/storage/managing-amazon-s3-access-with-vpc-endpoints-and-s3-access-points/
Relevant content
- Accepted Answerasked 2 years ago
- asked 2 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 9 days ago
- AWS OFFICIALUpdated 10 months ago