remove reliance on ami_launch_index for identifying bootstrapping leader
use simple "leader election" (term used extremely lightly) to identify first server based off ASGs instance id (alphanumeric). anything after first asg scale event is handled by querying the apiserver health from the load balancer with /dev/tcp
Change server userdata:
ami_launch_indexfor identifying bootstrapping leader/dev/tcp