AWS medialive documentation change
Summary
Clarified RTMP endpoint persistence and added note about upstream system timing requirements
Security assessment
Changes emphasize endpoint URL persistence and operational timing, but do not address vulnerabilities or modify security controls. Existing security context (IAM roles, security groups) remains unchanged.
Diff
diff --git a/medialive/latest/ug/setup-rtmp-vpc-result.md b/medialive/latest/ug/setup-rtmp-vpc-result.md index a1d0e1817..9894a9cfd 100644 --- a//medialive/latest/ug/setup-rtmp-vpc-result.md +++ b//medialive/latest/ug/setup-rtmp-vpc-result.md @@ -7 +7,3 @@ -As a result of this setup, an RTMP input exists that specifies one or two _endpoint_ URLs. These endpoints are elastic network interfaces on your VPC. MediaLive has permission to use these network interfaces for its inputs. MediaLive has permission (through the IAM trusted entity role) to automatically manage the network interfaces for its inputs. The upstream system has permission, through the Amazon VPC security group, to push content to these endpoints. +As a result of this setup, an RTMP input exists that specifies one or two _endpoint_ URLs. These addresses are fixed for the lifetime of the input, regardless of changes that occur (such as modifying other information in the input, or attaching the input to a different channel). + +These endpoints are elastic network interfaces on your VPC. MediaLive has permission to use these network interfaces for its inputs. MediaLive has permission (through the IAM trusted entity role) to automatically manage the network interfaces for its inputs. The upstream system has permission, through the Amazon VPC security group, to push content to these endpoints. @@ -12,0 +15,2 @@ Each output of the upstream system has an IP address in one of the specified sub +Keep in mind that with a push input, the upstream system must be pushing the video source to the input when you start the channel. The upstream system does not need to be pushing before then. +