Video Central

In this guide, you will compare two bulk file delivery methods for Prime Video. These methods are Amazon S3 Push Delivery (recommended) and IBM Aspera on Cloud. By the end, you will know which option fits your infrastructure, budget, and delivery needs.

Our Recommendation

Amazon S3 Push Delivery is the recommended method for delivering files to Prime Video. It offers faster speeds, lower costs, and tighter integration with the Prime Video ecosystem. If you use AWS or are open to adopting it, S3 is the clear choice.

Quick Tip

Partners using Amazon S3 Push Delivery report transfer speeds up to 3x faster than other bulk delivery methods. Choosing the recommended path means your team also spends less time managing deliveries and content can reach customers sooner.

How Each Method Works

Amazon S3 Push Delivery

You copy files directly from your own S3 bucket to a Prime Video S3 access point. Multiple transfer options are available. These include AWS CLI, SDKs, REST API, and AWS Lambda.

IBM Aspera

You upload files through the Aspera on Cloud web portal, Desktop Client, or CLI. Prime Video connects your account to its Aspera instance during onboarding.

Side-by-Side Comparison

Use the lists below to choose the method that fits your workflow.

Feature	Amazon S3 Push Delivery	IBM Aspera
Speed	Up to 3x faster than other bulk methods	Fast via FASP protocol, but slower than S3
Cost	Reduced AWS egress fees (NA and EMEA regions)	Free client tools under PV Slate license
Best For	Partners already using AWS infrastructure	Partners without AWS accounts
Availability	All partners	Managed contract partners only

Choosing the Right Path

Use the table below to compare the two delivery methods at a glance.

System diagram of an AWS DataSync transfer between two S3 accounts within the same region

Choose Amazon S3 Push Delivery if you…

Already have an AWS account with S3 storage
Want the fastest possible transfer speeds
Want to reduce delivery costs with lower egress fees
Need flexibility across multiple transfer tools (CLI, Lambda, SDK)
Want a streamlined, cloud-native workflow

Choose IBM Aspera if you…

Do not have an AWS account and prefer not to create one
Are a managed contract partner with existing Aspera workflows
Need a desktop drag-and-drop interface for non-technical users

Onboarding at a Glance

Follow these steps to get started with either delivery method.

Step	Amazon S3	IBM Aspera
1. Request access	Raise a Contact Us ticket or ask your POM/CAM	Submit the Aspera on Cloud form
2. Receive credentials	S3 access point ARN from your Amazon contact	Username and temporary password via email
3. Configure	Update IAM role policies with access point info	Log in to the web portal and set a new password
4. Test	Deliver a test file and confirm in Slate	Upload a test file and confirm in Slate

Know Before You Go

If you are starting fresh with no existing infrastructure preference, choose Amazon S3.

Amazon S3 supports automation through AWS Lambda, making it ideal for high-volume workflows.

IBM Aspera requires initial setup on the web portal before you can use the Desktop Client or CLI.

Both delivery methods require you to verify delivery by checking the Deliveries tab in Slate.

IP allowlisting is not required for either method.