Creating a transport stream flow that uses a
VPC source
Transport stream flows transport compressed content that is muxed into a single
stream.
When you create a flow that uses a source from your virtual private cloud (VPC), your
content does not go over the public internet. This is useful for security reasons as
well as reliability. You set up your VPC and then create a flow that has an interface to
that VPC. Alternatively, you can create a flow based on an entitlement that another
AWS account granted to allow you to use their content (entitled source) or a standard source.
Before you begin this procedure, make sure that the following steps have been
completed:
Create a transport stream flow that
uses a VPC source (console)
Open the MediaConnect console at https://console.aws.amazon.com/mediaconnect/.
-
On the Flows page, choose Create
flow.
-
In the Details section, for
Name, specify a name for your flow. This name will
become part of the ARN for this flow.
MediaConnect allows you to create multiple flows with the same name.
However, we encourage you to use unique flow names within an AWS
Region to help with organization. After you create a flow, you can't
change the name.
-
For Availability Zone, choose
Any or choose the Availability Zone where your VPC
subnet resides. We recommend that you leave this as Any
and let the service ensure that the Availability Zone is set correctly.
-
In the Source section, for Source
type, choose VPC source.
-
For Name, specify a name for your source. This value
is an identifier that is visible only on the MediaConnect console.
-
Determine which protocol your source uses.
If you want to specify redundant sources for failover, create the flow
with one of the sources. After the flow is created, update it to
activate failover on the source, and add the second source to the flow.
Because MediaConnect treats both sources as the primary source, it
doesn't matter which one you specify when you first create the flow.
-
For specific instructions based on your protocol, choose one of the
following tabs:
- RIST
-
-
For Protocol, choose
RIST.
-
For Ingest port, specify the port
that the flow will listen on for incoming content.
The RIST protocol requires one additional port for
error correction. To accommodate this requirement,
MediaConnect reserves the port that is +1 from the
port that you specify. For example, if you specify
port 4000 for the output, the service assigns ports
4000 and 4001.
-
For VPC interface name, choose
the name of the VPC interface that you want to use as
the source.
-
For Maximum bitrate, specify the
maximum expected bitrate (in bits per second) for the
flow. We recommend that you specify a value that is
twice the actual bitrate.
-
For Maximum latency, specify the
size of the buffer (delay) that you want the service to
maintain. A higher latency value means a longer delay in
transmitting the stream, but more room for error
correction. A lower latency value means a shorter delay,
but less room for error correction. You can choose a
value from 1-15,000 ms. If you keep this field blank,
the service uses the default value of 2,000 ms.
- RTP or RTP-FEC
-
-
For Protocol, choose
RTP or
RTP-FEC.
-
For Ingest port, specify the port
that the flow will listen on for incoming
content.
The RTP-FEC protocol requires two additional ports
for error correction. To accommodate this
requirement, MediaConnect reserves the ports that
are +2 and +4 from the port that you specify. For
example, if you specify port 4000 for the output,
the service assigns ports 4000, 4002, and 4004.
-
For VPC interface name, choose
the name of the VPC interface that you want to use as
the source.
-
For Maximum bitrate, specify the
maximum expected bitrate (in bits per second) for the
flow. We recommend that you specify a value that is
twice the actual bitrate.
- SRT listener
-
-
In the Source section, for
Source type, choose
VPC source.
-
For Name, specify a name for your
source. This value is an identifier that is visible only
on the MediaConnect console. It is not visible to
anyone outside of the current AWS account.
-
For Protocol, choose
SRT listener.
-
For Source description, enter a
description that will remind you later where this source
is from. This might be the company name or notes about
the setup.
-
For VPC interface name, choose
the name of the VPC interface that you want to use as
the source.
-
For Inbound port, specify the
port that the flow listens on for incoming
content.
-
For Maximum bitrate, specify the
maximum expected bitrate (in bits per second) for the
flow. We recommend that you specify a value that is
twice the actual bitrate.
-
For Minimum latency, specify the
size of the buffer (delay) that you want the service to
maintain. A higher latency value means a longer delay in
transmitting the stream, but more room for error
correction. A lower latency value means a shorter delay,
but less room for error correction. You can choose a
value from 10 -15,000 ms. If you keep this field blank,
the service uses the default value of 2,000 ms.
The SRT protocol uses a minimum
latency configuration on each side of the
connection. The larger of these two values is used as
the recovery latency. If the
transmitted bitrate, multiplied by the recovery latency,
is higher than the receiver
buffer, the buffer will overflow and the
stream can fail with a Buffer Overflow
Error
. On the SRT receiver side, the receiver
buffer is configured by the SRTO_RCVBUF value. The size
of the receiver buffer is limited by the flow control window
size (SRTO_FC) value. On the MediaConnect side, the
receiver buffer is calculated as the maximum bitrate value
multiplied by the minimum
latency value. For more information about
the SRT buffer, see the SRT Configuration Guidelines.
-
If the source is encrypted, choose
Activate in the
Decryption section and do the
following:
- SRT caller
-
-
In the Source section, for
Source type, choose
VPC source.
-
For Name, specify a name for your
source. This value is an identifier that is visible only
on the MediaConnect console. It is not visible to
anyone outside of the current AWS account.
-
For Protocol, choose
SRT caller.
-
For Source description, enter a
description that will remind you later where this source
is from. This might be the company name or notes about
the setup.
-
For VPC interface name, choose
the name of the VPC interface that you want to use as
the source.
-
For Source listener port, enter
the port the flow will use to pull the source
from.
-
For Maximum bitrate (optional),
specify the maximum expected bitrate (in bits per
second) for the flow. We recommend that you specify a
value that is twice the actual bitrate.
-
For Minimum latency, specify the
minimum size of the buffer (delay) that you want the
service to maintain. A higher latency value means a
longer delay in transmitting the stream, but more room
for error correction. A lower latency value means a
shorter delay, but less room for error correction. You
can choose a value from 10–15,000 ms. If you keep this
field blank, MediaConnect uses the default value of 2,000 ms.
The SRT protocol uses a minimum
latency configuration on each side of the
connection. The larger of these two values is used as
the recovery latency. If the
transmitted bitrate, multiplied by the recovery latency,
is higher than the receiver
buffer, the buffer will overflow and the
stream can fail with a Buffer Overflow
Error
. On the SRT receiver side, the receiver
buffer is configured by the SRTO_RCVBUF value. The size
of the receiver buffer is limited by the flow control window
size (SRTO_FC) value. On the MediaConnect side, the
receiver buffer is calculated as the maximum bitrate value
multiplied by the minimum
latency value. For more information about
the SRT buffer, see the SRT Configuration Guidelines.
-
For Stream ID (optional), enter
an identifier for the stream. This identifier can be
used to communicate information about the stream.
-
If the source is encrypted, choose
Activate in the
Decryption section and do the
following:
- Zixi push
-
-
For Name, specify a name for your
source. This value is an identifier that is visible only
on the MediaConnect console. It is not visible to
anyone outside of the current AWS account.
-
For Protocol, choose
Zixi push.
MediaConnect assigns the inbound port for Zixi
push VPC sources at the time of creation. A port
number 2090–2099 will be assigned
automatically.
-
For VPC interface name, choose
the name of the VPC interface that you want to use as
the source.
-
For Stream ID, specify the stream
ID set in the Zixi feeder.
If you leave this field blank, the service uses
the source name as the stream ID. Because the stream
ID must match the value set in the Zixi feeder, you
need to specify the stream ID if it is not exactly
the same as the source name.
-
For Maximum latency, specify the
size of the buffer (delay) that you want the service to
maintain. A higher latency value means a longer delay in
transmitting the stream, but more room for error
correction. A lower latency value means a shorter delay,
but less room for error correction. You can choose a
value between 0 and 60,000 ms. If you keep this field
blank, the service uses the default value of 6,000 ms.
-
If the source is encrypted, choose
Activate in the
Decryption section and do the
following:
-
For Decryption type,
choose Static key.
-
For Role ARN, specify the
ARN of the role that you created when you set up encryption.
-
For Secret ARN, specify
the ARN that AWS Secrets Manager assigned when you created the secret to store the encryption
key.
-
For Decryption algorithm,
choose the type of encryption that was used to
encrypt the source.
-
For each VPC that you want to connect to the flow, do the following:
-
In the VPC interface section, choose
Add VPC interface.
-
For Name, specify a name for your VPC
interface. The name of the VPC interface must be unique within the
flow.
-
For Role ARN, specify the Amazon Resource
Name (ARN) of the role that you created when you set up
MediaConnect as a trusted service.
-
For VPC, choose the ID of the VPC that you
want to use.
If you don't see the VPC that you want in the list, verify
that the VPC has been set up in Amazon Virtual Private Cloud and that you have
IAM permissions to view the VPC.
-
For Subnet, choose the VPC subnet that you
want MediaConnect to use to set up your VPC configuration. You must
choose at least one and can choose as many as you want.
-
For Security groups, specify the VPC security
groups that you want MediaConnect to use to set up your VPC
configuration. You must choose at least one security group.
-
Under Source monitoring configuration, choose which
monitoring features you want to enable.
-
Turn on Thumbnails state to generate source
thumbnails that you can preview in the console.
-
Turn on Content quality analysis state to
monitor for the following audio and video quality issues.
-
(Optional) Turn on Black frames to
detect periods of black video frames in the stream.
-
(Optional) Turn on Frozen frames to
detect periods of unchanging video frames in the
stream.
-
(Optional) Turn on Silent audio to
detect periods of audio silence in the stream.
-
(Optional) Set a duration threshold between 10 and 60
seconds for each metric that you enable. The default is 30
seconds.
-
At the bottom of the page, choose Create flow.
The flow doesn't start automatically. You must start the flow manually.
-
Add outputs to specify where you want
MediaConnect to send the content, or grant entitlements to allow users of other AWS accounts to
subscribe to your content.
Additional resources
For more information about source monitoring options, see Viewing thumbnails of the source video and
Monitoring with content quality
analysis in AWS Elemental MediaConnect.