AWS medialive documentation change
Summary
Added clarification about VPC security context and upstream system timing requirements
Security assessment
Emphasizes existing VPC security architecture without introducing new security features or addressing vulnerabilities. Operational note about push timing doesn't impact security controls.
Diff
diff --git a/medialive/latest/ug/setup-rtp-vpc-result.md b/medialive/latest/ug/setup-rtp-vpc-result.md index ae2648dd0..a5900b66a 100644 --- a//medialive/latest/ug/setup-rtp-vpc-result.md +++ b//medialive/latest/ug/setup-rtp-vpc-result.md @@ -8,0 +9,2 @@ As a result of this setup, an RTP input exists that specifies one or two _endpoi +Each address is in one of those subnets. In this way, the delivery of the content from the upstream system to MediaLive takes place within the security of the VPC. + @@ -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. +