Connect your accounts
Store a provider key on your machine and run aq connect so the Aquanode console can act on your account.
You need aq v0.8.0 or later, installed and signed in. See
Install. Your team must be on the general console line with
the $20 seat active.
1. Add a key
aq accounts add simplepodaq asks for the fields that provider needs, without echoing them, and writes
them to accounts.json in your aq config directory with file mode 0600. On first
use it downloads the local executor, then checks the key against the provider and
prints the result with a key fingerprint. A key the provider rejects is not kept,
and aq prints the provider's error.
Check what is stored:
aq accounts lsSee aq accounts for every subcommand.
2. Start the connector
aq connectaq connect downloads the local executor if it is missing or out of date, then
starts it with your stored keys. It prints a line such as
connected as <team-id>: simplepod, massecompute (work), where (work) is a label
set with --label, then one line per request it handles. Press Ctrl-C to end the
session.
Leave it running while you want to create, stop or terminate boxes from the
console or from aq up.
What leaves your machine
- Requests to your provider, made from your machine with your key.
- The result of each request, sent to Aquanode so the console can show it.
- A key fingerprint, which is a truncated hash. It identifies which key is in use and cannot be reversed into the key.
The key itself is not sent to Aquanode, not placed in command arguments or environment variables, and not written to logs.
If the connector is offline
Create requests answer with a message asking you to run aq connect. aq up
prints that message and exits with code 11.