Delivery methods

Overview

Roku supports two primary content delivery methods:

1. Aspera: via Aspera Shares (desktop app) or Aspera Enterprise/P2P (SSH-key authenticated)
2. Direct S3 connection: cross-account S3-to-S3 transfer

Roku will confirm your delivery method during onboarding. Other transfer methods, including physical media, may be considered case by case and must be approved in advance. If physical delivery is approved, any media or hard drives supplied to Roku will not be returned.

Aspera

Roku accepts content via Aspera, configured as either:

• Aspera Shares (using the IBM Aspera for Desktop application), or
• Aspera Enterprise/P2P (using Aspera Client or Console)

Aspera Shares suits occasional or smaller transfers. Aspera Enterprise/P2P uses SSH keys and is typically used for larger or more frequent automated transfers. Roku will confirm which option applies during onboarding.

Aspera Shares Delivery

Provide the names and email addresses of the people who will deliver content to Roku Channel.

• Roku's Aspera Shares URL: https://aspera.sr.roku.com
• Required application: IBM Aspera for Desktop. Installation is required to upload content via Aspera Shares.

Invitation emails: Aspera Shares invitations come from Roku's server. If yours has not arrived, check your spam or junk folder and move the message to your inbox before opening the link. Your organization's email filter or firewall may also block the invitation.

Aspera Enterprise/P2P/HSTS Delivery

Roku authenticates via RSA public/private key exchange. To complete configuration, provide a public RSA-SSH key.

• Steps to create SSH keys: Aspera's official documentation
• Roku will provide host and username information during onboarding.
• Required application: Aspera Client

Transfer Bandwidth

Roku applies a global bandwidth cap of 300 Mbps. Roku recommends verifying or updating your Aspera Client's global and user preferences to align with your preferred upload bandwidth.

Where you configure transfer speed depends on which client/connection type you're using:

Use the configuration option for your connection type.

Direct S3 Connection

Roku supports direct S3-to-S3 transfer for content delivery. The Roku delivery bucket for S3 direct connect uses a customer-managed KMS key. Because this is a cross-account transfer, a KMS key and policy granting the partner's account permission is required.

What Roku Needs From Partners

Provide the IAM role ARN that your transfer system assumes for multipart uploads or S3 copies. Roku adds that role to the KMS policy allow list.

Typical ARN format:

arn:aws:iam::<AWS_ACCOUNT>:role/<ROLE_NAME>

Required IAM policy for the partner's assumed role:

{
"Version": "2012-10-17",
"Statement": [
  {
    "Effect": "Allow",
    "Action": [
      "kms:\*",
      "s3:\*"
    ],
    "Resource": "\*"
  }
]
}

What Partners Need From Roku

1. Roku's production environment bucket name for direct ingest:

   Text

   ingest-direct1-886239521314

2. Partner-specific prefix within the bucket, supplied by Roku during onboarding, following this convention:

   Convention:

   Text

   ingest/<partner_name>/prod/

   Full bucket path example:

   Text

   ingest-direct1-886239521314/ingest/<partner_name>/prod/

Best Practices / Optimization

Roku's S3 bucket is located in the us-east-1 region. Cross-region transfers are expected to be slower. Transfers can be optimized via multipart upload/copy settings:

aws configure set default.s3.multipart_chunksize 128MB
aws configure set default.s3.max_concurrent_requests 30

Testing

To validate configuration, perform the following:

1. Test uploading a file to the Roku S3 bucket, into the designated partner prefix.
2. Test copying a file from the partner's S3 bucket to the Roku S3 bucket, into the designated partner prefix.

Glossary