Create a stream in YouTube Live Control Room, copy that stream’s RTMPS URL and key, and map them into an RTMP output group in AWS Elemental MediaLive. Starting the MediaLive channel sends video to YouTube; for a scheduled broadcast, you must also select Go live in Live Control Room after its preview appears.
The URL and key belong to the specific YouTube stream you selected, so do not substitute a remembered endpoint or a key from another stream. The setup below follows the values shown in your account, explains MediaLive’s destination fields, and gives you checks for confirming receipt before you make a scheduled broadcast public.
Create a YouTube stream and retrieve RTMPS details
In YouTube Studio, open Create → Go Live. From the Live Control Room, use the Stream tab to create a stream or select the scheduled stream you intend to use. Keep that stream selected while you copy its connection details; a key from a different stream will not authenticate the output you are configuring.
Open Stream settings and find the Stream URL field. YouTube normally shows an RTMP URL there. Select the lock icon beside the field to reveal the RTMPS URL, then copy the complete value exactly as displayed. Copy the stream key for the same stream as well. YouTube’s RTMPS instructions explain that RTMPS is RTMP carried over a TLS/SSL connection.
Treat the displayed endpoint as account-specific configuration, not a value to reconstruct from an example. Its protocol, host, port and path all matter. The public documentation describes where to find the values, but does not supply one universal endpoint to hard-code into every MediaLive channel.
Before leaving YouTube, check the stream’s intended timing and visibility in Live Control Room. If you are preparing a scheduled event, note its scheduled entry and leave the actual public start for the later Go live action. The encoder connection and the public broadcast action are separate steps.
Protect the stream key
YouTube describes the stream key as the password and address used by an encoder to send a stream. Anyone with the key may be able to send video to that stream, so handle it as a credential rather than ordinary setup text. Do not publish it in screenshots, a public document, a support forum, or a shared run sheet that more people can access than necessary.
Paste it only into the corresponding MediaLive stream-name field, and limit access to the MediaLive channel configuration to people who need to operate it. Avoid leaving a copied key on a shared computer’s clipboard or in an unprotected note. If you need to show the configuration to someone troubleshooting, mask the key and share only the field names or a redacted screenshot.
If you think the key has been exposed, use YouTube Live Control Room to reset it. YouTube’s live stream settings guidance describes managing stream settings. After a reset, update the value in MediaLive as well: the old key will no longer be the one YouTube expects. Plan this change with whoever operates the channel so an existing broadcast is not left sending with stale credentials.
Add an RTMP output group in MediaLive
In AWS Elemental MediaLive, create or edit the channel that will send the programme to YouTube. Add an RTMP output group. AWS documents this group for RTMP/RTMPS delivery; it has one output by default, whose destination and media stream settings you configure. The AWS MediaLive User Guide covers RTMP output groups and secure connections.
Think of the output group as the delivery path, and the output as the programme’s video, audio and, if used, caption streams. The group’s destination settings tell MediaLive where and how to send the output. Its output settings determine which of your channel’s video and audio encodes are carried. A valid destination does not by itself fix a missing or unsuitable media stream selection, so check both parts of the configuration.
The AWS console may present destination details as separate URL components, or allow a complete destination path, depending on the field and workflow. Use the fields available in your channel configuration and follow their labels; do not paste the entire YouTube URL into multiple component fields. The next section breaks down which piece belongs where.
MediaLive also provides connection and security options for the destination. For an RTMPS connection, use the secure protocol indicated by YouTube’s copied URL and the appropriate authentication-scheme and certificate-mode settings shown by MediaLive. AWS’s documentation describes these fields; use the settings that match the downstream connection rather than changing unrelated channel options to resolve a destination problem.
If you are planning a continuous channel and want to understand the operational cost side before configuring it, the MediaLive cost guide for a small YouTube channel in India is a useful companion. Costs depend on the AWS configuration and usage; that question is separate from whether the endpoint and key are mapped correctly.
Map the RTMPS URL and stream key
Use the actual RTMPS URL copied from the selected YouTube stream. In MediaLive’s destination fields, map the values according to the labels in your console. The URL can be understood as a set of components; the stream key is separate and goes in the stream-name field.
| YouTube detail | MediaLive destination field | What to check |
|---|---|---|
Secure URL protocol, shown as rtmps |
Protocol or URL scheme | It must be the secure protocol, not the ordinary rtmp address. |
| Host/address from the copied URL | Address or server | Copy it as displayed; do not replace it with an example hostname. |
| Port, if shown in the URL or requested separately | Port | Preserve the supplied value unless troubleshooting calls for the documented alternative. |
| Application/path portion of the URL | Application name or URL path | Keep the path associated with that stream’s displayed endpoint. |
| YouTube stream key | Stream name | Use the key for the selected YouTube stream, not a key from another entry. |
MediaLive distinguishes the destination URL components from the stream name. Enter the protocol, host/address, port and application portion where the destination fields request them. Then enter YouTube’s key in the stream-name field. Some MediaLive workflows accept a complete path rather than separate application and stream-name components; if so, follow the console’s field instructions and avoid adding the key twice.
Do not take the example URL in AWS documentation and treat it as YouTube’s endpoint. It illustrates the structure of a destination, not the value for your account. Likewise, do not assume the key is part of the application field simply because it appears after a slash in some encoder interfaces. Use the specific MediaLive field labels and the YouTube details for this stream.
For the security controls, confirm that the output is using RTMPS and the certificate and authentication settings required for that secure connection. If the console offers a choice of authentication scheme, AWS documents a common scheme, but the choice should reflect the downstream requirements. Avoid making unneeded changes to unrelated video or audio settings when investigating an SSL error.
Set destinations for the channel class
Check whether your MediaLive channel is standard or single-pipeline before finishing its destination configuration. AWS specifies two destinations for a standard channel and one for a single-pipeline channel. This is a MediaLive channel-class requirement; it is not evidence that YouTube necessarily gives you two different ingest URLs.
For a single-pipeline channel, configure the one destination using the YouTube values you copied. For a standard channel, configure the two destination entries that MediaLive requires, and inspect the actual values supplied for the specific YouTube stream before deciding what to enter in each. Do not invent a second endpoint or assume that two destinations should have different keys. The exact destination arrangement must be based on what the current YouTube stream details and MediaLive workflow provide.
If the console reports a destination-count or channel-configuration issue, recheck the channel class and its required number of destinations first. Then verify the available YouTube values rather than pasting a guessed URL into the additional destination. AWS’s MediaLive User Guide is the primary reference for the channel and output-group configuration.
This is a good point to review who can edit the channel and who can access its destination details. A standard channel may need more than one configured destination even when you are thinking of it as one YouTube programme. Keep the operator notes clear about which destination fields are in use, but do not include the unmasked key in those notes.
Start the channel and check YouTube preview
When the channel configuration is complete, start the MediaLive channel. That starts the sending side of the workflow; it does not prove that YouTube has received usable video. Open the selected stream in Live Control Room and wait for its preview or receiving status to appear. YouTube’s encoder setup instructions describe connecting an encoder and checking the stream in Live Control Room.
Look at the preview itself, not only at the fact that MediaLive reports that it has started. Confirm that moving video is visible and that audio is present if your programme includes it. If the picture is black, frozen or absent, keep the scheduled broadcast from going public while you investigate. A successful connection should be verified at YouTube’s receiving end.
For a continuous channel, make the check with representative content and sound before relying on the setup overnight. If you are using a computer-based encoder in other parts of your workflow, a recovery plan also matters: the advice on restarting a live stream after OBS crashes explains why recovery needs to be tested rather than assumed. It is not a MediaLive configuration guide, but the operational lesson applies: observe what happens after a fault before leaving a stream unattended.
If YouTube does not show a preview, start with the details most likely to prevent receipt: confirm that the MediaLive destination uses the copied RTMPS URL, that the key belongs to the selected stream, and that the key is entered in the stream-name field. Check that the channel class has the required destination count and that the channel is running. Change one relevant setting at a time so you can tell whether the symptom changes.
Go live for a scheduled broadcast
A preview means YouTube is receiving the encoder output; it does not mean a scheduled event has been made public. Once the preview is correct, use the Go live action in Live Control Room to start the scheduled broadcast. Keep the scheduled stream’s page open and confirm its state after selecting the action.
This distinction matters if you are preparing a devotional programme, a news loop or a business event ahead of its start time. You can have MediaLive running and YouTube receiving a preview while viewers still cannot watch the scheduled broadcast. Conversely, selecting Go live before checking the preview risks making a faulty picture or silent output public.
For an immediate stream, YouTube’s encoder workflow differs from a scheduled event: connecting and starting the encoder can create the watch page and put the stream live. Follow the controls shown for the selected stream in Live Control Room. Do not assume the immediate-stream behaviour applies to a scheduled broadcast, where YouTube gives you a separate public-start action.
If you use the channel for recurring content, keep a short operator checklist with the stream name, scheduled start, destination verification, preview check and public Go live action. Do not put the secret key on that checklist. Where your workflow is based on uploaded, repeating video rather than a live production, StreamNeo can remove the need to leave your own computer running to keep that file-based YouTube stream going; it does not replace this MediaLive-to-YouTube configuration.
Troubleshooting receipt and connection errors
If MediaLive starts but YouTube shows no preview, work through the connection from source to receiver. Confirm the protocol is rtmps, not the default RTMP URL YouTube displays before you reveal the secure URL. Re-copy the host, port and path from Live Control Room, then check that the selected stream and key match. A key that was reset in YouTube must also be updated in MediaLive.
For an SSL or certificate error, first recheck that you copied the RTMPS URL by using the lock control in Live Control Room. Confirm that the protocol and server are consistent with that URL. YouTube’s RTMPS help says to try port 443 if an SSL error persists and the URL otherwise appears correct. Use the actual stream URL, not an illustrative hostname from documentation, and make any port change in the field that MediaLive provides.
For a timeout, verify the endpoint and port and confirm that the sending configuration supports RTMPS. A typo in the host or path can look similar to a general network failure, so compare the MediaLive fields with the copied URL character by character. If you change the port, record the original value so you can return to it if the symptom remains.
If YouTube rejects the stream or the preview never appears, check the stream key and destination mapping before changing encode settings. If the preview appears but the scheduled event is not public, check whether you have separately selected Go live. For a later symptom such as audio dropping after playback changes, the YouTube live audio troubleshooting guide covers a different encoder scenario, but it can help you distinguish a receiving problem from an audio continuity problem.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
Is RTMPS different from RTMP?
RTMPS is RTMP sent over a TLS/SSL connection, providing an encrypted connection. YouTube displays RTMP by default in its Stream URL field, so reveal and copy the RTMPS URL before configuring MediaLive.
Which MediaLive field takes the YouTube stream key?
Enter the key in the stream-name field for the RTMP output destination. Keep it paired with the URL for the same YouTube stream, and replace it in MediaLive if you reset the key in Live Control Room.
Does starting MediaLive make a scheduled YouTube stream public?
No. Starting MediaLive sends the output, and YouTube may show a preview when it receives the stream. For a scheduled broadcast, check that preview and then select Go live in Live Control Room.
Why does MediaLive ask for more than one destination?
The required count depends on the MediaLive channel class: AWS specifies two destinations for a standard channel and one for a single-pipeline channel. Check the actual values YouTube provides for the selected stream; do not assume it supplies two distinct endpoints.