1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
1
I ran into the same issue today, seems like a bug with the AWS Console because I was able to create the rule through the CLI.
Here is the command:
aws iot create-topic-rule --rule-name <RULE_NAME> --topic-rule-payload file://iot.json
and the input file:
{
"sql": "<SQL_COMMAND>",
"description": "",
"actions": [
{
"kafka": {
"destinationArn": "arn:aws:iot:******************",
"topic": "<TOPIC>",
"clientProperties": {
"acks": "1",
"bootstrap.servers": "****************************",
"compression.type": "none",
"key.serializer": "org.apache.kafka.common.serialization.StringSerializer",
"sasl.mechanism": "SCRAM-SHA-512",
"sasl.scram.password": "************",
"sasl.scram.username": "*******************",
"security.protocol": "SASL_SSL",
"value.serializer": "org.apache.kafka.common.serialization.ByteBufferSerializer"
}
}
}
]
}
beantwortet vor 8 Monaten
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 3 Jahren
- AWS OFFICIALAktualisiert vor 3 Jahren
- AWS OFFICIALAktualisiert vor einem Jahr
Thank you for your answer! I had a feeling it was a bug in AWS Console, but being a noob here, I wasn't sure. I tried the CLI approach and that worked for me. kafka processing messages!
I'm not accepting this as the answer, because I believe the answer is for AWS to fix the Console.