The Kinesis Scaling Utility is designed to give you the ability to scale Amazon Kinesis Streams in the same way that you scale EC2 Auto Scaling groups – up or down by a count or as a percentage of the total fleet. You can also simply scale to an exact number of Shards. There is no requirement for you to manage the allocation of the keyspace to Shards when using this API, as it is done automatically.
Hey , i was exploring the autoscaling solution, and if i am correct we are currently using the cloud watch metrics and monitoring processing them and based on the analysis we are executing the tasks.
My doubt is why was the 'cloud watch Alarms' not used ? ( because as it is push based , we need not monitor the metrics by continues polling) ?
This solution was designed initially just to do the scaling action itself, and then autoscaling was added later. It is true that a single configuration could have been used to generate CloudWatch Alarms, but at the time there was no Lambda or SNS event sources, and so the architecture would have been far more complex to create and operate. A single daemon was able to implement the analysis and scaling in a single process and be hosted wherever a customer might want to.
Hey , i was exploring the autoscaling solution, and if i am correct we are currently using the cloud watch metrics and monitoring processing them and based on the analysis we are executing the tasks.