AWS Business Support Pricing: 10% of Your Bill for a One-Hour SLA

AWS Business Support costs a percentage of your monthly AWS spend, on a sliding scale that starts at 10% and steps down as you spend more, with a $100 monthly minimum. So a $1,000 AWS bill means $100 for support, and a $10,000 bill means roughly $1,000. What you buy is a one-hour response SLA for production-down incidents, 24/7 access to engineers by phone and chat, and full Trusted Advisor. The real question is not whether it is expensive - it is whether you have any other plan for the night production is down and you cannot work out why.

Table of contents

• What it actually costs
• What you get, and what Developer does not give you
• The Trusted Advisor argument
• When it is genuinely not worth it
• The trap in the percentage model
• How this fits the rest of the stack
• FAQ

What it actually costs

Business Support is billed as a percentage of your monthly AWS usage, tiered:

• 10% of the first $0-10K of monthly spend
• 7% of $10K-80K
• 5% of $80K-250K
• 3% above $250K

With a $100/month minimum, which is the number that matters for small teams.

Worked examples:

$500/month AWS bill   ->  $100/month  (the minimum bites; effectively 20%)
$1,000/month          ->  $100/month  (exactly 10%)
$5,000/month          ->  $500/month
$20,000/month         ->  $1,000 + $700 = $1,700/month

Two things worth noticing.

The minimum is punitive at low spend. On a $300/month AWS bill, $100 of support is a third of your infrastructure cost. The percentage model assumes you are big enough for 10% to be a sensible number, and below roughly $1,000/month you are paying a flat fee that does not feel proportionate.

And support is charged on usage across the whole AWS Organization. If you have consolidated billing across multiple accounts, the support charge applies to the aggregate, not per account - which is good news, as it means the tiering works in your favour.

What you get, and what Developer does not give you

The tiers, honestly:

Basic (free) - documentation, forums, and account/billing support. No technical help. If your production is down, you are on your own with a search engine.

Developer ($29/month or 3% of spend, whichever is greater) - email only, business hours only, 24-hour response for system-impaired issues. Read that again: 24 hours, business hours only, email. There is no production-down SLA at all. Developer support is for asking questions during development, not for incidents.

Business (10% tiered, $100 minimum) - the real one:

• 1-hour response for production-down, 24/7.
• 15-minute response on business-critical is Enterprise, not this - do not confuse them.
• Phone, chat, and email, 24/7.
• Unlimited contacts, unlimited cases.
• Full Trusted Advisor - all checks, including the cost-optimisation and security ones that Basic hides.
• Support for third-party software interoperability (they will help you with your OS and common stacks, within reason).

Enterprise On-Ramp / Enterprise - 30-minute and 15-minute critical SLAs, a Technical Account Manager, and prices that start at $5,500 and $15,000/month respectively.

The cliff between Developer and Business is the important one. Developer sounds like support and is not: there is no path to a human at 3am, at any price, on that tier.

The Trusted Advisor argument

This is the part of Business Support that is easiest to undervalue and often pays for itself on its own.

Basic support gives you a handful of Trusted Advisor checks. Business gives you all of them - and the cost-optimisation category is the interesting one: idle load balancers, unattached EBS volumes, underutilised instances, Reserved Instance and Savings Plan recommendations based on your actual usage.

On a $5,000/month AWS bill, Business Support is $500/month. It is entirely routine for the cost checks to surface more than $500/month of genuine waste - the load balancer left behind by a decommissioned service, the 500GB EBS volume detached three months ago and still billing, the over-provisioned RDS instance sized for a launch that never came.

And the security checks - exposed S3 buckets, security groups open to 0.0.0.0/0, IAM keys that have not been rotated in two years - are the kind of finding where one hit justifies a year of the fee.

This reframes the purchase. If you are above roughly $3,000/month in spend and you have never done a serious cost-optimisation pass, Business Support plausibly pays for itself out of the waste it finds, and the incident SLA becomes something you get for free.

When it is genuinely not worth it

Do not buy it just because it exists.

Skip it when:

• Your AWS spend is under about $500/month. The $100 minimum is a fifth of your infrastructure cost, and at that size your architecture is probably simple enough that Stack Overflow genuinely is your support tier.
• The workload is not production, or downtime costs nothing. A dev account does not need a 1-hour SLA.
• You have deep AWS expertise in-house and have never opened a support case. Some teams genuinely never need it.
• You are on a managed platform where the platform vendor is the one who owns the incident.

Buy it when:

• You have production traffic, and an hour of downtime costs more than a month of support. For most businesses with paying customers, that arithmetic is not close.
• Nobody on the team has run AWS at this scale before, and the failure modes are unfamiliar.
• You are above roughly $3,000/month and have never run a cost-optimisation pass - Trusted Advisor alone likely covers the fee.
• You need someone to escalate to who can see the AWS side of the problem. When the question is “is this us or is this you”, only AWS can answer, and without Business Support you cannot ask.

That last point is the one that decides it. When an AZ is misbehaving and the status page still says green, Basic support gives you a forum post and hope.

The trap in the percentage model

The pricing model has a structural weirdness worth naming: your support bill scales with your waste.

Support is a percentage of spend. If your AWS bill is inflated by over-provisioned instances, forgotten volumes, and idle load balancers, you are paying 10% of that waste to AWS in support fees, on top of the waste itself.

A $10,000 bill where $3,000 is genuine waste means you are paying roughly $300/month in support charges on the waste alone.

The uncomfortable incentive: AWS charges you more for support the more you overspend, and the tool it gives you to find the overspend is inside the support plan you are paying for.

The practical response is not cynicism, it is sequencing. Clean up the obvious waste first - Cost Explorer is free and will show you the top line items, and unattached volumes and idle load balancers are visible without any support tier at all. Then buy support against the corrected bill.

The same logic applies as you grow: revisit the support tier when your spend changes materially, and remember the percentage steps down. Nobody at AWS will call to tell you that you have crossed into a cheaper bracket, but they will also not stop you from checking.

How this fits the rest of the stack

Whatever you decide here, the cost of the decision only shows up as a bill. The RunxBuild hosting calculator is the right place to model that before committing: the compute, the database, the storage, the bandwidth, the worker - each one is a separate line item, and the real cost of a platform is the sum, not the headline number. The RunxBuild dashboard is where the team sees the actual usage once it is running.

Useful related references:

• AWS NAT Gateway Pricing: $0.045/Hour + $0.045/GB and How to Cut It
• AWS S3 Pricing Calculator: Storage, Requests, and Data Transfer
• AWS vs GCP Pricing for Startups: Credits, Sustained Use, and the Real Cost
• Services on RunxBuild

FAQ

How much does AWS Business Support cost?

A tiered percentage of monthly AWS spend: 10% of the first $10K, 7% of $10K-80K, 5% of $80K-250K, and 3% above that, with a $100 monthly minimum. A $5,000 bill costs about $500/month in support; a $500 bill costs $100 because of the minimum.

What is the difference between AWS Developer and Business Support?

Developer is email-only, business-hours-only, with a 24-hour response target and no production-down SLA at all. Business gives you a 1-hour response for production-down issues, 24/7 phone and chat, unlimited cases, and full Trusted Advisor. If you need a human at 3am, Developer will not provide one at any price.

Is AWS Business Support worth it?

If you have production traffic and an hour of downtime costs more than a month of support, yes - that arithmetic is usually not close. Above roughly $3,000/month of spend, the full Trusted Advisor cost checks alone often surface more waste than the fee. Below about $500/month of spend, the $100 minimum makes it poor value.

Does AWS Business Support include Trusted Advisor?

Yes, all checks - including the cost-optimisation and security categories that Basic hides. Those checks routinely find idle load balancers, unattached EBS volumes, and over-provisioned instances, which is why the plan can pay for itself on a mid-sized bill.

Is the AWS support fee charged per account?

It is charged on aggregate usage across the AWS Organization when you use consolidated billing, not per account. That works in your favour, since the percentage tiers step down as total spend rises.