You have an application running on Amazon EC2 in an Auto Scaling group. Instances are being bootstrapped dynamically,
and the bootstrapping takes over 15 minutes to complete. You find that instances are reported by Auto Scaling as being
In Service before bootstrapping has completed. You are receiving application alarms related to new instances before
they have completed bootstrapping, which is causing confusion. You find the cause: your application monitoring tool is
polling the Auto Scaling Service API for instances that are In Service, and creating alarms for new previously unknown
instances. Which of the following will ensure that new instances are not added to your application monitoring tool before
bootstrapping is completed?
Create an Auto Scaling group lifecycle hook to hold the instance in a pending: wait state until your bootstrapping is complete.
Once bootstrapping is complete, notify Auto Scaling to complete the lifecycle hook and move the instance into a pending: complete
Use the default Amazon CloudWatch application metrics to monitor your application’s health.
Configure an Amazon SNS topic to send these CloudWatch alarms to the correct recipients.
Tag all instances on launch to identify that they are in a pending state.
Change your application monitoring tool to look for this tag before adding new instances, and the use the Amazon API to set the
instance state to ‘pending’ until bootstrapping is complete.
Increase the desired number of instances in your Auto Scaling group configuration to reduce the time it takes to bootstrap future