- Amazon's data centers are in compliance with several recognized security standards, including a "demonstrated alignment with the MPAA best practices and AWS infrastructure is compliant with all applicable MPAA infrastructure controls". (https://aws.amazon.com/compliance/)
- Amazon S3 supports "at rest" encryption of files, which provides additional security. (http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingServerSideEncryption.html)
- Amazon can provide higher durability and availability guarantees than our present data center. Amazon S3 is designed for 99.999999999% durability and 99.99% availability of files over a given year... and it can withstand the loss of two of its facilities.
- By using Amazon EC2 for transcoding, we will be able to elastically scale the number of available transcoding servers to keep up with demand. This will make transcoded media available faster than we can currently with two dedicated transcoding servers.
Please feel free to get in touch through support if you have any questions or concerns!
Phase 1 (June 2013)
- Move existing uploaded files from our data center to Amazon S3, starting with the oldest files first.
- Once we've moved the bulk of the existing files, we'll start transferring all newly uploaded files to Amazon S3 as quickly as possible after they are uploaded.
- Transcoding will still happen in our data center.
- New sites and any existing sites that we detect do not upload via the API will be configured to upload directly to Amazon S3.
- Remaining sites will continue to use the file shipping process established in Phase 1.
- Transcoding will move to Amazon EC2.
- All remaining sites will be configured to upload directly to Amazon S3.