I never found a solution, no.
We ended up using a different product, since we do not need the clustered version yet and I can't really justify spending any more company resources on this problem.
But I would still like to hear if anyone else finds a ...
I realize the complexity involved can be quite high. I have tried reducing that by running the stack creation on my own personal account instead, to see if it was different. Note that I am still provisioning in N. Virginia (us-east-1) and the remaini...
Thank you for the feedback.
I agree with your assessments, however, I'm unsure how to actually do anything about it. Node0 is created by the cloudfront template; I'm not sure how anything in our setup would inject itself into the container and start ...
Node0.txt (21.8 KB) Node1.txt (55.3 KB) Node2.txt (14.9 KB)
I have truncated it a bit for brevity. The "Failed to load" log lines in Node1.txt are on all three instances.
Private IPs:
Node0: 10.0.0.46
Node1: 10.0.1.222
Node2: 10.0.2.84
Public IPs:
No...
And the same here, except us-east-1 and default machines (r4.large x 3).
Product code: 1emg6yskh0jf81czgzfadiu9w, if that helps.
Settings I have changed are:
VersionStack nameSSH Key name (I could log into the machines with it, when disabling the rol...
