log parser fails when blocked ip file doesn't exist about aws-waf-security-automations HOT 5 CLOSED

Hi,

We need to change this error message to just a info log. If the file does not exist, the solution should create a new one. Have you got a new file created?

from aws-waf-security-automations.

Hello,

Just like @dpmallinger, I had the same error and no file was created. I had to create manually an empty file in s3.
The error was then gone and the file contained a valid json. But no IPs are blocked.

from aws-waf-security-automations.

Hello,

I had the same experience as @gxof. I had to create the file manually with
{
"block": {}
}
to get the code to run.

from aws-waf-security-automations.

Got it. It's not the expected behavior.
Will change this error message to log but also check why the file was not created accordingly.

from aws-waf-security-automations.

We've just pushed a new version that fixes this. Added the following error handler for this case:

https://github.com/awslabs/aws-waf-security-automations/blob/c7b25b4f9005469f1606e8da19c9704268f0697a/source/log-parser/log-parser.py#L155

Many thanks

from aws-waf-security-automations.