Skip to content
SHC Docs

An AWS node

This page has not been walked: no SHC test account exists on AWS. Its command lines are what the CLI takes; its output lines are left open.

One aws connection serves Route53 DNS, EBS volumes and, once built, the load balancer. EBS volumes are pinned to one availability zone, so the connection carries the zone it creates volumes in and a node reads that zone as its location.

Write the key pair on home01 as ~/aws.json.

{"access_key": "<access key id>", "secret_key": "<secret access key>"}
home01
$ chmod 600 ~/aws.json

Create one EC2 instance: Debian 13, in us-east-1a, named after the node, in a security group that allows the cluster ports between it and the learn nodes. Install SHC on it. Call the node aws01.

The join asks home01 for its token over ssh, so give root on aws01 the learn nodes’ names and a key home01 accepts, as the learn nodes have.

aws01
$ ssh home01 shc node token --fields token -o text | shc node join - --name aws01 --cloud aws --location us-east-1a
...
home01
$ shc node ls
...
$ shc connection connect aws --cred region=us-east-1 --cred availability_zone=us-east-1a --cred volume_type=gp3 --value-file ~/aws.json
...
$ shc connection show aws
...
$ shc install notes -s awsdb --where node=aws01 --storage aws
...
$ shc volume ls
...
$ shc volume snapshot pgdata -s awsdb
...
$ shc uninstall awsdb -y
...
$ shc volume ls
...
aws01
$ shc node leave
...
home01
$ shc node ls
...
$ shc connection rm aws --yes
...

Terminate the instance and delete the snapshot in the console.

This page leaves the cluster as the runtimes ladder left it: the learn nodes, with no cloud node and no connection.

Next: An Azure node.