This isn't really a Silverstripe issue as much as it's an environment one. I have a bunch of docker images which makes up a stateless version of Silverstripe I've been tinkering away with for awhile and everything works flawlessly on my local server.

Problem is as soon as I deploy it using Beanstalk I get 502 errors in the CMS. All the issues people seem to face with this issue are to do with nginx but I'm still using apache and its a pretty default/stock/standard LAMP stack.

All suspect log files are empty so not getting much help there either.

Has anyone done anything similar or have any tips to try and resolve this?

Solved: Had to do a little learning about how EB provisions EC2 servers, but basically nginx is in the mix there and just needed to increase the buffers on the actual server rather than each docker container. Just need to put together a .ebextensions config to make sure its applied each time the server load balances itself.