Binding AWS Kinesis - reuse client credentials

[soisyourface]

Describe the proposal

Currently when creating a Kinesis binding, at least locally, you must pass in the "static credentials" for the secret(key, id, session?). This is not an ideal experience.

Propose that when creating the KCL for Kinesis that we use the existing AWS client credentials instead of remaking them.

If a complete replacement isn't wanted, then perhaps only using the existing client credentials will be used if the static credentials aren't defined in the config.

[yaron2]

This is definitely a good idea and we're doing the same for a lot of our other AWS components - please see how we reuse and handle authentication in AWS SQS for example

[github-actions]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions.

[github-actions]

This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as pinned, good first issue, help wanted or triaged/resolved. Thank you for your contributions.