Symptoms

You see a log message similar to the following:

WARN, Instance: [i‑xxxxxxxxxxxxxxxxx] has been detected as stopped.

Cause

Although AWS allows instances to be stopped, Elastigroup does not support the Stop action. When an instance is stopped outside of Elastigroup, the group cannot correctly track or manage its state, which results in a synchronization issue.

Solution

1. Restart the instance in AWS

   In the AWS console, start the stopped instance.
   
   

2. Allow Elastigroup to resync

   Once the instance is running again, Elastigroup automatically synchronizes the instance state.
   
   

3. Use pause and resume going forward

   To manage instance lifecycle safely, use Pause and Resume actions in the Flexera console instead of stopping instances in AWS.