Creating Access Keys in the Cluster Manager

Aspera clients connect to cluster nodes using access keys, which provide a more secure and flexible alternative to authenticating with the Aspera node user or system user. For more information about access keys, see Access Key Overview.
  1. On the ATC Manager Clusters page, click the cluster you want to configure. In the cluster details, click the Access Keys tab.
  2. Click New to create a new access key.
  3. Name your access key.
    Naming your keys with a descriptive name can help you keep track if you create multiple access keys for the same storage.
  4. In the License section, enter the Aspera Customer ID and Aspera Entitlement ID into their respective fields.
  5. In the Storage section, select your storage type (IBM S3 or IBM Swift).
  6. Enter the cloud storage credentials and options.
    To configure IBM S3 cloud storage, enter the following information:
    1. Bucket: Enter the name of your S3 bucket.
    2. Path: Enter the path of the directory in the bucket to which you want to grant access.
      The path must not be empty. Enter "/" if you want to access the entire bucket.
    3. Endpoint: Enter the cloud storage endpoint.
      The default is s3-api.us-geo.objectstorage.service.networklayer.com.
    4. Enter your Access Key ID and Secret Access Key.
    To configure IBM Swift cloud storage, enter the following information, all of which can be retrieved from the SoftLayer portal. Log in to the portal and go to Storage > Object Storage. Select your account name and the region of your cluster. Click View Credentials.
    1. Endpoint: Enter your Public Authentication Endpoint.
    2. Container: Enter the container name.
    3. Path: Enter the path for the directory of the bucket to which you want to grant access.
      The path must not be empty. Enter "/" if you want to access the entire bucket.
    4. Username: Enter the account username.
    5. API Key: Enter the API key.
  7. Click Create.

The new access key is added to the list of access keys with the state PENDING. If the cluster nodes can access the specified storage location successfully, the state turns to SYNCHRONIZED. Otherwise, the state turns to ERROR and the corresponding error message is displayed.