Key considerations with Watermarking
Review the points here before adding the Watermarking functionality to your property.
|Akamai needs to deliver HLS media manifests.||Delivery of watermarked content follows a specific scheme:
|There's a footprint increase when watermarking is enabled||Watermarking generates two separate versions of a media file to support its variant A to B switch model. So, storage on your origin will be impacted.|
|Watermarking can't be applied in Multi-CDN environments||This feature won't work in a multi-CDN environment because its functionality is unique to the Akamai CDN. If a request was to be switched mid-stream to another CDN, it would need a version of watermarking that mirrors Akamai's.|
|Prefetching isn't recommended||Our current Prefetching implementation uses an origin-assist model that is not optimal with watermarking. As a result, AMD can't properly apply the Segmented Media Streaming - Prefetch behavior and the Watermarking behavior to a single request. Avoid including both behaviors in the same rule. Also, don't apply either behavior in the Default Rule, if the other exists in a subsequent rule in your property. This is because the Default Rule applies to all requests.|
|Media Services Live isn't supported||Watermarking is currently only supported for use with on
demand media. Your Origin Server
1 must be set to either "Your
Origin" or "NetStorage."
Note: If you're applying a Mixed Mode 2 use case for both Media Services Live and other Origin Servers, we recommend that you create a separate rule for your non-Media Services Live requests and include the Watermarking behavior in that rule. Do not include it in the Default Rule because it applies to all requests.
|AMD Failover doesn't work with Watermarking||Currently, AMD failover does not work if you also include Watermarking. This should be fixed with an upcoming release.|
|Range requests aren't supported||This can cause a range mismatch. Arbitrary range requests are a security violation when requesting a watermarked stream.|
1 Access to this documentation requires login with a Control Center account.