AWS Documentation » AWS Solutions » Live Streaming on AWS » Automated Deployment

The AWS Documentation website is getting a new look!
Try it now and let us know what you think. Switch to the new look >>

You can return to the original look by selecting English in the language selector above.

Automated Deployment

Before you launch the automated deployment, please review the 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

Launch the Stack

This automated AWS CloudFormation template deploys the live streaming solution on the AWS Cloud.

Note

You are responsible for the cost of the AWS services used while running this solution. See the Cost section for more details. For full details, see the pricing webpage for each AWS service you will be using in this solution.

1. Log in to the AWS Management Console and click the button below to launch the live-streaming-on-aws AWS CloudFormation template.

   

   You can also download the template as a starting point for your own implementation.

2. The template is launched 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 service offerings by region.

3. On the Select Template page, verify that you selected the correct template and choose Next.

4. On the Specify Details page, assign a name to your live streaming solution stack.

5. Under Parameters, review the parameters for the template, and modify them as necessary.

   This solution uses the following default values.

   Parameter	Default	Description
   Deployment Options
   Source Code	<Requires input>	Choose whether to deploy the solution using NodeJS or Python source code for the AWS Lambda-backed custom resource
   Demo Console	True	Choose whether to deploy the preview player
   Live Streaming Source
   Source Input Type	URL_PULL	Specify the input type for AWS Elemental MediaLive: RTP_PUSH, RTMP_PUSH, RTMP_PULL, URL_PULL, or MEDIACONNECT
   Source Codec	AVC	Specify the codec for the source stream for MediaLive: AVC, HEVC, or MPEG2
   Encoding Profile	720	Specify the encoding profile to use with MediaLive
   Start MediaLive Channel	True	Choose whether to start the MediaLive channel when the solution is created. We recommend starting the channel if you will use the demo preview player.
   PUSH Source Input Types
   Input CIDR Block	<Requires input>	Specify the CIDR block for the MediaLive security group for PUSH Input Types
   PULL Source Input Types
   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
   MediaConnect Source Input Types
   Primary MediaConnect Flow 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 Flow 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.

6. Choose Next.

7. On the Options page, choose Next.

8. On the Review page, review and confirm the settings. Be sure to check the box acknowledging that the template will create AWS Identity and Access Management (IAM) resources.

9. Choose Create to deploy the stack.

   You can view the status of the stack in the AWS CloudFormation console in the Status column. You should see a status of CREATE_COMPLETE in roughly 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, you will see both Lambda functions in the AWS Lambda console, but only the primary Lambda function is regularly active. However, do not delete the solution-helper function as it is necessary to manage associated resources.

Once the live streaming event is complete, terminate the resources created by this solution to help ensure that you don’t incur unnecessary AWS charges.