Remi Torracinta

Also got this issue using kibana: ``` PayloadTooLargeError: request entity too large at readStream (/usr/local/lib/node_modules/aws-es-kibana/node_modules/raw-body/index.js:155:17) at getRawBody (/usr/local/lib/node_modules/aws-es-kibana/node_modules/raw-body/index.js:108:12) at read (/usr/local/lib/node_modules/aws-es-kibana/node_modules/body-parser/lib/read.js:77:3) at rawParser (/usr/local/lib/node_modules/aws-es-kibana/node_modules/body-parser/lib/types/raw.js:81:5) at Layer.handle [as handle_request] (/usr/local/lib/node_modules/aws-es-kibana/node_modules/express/lib/router/layer.js:95:5) at...

Would really, really like to see this as well.

Sidenote: might not be bad build instructions; eg perhaps there's a bug in the initialization sequence, I assume it was recently modified by the addition of lag fix.

It looks like the numbers are currently projections from 2012??? Here are some reasonable bandwidth numbers: https://www.forrestthewoods.com/blog/memory-bandwidth-napkin-math/

Hello, just want to voice my support for a change in this direction, as it caused a bug for me today. It does make sense that a change may be...