However putting a record on the stream :
yields:
➜ ~ cat ~/.aws/credentials [default] aws_access_key_id = x aws_secret_access_key = x region = us-east-1 |
Hi Avi, thanks for reaching out to the Flink community. I haven't worked with the KinesisConsumer. Unfortenately, I cannot judge whether there's something missing in your setup. But first of all: Could you confirm that the key itself is valid? Did you try to use it in other cases? Best, Matthias On Thu, Dec 10, 2020 at 12:48 PM Avi Levi <[hidden email]> wrote:
|
Hi, Thanks for your reply, The problem is actually with the FlinkKinesisProducer and not the consumer ( i did consume from the stream successfully ). the keys are valid On Thu, Dec 10, 2020 at 6:53 PM Matthias Pohl <[hidden email]> wrote:
|
True, I got this wrong. Do you have any reason to assume that it's a Flink issue? The configuration looks correct (relying on the Flink docs [1] here). Have you considered asking in the AWS community for help? Best, Matthias On Thu, Dec 10, 2020 at 6:31 PM Avi Levi <[hidden email]> wrote:
|
Hi, it seems that the issue is with mfa involved . I think that this is a flink issue because when sending commands (e.g put record etc') from the cli (while mfa is activated of course), it works fine (meaning credentials and security token works fine). update: after disabling the mfa the FlinkKinesisConsumer/Producer works fine, which also kind of makes me think that this is a Flink issue. Best Avi On Fri, Dec 11, 2020 at 2:03 PM Matthias Pohl <[hidden email]> wrote:
|
Free forum by Nabble | Edit this page |