AWS medialive documentation change
Summary
Restructured input type table to add 'Push or pull?' column and added new sections explaining ingestion methods for pull, RTMP push, and RTP push inputs
Security assessment
Changes primarily improve documentation structure and clarify input types. While some entries mention secure connections (HTTPS) and encryption (SRT), these were existing features. The RTMPS protocol unsupported statement remains unchanged. No specific security vulnerabilities or new security features are introduced.
Diff
diff --git a/medialive/latest/ug/inputs-supported-formats.md b/medialive/latest/ug/inputs-supported-formats.md index 95f0ca257..1b8067aaf 100644 --- a//medialive/latest/ug/inputs-supported-formats.md +++ b//medialive/latest/ug/inputs-supported-formats.md @@ -4,0 +5,2 @@ +Ingesting with a pull inputIngesting with an RTMP push inputIngesting with an RTP push input + @@ -9 +11 @@ The following table lists the input types that are supported in MediaLive, and d -For information about _push inputs_ and _pull inputs_ , see [Push and pull AWS Cloud inputs](./inputs-push-pull.html). +The sections after the table describe how MediaLive ingests a push or pull input. @@ -11,4 +13,4 @@ For information about _push inputs_ and _pull inputs_ , see [Push and pull AWS C -MediaLive input type | Use case | Upstream system and supported protocol ----|---|--- -CDI | Push an uncompressed stream in your VPC to a fixed endpoint on MediaLive. | Amazon VPC within a private cloud -HLSSee HLS inputs, after this table. | Pull an HLS stream or asset from an external endpoint using the HTTP protocol, with or without a secure connection. | HTTP server orHTTPS server +MediaLive input type | Push or pull? | Use case | Upstream system and supported protocol +---|---|---|--- +CDI | Push | Push an uncompressed stream in your VPC to a fixed endpoint on MediaLive. | Amazon VPC within a private cloud +HLSSee HLS inputs, after this table. | Pull | Pull an HLS stream or asset from an external endpoint using the HTTP protocol, with or without a secure connection. | HTTP server orHTTPS server @@ -17,3 +19,3 @@ HLS | Pull an HLS stream or VOD asset from an Amazon S3 bucket, using a secure c -Link | Push a transport stream (TS) from an AWS Elemental Link device. | AWS Elemental Link over an internal connection -MediaConnect | Push a transport stream (TS) from a flow in AWS Elemental MediaConnect.This input uses a MediaConnect flow ARN, not a URI. | AWS Elemental MediaConnect over an internal connection -MP4 | Pull an MP4 file from an HTTP server, with or without a secure connection. | HTTP server or HTTPS server +Link | Push | Push a transport stream (TS) from an AWS Elemental Link device. | AWS Elemental Link over an internal connection +MediaConnect | Push | Push a transport stream (TS) from a flow in AWS Elemental MediaConnect.This input uses a MediaConnect flow ARN, not a URI. | AWS Elemental MediaConnect over an internal connection +MP4 | Pull | Pull an MP4 file from an HTTP server, with or without a secure connection. | HTTP server or HTTPS server @@ -21,2 +23,2 @@ MP4 | Pull an MP4 file from an Amazon S3 bucket, using a secure connection. With -RTMP Pull | Pull a stream from an external endpoint using the RTMP protocol.MediaLive doesn't support inputs using the RTMPS protocol. | RTMP server over RTMP Pull -RTMP Push | Push a stream to a fixed endpoint on MediaLive using the RTMP protocol. MediaLive doesn't support inputs using the RTMPS protocol. | RTMP server over RTMP Push +RTMP Pull | Pull | Pull a stream from an external endpoint using the RTMP protocol.MediaLive doesn't support inputs using the RTMPS protocol. | RTMP server over RTMP Pull +RTMP Push | Push | Push a stream to a fixed endpoint on MediaLive using the RTMP protocol. MediaLive doesn't support inputs using the RTMPS protocol. | RTMP server over RTMP Push @@ -24 +26 @@ RTMP Push | Push a stream in your VPC to a fixed endpoint on MediaLive, using th -RTP | Push a transport stream (TS) to a fixed endpoint on MediaLive, using the RTP protocol. | RTP server over RTP Push +RTP | Push | Push a transport stream (TS) to a fixed endpoint on MediaLive, using the RTP protocol. | RTP server over RTP Push @@ -26,3 +28,2 @@ RTP | Push a transport stream (TS) in your VPC to a fixed endpoint on MediaLive, -SMPTE 2110 stream | Deliver a set of streams that are compliant with the SMPTE 2110 specification. MediaLive supports 2022-7 seamless protection switching with SMPTE 2110 inputs.MediaLive doesn't support SMPTE 2110 with NMOS. The SMPTE 2110 source must be Precision Time Protocol (PTP) locked, to ensure that the video, audio, and ancillary data synchronize properly. | A service provider that supports delivery of SMPTE 2110 using SDP files retrieved from the service provider. SMPTE 2110 is delivered over the RTP protocol -SRT caller | Pull a live transport stream using the SRT protocol. The SRT source can be encrypted or unencrypted. | A service provider that supports delivery over the SRT protocol. -Transport Stream (TS) file | Pull a TS file from an HTTP server, with or without a secure connection. File extensions of .ts or .m2ts are supported.MediaLive only supports static TS files. It does not support growing TS files that are written to while in use. | HTTP server or HTTPS server +SMPTE 2110 stream | Pull | Pull a set of streams that are compliant with the SMPTE 2110 specification. MediaLive supports 2022-7 seamless protection switching with SMPTE 2110 inputs.MediaLive doesn't support SMPTE 2110 with NMOS. The SMPTE 2110 source must be Precision Time Protocol (PTP) locked, to ensure that the video, audio, and ancillary data synchronize properly. | A service provider that supports delivery of SMPTE 2110 using SDP files retrieved from the service provider. SMPTE 2110 is delivered using RTP. +Transport Stream (TS) file | Pull | Pull a TS file from an HTTP server, with or without a secure connection. File extensions of .ts or .m2ts are supported.MediaLive only supports static TS files. It does not support growing TS files that are written to while in use. | HTTP server or HTTPS server @@ -34,0 +36,24 @@ With HLS, the media must be a transport stream. MediaLive doesn't support ingest +## Ingesting with a pull input + +A pull input works as follows: the source continually publishes to an endpoint that is outside of MediaLive. When the channel (that is connected to the input) is running, MediaLive connects to the input and ingests the content. + +When the channel is not running, MediaLive does not connect to the input. (There might be other applications that do connect.) + +A pull input works with a streaming input (where the source is continually being published) or a VOD input (where the source is made available on the endpoint and then does not change). + +## Ingesting with an RTMP push input + +An RTMP push input works as follows: the source attempts to deliver to an endpoint that is specified in the MediaLive input. There must be a handshake between the source and the MediaLive channel so that the source has information about the status of the input. + +When the channel (that is connected to this input) is started, MediaLive responds to the handshake message and ingests it. When the channel is not running, MediaLive does not react; the source goes into a paused state. + +A push input works only with a streaming source. + +## Ingesting with an RTP push input + +An RTP push input works as follows: the source attempts to deliver to an endpoint that is specified in the MediaLive input. The source is unaware of whether the content is being ingested by the MediaLive channel. + +When the channel (that is connected to this input) is started, MediaLive reacts to the source and ingests it. When the channel is not running, MediaLive does not react; the source continues to publish to the endpoint, but MediaLive ignores that action. + +A push input works only with a streaming source. + @@ -43 +68 @@ Supported input types -Input deployments +Support for live and file sources