Adding a High-Speed Transfer Server account to Connect

IBM Aspera High-Speed Transfer Server (HSTS) is the foundation under Connect transfers with Faspex and Shares, and under Connect transfers with AoC if your AoC uses an on-premises (tethered) transfer node. Therefore, in any of these cases, the configuration of your HSTS is fundamental to your Connect implementation.

Mostly, your HSTS does not need special configuration to work with Connect. You configure your HSTS for use with Connect in the same way as you would for use with Aspera on Cloud, Aspera Faspex, or Aspera Shares.

Setting Group Ownership

Sometimes, you might want to control the permissions on files that are uploaded to a transfer server. To do this, you can set the SGID bit on the directory on the transfer server into which files are transferred.

The following steps set the SGID bit on a directory named limited. When the steps are complete, transfers to the limited directory has group ownership rather than user ownership.

Note: The change in ownership applies to Connect transfers to this directory, and to files created in this directory on the transfer server itself, but does not apply to transfers ran through sync actions.

Set the transfer server to ignore group ownership.

asconfigurator -x "set_node_data;group_ownership,-"

Change the group associated with the limited directory to mygroup. The group that is named mygroup is not the user xfer's primary group.
```
chgrp -R mygroup limited/
```
Set the SGID bit for the destination directory limited.
```
chmod -R ug=rwx limited/
chmod -R g+s limited/
```
Verify your changes.
```
ls -la limited/
drwxrwsr-x 1 root mygroup 1234 Apr 23 10:42 . 
```
Your output might vary, but verify that the s is present in the group's permissions.