BRIDGE-1943: workaround to ignore 4xx status codes
BRIDGE-1943: workaround to ignore 4xx status codes

AWS currently does not provide a way to ignore 4xx errors from enhanced
health monitoring metrics[1].  This is a workaround from stackoverflow[2]
that will make AWS ignore all 4xx errors.

This means that EB will never degrade the environment health due to
4xx errors because it just won't know that they're occurring. This also
means that the "Health" page in the EB environment will always display
0 for the 4xx response code count.

[1] https://forums.aws.amazon.com/thread.jspa?messageID=716284
[2] https://stackoverflow.com/questions/36398456/elastic-beanstalk-disable-health-state-change-based-on-4xx-responses

Sage-Bionetworks/BridgePF,alxdarksage/BridgePF,Sage-Bionetworks/BridgePF,DwayneJengSage/BridgePF,DwayneJengSage/BridgePF,DwayneJengSage/BridgePF,Sage-Bionetworks/BridgePF,alxdarksage/BridgePF,alxdarksage/BridgePF