We run the Scala Stream Collector and the Kinesis S3 sink in autoscaling groups to ensure availability.
The setup for the collectors, load balancers, autoscaling groups etc is pretty straightforward and we have that all working fine. What I’m not sure of is the best practice for starting up the collector or kinesis sink on the machine after it starts up.
We have an AMI with all our config that is used to spin up new instances, but over the years several different people have set up the AMIs and there is a bit of a hodgepodge of ways that the actual process is kicked off, how logging is handled, etc. Just curious if there is some documentation anywhere for a standard way to handle this.