Skip to main content

Cloud Providers

Add hosts from AWS, Azure, Google Cloud, DigitalOcean, Hetzner and other clouds, and keep them in sync.

InfrastructureSourceAPIChangelog
  • Works with AWS EC2 and Lightsail, Azure, Google Cloud, DigitalOcean, Hetzner, Linode, Vultr, Oracle Cloud, Scaleway and UpCloud
  • Pick instances to import, or sync a whole account on a timer
  • Follows IP and name changes and can mark or remove hosts that are gone
  • Cloud keys are stored encrypted and never shown again
  • A dashboard card with each account and when it last synced

Cloud Providers turns the servers in your cloud accounts into Termix hosts. You can import the ones you pick, or sync a whole account on a timer.

Supported clouds​

AWS (EC2 and Lightsail), Microsoft Azure, Google Cloud, DigitalOcean, Hetzner Cloud, Linode (Akamai), Vultr, Oracle Cloud, Scaleway and UpCloud.

Add an account​

  1. Open the Cloud tab from the sidebar and press Add account.
  2. Pick the provider and give the account a name.
  3. Fill in the keys for that cloud (see below). Use read only keys.
  4. Choose how hosts are made, then save.
  5. Press Test keys on the account to check them.

Keys are stored encrypted on the server and are never shown again. To replace them, edit the account and fill in the fields.

Keys for each cloud​

CloudWhat you need
AWSAn IAM access key with ec2:DescribeInstances and ec2:DescribeRegions, or lightsail:GetInstances. Leave regions empty for all of them.
AzureA service principal (tenant ID, client ID, client secret) with the Reader role on the subscription, and the subscription ID.
Google CloudA service account JSON key with the Compute Viewer role.
DigitalOceanA personal access token with read access.
HetznerA read only API token from the project.
LinodeA personal access token with read only access to Linodes.
VultrAn API key.
Oracle CloudTenancy and user OCIDs, the API key fingerprint and private key, and the regions to scan.
ScalewayA secret key. Zones are optional.
UpCloudA user name and password for an API user.

Import servers​

Press Import servers on an account. Termix lists the servers it finds and which are already hosts. Tick the ones you want and press Import. Servers with no address are shown but cannot be chosen.

Sync​

Each account is either Manual or Automatic.

  • Manual accounts only change when you press Import servers or Sync now.
  • Automatic accounts sync on their own every few minutes. If a sync fails you get an alert.

A sync adds hosts for new servers and follows name and IP changes. Hosts are matched by the cloud's instance ID, so a host keeps its login, tags and settings when its IP changes. Sync never changes the SSH user, login, folder or port of a host after it is made. Tags that start with cloud: are managed by the plugin and your own tags are kept.

When a server is gone from the cloud, the account decides what happens to its host:

  • Keep the host. This is the default.
  • Tag the host as cloud:missing.
  • Delete the host.

Deleting an account does not delete its hosts.

On the dashboard​

Add the Cloud accounts card in the dashboard's edit mode. It lists each account with when it last synced, or the error when a sync failed, and a Sync now button for users who can manage accounts.

Logins​

New hosts use the account's default SSH user and default login. If the cloud knows the user (Azure and Lightsail do) that is used instead. To use another user for one server, add the tag termix-user:name to it in the cloud, or the label termix-user with the value name where the cloud uses key and value tags.

Hosts are made with the folder set on the account, or a folder named after the account.

Address​

Choose which address is used: public first then private, public only, or private only. Stopped servers often have no public address. The host keeps its last address until the server has one again.