WardtermSSH client
EN
Download

Wardterm documentation

Servers from the cloud

Bring the servers of DigitalOcean, Hetzner, Linode, Vultr, AWS, Azure, Google Cloud or Scaleway into Wardterm as a group that stays up to date.

Connect an account

  1. On Mac and iPad, choose the arrow next to New server. On iPhone, choose + in Servers, then From the cloud.
  2. Choose the provider: DigitalOcean, Hetzner Cloud, Linode, Vultr, AWS, Azure, Google Cloud or Scaleway.
  3. Paste a read-only access key, made as the sheet explains. The link in the sheet opens the right page of the provider.
  4. Choose Connect.

The app reads the servers of the account, then makes a group named after the provider, with one server for each machine: its name, its address and its system. If you have shared vaults, the app asks which vault the group goes in.

What each provider asks for

  • DigitalOcean: in API, Generate New Token, with Read Only, or Custom Scopes with droplet:read.
  • Hetzner Cloud: in the Hetzner Console, your project, then Security and API tokens: a token with the Read permission.
  • Linode: in Cloud Manager, your profile, then API Tokens and Create a Personal Access Token, with Linodes set to Read Only and everything else to No Access.
  • Vultr: in Manage Organization, a Service User with a policy that allows only compute.instance.List, and its API key. A personal API key also works: limit it to your IP addresses in Account, API, Access Control.
  • AWS: in IAM, a user with only the AmazonEC2ReadOnlyAccess policy. In its Security credentials, an access key: paste the Access key ID and the Secret access key.
  • Azure: an App registration with a client secret, and the Reader role for the app in the Access control (IAM) of your subscription. Paste the Tenant ID, the Client ID and the Client secret.
  • Google Cloud: in IAM and Service accounts, a service account with the Compute Viewer role. Under Keys, add a JSON key and paste the whole file.
  • Scaleway: in IAM, an application with a policy that gives it InstancesReadOnly. Generate an API key for it and paste its secret key.

Show more

  • Use private addresses, for servers you reach through a VPN or a jump server.
  • Default user, root unless you change it.
  • Only servers with tag, to bring in part of the account.
  • Regions on AWS: all enabled regions, or the ones you list.

Keep it up to date

  • The group updates when you open the list of servers, at most every 10 minutes, and when you choose Refresh in the menu of the group.
  • New machines are added. What changed in the account changes here too, except the fields you changed by hand in the app: those stay as you set them.
  • A machine that is gone from the account goes to the Trash, and comes back if it appears again.
  • The settings of the provider, in the menu of the group, change the key and the options.