Amazon Neptune now supports Auto Scaling for Read Replicas
You can now use Amazon Neptune Auto Scaling to automatically add or remove Read Replicas in response to changes in performance metrics you specify. Neptune Read Replicas share the same underlying volume as the primary instance and are well suited for read scaling. With Neptune Auto Scaling, you can specify a desired value for CloudWatch (CW) metrics for your Replicas such as average CPU utilization. Neptune Auto Scaling adjusts the number of Read Replicas to keep the CW metric closest to the value you specify.
You can now use Amazon Neptune Auto Scaling to automatically add or remove Read Replicas in response to changes in performance metrics you specify. Neptune Read Replicas share the same underlying volume as the primary instance and are well suited for read scaling. With Neptune Auto Scaling, you can specify a desired value for CloudWatch (CW) metrics for your Replicas such as average CPU utilization. Neptune Auto Scaling adjusts the number of Read Replicas to keep the CW metric closest to the value you specify.
For example, an increase in traffic could cause the average CPU utilization of your Replicas to go up and beyond your specified value. New Read Replicas are automatically added by Neptune Auto Scaling to support this increased traffic. Similarly, when CPU utilization goes below your set value, Read Replicas are terminated so that you don't pay for unused database instances.
Neptune Auto Scaling works with Amazon CloudWatch to continuously monitor performance metrics of your Read Replicas. You can create an Neptune Auto Scaling policy for any of your existing or new Neptune clusters. To get started, download the latest CLI or SDKs to create Neptune Auto Scaling policies programmatically or refer our documentation for more information. There is no additional cost to use Neptune Auto Scaling beyond what you already pay for Neptune and CloudWatch alarms.