In my case I was proxying a call with all the headers, which container "host" and it resulted in 403. Removing all the unplanned headers solved the issue. AWS is so unintuitive in those API GW errors.