Prevent Elastic Agent from Termination

[Jeremy]

I have an on-prem bamboo server and single elastic bamboo agent in AWS. There have been a few occasions where the communication between the server and agent are interrupted, which results in the elastic agent getting terminated. Deploying a new agent isn't too big of a deal, but there is a bit of configuration that we apply to the instance after it is deployed. Is it possible to increase the timeout between elastic agent and server to prevent the agent from getting terminated? Is there a better way to address the problem? The Automatic instance management feature is currently Disabled.

[jira guy]

Update your Elastic management to custom. You can then update Idle agent delay time as you wish. 

[Jeremy]

Thanks for the suggestion, I will give it a try. Is 10mins the default value used when Automatic instance management is Disabled? 

[jira guy]

10 is the default

[Jeremy]

Thanks for your help, jira guy!

While I'm waiting to see if the change worked, can you help me understand why the instance is being terminated to begin with? The config for Automatic Termination shows EC2 instances will not be automatically terminated. Under Automatic elastic instance management, it says EC2 instances must be manually created and terminated as needed. So why does mine disappear?