Module types

Data structures used by operation inputs/outputs.

Modules

• builders
  Builders
• error
  Error types that AWS Elemental MediaPackage v2 can respond with.

Structs

• ChannelGroupListConfiguration

  The configuration of the channel group.

• ChannelListConfiguration

  The configuration of the channel.

• CreateDashManifestConfiguration

  Create a DASH manifest configuration.

• CreateHlsManifestConfiguration

  Create an HTTP live streaming (HLS) manifest configuration.

• CreateLowLatencyHlsManifestConfiguration

  Create a low-latency HTTP live streaming (HLS) manifest configuration.

• DashUtcTiming

  Determines the type of UTC timing included in the DASH Media Presentation Description (MPD).

• Destination

  The configuration for the destination where the harvested content will be exported.

• Encryption

  The parameters for encrypting content.

• EncryptionContractConfiguration

  Configure one or more content encryption keys for your endpoints that use SPEKE Version 2.0. The encryption contract defines which content keys are used to encrypt the audio and video tracks in your stream. To configure the encryption contract, specify which audio and video encryption presets to use.

• EncryptionMethod

  The encryption type.

• FilterConfiguration

  Filter configuration includes settings for manifest filtering, start and end times, and time delay that apply to all of your egress requests for this manifest.

• ForceEndpointErrorConfiguration

  The failover settings for the endpoint.

• GetDashManifestConfiguration

  Retrieve the DASH manifest configuration.

• GetHlsManifestConfiguration

  Retrieve the HTTP live streaming (HLS) manifest configuration.

• GetLowLatencyHlsManifestConfiguration

  Retrieve the low-latency HTTP live streaming (HLS) manifest configuration.

• HarvestJob

  Represents a harvest job resource in MediaPackage v2, which is used to export content from an origin endpoint to an S3 bucket.

• HarvestedDashManifest

  Information about a harvested DASH manifest.

• HarvestedHlsManifest

  Information about a harvested HLS manifest.

• HarvestedLowLatencyHlsManifest

  Information about a harvested Low-Latency HLS manifest.

• HarvestedManifests

  A collection of harvested manifests of different types.

• HarvesterScheduleConfiguration

  Defines the schedule configuration for a harvest job.

• IngestEndpoint

  The ingest domain URL where the source stream should be sent.

• InputSwitchConfiguration

  The configuration for input switching based on the media quality confidence score (MQCS) as provided from AWS Elemental MediaLive.

• ListDashManifestConfiguration

  List the DASH manifest configuration.

• ListHlsManifestConfiguration

  List the HTTP live streaming (HLS) manifest configuration.

• ListLowLatencyHlsManifestConfiguration

  List the low-latency HTTP live streaming (HLS) manifest configuration.

• OriginEndpointListConfiguration

  The configuration of the origin endpoint.

• OutputHeaderConfiguration

  The settings for what common media server data (CMSD) headers AWS Elemental MediaPackage includes in responses to the CDN.

• S3DestinationConfig

  Configuration parameters for where in an S3 bucket to place the harvested content.

• Scte

  The SCTE configuration.

• ScteDash

  The SCTE configuration.

• ScteHls

  The SCTE configuration.

• Segment

  The segment configuration, including the segment name, duration, and other configuration values.

• SpekeKeyProvider

  The parameters for the SPEKE key provider.

• StartTag

  To insert an EXT-X-START tag in your HLS playlist, specify a StartTag configuration object with a valid TimeOffset. When you do, you can also optionally specify whether to include a PRECISE value in the EXT-X-START tag.

Enums

• AdMarkerDash
  When writing a match expression against AdMarkerDash, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• AdMarkerHls
  When writing a match expression against AdMarkerHls, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• CmafEncryptionMethod
  When writing a match expression against CmafEncryptionMethod, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• ConflictExceptionType
  When writing a match expression against ConflictExceptionType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• ContainerType
  When writing a match expression against ContainerType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• DashDrmSignaling
  When writing a match expression against DashDrmSignaling, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• DashPeriodTrigger
  When writing a match expression against DashPeriodTrigger, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• DashSegmentTemplateFormat
  When writing a match expression against DashSegmentTemplateFormat, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• DashUtcTimingMode
  When writing a match expression against DashUtcTimingMode, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• DrmSystem
  When writing a match expression against DrmSystem, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• EndpointErrorCondition
  When writing a match expression against EndpointErrorCondition, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• HarvestJobStatus
  When writing a match expression against HarvestJobStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• InputType
  When writing a match expression against InputType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• PresetSpeke20Audio
  When writing a match expression against PresetSpeke20Audio, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• PresetSpeke20Video
  When writing a match expression against PresetSpeke20Video, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• ResourceTypeNotFound
  When writing a match expression against ResourceTypeNotFound, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• ScteFilter
  When writing a match expression against ScteFilter, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• TsEncryptionMethod
  When writing a match expression against TsEncryptionMethod, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• ValidationExceptionType
  When writing a match expression against ValidationExceptionType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.