Ask a Question
Back to All

Eage Bank is broken on community version

Hi - I've gone through several attempts to start EagleBank, but every time some machines are not created at all (are hung in state in the console) - aws clearly shows the VM is not created. Some are - but are still stuck in state even after manually rebooting them in aws. I guess for some cases the provisioning dependencies will be broken.

Could SnapLabs staff get a look at this, or at least advise on how to debug it.
My CloudFormation stack has been created a while ago - does it make sense to re-create it?