OBS STUDIO TO AWS ELEMENTAL MEDIALIVE TO AWS ELEMENTAL MEDIAPACKAGE

Transcription

1 DOCUMENT TITLE OBS STUDIO TO AWS ELEMENTAL MEDIALIVE TO AWS ELEMENTAL MEDIAPACKAGE Workflow Example

2 CONTENTS Introduction... 3 Requirements... 3 Order of Work... 3 Prerequisite: Obtain Needed Information... 3 Step A: Create Channels in AWS Elemental MediaPackage... 3 Step B: Set up Inputs in AWS Elemental MediaLive... 5 Step C: Configure the Appliance... 8 Step D: Create a Channel in AWS Elemental MediaLive... 9 Step E: Start Streaming the Video , Amazon Web Services, Inc. or its affiliates. All rights reserved. 2

3 INTRODUCTION This workflow example illustrates how to use a workstation running OBS Studio to send a high definition (HD) feed to AWS Elemental MediaLive, where we will encode an ABR stream set using an HLS output group and send the content to AWS Elemental MediaPackage. In the text below the OBS Studio workstation is referred to as the appliance. Warning: This workflow is intended as an example and for testing purposes only. AWS Elemental MediaLive requires two inputs as part of its redundancy model. OBS Studio does not have a provision to send its output to multiple destinations at the same time. As such, OBS Studio can t provide redundancy and you should use caution running this example in a production workflow. REQUIREMENTS To perform this procedure, you must be familiar with the configuration of the OBS Studio software. You also must have all of the required information for your particular source, excluding the configuration of the streaming settings directed towards AWS Elemental MediaLive. ORDER OF WORK 1. Obtain needed information. 2. Create two channels in AWS Elemental MediaPackage. 3. Create an input in AWS Elemental MediaLive. 4. Configure the OBS Studio software ( the appliance ). 5. Create a channel in AWS Elemental MediaLive. 6. Start the video stream. PREREQUISITE: OBTAIN NEEDED INFORMATION Obtain the public IP address (or addresses) from the appliance that you will use to send the feed to the AWS Elemental MediaLive input. Note: If there is a firewall between the appliance and the internet (highly recommended), the public IP addresses will likely be different from those that the appliance reports. If so, you need to determine the external address being used. The appliance network may also be configured to utilize a pool of external IP addresses. In this case, you will need the CIDR range for the entire pool to include in the Input Security Group. STEP A: CREATE CHANNELS IN AWS ELEMENTAL MEDIAPACKAGE In order to create your AWS Elemental MediaLive channel, you must first know the destination URLs and credentials for your output(s). For this example, use AWS Elemental MediaPackage as your destination. MediaLive requires two output endpoints per output group, so create two MediaPackage channels as follows: 1. Log into the AWS Elemental MediaPackage console for the same region where you will be using AWS Elemental MediaLive. 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved. 3

4 2. If you have previously created channels in MediaPackage, the channel listing view will appear. Otherwise the introductory landing page will appear. a. From the landing page, enter a channel name and choose Next Step. b. From the Channel Listing page, choose Create Channel. 3. For either case above, you should now see the Create channel page: 4. Add a description if desired, and choose Create to save and create the channel. The channel detail page appears. Make a note of the Input URL, Username, and Password (use the show button to reveal the password) as you will need to use these values when creating your AWS Elemental MediaLive channel. 5. Just below the channel detail tile choose Add endpoints to create an appropriate endpoint to be able to view your channel. For this example it is sufficient to create a simple HLS endpoint so just give it a unique name in the ID field and choose Save to create the endpoint. 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved. 4

5 When the MediaLive channel is up and running you will be able to point an HLS compatible player or browser at the endpoint to view the channel, or you can preview it from inside the MediaPackage console. 6. Repeat this process to create a second AWS Elemental MediaPackage channel for the second pipeline. 7. Keep this browser session active so you can easily come back later to check your channel. STEP B: SET UP INPUTS IN AWS ELEMENTAL MEDIALIVE 1. In a new browser tab or window, log into the AWS Elemental MediaLive console for the same region you just used to create your AWS Elemental MediaPackage channels and endpoints. 2. Take the appropriate action: If the standard service page appears, choose Inputs from the navigation panel on the left side. If the service landing page appears, expand the left-hand menu by choosing the three horizontal lines near the top just below the AWS icon. Choose Inputs. The Input listing page appears. 3. Choose Create input. The Create input page appears. 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved. 5

6 4. Complete the fields as follows: Input name: Assign a meaningful name. Input type: Choose RTMP (push). Input security group: Choose Create. New security group: Using CIDR format, type the set of IP addresses from the Prerequisite step in this document. If you re entering a range, specify a mask that encompasses all of the addresses, or enter several CIDR entries to encompass all of the addresses. 5. Choose Create input security group. The tile changes to show the newly created group. 6. In the Input destinations section, enter application name and application instance (stream name), in the fields provided. You will use these names in the OBS setup in Step C. 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved. 6

7 7. Choose Create. The new input appears in the list of inputs. 8. Open the detail page for the newly-created inputs, and make a note of the endpoint URLs, as you will need to enter them in the OBS streaming configuration in Step C. 9. Leave this page open. You will return to it in a later step. 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved. 7

8 STEP C: CONFIGURE THE APPLIANCE 1. Launch OBS Studio on the source system. Choose Settings to open the settings window. Choose Stream to access the streaming settings. 2. Complete the fields as follows and choose Apply to save your changes: For Stream Type, choose Custom Streaming Server. For URL, copy one of the endpoint URLs from the input you created in Step B. Remove the /<stream_name> at the end of the URL. For Stream key, type the stream name. Leave the Use authentication box unchecked. 3. Choose Output from the left-hand menu and in Output Mode, choose Advanced. 4. Complete the Streaming tab as follows and choose Apply to save your changes: For the Encoder, choose x264. Select Rescale Output box and type 1920x1080 in the drop-down (it s not a drop-down option, but you can enter it manually). Change Bitrate to (this assumes your uplink bandwidth is sufficient). Leave the remaining settings at their defaults. 5. Choose Audio from the left-hand menu, confirm the following, and choose Apply if you had to make any changes: Sample rate is 44.1 khz. Channels are set to Stereo. 6. Choose Video from the left-hand menu complete the fields as follows. Choose Apply to save your changes. For Base (Canvas) Resolution, choose 1920x1080. For Output (Scaled) Resolution, choose 1920x1080. Set the desired frame rate in Common FPS Values. 7. Choose OK to dismiss the settings window. 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved. 8

9 STEP D: CREATE A CHANNEL IN AWS ELEMENTAL MEDIALIVE 1. Switch back to the AWS Elemental MediaLive console. 2. Choose Channels from the left-hand column, then choose Create channel. The Create channel page appears. 3. For Channel name, type a meaningful identifier for the channel. 4. In the Channel template section at the bottom, choose HTTP Live Streaming. The Channel navigation panel is populated with: One output group named TN2224 (HLS) Ten outputs that all belong to that output group. 5. In the IAM role section, take the appropriate action: If the Create role from template option is enabled, select that option and choose Create IAM role. The role is created. Once the creation process is complete, the role is automatically selected from the Use existing role drop-down. If the Create role from template option is grayed out, select Use existing role and then select MediaLiveAccessRole from the dropdown. 6. In the Channel input section, choose your newly created input from the drop-down. 7. Under Input specifications, choose the Input codec (AVC for our example settings), Input resolution (select HD for our example), and Maximum input bitrate (use MAX_10_MBPS in our example). 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved. 9

10 8. In the navigation panel on the left under Output groups, choose the TN2224 (HLS) output group. The details for that output group appear. 9. In the HLS group destination A section, expand the Credentials sub-section, then complete the fields with the information from the first channel AWS Elemental MediaPackage (as described in Step A, part 4). URL: Type the URL for the first channel you created in AWS Elemental MediaPackage. Username: Type the username for the first channel in AWS Elemental MediaPackage. From the list of Password options, select the Create AWS Elemental MediaLive parameter radio button. In Name, enter a meaningful name for the EC2 parameter store entry where your credentials will be stored. Password: Type the password for the first channel in AWS Elemental MediaPackage. The password will be stored securely in the AWS EC2 parameter store under the name medialive/<name you entered above>. Choose the Create AWS Elemental MediaLive parameter button to create it. 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved. 10

11 10. Repeat step 9 for HLS group destination B, using the information from the second channel that you created in AWS Elemental MediaPackage. You must specify two destinations to create a valid AWS Elemental MediaLive channel. 11. Under HLS Settings, choose Hls webdav from the CDN Settings drop-down. This is the preferred setting for sending HLS output to AWS Elemental MediaPackage. 12. In the Channel navigation panel on the left, choose Output 1 from the list of Output groups under TN2224 (HLS). The details for that output appear. 13. Examine the video and audio encodes for this output and make any desired changes. 14. Repeat for the other outputs. The only differences among the outputs are in resolution and bitrate. 15. Choose Create channel. The page with the list of channels appears, showing the new channel. The status of the channel changes from Creating to Idle. STEP E: START STREAMING THE VIDEO You must start the event on the appliance and the AWS Elemental MediaLive channel in the correct order. This example uses RTMP, so you must start the AWS Elemental MediaLive channel first. If the channel is not in a Running state when you start the OBS stream, the handshake attempt from OBS to the channel will fail. 1. In AWS Elemental MediaLive, on the Channels page, choose the radio button next to your new channel. The buttons along the top are enabled. 2. Choose Start. The channel state changes to Starting, and then to Running. 3. Switch to OBS and start the stream connection. 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved. 11

12 Video should begin streaming from the appliance through to AWS Elemental MediaLive, then to AWS Elemental MediaPackage, where you can view it in a preview window. Note that only one of the two MediaPackage channels will show input as you are only feeding one of the two AWS Elemental MediaLive encoding pipelines. 2018, Amazon Web Services, Inc. or its affiliates. All rights reserved. 12