Before you can access a server via ScaleFT, you’ll need to install the ScaleFT Server Tools on the server, and enroll your server into a project,
The primary method of enrolling a server into your ScaleFT project is to use an Enrollment Token.
In the ScaleFT Dashboard, browse to the desired project, then select “Server Enrollment Tokens”. Either use an existing token, or generate a new Enrollment Token with a description of what the token is used for, such as “First Production Buildout”, or “Testing ScaleFT”.
Once you have a token, ensure it exists on the server in question either via your configuration management system, or by just writing the token to a file yourself.
On Linux, the appropriate path is
On Windows, the appropriate path is
To validate that the server is enrolled, run
sft list-servers on
a client machine. You should see the enrolled server listed.
ScaleFT supports optionally associating an AWS account with a ScaleFT project.
The ScaleFT Server Agent uses AWS’s signed instance metadata to identify itself, and can automatically enroll into a project in your team.
This method is best when all your AWS servers will belong to only one project. You can use this method to enroll servers into that project instead of using an Enrollment Token. For bare metal or on-premise servers, or servers on non-AWS clouds, enroll servers using per-project Enrollment Tokens.
To associate an AWS account with a ScaleFT project:
From this point forward, when
sftd starts on a server that belongs to this AWS
account, if that server has not been previously enrolled in ScaleFT,
submit the server’s signed AWS metadata as proof of its identity, and enroll it
in your ScaleFT project.