By using AWS re:Post, you agree to the Terms of Use
/Issues Creating MediaConnect Flows with Cloudformation Template/

Issues Creating MediaConnect Flows with Cloudformation Template

0

Hi,

I'm struggling creating Media Connect flows using cloudformation where the ingest protocol is not zixi-push. The documentation does state that srt-listener is not supported via cloudformation ( reference https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-mediaconnect-flowsource.html#cfn-mediaconnect-flowsource-maxlatency ) but I'm trying "rtp" and it fails.

Additionally, the error message is not very helpful "Error occurred during operation 'AWS::MediaConnect::Flow'." (RequestToken: <redacted>, HandlerErrorCode: GeneralServiceException)"

A working template (using Zixi on port 2088) looks like this;

`{
    "AWSTemplateFormatVersion": "2010-09-09",
    "Description": "Media Connect Flow Test",
    "Resources": {
        "MediaConnectFlowA": {
            "Type": "AWS::MediaConnect::Flow",
            "Properties": {
                "Name": "WIZARDA",
                "AvailabilityZone": "eu-west-1b",
                "Source": {
                    "Name": "WIZARDASource",
                    "StreamId": "A",
                    "Description": "Media Connect Flow Test - WIZARDA",
                    "Protocol": "zixi-push",
                    "IngestPort": 2088,
                    "WhitelistCidr": "<redacted>/32"
                }
            }
        }
    }
}`

but keeping the protocol as zixi and changing the ingress port results in failure (this could be be design I guess as it's a non-standard Zixi port).

Similarly, and more importantly for what I want to do, trying to change the protocol to "rtp" fails e.g.

{
    "AWSTemplateFormatVersion": "2010-09-09",
    "Description": "Media Connect Flow Test",
    "Resources": {
        "MediaConnectFlowA": {
            "Type": "AWS::MediaConnect::Flow",
            "Properties": {
                "Name": "WIZARDA",
                "AvailabilityZone": "eu-west-1b",
                "Source": {
                    "Name": "WIZARDASource",
                    "StreamId": "A",
                    "Description": "Media Connect Flow Test - WIZARDA",
                    "Protocol": "rtp",
                    "IngestPort": 2088,
                    "WhitelistCidr": "<redacted>/32"
                }
            }
        }
    }
}

Can anyone advise on the right construct to create a flow with RTP source? (also rtp-fec failed)

for completeness, the I've run via the console and also using the CLI e.g.

aws --profile=aws-course  --region=eu-west-1 cloudformation create-stack --stack-name="mediaconnect-rtp" --template-body file://..\MConly.json
1 Answers
0
Accepted Answer

Hi Matt,

Thanks for using AWS re:Post. In order to complete your MediaConnect rtp protocol CloudFormation stack, you'll need to remove the StreamId parameter which you've included as part of the AWS::MediaConnect::FlowSource resource.

Referencing the documentation link you were able to provide, I noted that the StreamId applies only to Zixi-based streams. After removing it, and including the MaxBitrate parameter, I was able to successfully create the stack.

As an example:

{
  "AWSTemplateFormatVersion": "2010-09-09",
  "Description": "Media Connect Flow Test West2a",
  "Resources": {
    "MediaConnectFlowWest2a": {
      "Type": "AWS::MediaConnect::Flow",
      "Properties": {
        "Name": "adrian-emx-rtp-flow",
        "AvailabilityZone": "us-west-2a",
        "Source": {
          "Name": "adrian-emx-rtp-flow",
          "MaxBitrate": "80000000",
          "Description": "Media Connect Flow Test - West2a",
          "Protocol": "rtp",
          "IngestPort": 5000,
          "WhitelistCidr": "<redacted>/20"
        }
      }
    }
  }
}
answered 19 days ago
  • Brilliant - thanks so much for taking the time to answer this. Working well now!

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions