You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For components which are controlled by an ASG(Author-Dispatcher, Publish-Dispatcher, Publish Chaos-Monkey & Orchestrator) we are checking if the provisioning was successful or not and are updating the ec2 tag ComponentInitStatus accordingly.
Our readiness check, in inspec-aem-aws, used to rely on the ec2 instance IDs for determining the stack healthiness. This is not the case anymore which means if one of these components author-dispatcher, publish-dispatcher or publish cycles during stack creation the readiness check will wait until the ASG/ELB resource is healthy.
These recently added new enhancements allows us to think about of new features like an auto termination feature for these instances if the provisioning failed. In some cases an instance may fail provisioning but the ELB still sees these instances as healthy, since the ELB is just checking a web endpoint in AEM.
The text was updated successfully, but these errors were encountered:
mbloch1986
changed the title
Terminate instance if provisoining failed
auto terminate failed instances
Oct 18, 2019
For components which are controlled by an ASG(Author-Dispatcher, Publish-Dispatcher, Publish Chaos-Monkey & Orchestrator) we are checking if the provisioning was successful or not and are updating the ec2 tag
ComponentInitStatus
accordingly.Our readiness check, in
inspec-aem-aws
, used to rely on the ec2 instance IDs for determining the stack healthiness. This is not the case anymore which means if one of these componentsauthor-dispatcher, publish-dispatcher or publish
cycles during stack creation the readiness check will wait until the ASG/ELB resource is healthy.These recently added new enhancements allows us to think about of new features like an auto termination feature for these instances if the provisioning failed. In some cases an instance may fail provisioning but the ELB still sees these instances as healthy, since the ELB is just checking a web endpoint in AEM.
The text was updated successfully, but these errors were encountered: