This broke unexpectedly in July. Hot fix came about a month later. Upgrading to v4 completely broke backwards compatibility.

Wasn't expecting that from an aws created lambda solution