After working with the AWS Support Team, we've identified a regression in the AWS ELB API that's creating the root cause of this error. We're currently waiting for a full diagnosis and fix from AWS. In the meantime, we will continue to disable operations to apps using legacy ELB endpoints. We'll also update this status page as we have any additional information.
Posted May 15, 2019 - 22:07 EDT
We are currently investigating an issue where headers are not being passed through correctly for some legacy ELB endpoints. We have disabled any operations to apps and endpoints using the using legacy ELB endpoint while we investigate.