Menu
Amazon CloudFront
Developer Guide (API Version 2016-09-07)

Creating an AWS CloudFormation Stack for Live Streaming

The following procedure uses an AWS CloudFormation template to create a stack that launches the AWS resources required by live streaming, including an Amazon EC2 instance and a CloudFront distribution.

Important

You incur hourly charges for an Amazon EC2 instance beginning when you create the AWS CloudFormation stack that deploys the Amazon EC2 instance. Charges continue to accrue until you delete the AWS CloudFormation stack regardless of whether you use the Amazon EC2 instance to stream live video. For more information, see the Adobe Media Server 5 Extended page on the AWS Marketplace website. When your live event is over, delete the stack that you created for live streaming. This deletes the AWS resources that were created for your live-streaming event, and stops the AWS charges for the resources. For more information, see Deleting an AWS CloudFormation Stack and an Amazon EBS Volume for Live Streaming.

For more information about AWS CloudFormation, see AWS CloudFormation Documentation.

To create an AWS CloudFormation stack for live streaming

  1. To start the Create Stack wizard, click one of the following Amazon EC2 regions:

    The wizard starts and the applicable URL automatically appears in the Provide an S3 URL to template field.

    Note

    If you want users to view your live stream using a Flash-based player that is hosted on your own domain, see How do I update crossdomain.xml for a Flash-based stream hosted on my own domain?.

  2. If you are not already signed in to the AWS Management Console, sign in when prompted.

  3. (Optional) Change the Stack Name. The stack name must not contain spaces, and it must be unique within your AWS account.

    Do not change the Template option or the address in Provide an S3 URL to template.

  4. Click Next Step.

  5. On the Specify Parameters page, for AMSAdminPassword, enter a password (minimum 8 characters) for the AMS Administration Console.

  6. For AMSAdminUserName, enter a user name. You'll use this value and the password that you entered in the previous step to log in to the AMS Administration Console after your Amazon EC2 Adobe Media Server instance is created.

  7. For InstanceType, enter an instance type, which determines pricing for your Adobe Media Server instance. For more information about Amazon EC2 instance types, see Available Instance Types in the Amazon EC2 User Guide for Linux Instances.

    For information about pricing, see the Adobe Media Server 5 Extended page on the AWS Marketplace website.

  8. For KeyPair, enter the name of an Amazon EC2 key pair in the same region that you chose in Step 1. The key pair must be associated with the account that you're currently signed in with. If you created a key pair when you performed the procedure in Creating an Amazon EC2 Key Pair, enter the name of that key pair.

  9. For StreamName, enter a short name (without spaces) for your live stream.

  10. Click Next Step.

  11. (Optional) On the Add Tags page, add one or more tags.

  12. (Optional) To configure SNS notification, to specify how long you're willing to wait for the stack to be created, to choose whether to roll back changes if stack creation fails, and to enter a stack policy, click Advanced, and adjust settings as desired.

  13. Click Next Step.

  14. Review the settings for the stack. When you're satisfied with the settings, click Create, and AWS CloudFormation creates the stack.

    Creating your stack may take several minutes. To track the progress of the stack creation, select the stack, and click the Events tab in the bottom frame. If AWS CloudFormation cannot create the stack, the Events tab lists error messages.

    When your stack is ready, in the top frame, the status for the stack changes to CREATE_COMPLETE.

    When your stack is created, click the Outputs tab, which displays the stack creation outputs. You will use these values when you set up Adobe Flash Media Live Encoder later in the process.

Next: Verifying that Adobe Media Server Is Running