Do you think IIT Guwahati certified course can help you in your career?
No
Introduction
MediaConnect combines dependable video transport, highly secure stream sharing, and real-time network traffic and video monitoring to let you concentrate on your content rather than your transport infrastructure.AWS Elemental MediaLive is a live video processing service for broadcasters. It enables you to create high-quality video streams for broadcast televisions and internet-connected multiscreen devices such as connected TVs, tablets, smartphones, and set-top boxes.
AWS Elemental MediaConnect
Elemental AWS MediaConnect is a service that allows broadcasters and other premium media providers to easily ingest live video into the AWS Cloud and deliver it to numerous destinations both inside and outside of the AWS Cloud. MediaConnect combines the dependability, security, and visibility that you've come to expect from traditional distribution methods with the flexibility and cost-effectiveness of internet-based transmission.
For intake, you transfer footage via an on-premises contribution encoder to AWS Elemental MediaConnect, which encodes your video into a single, high-quality mezzanine file for cloud contribution. After the video is uploaded to the AWS Cloud, MediaConnect transmits it to the outputs you select, such as a cloud encoder, another MediaConnect flow, or an on-premises location.
Source: docs.aws.amazon.com
AWS Elemental MediaConnect Functionalities
The functionalities of AWS Elemental MediaConnect are as follows:-
You create a flow in AWS Elemental MediaConnect to establish transport between a source and one or more outputs.
You may also create entitlements to share content with other AWS accounts. The receiving account can now establish a flow using your content as the source.
Live video can be ingested into the AWS Cloud.
Distribute live video to numerous destinations both inside and outside of the Amazon Web Services Cloud.
Subscribe to a live video stream provided by another Amazon Web Services account. (This requires the content creator's authorization via an entitlement.)
Transmit data from one AWS Region to another.
Use case
AWS Elemental MediaConnect can help you distribute your content to different parts of the world. Assume your on-premises contribution encoder is in Portland, Oregon, and your receivers are scattered throughout the globe. (Any entity that will receive material from your flow is referred to as a receiver.) This could be a cloud encoder, a recipient facility's on-premises encoder, or another MediaConnect flow.) The us-west-1 Region is the closest physical AWS Region to your encoder, so you set up your initial MediaConnect flow there. You send your material to additional MediaConnect flows in Regions that are closer to your receivers after it has been uploaded to the AWS Cloud.
Use case: entitlements
Entitlements enable one AWS account holder to exchange material in a transport streamflow with other AWS accounts. A sports firm, for example, wants to share a flow (Baseball-Game) with a local television station. On the Baseball-Game flow, a sports broadcaster (the originator) generates an entitlement to grant access to the local TV station (the subscriber). AWS Elemental MediaConnect flow is created by the local TV station utilizing output from the Baseball-Game flow as the source.
Source: docs.aws.amazon.com
Use case: contribution to transport stream flows
You can utilize AWS Elemental MediaConnect to import content into the AWS Cloud from an on-premises contribution encoder. Your on-premises contribution encoder is the source of your MediaConnect flow, and the output refers to your cloud encoder, such as AWS Elemental MediaLive. You can use a CDI workflow if your source content is uncompressed.
You can build up your flow to have two outputs that point to your cloud encoder for redundancy. Another redundancy solution comprises two on-premises contribution encoders—one primary and the other backup—each sending content to a separate MediaConnect flow. Each flow's output then goes to the same cloud encoder.
Use case: Contribution to CDI flows
You can connect your on-premises live video network (SDI, 2022-6, or 2110) to your VPC live video network using AWS Elemental MediaConnect and AWS Direct Connect (CDI). The JPEG XS codec is used by MediaConnect to drastically minimize your AWS Direct Connect network bandwidth. For video, audio, and metadata transfer, MediaConnect supports the SMPTE 2110 standard (parts 22, 30, and 40). MediaConnect turns the content into CDI streams, which may then be ingested by other cloud services like AWS Elemental MediaLive. You can utilize MediaConnect to convert the CDI streams back to the SMPTE 2110 standard (parts 22, 30, and 40) for transport when your cloud VPC content is ready to be sent back to on-premises networks.
Set up two connections via AWS Direct Connect to transmit material between your on-premises configuration and the AWS Cloud for redundancy. Make sure that the AWS Elemental Live appliance is configured with the same settings as the MediaConnect flows. See SMPTE 2110 inputs and outputs in the AWS Elemental Live User Guide for more information on configuring the appliance.
Use case: replication and monitoring for CDI flows
AWS Elemental MediaConnect allows you to copy and transmit video to various locations while simultaneously monitoring the different video streams.
For example, to generate a single output broadcast, you can flip between many live events taking place at separate sites. You can deliver the outputs from several production switchers to a master control switcher and a multiviewer application using a MediaConnect CDI process. You can send the final output to the distribution encoder (for example, AWS Elemental MediaLive) and the multiviewer application using a different CDI flow. The output from the multiviewer is sent to the production crew, allowing them to monitor several video sources in real-time.
A flow is transport between a source and one or more destinations. When you create a flow, you specify the source, a name, and an Availability Zone. After you create a flow, you can add outputs to indicate where you want your content to be sent and how you want it transported.
MediaConnect supports mainly two types of flows:
Transport stream flows
CDI Flow
Transport muxed (audio, video, and auxiliary data are merged) compressed material in a single stream The quality is good enough to utilize as a starting point for developing final encodes for consumer devices. You can use outputs to specify where the content should be sent and how it should be delivered.
You can give another AWS account permission to share the content. A subscriber account user can then utilize your flow as the source for a new MediaConnect flow. The service creates an output on your flow to represent the stream that feeds the subscriber's flow when this happens.
Transmits uncompressed or lightly compressed high-quality information into and out of the AWS Cloud To transfer weakly compressed content, you can configure a CDI flow to use JPEG XS. The content is decoded into independent audio, video, and ancillary data media streams. Multiple media streams can be used for the source and multiple media streams can be used for each output in a CDI flow. MediaConnect transports content that corresponds to the SMPTE 2110, part 22 transport standard using AWS Cloud Digital Interface (AWS CDI) network technology.
Source failover
An arrangement including two redundant sources for a transport streamflow is known as source failover. This redundancy helps to keep your video feed running smoothly. To use source failover, create a flow with two sources and then select one of two failover modes: merge or failover.
Merge mode merges the sources into a single stream, allowing for a smooth recovery after a single-source loss. If you choose to Merge as the failover mode, you can specify the recovery window, which is the amount of the buffer (delay) that MediaConnect should keep. The longer the recovery window, the longer the delay in transmitting the stream, but the more room for error correction. A shorter latency is achieved with a smaller recovery window, but there is less flexibility for mistake correction. The sources utilized in this method must be binary identical, which implies they must have come from the same encoder.
Switching between a primary and a backup stream is possible in failover mode. This setting allows for a smooth transition to a more stable stream. You can designate a source as the primary source if the failover mode is set to Failover. The second source serves as the backup. If no primary source is specified, MediaConnect prioritizes both sources equally and switches to the more trustworthy source as needed.Media connects use two modes of failure over let’s understand that.
MediaConnect takes content from both sources in Merge mode. To begin, the service chooses one of the sources at random. If a packet is missing from that source, the service retrieves it from another source. If packet 123 is missing from source A and the flow is utilizing source A, MediaConnect gets packet 123 from source B and continues to use source A. The two sources are binary identical and ST 2022-7 compliant in this mode.
If you don't choose a primary source in Failover mode, MediaConnect will use one of the sources at random to deliver material for the flow. If that source fails, the service moves to the next available source and changes back and forth as needed. If a primary source is specified, MediaConnect will use that source to supply content for the flow. If the primary source fails, the service changes to the alternate source, which it returns to as soon as it is reliable.
Frequently Asked Questions
What is the Availability Zone? AWS Cloud computing resources are housed in a given place. Within an AWS Region, Availability Zones are connected with low latency, high throughput, and highly redundant networking. They are also physically segregated and isolated from one another. For redundancy, you can build MediaConnect flows in separate Availability Zones.
What is the AWS region?
A geographical area including one or more Availability Zones. Each AWS Region operates independently of the others. To distribute material to receivers in different parts of the world, you can construct MediaConnect flows in distinct Regions.
What is CDI flow?
A MediaConnect flow that transfers JPEG XS-lightly compressed high-quality material. The content is decoded into independent audio, video, and ancillary data media streams. Multiple media streams can be used for the source and multiple media streams can be used for each output in a CDI flow. To ingest content that corresponds to the SMPTE 2110, part 22 transport standard, MediaConnect leverages AWS Cloud Digital Interface (AWS CDI) network technology.
What do you mean by distribution?
The result of creating outputs that point to MediaConnect flows in other AWS Regions, for the purpose of delivering content to different geographical locations.
What do you mean by entitlement? An AWS account is granted authorization to access the content in a certain MediaConnect flow. The creator of the material authorizes access to a specific AWS account (the subscriber). The subscriber can build a flow using the originator's flow as the source if the entitlement has been granted. Only transport stream flows are eligible for entitlements.
Conclusion
In this article, we have extensively discussed AWS Elemental MediaConnect.We hope that this blog has helped you enhance your knowledge regarding AWS Elemental MediaConnect.