Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

auto terminate failed instances #343

Open
mbloch1986 opened this issue Oct 18, 2019 · 0 comments
Open

auto terminate failed instances #343

mbloch1986 opened this issue Oct 18, 2019 · 0 comments

Comments

@mbloch1986
Copy link
Contributor

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.

@mbloch1986 mbloch1986 changed the title Terminate instance if provisoining failed auto terminate failed instances Oct 18, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant