AWS mediapackage documentation change
Summary
Removed real-world examples of encryption implementations and added PlayReady documentation reference
Security assessment
Added link to Microsoft PlayReady documentation improves security guidance for DRM implementation. Removed examples reduced implementation details but did not remove security requirements. The change enhances security documentation by providing authoritative external references.
Diff
diff --git a/mediapackage/latest/userguide/mss-encryption.md b/mediapackage/latest/userguide/mss-encryption.md index a2e87af61..5ea710215 100644 --- a//mediapackage/latest/userguide/mss-encryption.md +++ b//mediapackage/latest/userguide/mss-encryption.md @@ -51,17 +50,0 @@ To encrypt your MSS content: -###### Example Real-world example: Multi-region content protection setup - -A global media company needed to encrypt their MSS content for delivery to corporate clients with legacy Microsoft infrastructure. They implemented the following solution: - - * **Encryption configuration** : They set up CENC encryption with PlayReady DRM on all MSS endpoints - - * **Key provider integration** : They integrated with a third-party SPEKE key provider that supported multi-region key distribution - - * **License server setup** : They configured regional PlayReady license servers to minimize latency for global viewers - - * **Fallback strategy** : They implemented a license server failover mechanism to ensure high availability - - - - -This approach allowed them to securely deliver content to corporate environments across multiple regions while maintaining a consistent user experience. The company reported a 40% reduction in unauthorized content access after implementing this solution. - @@ -83,17 +65,0 @@ For more information about configuring SPEKE with MediaPackage, see [Content enc -###### Example Real-world example: Premium sports content protection - -A sports streaming service needed to protect their premium content from unauthorized access while ensuring compatibility with legacy devices. They implemented the following solution: - - * **Content protection strategy** : They used PlayReady DRM with CENC encryption for their MSS streams to protect premium sports content - - * **Implementation approach** : They configured a SPEKE key provider to generate and manage encryption keys - - * **Security approach** : They implemented additional security measures at the application level since MSS does not support key rotation - - * **Testing strategy** : They verified playback on Xbox 360 consoles and legacy smart TVs using the Microsoft PlayReady Test Player - - - - -This approach allowed them to securely deliver premium sports content to legacy devices while maintaining strong content protection. The service reported a 99.8% successful playback rate across their legacy device audience. - @@ -106 +72 @@ When setting up a key server for MSS content, ensure that: - * The UUIDs are properly configured. For more information, see [Microsoft's PSSH box documentation](https://docs.microsoft.com/en-us/playready/overview/pssh-box-unified-streaming-and-documentation-why-pssh_over_html). + * The UUIDs are properly configured @@ -112,0 +79,2 @@ When setting up a key server for MSS content, ensure that: +For more information about requirements for using PlayReady with MSS, see [Microsoft PlayReady documentation](https://docs.microsoft.com/en-us/playready/packaging/mp4-based-formats-supported-by-playready-clients ). + @@ -143,25 +110,0 @@ For comprehensive testing procedures and compatible players for MSS content, see -###### Example Real-world example: Pre-launch encryption testing - -A video-on-demand service preparing to launch a library of premium content on legacy devices implemented the following testing strategy: - - * **Testing environment** : They created a staging environment with identical encryption settings to production - - * **Device testing matrix** : They tested encrypted MSS playback on 12 different device models representing their target audience - - * **Validation process** : For each device, they verified: - - * Successful license acquisition - - * Proper decryption of content - - * Smooth playback without buffering - - * License persistence across sessions - - * **Issue resolution** : They discovered and fixed a license delivery issue affecting certain smart TV models before launch - - - - -This comprehensive testing approach helped them achieve a successful launch with over 98% playback success rate across their supported legacy device ecosystem. -