Hi Sree, Are Temporary Credentials automatically shipped with AWS EC2 instances when delegated to the role? If yes, you should be able to just configure the properties so that the Kinesis consumer automatically fetches credentials from the AWS instance. To do that, simply do not provide the Access Key and Secret Key explicitly in the properties, and it will use the above default behaviour.
Apparently, the Kinesis connector docs [1] do not educate this preferred default behavior well enough. I’ll file a JIRA to improve that. Cheers, Gordon [1] https://ci.apache.org/projects/flink/flink-docs-release-1.5/dev/connectors/kinesis.html On 12 January 2018 at 7:25:58 AM, sreenath kodedala (veda...@me.com) wrote: > > Hi, > > According to my understanding, Kinesis Connector requires Access Key and > Secret Key to connect. > > Is it possible or any work around to use Temporary Credentials from AWS to > use in Kinesis Connector? > We have scenario where we are trying to access cross-account Stream and we > are assuming the role. So, in this scenario we get temporary credentials with > a token which will expire every hour. > > Thank you > -Sree
