AWS solutions documentation change
Summary
Restructured deployment documentation, added detailed step-by-step deployment instructions with parameters including authentication credentials, and replaced 'Quotas' section with 'Plan your deployment' and monitoring content.
Security assessment
The change adds documentation for optional username/password parameters for source authentication, which is a security feature. However, there's no evidence this addresses a specific vulnerability; it's routine deployment documentation for authentication capabilities.
Diff
diff --git a/solutions/latest/live-streaming-on-aws/deploy-the-solution.md b/solutions/latest/live-streaming-on-aws/deploy-the-solution.md index 9f1d81d07..d8a0b523f 100644 --- a//solutions/latest/live-streaming-on-aws/deploy-the-solution.md +++ b//solutions/latest/live-streaming-on-aws/deploy-the-solution.md @@ -5,2 +4,0 @@ -Deployment consideration - @@ -8,0 +7,2 @@ Deployment consideration +How to deploy the Live Streaming on AWS solution + @@ -11 +11 @@ This solution uses [AWS CloudFormation templates and stacks](https://docs.aws.am -## Deployment consideration +== Deployment consideration @@ -27,0 +28,71 @@ This solution includes an option to send anonymized operational metrics to AWS. +== AWS CloudFormation template + +[  ](https://s3.amazonaws.com/solutions-reference/live-streaming-on-aws/latest/live-streaming-on-aws.template) **live-streaming-on-aws.template** \- Use this template to launch the solution and all associated components. The default configuration deploys an AWS Lambda function, an AWS Elemental MediaLive input and channel, an AWS Elemental MediaPackage channel, two Amazon CloudFront distributions, and an Amazon Simple Storage Service (Amazon S3) bucket for the demo HTML preview player, but you can also customize the template based on your specific needs. + +== Launch the stack + +Before you launch the solution, review the cost, architecture, security, and other considerations discussed in this guide. Follow the step-by-step instructions in this section to configure and deploy the solution into your account. + +**Time to deploy:** Approximately 20 minutes + +This automated AWS CloudFormation template deploys the Live Streaming on AWS solution in the AWS Cloud. + + 1. Sign in to the [AWS Management Console](https://console.aws.amazon.com/) and select the button to launch the `live-streaming-on-aws` AWS CloudFormation template. + +[  ](https://console.aws.amazon.com/cloudformation/home?region=us-east-1#/stacks/new?stackName=LiveStreaming&templateURL=https:%2F%2Fs3.amazonaws.com%2Fsolutions-reference%2Flive-streaming-on-aws%2Flatest%2Flive-streaming-on-aws.template&redirectId=ImplementationGuide) + + 2. The template launches in the US East (N. Virginia) Region by default. To launch this solution in a different AWS Region, use the Region selector in the console navigation bar. + +###### Note + +This solution uses the AWS Elemental MediaLive, MediaPackage, and MediaConnect services, which are currently available in specific AWS Regions only. Therefore, you must launch this solution in an AWS Region where these services are available. For the most current service availability by Region, see the [AWS Regional Service List](https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/). + + 3. On the **Create stack** page, verify that the correct template URL is in the **Amazon S3 URL** text box and choose **Next**. + + 4. On the **Specify stack details** page, assign a name to your Live Streaming on AWS solution stack. + + 5. Under **Parameters** , review the parameters for the template, and modify them as necessary. This solution uses the following default values. Refer to the table below for detailed instruction for setting up each input type. + +Parameter | Default | Description +---|---|--- +**LIVE STREAM SOURCE** | | +**Source Input Type** | `URL_PULL` | Specify the input type for AWS Elemental MediaLive: `RTP_PUSH`, `RTMP_PUSH`, `RTMP_PULL`, `URL_PULL`, or `MEDIACONNECT`. +**URL_PULL and RTML_PULL CONFIGURATION** | | +**Primary Source URL** | `https://d15an60oaeed9r.cloudfront.net/live_stream_v2/sports_reel_with_markers.m3u8` | The primary source URL for the live feed. By default, this parameter contains the primary demo source URL. +**Primary Source Username** | _< Optional input>_ | If authentication is required to access the source, enter the username. +**Primary Source Password** | _< Optional input>_ | If authentication is required to access the source, enter the password. +**Secondary Source URL** | `https://d3h5srgm8b0t83.cloudfront.net/live_stream_v2/sports_reel_with_markers.m3u8` | The secondary (backup) source URL for the live feed. By default, this parameter contains the secondary demo source URL. +**Secondary Source Username** | _< Optional input>_ | If authentication is required to access the secondary source, enter the username. +**Secondary Source Password** | _< Optional input>_ | If authentication is required to access the secondary source, enter the password. +**RTP_PUSH and RTMP_PUSH CONFIGURATION** | | +**Input CIDR Block** | `<Requires input>` | Specify the CIDR block for the MediaLive security group for push input types. +**MEDIACONNECT CONFIGURATION** | | +**Primary MediaConnect ARN** | _< Optional input>_ | The primary source MediaConnect flow for the live feed. You can create the flow in the MediaConnect console. To provide redundancy, create the primary and secondary flows in different Availability Zones. +**Secondary MediaConnect ARN** | _< Optional input>_ | The secondary source MediaConnect flow for the live feed. You can create the flow in the MediaConnect console. To provide redundancy, create the primary and secondary flows in different Availability Zones. +**ENCODING OPTIONS** | | +**Encoding Profile** | `720` | Specify the encoding profile to use with MediaLive. +**Start MediaLive Channel** | `yes` | Choose whether to start the MediaLive channel when the solution is created. We recommend starting the channel if you will use + + 6. Choose **Next**. + + 7. On the **Configure stack options** page, choose **Next**. + + 8. On the **Review and create** page, review and confirm the settings. Check the box acknowledging that the template will create AWS Identity and Access Management (IAM) resources. + + 9. Choose **Submit** to deploy the stack. + +You can view the status of the stack in the AWS CloudFormation console in the **Status** column. You should receive a **CREATE_COMPLETE** status in approximately 20 minutes. + +To test the live stream playback, navigate to the AWS CloudFormation stack **Outputs** tab, select the **Demo Console URL** from the **Value** column. + + + + +###### Note + +In addition to the primary AWS Lambda function, this solution includes the `solution-helper` Lambda function, which runs only during initial configuration or when resources are updated or deleted. + +When running this solution, both Lambda functions are displayed in the AWS Lambda console, do not delete the `solution-helper` function because it is necessary to manage associated resources. + +Once the live streaming event is complete, stop the resources created by this solution to help ensure that you don’t incur unnecessary AWS charges. + @@ -34 +105 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -Quotas +Plan your deployment @@ -36 +107 @@ Quotas -AWS CloudFormation template +Monitor the solution with AppRegistry