While IAM roles are preferable, we're seeing a lot of cases where we need to pass AWS credentials when creating the KinesisReceiver.
- Make sure we don't log the credentials anywhere
- Maintain compatibility with existing KinesisReceiver-based code.
- is related to
SPARK-3640 KinesisUtils should accept a credentials object instead of forcing DefaultCredentialsProvider
SPARK-6599 Improve usability and reliability of Kinesis stream
- links to