AWS Security ChangesHomeSearch

AWS medialive documentation change

Service: medialive · 2025-04-28 · Documentation low

File: medialive/latest/ug/setup-input-rtmp-vpc.md

Summary

Added 'Topics' section headers, restructured content, and updated port number formatting for RTMP inputs

Security assessment

Documentation formatting changes with no security implications. Port number update (1935) is a standard RTMP port clarification without security context. No evidence of vulnerability remediation or security feature addition.

Diff

diff --git a/medialive/latest/ug/setup-input-rtmp-vpc.md b/medialive/latest/ug/setup-input-rtmp-vpc.md
index e99736839..20578dcdf 100644
--- a//medialive/latest/ug/setup-input-rtmp-vpc.md
+++ b//medialive/latest/ug/setup-input-rtmp-vpc.md
@@ -5 +5 @@
-IAM role and ARN
+Create an RTMP VPC push inputIAM role and ARN
@@ -10,0 +11,11 @@ After the Amazon VPC user has set up on the VPC, you can create the RTMP VPC pus
+###### Topics
+
+  * Create an RTMP VPC push input
+
+  * IAM role and ARN
+
+
+
+
+## Create an RTMP VPC push input
+
@@ -81 +92 @@ For example:
-MediaLive creates the input and automatically creates two endpoints on that input. These endpoints have a private IP address from the subnet range, and they specify port 1935\. For example:
+MediaLive creates the input and automatically creates two endpoints on that input. These endpoints have a private IP address from the subnet range, and they specify port 1935. For example: