AWS mediaconnect documentation change
Summary
Restructured documentation with added prerequisites, procedure steps, and next steps. Added flow size selection step (Large 4x) and renumbered subsequent steps. Converted headings to hierarchical structure.
Security assessment
Changes are organizational and procedural improvements without mentioning security vulnerabilities or new security features. The 'Grant entitlements' link in next steps references existing access control documentation but doesn't introduce new security content.
Diff
diff --git a/mediaconnect/latest/ug/flows-create-cdi.md b/mediaconnect/latest/ug/flows-create-cdi.md index a4dc16708..924687c31 100644 --- a/mediaconnect/latest/ug/flows-create-cdi.md +++ b/mediaconnect/latest/ug/flows-create-cdi.md @@ -5 +5 @@ -AWS CDI flow (console)AWS CDI flow (AWS CLI) +PrerequisitesProcedureNext steps @@ -15 +15 @@ MediaConnect doesn't support two sources on CDI flows. For redundancy with ST 21 -###### Important +## Prerequisites @@ -28 +28,3 @@ Before you begin this procedure, make sure that the following steps have been co -## Create an AWS CDI flow (console) +## Procedure + +### Create an AWS CDI flow (console) @@ -42 +44,3 @@ MediaConnect allows you to create multiple flows with the same name. However, we - 5. In the **Source** section, for **Source type** , choose **VPC source**. + 5. For **Flow size** , select **Large 4x**. + + 6. In the **Source** section, for **Source type** , choose **VPC source**. @@ -44 +48 @@ MediaConnect allows you to create multiple flows with the same name. However, we - 6. For **Name** , specify a name for your source. This value is an identifier that is visible only on the MediaConnect console. + 7. For **Name** , specify a name for your source. This value is an identifier that is visible only on the MediaConnect console. @@ -46 +50 @@ MediaConnect allows you to create multiple flows with the same name. However, we - 7. Skip to the **VPC interface** section. + 8. Skip to the **VPC interface** section. @@ -48 +52 @@ MediaConnect allows you to create multiple flows with the same name. However, we - 8. For each VPC that you want to connect to the flow, do the following: + 9. For each VPC that you want to connect to the flow, do the following: @@ -68 +72 @@ If you don't see the VPC that you want in the list, verify that the VPC has been - 9. For each media stream that you want to add to the flow, do the following: + 10. For each media stream that you want to add to the flow, do the following: @@ -139 +143 @@ Ancillary data - 10. Scroll back up to the **Sources** section. + 11. Scroll back up to the **Sources** section. @@ -141 +145 @@ Ancillary data - 11. Determine which protocol your source uses. + 12. Determine which protocol your source uses. @@ -143 +147 @@ Ancillary data - 12. For specific instructions based on your protocol, choose one of the following tabs: + 13. For specific instructions based on your protocol, choose one of the following tabs: @@ -195 +199 @@ ST 2110 JPEG XS - 13. At the bottom of the page, choose **Create flow**. + 14. At the bottom of the page, choose **Create flow**. @@ -201 +205 @@ The flow doesn't start automatically. You must [start the flow](./flows-start.ht - 14. [Add outputs](./outputs-add-vpc.html) to specify where you want MediaConnect to send the content. + 15. [Add outputs](./outputs-add-vpc.html) to specify where you want MediaConnect to send the content. @@ -206 +210 @@ The flow doesn't start automatically. You must [start the flow](./flows-start.ht -## Create an AWS CDI flow (AWS CLI) +### Create an AWS CDI flow (AWS CLI) @@ -562,0 +567,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 + + + +