CloudCostCompareCloud support plans: how they are priced and when to buy
Short answer: every cloud includes basic support for billing and account questions. Help with technical problems is a paid plan, and it appears on the bill as its own line, often as a percentage of your monthly spend with a minimum fee. The more you spend, the more it costs, so it is a line to budget, not to forget.
Key points
- Basic support is free. Technical support is paid.
- Pricing is a share of spend with a minimum, or a flat fee.
- Response targets depend on severity and plan.
- Support grows as spend grows.
- Plan names and structures change, so use the vendor page.
How is support priced?
Most plans use one of two shapes:
- A share of monthly spend, with a minimum. The fee rises with your usage, usually with lower percentages on higher spend bands, and never falls below a set monthly amount.
- A flat monthly fee per plan. Easier to budget, but you pay it even in a quiet month.
Vendor pages: AWS Support, Azure support plans, Google Cloud Customer Care and Oracle support. AWS has announced a new plan lineup and retirement dates for some older ones, so confirm the current names before you budget.
What do I get as I move up?
| Level | Typical features |
|---|---|
| Basic or free | Billing help, documentation, health dashboards |
| Developer or standard | Technical questions by email, response in business hours |
| Business or professional | Round-the-clock help, faster response for production issues |
| Enterprise | A named contact, reviews and architecture help |
Response targets are by severity. A production-down case gets a faster response than a general question.
What does a worked example look like?
Made-up round numbers to show the method, not real plan prices. A plan charges the higher of a 100 minimum or 10 percent of the first 10,000 of spend, 7 percent of the next 20,000 and 5 percent above that.
| Monthly spend | Calculation | Support fee |
|---|---|---|
| 500 | 10% = 50, below the minimum | 100 |
| 5,000 | 10% x 5,000 | 500 |
| 25,000 | 10% x 10,000 + 7% x 15,000 = 1,000 + 1,050 | 2,050 |
| 60,000 | 1,000 + 7% x 20,000 (1,400) + 5% x 30,000 (1,500) | 3,900 |
At low spend the minimum dominates: a 500 bill pays 20 percent for support. At 60,000 the effective rate falls to 6.5 percent. Two lessons follow. A small team pays more in relative terms, and consolidating production onto one account where terms allow can lower the effective rate.
Should I buy one?
- Learning, tests, side projects. Basic is enough.
- A product with paying customers. Take the lowest plan with round-the-clock response before launch, then review it once you are stable.
- Regulated or large systems. Take the higher plan, and add a partner who knows the platform.
Support costs scale with spend, so it grows as you grow. A cloud estimate built from services alone leaves it out. Add it as a line in your budget.
How can I lower it?
- Buy support only on the accounts that run production.
- Check whether the fee is calculated on total spend, or on spend after credits and discounts.
- Use community channels and documentation for non-urgent questions.
- Review the plan once a year against the number of cases you opened.
Which mistakes are common?
- Paying for the top plan on a test account.
- Never opening a case, then paying for support for years.
- Forgetting support when forecasting spend growth.
- Assuming the fee is a flat amount.
Decision checklist
- How many production incidents did we have last year?
- Which accounts run production?
- Is the support line in the budget?
- When is the next plan review?
Next steps
See hidden cloud costs for the other extras that rarely make it into a plan, and FinOps basics for small teams for a routine that catches them.
Frequently asked questions
Is cloud support included in the price?
Basic support for billing and account questions is included on all four clouds. Help with technical problems is a paid plan, billed as its own line.
How is cloud support priced?
Usually as a share of monthly spend with a minimum, often with lower percentages on higher spend bands, or as a flat monthly fee per plan. Plan names and rates change, so check the vendor page.
Do I need a paid support plan?
Learning projects and tests do not. A product with paying customers usually needs a plan with round-the-clock response for production issues, at least around launch.
Is support billed on every account?
It depends on the cloud and plan. Some bill per account and others on the combined spend across accounts. Buy support only on the accounts that run production where the terms allow.
Are AWS support plans changing?
AWS has announced new plan names and structure and a retirement date for some older plans. Check the AWS support page for the current lineup before budgeting.