As per the eb_deployer inactive_settings configuration, Cool Down option will help to make the Auto Scaling Group setting changes for the DNS Caching.
inactive_settings:
reduce instance count to 0 to save cost
- namespace: aws:autoscaling:asg
option_name: MinSize
value: "0"
- namespace: aws:autoscaling:asg
option_name: MaxSize
value: "0"
# make sure cooldown is big enough to cope with DNS cache
- namespace: aws:autoscaling:asg
option_name: Cooldown
value: "900"
As per the above setting, we have configured as 900 sec(15 mins), So once the environment changed to inactive it should wait for 15 mins and instances should terminate.
But, Its not working as the above behaviour, with in 60 sec instances are getting terminated.
Can you tell us the exact behaviour of Cooldown as how it works ? or Am I missing anything ?
Hi,
As per the eb_deployer inactive_settings configuration, Cool Down option will help to make the Auto Scaling Group setting changes for the DNS Caching.
inactive_settings:
reduce instance count to 0 to save cost
As per the above setting, we have configured as 900 sec(15 mins), So once the environment changed to inactive it should wait for 15 mins and instances should terminate.
But, Its not working as the above behaviour, with in 60 sec instances are getting terminated.
Can you tell us the exact behaviour of Cooldown as how it works ? or Am I missing anything ?
Please suggest us to proceed further ?
Thanks Puneeth