Overview
The Media Exchange on AWS solution provides publishers and subscribers a common method for directly and securely transferring media assets. It creates a shared object storage area in a separate, secured AWS account between publishers and subscribers. Publishers copy assets into a shared Amazon Simple Storage Service (Amazon S3) bucket and create permissions to allow subscribers to pull the content from the shared resource. Each publisher-subscriber transfer relationship has its own Amazon S3 bucket to share the assets. Publishers have write permissions to this bucket, a subscriber can only view assets under their assigned bucket and import assets that are shared with them. As a result, assets do not leave the Amazon S3 data plane and are securely tracked with receipt confirmations, helping to ensure asset quality and fidelity.
Benefits
Publishers and subscribers do not share credentials. Assets are encrypted at rest and in transit.
There are no per GB data egress and transfer costs within the same AWS Region and no servers to manage or licensing fees.
You can get up to 100GB/s in transfer speeds in the same Region because assets never leave the S3 data plane. In addition, S3 conducts asset integrity checks before, during, and after transfer.
All operations on assets are tracked via Amazon S3 server access logs. Publishers and subscribers receive automatic notifications.
Technical details
You can automatically deploy this architecture using the implementation guide and the accompanying AWS CloudFormation template.
Step 1
The AWS CloudFormation template deploys an Amazon S3 bucket. The publisher selects assets from the user-created Source S3 bucket in their account and copies them to the S3 bucket.
The subscriber copies assets from the shared S3 bucket to the user-created Destination S3 bucket in their account.
Step 2
An AWS Key Management Service (Amazon KMS) key to configure default encryption for the S3 bucket.
Step 3
An Amazon EventBridge bus to receive notifications from Amazon S3.
Step 4
Amazon Simple Notification Service (Amazon SNS) topics and Amazon Simple Queue Service (Amazon SQS) messages for subscriber and publisher notifications.
Step 5
A set of products in AWS Service Catalog to onboard publishers and subscribers, and to set up new transfer agreements.
Step 1
The AWS CloudFormation template deploys an Amazon S3 bucket. The publisher selects assets from the user-created Source S3 bucket in their account and copies them to the S3 bucket.
The subscriber copies assets from the shared S3 bucket to the user-created Destination S3 bucket in their account.
Step 2
An AWS Key Management Service (Amazon KMS) key to configure default encryption for the S3 bucket.
Step 3
An Amazon EventBridge bus to receive notifications from Amazon S3.
Step 4
Amazon Simple Notification Service (Amazon SNS) topics and Amazon Simple Queue Service (Amazon SQS) messages for subscriber and publisher notifications.
Step 5
A set of products in AWS Service Catalog to onboard publishers and subscribers, and to set up new transfer agreements.
- Publish Date