There is no single monthly price for AWS Elemental MediaLive from “24/7 YouTube channel in India” alone. Your estimate depends on the actual inputs, outputs, channel class, add-ons, running time and AWS Region; GST is a separate invoice question tied to the billing entity and payer details.
Build the configuration in AWS Pricing Calculator using the Region you intend to run in, such as Mumbai, then check the resulting AWS estimate and the tax treatment on the payer’s invoice. AWS’s published examples discussed here use US East, so they are not a Mumbai quote.
Why the title is not enough to price a month
MediaLive is metered by configured components rather than sold as one flat “24/7 YouTube” monthly fee. AWS says to add the charges for each input, output and enabled add-on. A channel can continue to accrue charges while it is running even if an input is not receiving content or an output is not producing it. That distinction matters for an always-on channel: quiet hours are not necessarily unbilled hours.
The title does not tell you whether the source is pushed into AWS or pulled from elsewhere, how many inputs are attached, which codec and bitrate are used, how many output variants are configured, or whether the channel needs a single or standard pipeline. It also says nothing about resolution, frame rate, advanced audio, motion graphics, the Region, or any separate packaging and delivery services. Each missing choice can affect the estimate or its scope.
The monthly result should therefore be labelled clearly. “MediaLive-only” means the configured MediaLive components, not every service needed to deliver a stream to viewers. A broader workflow may include packaging, origin, storage, transfer or a CDN, depending on how it is designed. YouTube’s ingest and viewer-side arrangements are distinct from those AWS service charges. AWS’s MediaLive pricing page describes the billable components and pricing examples; use the calculator for your configuration rather than borrowing an example total.
Write down the source and encoding assumptions
Before opening the calculator, document what you will actually send to MediaLive. Record the number of attached inputs and their source type, protocol or workflow, codec, resolution and bitrate. If you are feeding a pre-encoded video loop, specify the format and settings of that feed rather than treating the original file as the input. If a person or software package encodes the file before transmission, that encoder is a separate part of the workflow and should not be silently included in a MediaLive estimate.
Bitrate and codec are not interchangeable details. Two feeds with the same resolution can use different codecs and bitrates, and the pricing configuration must reflect the actual selection. An estimate based on an assumed HD input is not useful if the live contribution is configured differently. For a channel with a fixed library of videos, first confirm how that material will reach the input and whether any transformation or storage services sit before MediaLive.
Include the input count as it will be attached during operation, not merely the number actively selected at a particular moment. AWS notes that input switching can affect how many inputs are billed, and that a running attached input can incur charges even while it is not receiving content. Push inputs may also have idle-resource charges when unused; AWS says pulled inputs do not incur that idle-input charge. Check the current pricing and resource behaviour for the input arrangement you choose.
If you are building a local workflow before moving it to AWS, keep the broadcast method and the cloud estimate separate. The practical details in our guide to starting an FFmpeg YouTube stream automatically when a PC boots help identify what a local encoder handles, but they do not determine MediaLive’s AWS rate. Likewise, a continuous Malayalam video playlist workflow can help you plan content rotation without assuming that the playlist format sets the cloud input price.
Count outputs, ladder variants and add-ons
List every output configured in the channel. If you create a multi-resolution ladder, count each variant separately and note its codec, resolution, bitrate and frame rate. A single high-quality output and a ladder with several renditions are not the same estimate. The exact available selections and their prices need to be checked for the chosen Region in the calculator.
Set frame rate explicitly when the workflow requires a particular rate. AWS notes that if frame rate is left to initialise from the source, MediaLive may provision the greater-than-30-fps pricing tier. That can matter if a source has a higher frame rate than the output you intended. Confirm the setting in the channel configuration and carry the same assumption into the estimate rather than leaving the calculator’s configuration ambiguous.
Add only features you intend to enable. AWS identifies advanced audio, audio normalization and motion graphics among features that can add channel cost. If you do not need an add-on, do not include it as a precautionary allowance; if the channel uses one, do not omit it to make a headline estimate look smaller. Keep a short configuration note alongside the estimate so another person can see what was priced.
| Estimate choice | What to record | Why it changes the comparison |
|---|---|---|
| Input | Count, type, codec, resolution and bitrate | The input configuration contributes to the MediaLive total; attached idle resources may matter |
| Output | Each codec, resolution, bitrate and frame rate | Every configured output contributes, and a ladder has multiple components |
| Add-ons | Audio and graphics features actually enabled | Optional channel features can add charges |
| Runtime | Hours the channel is running | A continuous channel accrues charges across its running time |
| Scope | MediaLive-only or wider workflow | Packaging and delivery services are separate line items |
A good working sheet has one row per input and output, plus a separate note for add-ons. This prevents the common mistake of entering a single “stream” and assuming that it represents all variants. It also lets you test a change, such as removing an output or changing its codec, without losing the baseline configuration.
Choose channel class and AWS Region
AWS describes single-pipeline as using one processing pipeline in one Availability Zone, while standard uses two pipelines in different Availability Zones for added resiliency. The two channel classes have different rates. Choose based on the failure tolerance your channel needs and the configuration you are prepared to operate; do not assume the standard class is required for every YouTube loop or that single-pipeline provides the same redundancy.
Select Mumbai in the calculator if that is the Region you plan to use. The region selection is an input to the estimate, not a cosmetic label. The AWS examples referenced in its pricing materials are for US East (N. Virginia), and they must not be carried across as a Mumbai price. A different Region may be appropriate for a particular workflow, but compare it by entering that Region and its configuration directly.
For context only, AWS’s page gives a US East example involving a standard channel, two HEVC HD inputs, five AVC outputs and advanced audio, with an hourly on-demand figure. It also presents a separate 30-day reserved example for a specified configuration. Neither example is a forecast for your channel or a Mumbai quotation. Even multiplying a US East hourly example by a month would not turn it into an India estimate, and the configurations in examples may not match yours.
If considering a 12-month commitment, compare the matching component reservations and the on-demand estimate rather than treating the advertised maximum saving as guaranteed. AWS says reserved pricing can be used for channels running more than 180 hours a month and describes savings of up to 75% against on-demand for inputs, outputs and add-ons. The wording is a maximum, not a promise for your configuration; reserved components are billed for each hour of each month in the commitment. Check the current terms before committing. A channel with changing requirements may value flexibility over a lower configured rate.
Build an account-specific estimate in AWS Pricing Calculator
Use AWS Pricing Calculator to build the estimate rather than transcribing a public example. Treat it as a model of the configuration you enter, not an invoice guarantee. Start with the actual Region and MediaLive channel class, then enter each input and output with its relevant type, codec, bitrate, resolution and frame rate. Add the features you will run and set the usage period to reflect the channel’s real operating schedule.
For a genuinely continuous channel, model the full running schedule, including periods when no one is watching or an upstream feed is temporarily quiet. Review any attached input that is not active all the time and determine whether it is push or pull, because idle resource treatment can differ. If your channel is not intended to run continuously, use its actual hours rather than calling it 24/7.
Keep on-demand and commitment cases as separate estimates. For a commitment case, make sure each reservation corresponds to the components in the configuration; do not apply a blanket discount to the whole service. Save the assumptions with a date and a short label, for example “Mumbai, standard, two configured outputs, on-demand, MediaLive-only”. The label is more useful than an unexplained figure when settings change or someone else reviews the estimate.
The calculator’s MediaLive result is not automatically the cost of the complete broadcast. If your architecture needs MediaPackage, storage, data transfer or CloudFront, estimate those services separately and state the assumptions. AWS’s Live Streaming on AWS guide illustrates a workflow with MediaLive, MediaPackage and CloudFront as distinct cost components. Its event example is not a price for your India channel, but it is a useful reminder to keep service boundaries visible.
Viewer delivery is a separate planning question from the MediaLive encoding subtotal. A YouTube stream’s distribution to YouTube viewers is not the same thing as operating an AWS CDN for those viewers; do not add CloudFront by default or omit it if your chosen architecture actually uses it. Work through the delivery path, audience assumptions and any other services deliberately. For a broader operating comparison, our article on 24/7 YouTube streaming VPS options in India can help frame where a continuously running computer fits, but it does not replace an AWS calculator estimate.
Check the payer invoice and GST treatment
“Cost with GST” cannot be resolved from the channel Region or the operator’s physical location alone. AWS’s India tax guidance, last updated March 2026, says AWS India charges GST on cloud-service sales to customers in India. It describes 9% CGST plus 9% SGST for Delhi customers and 18% IGST for customers in other states. The same guidance distinguishes purchases from Amazon Web Services, Inc. outside India and describes treatment for OIDAR and registered business customers. Confirm the contracting seller and the payer’s actual tax profile against the current AWS tax page and invoice.
For a limited illustration, if 18% GST applies to the taxable AWS subtotal, multiplying that subtotal by 1.18 gives a tax-inclusive amount. For the Delhi AWS India case described by AWS, 9% CGST plus 9% SGST also sums to 18%. This is an arithmetic example, not a determination that a particular invoice is taxable in that way, and it does not establish a fixed monthly total. The taxable base and applicable treatment must come from the actual billing arrangement.
If the payer is a registered Indian business, AWS directs business customers to update the GSTIN and registered address in tax settings for the payer and linked accounts. Check that the details used to issue the tax invoice are correct before relying on an estimate. Whether a business can claim input tax credit depends on local law and its circumstances; a tax-inclusive cash payment and the ultimate tax cost need not be the same. Ask your finance or tax adviser where your situation requires interpretation.
The official AWS India tax help page is the appropriate place to verify the current seller-specific guidance. Do not add an assumed GST amount to a calculator subtotal and present it as a final invoice price when you have not checked the payer, seller and tax settings. The calculator helps estimate service usage; the invoice confirms what AWS actually billed and how tax was applied.
Keep the estimate current and label its scope
An estimate is a snapshot of a configuration and the pricing available when you built it. Revisit it when you change Region, channel class, input count, codec, bitrate, output ladder, frame rate, add-ons or operating hours. Refresh it when AWS pricing changes, and check tax guidance again before publication or budgeting decisions. Record the date, currency and whether the view is on-demand or commitment-based so that a later estimate can be compared fairly.
Keep a “MediaLive-only” number separate from the wider workflow total. If you add packaging, storage or delivery services, show them as distinct items with their own assumptions. That makes it clear whether a rise came from more outputs, a different channel class, an extra service or a tax line. It also prevents a team from using a MediaLive subtotal as the budget for an entire streaming operation.
Operational choices affect what you need to price. A local machine that must remain powered on and recover after interruption has a different operating burden from an approach where the source is delivered to a cloud service. For a local workflow, keep a recovery plan: our guide to fixing FFmpeg reconnect errors on a 24/7 meditation stream in India covers one class of continuity issue. If keeping a computer switched on and restarting a dropped broadcast is the specific burden you want to remove, StreamNeo turns an uploaded file into a 24/7 YouTube stream without needing your computer to stay on.
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
How much does AWS Elemental MediaLive cost per month?
There is no universal monthly figure: the total depends on the running inputs, outputs, add-ons, channel class, Region and usage. Enter your actual configuration in AWS Pricing Calculator and label the result as MediaLive-only or a wider workflow estimate.
What is the cost of running a 24/7 live stream on AWS in India?
Start by pricing the MediaLive configuration in the Region you plan to use, such as Mumbai, then estimate any other AWS services the architecture requires. The AWS examples cited here are US East examples, not an India or Mumbai quote, so do not use them as a substitute for a calculator result.
Does AWS charge 18% GST on MediaLive?
AWS’s India tax guidance describes 18% GST in the cases it covers, split as IGST or as CGST and SGST for the stated AWS India customer situations. The seller, payer tax settings and invoice determine the relevant treatment; check the current AWS tax page rather than assuming the same outcome from your location alone.
Is AWS MediaLive cost separate from CloudFront?
Yes, the MediaLive estimate covers its configured inputs, outputs and add-ons, while CloudFront is a separate service if your architecture uses it. Packaging and delivery costs should be estimated separately as well, rather than presented as part of a MediaLive-only subtotal.