AWS mediaconnect documentation change
Summary
Added new section 'Transport stream flows with NDI® outputs' with performance optimization guidance including VPC interface limitations, bandwidth calculations, and workflow testing recommendations
Security assessment
Changes focus on performance optimization and resource management for NDI outputs. While mentioning VPC interface configuration, there's no discussion of vulnerabilities or security controls. The guidance is operational rather than security-focused.
Diff
diff --git a/mediaconnect/latest/ug/best-practices.md b/mediaconnect/latest/ug/best-practices.md index 77e6bfd32..74e21e818 100644 --- a/mediaconnect/latest/ug/best-practices.md +++ b/mediaconnect/latest/ug/best-practices.md @@ -12,0 +13,2 @@ For the best performance and availability, follow best practices when you config +###### Transport stream flows + @@ -29,0 +32,29 @@ Because you can specify two destinations for a single ST 2110 JPEG XS output, th +###### Transport stream flows with NDI® outputs + +MediaConnect doesn’t impose a hard limit on the number of NDI outputs you can configure for each transport stream flow. However, as you scale your NDI outputs, keep in mind that each additional NDI output receiver connected to your flow increases the CPU and memory usage on the MediaConnect service. This is because MediaConnect is acting as the NDI sender, and needs to encode and transmit the video and audio streams to all connected receivers. + +The following best practices describe how to optimize the performance of NDI flows: + + * Monitor the performance of your MediaConnect flow as you scale NDI outputs. In particular, watch for signs of over-subscription, such as: + + * Dropped frames or stuttering video on your NDI receivers + + * Dropped NDI connections + +If you notice these issues, consider reducing the number of outputs or investigating ways to optimize your workflow. + + * Calculate the aggregate bandwidth of your NDI outputs and ensure it fits within the total throughput capacity of your MediaConnect flow size. The large flow size supports up to 2.5 Gbps of aggregate throughput. + + * Use descriptive naming conventions for your NDI outputs to make it easier for production systems to quickly discover and connect to the correct sources. + + * Consider segmenting your NDI outputs across multiple MediaConnect flows, rather than concentrating all outputs in a single flow. This can help distribute the resource load. However, keep in mind that using multiple NDI flow outputs will generate multiple NDI sources, each with their own unique machine name and program name. This will need to be accounted for in your overall workflow. + + * Test your full NDI workflow, including connecting multiple receivers, to understand the performance characteristics and limits for your specific use case. + + * Limit your NDI configuration setup to a single interface adapter per VPC. Each VPC interface has its own private IP address. When you use multiple VPC interfaces, this can confuse the NDI discovery server and lead to unexpected routing behavior. + + + + +###### CDI flows + @@ -36,0 +68,2 @@ The following best practices describe how to optimize the performance of CDI flo +###### Gateways + @@ -43,0 +77,2 @@ The following best practices describe how to optimize the performance of Gateway +###### Flows with managed outputs +