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.
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?
G’day Bamboo customers, The wait is almost over! We are in the final stages of work on the first release of Bamboo Data Center, our self-managed enterprise offering of Bamboo. This Data Center offe...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events