Thanks bob. Turns out this only happens when I’m launching a single instance from the console (whether that’s manually, or via the marketplace launch path. When I launch a cluster from marketplace with cloudformation, all is good in the world.
But on the single instance:
[alces@ip-172-31-9-110(unconfigured) ~]$ alces configure node
Cluster name [mycluster]:
Cluster UUID [8c3d0c6a-3024-4b3f-b0f4-6a08ede7c369]:
Cluster secret [VevnKm9UAoguo0LDl1+k]:
Master node IP address :
Node role [master]:
Configuration of this node is now underway. When configuration is
complete you will receive a notice at the prompt. Additionally, the
prompt will be updated to include the name of your cluster.
Once configured, you can access the information required to
configure further nodes as part of your cluster by running the
"alces about identity" command.
[alces@ip-172-31-9-110(mycluster) ~]$ which aws
/usr/bin/which: no aws in (/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/home/alces/.local/bin:/home/alces/bin)
[alces@ip-172-31-9-110(mycluster) ~]$ module initlist
bash initialization file $HOME/.modules loads modules: