AWS mediaconnect documentation change
Summary
Restructured documentation with added prerequisites for encryption and NDI configuration, expanded NDI setup guidance, and clarified flow creation procedures
Security assessment
Added encryption setup requirements and security group configuration guidance for NDI servers. While these are security-related best practices, there's no evidence they address a specific disclosed vulnerability.
Diff
diff --git a/mediaconnect/latest/ug/flows-create-standard-source.md b/mediaconnect/latest/ug/flows-create-standard-source.md index 27b39377e..5d49cf3a7 100644 --- a/mediaconnect/latest/ug/flows-create-standard-source.md +++ b/mediaconnect/latest/ug/flows-create-standard-source.md @@ -5 +5 @@ -Transport stream flow, standard source (console)Transport stream flow, standard source (AWS CLI)Additional resources +PrerequisitesProcedureNext stepsAdditional resources @@ -11 +11,23 @@ Transport stream flows transport compressed content that is muxed into a single -A flow uses a _standard_ source when the content comes from anywhere other than a VPC ([VPC source](./flows-create-vpc-source.html)) or another AWS account ([entitled source](./flows-create-entitled-source.html)). +A flow uses a _standard_ source when the content comes from anywhere other than a VPC ([VPC source](./flows-create-vpc-source.html)) or another AWS account (entitled source). + +## Prerequisites + +Before you begin, make sure you've completed the following steps: + +**Encryption setup (if required)** + + +If the source of your flow requires encryption, you'll need to [set up encryption](./encryption-static-key-set-up.html). + +**NDI® configuration (for NDI use cases only)** + + +We recommend reviewing the [NDI outputs](./outputs-using-ndi.html) documentation to familiarize yourself with this feature before getting started. + +If you want to add an NDI output to your flow, you need a VPC with NDI discovery servers provisioned in your network. MediaConnect connects to these servers, but it doesn't create them for you. + + * For a quick start with VPCs, you can use our [AWS CloudFormation VPC template](https://docs.aws.amazon.com/vpc/latest/userguide/create-vpc.html) to automatically create a VPC with public and private subnets. For more information about VPCs, see the [Amazon VPC User Guide](https://docs.aws.amazon.com/vpc/latest/userguide/). + + * For NDI discovery server deployment, AWS provides guidance on automated setup across multiple Availability Zones using AWS CloudFormation, including best practices for installation and configuration. For instructions, see [Setting Up NDI Discovery Servers for Broadcast Workflows](https://aws.amazon.com/solutions/guidance/programmatic-deployment-of-ndi-discovery-servers-for-broadcast-workflows-on-aws/). + + * We recommend that you configure your security groups with a self-referencing ingress rule and egress rule. You can then attach this security group to the EC2 instances where your NDI servers are running within the VPC. This approach automatically allows all necessary NDI communication between components in your VPC, and all required network traffic is permitted. For guidance on setting up self-referencing security group rules, see [Security Group Referencing](https://docs.aws.amazon.com/vpc/latest/userguide/security-group-rules.html#security-group-referencing) in the Amazon VPC User Guide. @@ -13 +34,0 @@ A flow uses a _standard_ source when the content comes from anywhere other than -###### Important @@ -15 +35,0 @@ A flow uses a _standard_ source when the content comes from anywhere other than -If the source of your flow requires encryption, [set up encryption](./encryption-static-key-set-up.html) before you begin this procedure. @@ -17 +37,4 @@ If the source of your flow requires encryption, [set up encryption](./encryption -## Create a transport stream flow that uses a standard source (console) + +## Procedure + +### Create a transport stream flow that uses a standard source (console) @@ -31 +54,37 @@ MediaConnect allows you to create multiple flows with the same name. However, we - 5. Determine which protocol your source uses. + 5. Under **Flow size** , select the size that matches your use case. For more information about flow sizes, see [Flow sizes and capabilities](./flow-sizes-capabilities.html). + +**For medium flows:** + + * Proceed directly to step 6. + +**For large flows:** + + * If you don't need NDI outputs for your flow, proceed directly to step 6. + + * If you want to add NDI outputs to your flow, configure the NDI settings as follows: + + 1. Set **Flow NDI support** to **Enabled**. + + 2. (Optional) Enter an **NDI machine name**. + + * This name is used as a prefix to help you identify the NDI sources that your flow creates. For example, if you enter `MACHINENAME`, your NDI sources will appear as `MACHINENAME` `(ProgramName)`. + + * If you don’t enter a name, MediaConnect generates a unique 12-character ID as the prefix. This ID is derived from the flow's Amazon Resource Name (ARN), so the machine name references the flow resource. + +###### Tip + +Thoughtful naming is especially important when you have multiple flows creating NDI sources. For example, a production environment with 100 NDI sources would benefit from clear, descriptive machine name prefixes like `STUDIO-A`, `STUDIO-B`, `NEWSROOM`, and so on. + + 3. Add up to three **NDI discovery servers**. For each server, provide the following information: + + * Enter the server IP address from your existing NDI infrastructure. + + * Select the VPC interface adapter to control network access. + + * (Optional) Specify a port number. If you leave this blank, MediaConnect uses the NDI Discovery server default of TCP-5959. + +###### Tip + +You can add up to three discovery servers. Having multiple discovery servers improves reliability and helps ensure your NDI sources are discoverable across your network. + + 6. Determine which protocol your source uses. @@ -37 +96 @@ If you want to specify redundant sources for failover, create the flow with one - 6. For specific instructions based on your source type and protocol, choose one of the following tabs: + 7. For specific instructions based on your source type and protocol, choose one of the following tabs: @@ -221 +280 @@ If you know the range of public IP addresses that your Link device uses to conne - 7. Under **Source monitoring configuration** , choose which monitoring features you want to enable. + 8. Under **Source monitoring configuration** , choose which monitoring features you want to enable. @@ -235,7 +294 @@ If you know the range of public IP addresses that your Link device uses to conne - 8. At the bottom of the page, choose **Create flow**. - -###### Note - -The flow doesn't start automatically. You must [start the flow](./flows-start.html) manually. - - 9. [Add outputs](./outputs-add.html) to specify where you want MediaConnect to send the content, or [grant entitlements](./entitlements-grant.html) to allow users of other AWS accounts to subscribe to your content. + 9. At the bottom of the page, choose **Create flow**. @@ -246 +299 @@ The flow doesn't start automatically. You must [start the flow](./flows-start.ht -## Create a transport stream flow that uses a standard source (AWS CLI) +### Create a transport stream flow that uses a standard source (AWS CLI) @@ -313,0 +367,13 @@ The following example shows the return value: +## Next steps + +Now that you've created a flow, complete these steps to start delivering your content: + + * [Add outputs](./outputs-add.html) to specify where you want MediaConnect flow to send your content + + * [Grant entitlements](./entitlements-grant.html) to allow users of other AWS accounts to subscribe to your content + + * [Start your flow](./flows-start.html) to begin content delivery + + + + @@ -316 +382,8 @@ The following example shows the return value: -For more information about source monitoring options, see [Viewing thumbnails of the source video](./monitor-with-thumbnails.html) and [Monitoring with content quality analysis in AWS Elemental MediaConnect](./monitor-content-quality-analysis.html). +For more information about source monitoring options for your flow, see the following pages in this guide: + + * [Viewing thumbnails of the source video](./monitor-with-thumbnails.html) + + * [Monitoring with content quality analysis in AWS Elemental MediaConnect](https://docs.aws.amazon.com/mediaconnect/latest/ug/monitor-content-quality-analysis.html) + + +