S3 Data Ingest documentation should be updated to reflect using IAM roles instead of AWS Keys

Description

In later EMR environments the 400 error below is experienced and can be resolved by switching to using IAM roles instead of AWS keys in the core-site.xml. The suggestion was given by AWS support and proved to alleviate the problem. They didn’t offer much in the way of explaining why the configured credentials was causing an issue, but switching to roles did solve the problem.

Environment

None

Assignee

Tim Harsch

Reporter

Tim Harsch

Labels

Reviewer

None

Story point estimate

None

Components

Priority

Medium
Configure