Aquanode DocsGeneral console
When aq connect is off
What keeps working and what waits when the connector is not running on your machine.
Your key stays on your machine, so any action that must call your provider with
that key can only run while aq connect is running.
What keeps running
- Scheduled snapshots. A running box keeps capturing its Environment and Volume on schedule. Capture runs on the box itself, not through your provider key.
- Stats. Utilization sampling from the box keeps reporting.
- The console. You can sign in, browse your boxes, Environments and Volume history, and read what is stored.
What does not run
- Create. A new box is not rented until the connector is online. Restoring a snapshot onto a new box is a create, so it waits too.
- Stop and terminate. The request waits for the connector, and the pod page shows "Stop is waiting for your connector". Your provider keeps billing the account until it runs.
- Auto-pause. Auto-pause is off unless you turn it on when you create the pod.
When it is on, the idle stop is sent through the connector, so an idle box keeps
running and billing while
aq connectis off.
Stop is not instant
A stop or terminate you request while the connector is off is queued, not done.
Start aq connect to run it. Some providers also keep billing a stopped box, so
check your provider's own page after you stop.
If the connector stops answering during a create, Aquanode does not retry. A box may exist on your provider account, so check its instance list.