Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
Description
Right now, the Kinesis Consumer / Producer by default directly expects the access key id and secret access key to be given in the config properties.
This isn't a good practice for accessing AWS services, and usually Kinesis users would most likely be running their Flink application in AWS instances that have embedded credentials that can be access via the default credential provider chain. Therefore, it makes sense to change the default AWS_CREDENTIALS_PROVIDER to AUTO instead of BASIC.
To avoid breaking user code, we only use directly supplied AWS credentials if both access key and secret key is given through AWS_ACCESS_KEY and AWS_SECRET_KEY. Otherwise, the default credential provider chain is used.
Attachments
Issue Links
- links to