3. StreamLink Flow Connection โ
StreamLink receives the encoder's original signal and delivers it to the StreamLive input created in the previous step. The goal of this step is not resolution conversion but the transport connection between input and output.
Prerequisites โ
- Complete 2. StreamLive input and channel.
- Prepare the server address and Stream Key of the StreamLive RTMP input.
- Check the encoder's public IP and input access policy.
- The StreamLive security group must allow the StreamLink output-side address that actually connects to StreamLive. If only the encoder IP is allowed, the connection may be blocked at the relay stage.
- This guide is based on the Seoul region and RTMP transport.
Connection Structure โ
| Address | Where to Enter | Purpose |
|---|---|---|
| StreamLink input server address and key | Source encoder | The encoder sends the stream to StreamLink |
| StreamLive input server address and key | StreamLink Output | StreamLink relays to StreamLive |
| StreamPackage channel ID | StreamLive output group | Packaging destination for transcoding results |
| CSS playback URL | Viewer player | Plays the packaged video |
Even when the same RTMP is used, the StreamLink input address and the StreamLive input address are separate connections.
1. Selecting the Event and Flow โ
In the StreamLink console, select the Event you want to work with, then go to Flow management โ Create. For new work, use Event and Flow names that are distinct from existing services.
| Setting | Example | What to Check |
|---|---|---|
| Flow name | demo_flow | A name that identifies the transport path |
| Region | Seoul | Location of the source and the receiving service |
| Max bandwidth | Select with margin above the input bitrate | Source bitrate and network headroom |
The created Flow may not yet have input and output connections. You will configure both connections in the next step.
2. Adding an RTMP Input โ
- In the target Flow, select Add input.
- Specify the name and the input region / availability zone.
- In the console, select RTMP_PUSH as the protocol type.
- In the security group, allow only the public IP of the source encoder.
- After saving, check the generated input address and Stream Key.
This input is the address that the encoder connects to in order to send video. Input redundancy is configured separately when two transmission paths are prepared.
3. Adding an Output to Send to StreamLive โ
- In the same Flow, select Add Output.
- Select Pinpoint as the output type and RTMP_PUSH as the protocol.
- Check the output region and availability zone.
- In Destination URL, enter the StreamLive RTMP server address.
- In Stream key, separately enter the Stream Key of the StreamLive input and save.
| StreamLive Input Information | StreamLink Output Field |
|---|---|
| Server address: rtmp://YOUR_STREAMLIVE_HOST/demo | Destination URL |
| Stream name: demo_stream | Stream key |
Configure based on the values provided in the actual console.
4. Starting and Verifying the Flow โ
After re-checking the input and output of the target Flow, select Start in the upper-right corner. Clicking an input / output item lets you view the details of each connection.
| Check Point | How to Determine Normal Operation |
|---|---|
| Flow settings | The correct input and StreamLive destination are connected |
| Encoder transmission | Continuously transmitting to the StreamLink input |
| StreamLink input / output | Check reception and delivery status to the destination |
| StreamLive input | Receives the relayed original signal |
| Final playback | In the next step, check the original and CDN video / audio |
RUNNING indicates the execution state. Whether an input signal exists and is delivered to the destination must be checked separately.
Ending the Test โ
After finishing the test, select Stop on the Flow. After checking the reference relationships, clean up the test-only resources.
Next is 4. Transmitting and Verifying Playback.
Official Documentation โ
When Configuring with API โ
The following is an example of the existing API call format. Masked IDs / addresses / keys and the illustrative IPs must be replaced with actual values.
Distinguish between the RTMP_PUSH label in the console and the Protocol: RTMP notation in the existing API example below. For the API value, check and apply the input schema of the API / SDK you are using.
Creating a Flow โ
tccli mdc CreateStreamLinkFlow \
--region ap-seoul \
--FlowName demo_flow \
--MaxBandwidth 20000000{
"FlowId": "82iv************74eg"
}Creating an Input โ
This is the RTMP input that the encoder will push to.
tccli mdc CreateStreamLinkInput \
--region ap-seoul \
--FlowId 82iv************74eg \
--InputGroup '[
{
"InputName": "demo_input",
"Protocol": "RTMP",
"Description": "Demo RTMP ingest",
"AllowIpList": ["203.0.113.10/32"]
}
]'Check the push address in the query response.
tccli mdc DescribeStreamLinkFlow \
--region ap-seoul \
--FlowId 82iv************74eg{
"InputGroup": [
{
"InputName": "demo_input",
"Protocol": "RTMP_PUSH",
"InputAddressList": [
{
"Ip": "192.0.2.10",
"Port": 1935
}
],
"RTMPSettings": {
"AppName": "live_13******46",
"StreamKey": "7rvp****31j2o"
}
}
]
}In other words, the values to enter in the encoder are as follows.
URL rtmp://192.0.2.10:1935/live_13******46
StreamKey 7rvp****31j2oCreating an Output (Relay to StreamLive) โ
The output protocol is RTMP, and the destination is the StreamLive input address created in step 2.
tccli mdc CreateStreamLinkOutputInfo \
--region ap-seoul \
--FlowId 82iv************74eg \
--Output '{
"OutputName": "demo_output",
"Description": "Demo relay to StreamLive",
"Protocol": "RTMP",
"OutputRegion": "ap-seoul",
"RTMPSettings": {
"Destinations": [
{
"Url": "rtmp://13******46.ap-seoul-1.streamlive.myqcloud.com/demo",
"StreamKey": "quickstart"
}
]
}
}'Enter up to AppName (demo) in Url, and the stream name (quickstart) in StreamKey.
Starting the Flow โ
tccli mdc StartStreamLinkFlow \
--region ap-seoul \
--FlowId 82iv************74egtccli mdc DescribeStreamLinkFlow \
--region ap-seoul \
--FlowId 82iv************74egFlow demo_flow 82iv************74eg RUNNING
IN demo_input RTMP_PUSH 192.0.2.10:1935
OUT demo_output RTMP rtmp://13******46.ap-seoul-1.streamlive.myqcloud.com/demo (key quickstart)