it was a permissions issue. Too bad aws doesn’t tell that permissions aren’t met, and silently blocks accessing logs