From 8dbd6ccd9fe1f04e63b79d7901a6f23549404b3e Mon Sep 17 00:00:00 2001 From: Dave Horton Date: Tue, 21 Apr 2020 10:18:50 -0400 Subject: [PATCH] minor --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index be2b148..7fc5837 100644 --- a/README.md +++ b/README.md @@ -12,7 +12,7 @@ There are two supported deployment configurations: #### autoscaling feature servers Both the devtest and production deployments create a single feature server in an autoscale group. -There is initially no scaling policy applied, but after running the terraform script and creating the infrastructure you can use the AWS console to apply a scaling policy (e.g. scale up when cpu > 60%) or a schedule (e.g. run 3 feature servers during the day and only one overnight) or modify the static configuration to alter the desired/min/max instances as you wish. +There is initially no scaling policy applied, but after running the terraform script and creating the infrastructure you can use the AWS console to apply a scaling policy (e.g. scale up when cpu > 60%) or a schedule (e.g. run 3 feature servers during the day and only one overnight) or modify the static configuration to set the desired/min/max instances as you wish. #### graceful scale-in The feature servers make use of AWS SNS lifecycle notifications to scale-in gracefully, allowing calls in progress to complete before shutting down. A maximum of 15 minutes is given for calls to complete; after that period any remaining calls will be torn down. This duration interval can be edited in the autoscale group configuration via the AWS console or cli if desired.