IBM Aspera On Cloud

https://www.ibm.com/docs/en/aspera-on-cloud
Admin
IBM Aspera on Cloud is a cloud service designed for fast and reliable transfer of large files and...
Tokens:186,167
Snippets:1,083
Trust Score:10
Update:10 months ago
Show doc for...
Tokens:
Raw
### Register ALEE Entitlement

Source: https://www.ibm.com/docs/en/aspera-on-cloud/index_topic=node-configure-monitoring-metering-your-tethered

Registers the ALEE entitlement using the customer ID and entitlement ID obtained previously. This step finalizes the ALEE service setup with Aspera on Cloud.

```bash
sudo /opt/aspera/bin/alee-admin register customer_ID entitlement_ID
```

--------------------------------

### Mark Folder as Mount Point (Example) - Bash

Source: https://www.ibm.com/docs/en/aspera-on-cloud/index_topic=ayoahn-mark-remote-storage-attached-your-tethered-node-as-mount-points

This is an example of marking a folder as a mount point, specifically when the folder ID is 10. It demonstrates the usage of the PUT request with the 'mount_point' flag set to true.

```bash
curl -ki -u [access_key]:[secret] https://[host]:[port]/files/10 -XPUT -d’{"mount_point":true}'
```

--------------------------------

### Initialize Terraform Working Directory (Bash)

Source: https://www.ibm.com/docs/en/aspera-on-cloud/index_topic=storage-installing-file-preview

Initializes a Terraform working directory for deploying AWS resources. This command downloads necessary provider plugins. Dependencies: Terraform.

```bash
cd terraform-aws/previews
terraform init
```

--------------------------------

### S3 Bucket Resource ARN Example

Source: https://www.ibm.com/docs/en/aspera-on-cloud/index_topic=storage-creating-aws-iam-roles-transfer-service-nodes

This example shows how to specify the Resource object within an IAM policy statement when your S3 bucket is named 'ats-s3-policy'. This is a crucial part of defining the scope of access granted by the policy.

```json
"Resource": "arn:aws:s3:::ats-s3-policy"
```

--------------------------------

### Build Docker Image for Previews (Bash)

Source: https://www.ibm.com/docs/en/aspera-on-cloud/index_topic=storage-installing-file-preview

Builds the Docker image for the File Preview service. Allows selection of different video encoders (vp9, av1, x264, openh264). The image is tagged for ECR. Dependencies: Docker, ECR repository name.

```bash
cd previews && docker build --build-arg encoder=vp9 -t {account_id}.dkr.ecr.{region}.amazonaws.com/{repo_name}:previews .
```

--------------------------------

### Terraform Plan (Bash)

Source: https://www.ibm.com/docs/en/aspera-on-cloud/index_topic=storage-installing-file-preview

Generates an execution plan for Terraform, showing the changes that will be made to the AWS infrastructure. This allows for review before applying. Dependencies: Terraform, initialized working directory.

```bash
terraform plan
```

--------------------------------

### Stop and Start Aspera Node Service

Source: https://www.ibm.com/docs/en/aspera-on-cloud/index_topic=node-backing-up-restoring-tethered-database

Commands to stop and start the asperanoded service using systemctl. These are fundamental for service management and apply to most systemd-based Linux distributions.

```bash
# systemctl stop asperanoded

# systemctl start asperanoded
```

--------------------------------

### Build Docker Image for Previews Checker (Bash)

Source: https://www.ibm.com/docs/en/aspera-on-cloud/index_topic=storage-installing-file-preview

Builds the Docker image for the 'previews-checker' component, which identifies files needing previews. The image is tagged for ECR. Dependencies: Docker, ECR repository name.

```bash
cd ../previews-checker && docker build -t {account_id}.dkr.ecr.{region}.amazonaws.com/{repo_name}:checker .
```

--------------------------------

### AWS KMS Alias Management Configuration Example

Source: https://www.ibm.com/docs/en/aspera-on-cloud/index_topic=storage-attach-kms-encrypted-aws-bucket

An example of a configured AWS KMS alias management policy with specific region, account ID, and KMS key ID. This configuration allows Aspera on Cloud to utilize the specified KMS key for encryption and decryption tasks.

```json
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "Stmt1464034295000",
      "Effect": "Allow",
      "Action": [
        "kms:EnableKey",
        "kms:Encrypt",
        "kms:Decrypt",
        "kms:GenerateDataKey",
        "kms:GenerateDataKeyWithoutPlaintext",
        "kms:ReEncryptTo",
        "kms:ReEncryptFrom"
      ],
      "Resource": ["arn:aws:kms:us-east-1:239600258224:key/65a140e1-8c8f-4dd5-b2d7-d6cf05e15b46"
      ]
    }
  ]
}
```
Tokens:
Raw