Subject: [EXTERNAL] Re: Kinesis Producer - Support separate Cloudwatch
credentials
Hey,
The FlinkKinesisProducer is deprecated in favour of the KinesisSink. The new
sink does not rely on KPL, so this would not be a problem here. Is there a
reason you are using the FlinkKinesisProducer instead
Hey,
The FlinkKinesisProducer is deprecated in favour of the KinesisSink. The
new sink does not rely on KPL, so this would not be a problem here. Is
there a reason you are using the FlinkKinesisProducer instead of
KinesisSink?
Thanks for the deep dive, generally speaking I agree it would be
p
Hey Team,
Looking for some thoughts here:
* We have a Kinesis Producer that produces to a topic in another AWS account
* The producer allows for configurations to set credentials for that
account:
https://github.com/apache/flink-connector-aws/blob/main/flink-connector-aws/flink-connecto