I received a response from AWS a short time ago regarding this issue. They are able to reproduce the problem and are currently testing a fix. I will send a follow up once we receive confirmation that the issue has been fixed.