Aspera on Cloud Migration

Our team will create your account with the email you provide to the Aspera on Cloud Migration form. Once that is done, you will receive an email from noreply@beta.idprism-auth.amazon.dev containing your username and a temporary password. Please check your spam/junk folder if you do not see this email in your inbox.

⚠️ Note: All new users must be submitted through this form. Amazon Prime Video will manage individual e-mail additions to the Aspera on Cloud instance.

1. Go to https://contentdelivery.cupid-na.idprism-auth.amazon.com/
2. Enter your username(your registered email address) and the temporary passwordfrom the email.
3. You will be prompted to create a new password.
4. A verification code will be sent to your email. Enter the code to complete the password reset.

1. Go to https://pvslate.ibmaspera.com
2. Enter your username and the new password you created in Step 1.
3. A verification code will be sent to your email for multi-factor authentication. Enter the code to complete the login.
4. You now have access to Aspera on Cloud.

Important Notes

• Verification codes expire in 3 minutes. If your code expires, request a new one.
• If you are using a browser translation tool (e.g., Google Translate), please disable it during the login process as it may cause issues.
• Keep your credentials secure and do not share them with others.

To test if theset uphas been correctly configured, you will need to deliver assets through the Aspera on Cloud portal as you would Aspera Shares.

If using the Desktop UI, drop content into the GLOBAL folder.

Once you’ve delivered, review that the content has appeared in your Slate account.

If the ingestion is a success, the content has appeared in Slate. You can now use Aspera on Cloud to deliver via Desktop or CLI. For CLI instructions, see the “CLI Set Up Section Below”

If the ingestion is not a success, you may experience two things:

1. The asset does not appear in Slate. Please provide a screenshot of this instance to your Amazon contact or Contact Us.
2. The asset appears in Slate but does not process and remains in an “In Progress” state. Please provide a screenshot of this instance to your Amazon contact or Contact Us.
   

This section through installing the IBM Aspera CLI (ascli) locally. Since ascliis a Ruby gem, we first install a standalone Ruby environment using RVM (Ruby Version Manager) in the user’s home directory, then install ascli on top of it.

Part 1: Install RVM and Ruby

Step 1: Import GPG keys for RVM verification

Note: If gpg2 --keyserveris used instead, it may time out on dev desktops. Use the curl method above.

Step 2: Install RVM

Step 3: Load RVM into current shell

Step 4: Install Ruby 3.2.2

This downloads and compiles Ruby from source. It may take a few minutes.

Step 5: Set Ruby version

Part 2: Install ascli

Step 6: Install the aspera-cli gem

This install sascli and all its dependencies.

Step 7: Verify installation

Part 3: Configure ascli for Aspera on Cloud

Step 8: Run the configuration wizard

The wizard will prompt for:

1. URL-https://260528yhwmll.ibmaspera.com/
2. Username- Your full email address (e.g.user@amazon.com)
3. Key path- Press Enter to auto-generate a new RSA key pair

Step 9: Add public key to AoC profile
The wizard will display a public key. Copy it (including BEGIN/END lines) and:

1. Log into your AoC instance in a browser
2. Navigate to: User icon → Account Settings → Profile → Public Key
3. Paste the public key and save

Step 10: Verify connectivity

This should display your AoC user profile.