AWS does not document a separate charge for each MediaLive input-switch action. The added cost comes from the inputs attached to a running channel: AWS describes input-switching configurations as billed for two active inputs, so compare that setup with a one-input baseline and verify the rate for your channel.
That estimate is about MediaLive, not the complete cost of putting a live stream on YouTube. Your Region, input specification, channel class and running time affect the calculation, and YouTube-specific charges are not established by the AWS sources discussed here.
Is there a charge for each input switch?
The AWS pricing documentation describes charges for running channels and their attached inputs, not a fee for each time you schedule or execute a switch. In other words, the cost model to investigate is the channel configuration over its running period, rather than the number of times an operator changes the source.
This distinction matters if your programme moves between a studio feed, a backup feed, or scheduled segments. A channel that switches many times is not thereby shown to incur a corresponding series of switch-action fees in the cited AWS pricing description. That does not mean switching is cost-free: the inputs configured for switching affect the running input charges.
AWS also says a multiple-input channel needs scheduled input switches. Attaching several inputs does not make MediaLive move between them automatically, and there is no implicit main input. The schedule is an operational requirement for the intended behaviour, while the attached-input billing rule is a separate budgeting concern. See AWS’s guide to scheduling and switching inputs before planning the sequence.
For a YouTube channel, keep the scope clear. This estimate does not establish any YouTube fee, nor does it include other AWS services you might use around a stream. It isolates the MediaLive input cost so you can compare one-input and switching configurations without treating the result as an end-to-end quote.
How AWS bills attached inputs
AWS’s MediaLive pricing guide states that a running input charge applies to each input attached to a running channel. The guide includes inputs that are not currently active or receiving content. Consequently, an input that is present as a standby or alternate source can still matter to the bill while the channel is running.
This is why “only the source currently on air” is not a safe assumption for an estimate. If your channel has a primary source and a backup attached, the inactive state of that backup does not by itself remove it from the documented running-input charge. Check the actual billing treatment and current rate for your configuration in AWS’s MediaLive pricing guide.
The word “attached” is important. Think of the channel configuration as a set of inputs associated with a running channel, not simply the picture viewers see at a given moment. A scheduled switch changes which input is used; it does not necessarily change the fact that both inputs are attached to the running channel.
For example, a local news loop might use a scheduled programme feed for most of the day and keep a separate source ready for an interruption. The practical question is not just whether the backup was used; it is whether it remains attached while the channel runs and how AWS prices that channel arrangement. Similarly, a bhajan channel switching between two prepared playlists should budget from the switching configuration, rather than assuming the second input costs nothing when it is not selected.
AWS summarises the principle plainly: “There is a running input charge for each input that is attached to a channel that is running.” Use that as a prompt to inspect the configuration, not as a substitute for checking current rates and account-specific billing terms.
The two-input rule for switching
AWS’s pricing page says a channel configured for input switching is charged for two active inputs, even if its schedule contains more than two inputs. This is the central rule for a first-pass comparison: input switching has a two-input cost basis in the documented pricing description, rather than a charge for every switch action or an assumption that only the currently selected input counts.
If the schedule includes several alternate sources, do not multiply a guessed per-switch price by the number of scheduled transitions. Nor should you automatically multiply the input rate by every item on a long schedule. The pricing language identifies two active inputs for a switching channel even when more than two inputs are configured. Because AWS’s user guide also discusses charges for attached inputs, confirm how the rule applies to your precise configuration on the current pricing page or with AWS before relying on a final invoice estimate.
There is an operational distinction between having inputs available and actually arranging a switch. AWS’s schedule documentation says switching is scheduled; it is not triggered merely by attaching another input. If a transition needs to occur at a planned time, create the appropriate schedule action and test the event sequence. For a rapid transition, AWS documents an input prepare action that can reduce delay for an immediate switch. This is a timing aid, not a documented way to avoid the input charges.
The broader workflow may involve additional services, but this article does not estimate them. AWS’s live-streaming deployment guide, for example, discusses a wider solution beyond MediaLive; the components you choose can have their own costs. Likewise, the fact that MediaLive sends a feed towards YouTube does not establish YouTube’s charges. Keep your estimate’s boundary visible so an input comparison is not mistaken for a total operating budget.
Compare with a one-input baseline
A useful comparison starts with two otherwise equivalent channel cases: a single-input channel and a channel configured for input switching. Hold the Region, channel class, input codec, resolution, bitrate and running period constant as far as the intended design permits. Then compare the applicable hourly input charges under the current AWS pricing for each configuration.
| Estimate component | One-input baseline | Input-switching setup |
|---|---|---|
| Channel purpose | One source attached for the stream | Alternate sources are configured for switching |
| Input cost basis | Applicable input rate for the one-input configuration | AWS describes charges for two active inputs |
| Switch action count | Not applicable | Do not model as a fee for every action |
| Runtime | Use the channel’s billable running period | Use the same period to make the comparison meaningful |
| Rate inputs to verify | Region, specification and channel class | Same items, with the switching configuration checked |
In a straightforward estimate, the incremental amount is approximately one applicable input rate multiplied by the running period: the switching configuration uses a two-input basis against a one-input baseline. Treat this as a budgeting method derived from AWS’s stated model, not a guaranteed invoice calculation. Reservations, channel class, unusual input arrangements, minimums or changes to current pricing can change what you actually pay.
For a concrete planning worksheet, write down the channel’s intended Region and class, the codec, resolution and bitrate of each input, and the hours the channel will run. Get the relevant current rates from AWS for the chosen setup. Calculate the baseline and switching totals over the same period, then subtract the baseline from the switching estimate. If inputs differ materially in specification, do not assume their rates match; check the pricing treatment for each configuration.
This method is more useful than asking how many times the programme will switch. A stream that changes source frequently and one that changes only occasionally may have the same input configuration over a comparable running period. Their operational schedule differs, but the cited price description points the cost comparison towards the running inputs.
For readers weighing a managed, recorded-video approach against building an AWS workflow, the AWS live-streaming solution selection guide can help frame the architectural decision. If your alternative is a local computer running a playlist, the lightweight OBS alternatives for a continuous playlist stream are a separate comparison: local playback and MediaLive input switching are not identical operating models.
Estimate the running-period impact
Once you have an applicable hourly rate, multiply it by the channel’s billable running time to estimate the input component. For a month-long schedule, use the actual planned running period rather than assuming a universal month length; account for starts, stops, planned maintenance and any minimum or reservation arrangement shown in current AWS pricing. This produces a running-period estimate, not a complete YouTube delivery budget.
The increment over a one-input baseline is approximately one additional applicable input rate for the same period, subject to the configuration-specific pricing rules. It is not the hourly rate multiplied by the number of changes in the schedule. If a channel runs continuously, even a modest hourly difference can accumulate over a long period, so calculate with the hours relevant to your own schedule rather than relying on an isolated short test.
AWS’s live-streaming solution guide includes an HD AVC input example at $0.234 per hour in its stated US East (N. Virginia) scenario and under the guide’s encoding assumptions. That is an illustration from a particular example, not a universal or necessarily current quote for another Region, codec, bitrate, resolution or channel class. Do not use it as a price for your channel without checking the current AWS rate and matching assumptions. The example appears in AWS’s deployment planning guide.
The total AWS-side workflow may include services beyond MediaLive, depending on how you ingest, package, distribute or monitor video. The cited deployment example includes other AWS components, which makes clear that an input-only estimate leaves out potentially relevant line items. Conversely, this research does not establish YouTube-specific fees, so do not add an unverified YouTube cost to the MediaLive figure or present MediaLive as the entire YouTube streaming cost.
If a constant recorded loop is your actual requirement, compare the operational need before paying for switching capacity. A backup feed may be valuable if a live source can fail; scheduled variations may be useful for news, devotional programming or business updates. If a single prepared file is sufficient, a one-input design may be easier to reason about. For a non-AWS route based on a recorded lecture, the cloud-server cost comparison for a 24/7 lecture stream offers a different cost frame, but its assumptions should not be substituted for MediaLive rates.
Verify rates for your channel configuration
Before approving a budget, confirm the current price against the exact configuration. Start with the AWS MediaLive pricing page and identify the Region, channel class and input attributes that correspond to your deployment. AWS says input rates depend on details such as codec, resolution and bitrate; channel class also changes the rate basis. A generic figure found in an example is not enough to price a different setup.
Check whether the current pricing page or calculator reflects any applicable minimums, reservations or account-specific arrangement. Then verify how your schedule and attached inputs map to the billing description. This is particularly important if you have more than two inputs, use unusual specifications, or have a design that changes configuration during the running period. The documentation gives the general rule, but your estimate should reflect the actual channel you intend to run.
Keep two columns in your working budget: the one-input baseline and the switching configuration. Record the source and date of every rate you use, the time basis, and the assumptions that make the comparison fair. When AWS updates pricing, or you change the Region or input specification, refresh both columns rather than adjusting only the difference. A small spreadsheet is often enough to reveal whether a quoted total includes just MediaLive inputs or additional services as well.
Finally, test the operational plan separately from the cost estimate. Confirm that scheduled actions select the intended source and that a prepared input behaves as expected for any time-sensitive switch. AWS’s input preparation documentation describes how preparation can reduce delay for an immediate switch. It does not turn a budget estimate into a guarantee of uninterrupted output, and it does not establish a separate fee or a billing exemption.
If the main difficulty is keeping a prerecorded channel running after a local playlist or computer fails, consider whether your need is really MediaLive input switching. StreamNeo takes the burden of keeping a computer on and restarting a dropped broadcast out of that particular workflow by turning an uploaded video into a YouTube live stream; it is YouTube-only and does not replace a multi-input live production setup.
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
Do I pay every time the schedule switches inputs?
AWS’s cited pricing description does not list a separate per-switch action fee. It describes charges for inputs on a running channel and says input-switching channels are charged for two active inputs. Verify the live pricing page for your configuration before treating an estimate as final.
Does an inactive backup input still cost money?
AWS’s user guide says a running channel incurs a charge for each attached input, including an input that is not currently active or receiving content. Do not assume that a standby source is free while attached. Check the exact treatment and applicable rate for your channel.
If my schedule has more than two inputs, should I budget for every one?
AWS’s pricing page describes a two-active-input charge for a channel configured for switching even when more than two inputs are configured in the schedule. The general documentation should not replace a configuration-specific check, particularly for unusual arrangements. Confirm the current rule against your channel in AWS pricing.
Is the MediaLive input estimate the full cost of a YouTube stream?
No. It is only an estimate of the MediaLive input component, and AWS’s wider streaming examples can include other services. The sources used here do not establish YouTube-specific fees, so check current official information and keep other services separate in your budget.