The Kinesis and Kinesis Firehose connectors should support the use of an IAM role with an external-id. This is a popular method of restricting access to AWS resources across accounts. In my case, I need to configure the Kinesis connector to read from Kafka and write to a Kinesis stream owned by another AWS account.
The connectors should take the following additional config values:
IAM Role ARN (optional)
IAM Role Session-Name (optional)
IAM Role External ID (optional)
If the Role ARN is supplied, then an STS AssumeRole request should be made; otherwise, use the default AWS authentication provider without an STS call.
The Kinesis and Kinesis Firehose connectors should support the use of an IAM role with an external-id. This is a popular method of restricting access to AWS resources across accounts. In my case, I need to configure the Kinesis connector to read from Kafka and write to a Kinesis stream owned by another AWS account.
The connectors should take the following additional config values:
If the Role ARN is supplied, then an STS AssumeRole request should be made; otherwise, use the default AWS authentication provider without an STS call.