Closed kamaroyl closed 4 years ago
Benthos Version: 3.18.0 calling benthos -c path_to_my_yaml returns:
benthos -c path_to_my_yaml
"Failed to connect to kinesis_balanced: Failed to start Checkpointer: SerializationError: failed to unmarshal response error\n\tstatus code: 403, request id: fe7b59d5-d0c4-a717-a91e-d159f61c25ac\ncaused by: UnmarshalError: failed decoding error message\n\t00000000 3c 49 6e 76 61 6c 69 64 53 69 67 6e 61 74 75 72 |<InvalidSignatur|\n00000010 65 45 78 63 65 70 74 69 6f 6e 3e 0a 20 20 3c 4d |eException>. <M|\n00000020 65 73 73 61 67 65 3e 43 72 65 64 65 6e 74 69 61 |essage>Credentia|\n00000030 6c 20 73 68 6f 75 6c 64 20 62 65 20 73 63 6f 70 |l should be scop|\n00000040 65 64 20 74 6f 20 63 6f 72 72 65 63 74 20 73 65 |ed to correct se|\n00000050 72 76 69 63 65 3a 20 27 6b 69 6e 65 73 69 73 27 |rvice: 'kinesis'|\n00000060 2e 20 3c 2f 4d 65 73 73 61 67 65 3e 0a 3c 2f 49 |. </Message>.</I|\n00000070 6e 76 61 6c 69 64 53 69 67 6e 61 74 75 72 65 45 |nvalidSignatureE|\n00000080 78 63 65 70 74 69 6f 6e 3e 0a |xception>.|\n\ncaused by: invalid character '<' looking for beginning of value"}
after a few minutes. This seems to be indicative of underlying aws library being used with the wrong scoping of the credentials (https://docs.aws.amazon.com/general/latest/gr/signature-v4-troubleshooting.html)
Config: balanced_kinesis_config_yaml.txt
Benthos Version: 3.18.0 calling
benthos -c path_to_my_yamlreturns:after a few minutes. This seems to be indicative of underlying aws library being used with the wrong scoping of the credentials (https://docs.aws.amazon.com/general/latest/gr/signature-v4-troubleshooting.html)
Config: balanced_kinesis_config_yaml.txt