Hi there! Are you looking for the official Deno documentation? Try docs.deno.com for all your Deno learning needs.

SpekeKeyProviderCmaf

import type { SpekeKeyProviderCmaf } from "https://aws-api.deno.dev/v0.4/services/mediaconvert.ts?docs=full";

If your output group type is CMAF, use these settings when doing DRM encryption with a SPEKE-compliant key provider. If your output group type is HLS, DASH, or Microsoft Smooth, use the SpekeKeyProvider settings instead.

interface SpekeKeyProviderCmaf {
CertificateArn?: string | null;
DashSignaledSystemIds?: string[] | null;
HlsSignaledSystemIds?: string[] | null;
ResourceId?: string | null;
Url?: string | null;
}

§Properties

§
CertificateArn?: string | null
[src]

If you want your key provider to encrypt the content keys that it provides to MediaConvert, set up a certificate with a master key using AWS Certificate Manager. Specify the certificate's Amazon Resource Name (ARN) here.

§
DashSignaledSystemIds?: string[] | null
[src]

Specify the DRM system IDs that you want signaled in the DASH manifest that MediaConvert creates as part of this CMAF package. The DASH manifest can currently signal up to three system IDs. For more information, see https://dashif.org/identifiers/content_protection/.

§
HlsSignaledSystemIds?: string[] | null
[src]

Specify the DRM system ID that you want signaled in the HLS manifest that MediaConvert creates as part of this CMAF package. The HLS manifest can currently signal only one system ID. For more information, see https://dashif.org/identifiers/content_protection/.

§
ResourceId?: string | null
[src]

Specify the resource ID that your SPEKE-compliant key provider uses to identify this content.

§
Url?: string | null
[src]

Specify the URL to the key server that your SPEKE-compliant DRM key provider uses to provide keys for encrypting your content.