What Business Support+ costs on a $40,000 monthly cloud bill

Five plans on $8,000, $40,000 and $120,000 bills

On one AWS account with $40,000 of monthly charges, AWS Business Support+ bills $3,000 a month: 9 percent of the first $10,000, which is $900, and 7 percent of the remaining $30,000, which is $2,100. Developer Support and Business Support are discontinued on January 1, 2027. Business accounts pay less on Business Support+ and Developer accounts pay more, so the two should switch at different times.

Every AWS support plan bills whichever is larger, its monthly minimum or its banded total, and each band's rate applies only to the dollars inside that band. AWS's support plan pricing page lists Business Support+ at 9 percent up to $10,000, 7 percent to $80,000, 5 percent to $250,000 and 3 percent above that, with a $29 floor per account. Enterprise Support charges 10 percent up to $150,000 over a $5,000 floor. The same page lists Unified Operations, which starts at $50,000 a month and sits above this comparison. AWS dropped the three retiring plans from the page, so their rows use the rates it published for them in 2025.

Enterprise shows how the floors work. Ten percent of $40,000 is $4,000, below the $5,000 minimum, so the fee is $5,000, and it stays there until monthly charges pass $50,000. On-Ramp's $5,500 floor holds the same way up to $55,000.

Three results matter for January. Business Support+ costs less than Business at every bill size: $100 a month less above $10,000, because only the first band dropped a point, and its floor falls from $100 to $29. Developer accounts move the other way: at $40,000 the fee goes from $1,200 to $3,000, two and a half times what they pay now. For a single account, Business Support+ also costs less than Enterprise at every bill size, since its minimum is lower and its rate is equal or lower in every band. The gap is narrowest at $50,000, where Enterprise costs $1,300 more, and it reaches $2,000 at $40,000 and $4,200 at $120,000.

To price each account in a spreadsheet, put a month's charges in cell A2. For Business Support+:

=MAX(29, MIN(A2,10000)*0.09 + MAX(0,MIN(A2,80000)-10000)*0.07 + MAX(0,MIN(A2,250000)-80000)*0.05 + MAX(0,A2-250000)*0.03)

For Enterprise, A2 holds the total across every subscribed account:

=MAX(5000, MIN(A2,150000)*0.1 + MAX(0,MIN(A2,500000)-150000)*0.07 + MAX(0,MIN(A2,1000000)-500000)*0.05 + MAX(0,A2-1000000)*0.03)

Which accounts need Business Support+ before January 1, 2027?

AWS stopped taking new Developer and Business subscriptions on December 2, 2025, and it emails 30 days before it changes anything on an account.

Enterprise's minimum fell from $15,000 to $5,000, which is why On-Ramp accounts pay less after the switch. AWS GovCloud (US) keeps all three retiring plans.

A Developer account that drops to Basic loses technical cases entirely, because Basic allows only account and billing cases and service limit increases.

Business Support+ can be enrolled two ways in the Support Plans console. Choosing My organization from the management account, with all features enabled in AWS Organizations, subscribes the whole organization, and every account created in or invited to it afterward is subscribed automatically. An account enrolled that way drops to Basic if it leaves the organization. My account enrolls one account at a time.

Some teams plan to keep low-traffic accounts on Basic and upgrade when something breaks. The upgrade can be bought mid-incident, and each registration carries a one-month minimum charge. AWS also reserves the right to refuse support to any customer that frequently signs up and then cancels, so a habit of upgrading for incidents and downgrading afterward puts the account at risk.

Splitting one organization's spend across five accounts

Take a hypothetical payroll software company, Pellbrook Payroll, with $40,000 of monthly AWS charges spread across five accounts. Business Support+ is calculated per account, so each account starts again at 9 percent.

Held in one account, the same $40,000 costs $3,000. The $240 difference is 2 percentage points on the $12,000 sitting in the four smaller accounts, each billed at 9 percent where a single account would pay 7. Enrolled at the organization level, the management account and four sandboxes with almost no spend add the $29 floor each, which brings the total to $3,385. Enterprise bills its $5,000 on the aggregate of every subscribed account, however the spend is split.

An AWS Organization groups accounts for billing, and Business Support+ still computes each one separately. The common advice to consolidate under Organizations and buy support once pays off only on Enterprise.

Merging accounts to recover $385 a month would put production credentials in the same account as staging, CI runners and developer experiments. Keep the accounts and pay the $385. Enrolling account by account keeps the management account and sandboxes on Basic and saves $145, and then every new production account has to be enrolled by hand. The one somebody forgets reaches its first incident without technical cases.

For how the fee changes when one application leaves an account, see Counting engineer hours and support fees in cloud TCO.

Pull the fee base from Cost Explorer

From the management account, one query returns a month of charges for each linked account, split by charge type:

aws ce get-cost-and-usage \
  --time-period Start=2026-08-01,End=2026-09-01 \
  --granularity MONTHLY --metrics UnblendedCost \
  --filter '{"Dimensions":{"Key":"BILLING_ENTITY","Values":["AWS"]}}' \
  --group-by Type=DIMENSION,Key=LINKED_ACCOUNT Type=DIMENSION,Key=RECORD_TYPE \
  --query 'ResultsByTime[].Groups[].[Keys[0],Keys[1],Metrics.UnblendedCost.Amount]' \
  --output text

The end date is exclusive, so this window is August. Unblended cost books an upfront reservation fee on the day it is charged, which matches how AWS counts it for support. Filtering to the AWS billing entity drops AWS Marketplace charges, which the fee excludes. Grouping by record type puts credits, refunds, tax and the support fee on rows of their own. Leave those out and add up the rest, since the fee uses gross charges before discounts or credits.

Three adjustments remain. Accounts with Savings Plans return covered usage at on-demand rates next to negation rows that offset it, and AWS does not say which figure the fee base uses, so total it both ways. Bedrock Marketplace and Bedrock serverless purchases fall out with the Marketplace filter even though AWS counts them as Bedrock usage, so add them back. AWS Managed Services and AWS Professional Services arrive under the AWS billing entity and are excluded from the fee, so subtract them by service. Compare the result with the support line on that month's invoice before trusting it for other months.

Savings Plan and RI prepayments, counted in the purchase month

Upfront charges for Savings Plans, Reserved Instances and reserved nodes count in the month you buy them, and recurring charges in the month they are incurred. On a single $40,000 account, a $60,000 All Upfront purchase in March makes March's charges $100,000. Business Support+ for March comes to $6,800 instead of $3,000. The increase of $3,800 is $400 less than 7 percent of the purchase, because the last $20,000 of the month falls in the 5 percent band above $80,000. Enterprise's March fee is $10,000 instead of $5,000.

On Enterprise below $50,000 a month, that extra $5,000 never comes back. The minimum already applies in every other month, so lower usage later in the term leaves the fee at $5,000. A No Upfront or Partial Upfront purchase that keeps every month under $50,000 leaves it at $5,000 as well, so weigh the extra $5,000 against the larger discount All Upfront earns in your own quote. For Business Support+, comparing payment options depends on how Savings Plan covered usage enters gross charges, which AWS does not document, so price only the purchase month.

One more rule applies at sign-up. An account that starts a paid plan while holding reservations pays, in its first month, on their upfront charges prorated over each term. AWS does not say whether moving from Developer or Business to Business Support+ counts as signing up, so an account with large prepaid reservations should ask AWS billing before it switches.

Outside the support case: patching, restores and SQL Server fixes

A paid plan buys fast help with AWS's own layer. First-response targets are under 30 minutes for a business-critical system down case on Business Support+ and under 15 minutes on Enterprise, and 1 hour for production system down on both. AWS makes "every reasonable effort" to meet them. Raising a case to either of those severities means contacting AWS by web, chat or phone from the case, and the severity then stays fixed for 60 minutes, so open the case at the level the outage warrants. Business Support+ and Enterprise both include technical support at any hour.

Above that layer, the shared responsibility model gives EC2 customers the guest operating system, including updates and security patches. AWS Support excludes custom code development, software debugging, system administration and remote access to customer systems. Its third-party software support covers operating systems, web servers and databases on EC2 as guidance for experienced administrators, with no hands-on administration.

Take Pellbrook again. Its payroll API runs on EC2, with SQL Server on its own EC2 instance. During a month-end payroll run the transaction log fills its volume, and SQL Server raises error 9002: the database stays online and can only be read. Pellbrook opens a business-critical case. AWS's engineer can confirm that the EBS volume is healthy, explain how Elastic Volumes grows it in place, and point to Microsoft's guidance on error 9002.

The rest falls to Pellbrook's engineers, in this order:

1. Find what is holding the log. SELECT name, log_reuse_wait_desc FROM sys.databases; returns LOG_BACKUP for the payroll database, and the SQL Server Agent job that backs up its log has been failing since a credential change three weeks earlier. Check max_size and growth for the log file in sys.master_files as well. A log capped by its own maximum, or with autogrow off, fills before the disk does, and raising the cap is faster than growing the volume.
2. Back up the log to a volume with free space. The backup frees log space that no open transaction needs, and writes resume, though the file stays the same size. A log that has never been backed up needs two log backups before it truncates.
3. Grow the volume for headroom with aws ec2 modify-volume --volume-id vol-0example --size 400. The new size is usable once the modification reaches the optimizing state, usually within seconds. If Windows still shows the old size, rescan disks in Disk Management, then extend the partition with Resize-Partition -DriveLetter L -Size (Get-PartitionSupportedSize -DriveLetter L).SizeMax.
4. Repair the job's credentials, watch the next scheduled log backup succeed, and restore the latest full and log backups to a scratch instance to prove the chain.

Size the volume once, with room to spare. EBS allows four modifications to a volume in a rolling 24 hours, and each one has to reach completed before the next can start, so a second resize waits on the first. Every step in that list is system administration, the category the support case excludes. To give each of those tasks a named owner before the next incident, see the managed hosting responsibility matrix.

On our cloud, customers file database work, backups and restores as tickets, and one of our engineers does them. They also have names and phone numbers for people at Petrichor. What our engineers handle covers our side of that ticket.

When Enterprise earns its extra $2,000 a month

At $40,000 on one account, Enterprise Support costs $5,000 against Business Support+'s $3,000, or $24,000 a year more. The difference buys a designated Technical Account Manager, AWS Security Incident Response included where Business Support+ charges extra for it, a business-critical first response under 15 minutes instead of 30, and one fee on the total across accounts. Enterprise's $5,000 minimum also absorbs growth, since the fee stays flat until charges pass $50,000.

Pay for Enterprise when the named TAM, the faster first response or the included incident response changes an outcome you can put a price on. AWS itself calls Business Support+ its minimum recommended plan for production workloads, which makes it the default at this spend.

Aggregate billing seldom tips the decision at $40,000. Spread that spend across accounts that each stay under $10,000 and Business Support+ costs $3,600, and it takes 49 more enrolled accounts at the $29 floor before Enterprise's $5,000 is the cheaper bill.

DevOps Agent credits at 30 and 75 percent

Both plans now come with credits for AWS DevOps Agent. The credits come to 30 percent of the prior month's support charge on Business Support+ and 75 percent on Enterprise, issued by the 10th, usable only on that month's DevOps Agent usage, and expiring at month end. The agent bills $0.0083 per agent-second, or $29.88 an hour. At $40,000, that comes to $900 of credit on Business Support+, about 30 agent-hours, and $3,750 on Enterprise, about 125. Enterprise's $2,000 premium returns $2,850 more in credits, which is worth something only to a team that would run that many agent-hours anyway. Unused credits lapse, and none of them reduce the support fee itself.

RDS and DynamoDB versus SQL Server on EC2

A support plan is worth more when AWS runs more of the stack. For abstracted services such as S3 and DynamoDB, AWS operates the infrastructure, the operating system and the platform. RDS schedules required operating system patches itself and, on a Multi-AZ instance, applies them to the primary through a failover that typically lasts under a minute. Engine upgrades take primary and standby down together, except on RDS for SQL Server, which rolls them through a single failover. aws rds describe-pending-maintenance-actions lists what is waiting, and a required action carries an AutoAppliedAfterDate, after which it goes in during the next maintenance window. A case about an RDS failover reaches the layer AWS operates, so $3,000 a month buys more there than it does for Pellbrook. Teams in that position should buy Business Support+ and stay.

Self-managed SQL Server or Windows applications on EC2, and software written before the cloud, sit on the other side. Every step Pellbrook took after error 9002 lands on the team whatever plan it buys. We built our cloud to run software that was never designed for one. It runs on our own hardware, in one U.S. data center, so an application whose users need a second region should stay with AWS or Azure.