AWS Enterprise Support: Pricing, Value, and Negotiation Guide 2026

The AWS Support Tier Landscape in 2026

AWS restructured its support plan lineup significantly in late 2025, reducing minimum pricing, renaming tiers, and discontinuing the Enterprise On-Ramp tier that sat between Business and Enterprise. Understanding these changes is critical for any enterprise currently on a pre-2026 support plan or approaching a renewal.

The Four Tiers (Post-2025 Structure)

Basic Support is included with every AWS account at no charge. It provides customer service access for billing and account questions, AWS documentation, whitepapers, and support forums. It does not include technical support cases, trusted advisor checks beyond the basic seven, or any form of proactive guidance. Basic Support is not suitable for any production workload.

Developer Support is intended for development and test environments. Pricing starts at $29 per month (the greater of $29 or 3 percent of monthly charges). Business-hours access to Cloud Support Engineers is provided via email, with general guidance response times of less than 24 hours and system-impaired responses within 12 business hours. Developer Support provides no TAM, no Trusted Advisor automation, and no production workload SLAs.

Business Support+ (formerly Business Support) is the first tier suitable for production workloads. Pricing is $29 minimum, scaled at 9 percent of charges up to $10,000 per month, 7 percent from $10,000 to $80,000, 5 percent from $80,000 to $250,000, and 3 percent above $250,000. Business Support+ provides 24/7 phone, chat, and email access, production system-down response within one hour, and access to all Trusted Advisor checks. Critically, Business Support+ does not include a designated Technical Account Manager.

Enterprise Support is the premium tier, with a minimum of $5,000 per month (reduced from $15,000 in the previous structure), scaled at 10 percent of charges up to $150,000, 7 percent from $150,000 to $500,000, 5 percent from $500,000 to $1,000,000, and 3 percent above $1,000,000. Enterprise Support provides all Business Support+ features plus a designated Technical Account Manager, 15-minute response for business-critical system-down cases, AWS Security Incident Response at no additional cost (added in the 2025 restructure), and access to Infrastructure Event Management for major product launches and migrations.

Enterprise On-Ramp Discontinuation

AWS discontinued Enterprise On-Ramp for new customers as part of the 2025 support plan restructure. Existing Enterprise On-Ramp customers will be automatically upgraded to full Enterprise Support during contract renewal throughout 2026, with notifications sent approximately 30 days before the upgrade. If you are currently on Enterprise On-Ramp, your support costs will change at your next renewal — and this creates a negotiation moment. The transition should not be treated as an automatic acceptance of the new pricing terms.

Enterprise Support Pricing Mechanics in Detail

The percentage-based pricing structure means that Enterprise Support cost scales automatically with your AWS spend — and without action, it grows faster than your discount programme reduces it. Understanding the mechanics is essential for modelling your support cost trajectory.

The Tiered Rate Calculation

For a company spending $800,000 per month on AWS, the Enterprise Support calculation works as follows: 10 percent of the first $150,000 equals $15,000. Seven percent of $150,000 to $500,000 ($350,000) equals $24,500. Five percent of $500,000 to $800,000 ($300,000) equals $15,000. Total: $54,500 per month, or $654,000 per year. This represents 6.8 percent of total AWS spend — a significant cost centre that many enterprises treat as non-negotiable overhead.

The $5,000 monthly minimum matters most for organisations with highly variable AWS spend. If your monthly AWS bill drops below $50,000 (10 percent of which is $5,000), you pay the minimum rather than the percentage. For organisations with seasonal workloads that include low-spend months, the effective annual support rate can be higher than the nominal percentage implies.

What Changed in the 2025 Restructure

The reduction in Enterprise Support minimum from $15,000 to $5,000 per month is significant for smaller enterprises that were previously paying $180,000 per year for the privilege of having a TAM regardless of their actual AWS spend level. However, the addition of AWS Security Incident Response as an included feature (previously sold as a separate add-on) partially offsets the pricing reduction for organisations that had purchased SIR separately. The net cost impact depends on your specific configuration and prior add-on purchases.

The Technical Account Manager: What You Actually Get

The TAM is the primary differentiator between Business Support+ and Enterprise Support. Understanding what a TAM actually delivers — versus what AWS's sales narrative promises — is essential for evaluating whether Enterprise Support is worth the premium for your organisation.

The TAM's Core Functions

A Technical Account Manager serves as a designated, named point of contact within AWS who understands your specific environment, architecture, and business objectives. Their primary activities include proactive architectural reviews, Well-Architected Framework assessments, event-driven operational support (major product launches, planned failover tests, migration events), and regular cadence calls to surface AWS service updates and roadmap items relevant to your workload.

TAMs also serve as internal AWS advocates — escalating issues within AWS support, connecting you with specialist solution architects, and facilitating introductions to AWS service teams when your use case requires input that goes beyond standard support channels.

The Cost Optimisation Value

AWS data indicates that Enterprise Support customers with active TAM engagement see more than 15 percent cost savings across select services compared to customers on other support tiers with similar AWS spend. This reflects the TAM's role in identifying Right Sizing opportunities, flagging underutilised Reserved Instances, recommending Savings Plan coverage adjustments, and surfacing cost anomalies before they compound.

For a company spending $1M per month on AWS, a 15 percent cost reduction represents $150,000 per month in savings — a figure that exceeds the Enterprise Support cost by a significant margin. However, this outcome requires active engagement with your TAM, not passive receipt of quarterly reports. The value delivered by a TAM is proportional to the quality of the relationship and the frequency and depth of engagement.

TAM Coverage Limitations

A critical limitation that AWS does not emphasise in its Enterprise Support marketing: TAMs typically carry portfolios of 20 to 60 enterprise accounts. Your designated TAM is not exclusively dedicated to your organisation. Response times for non-critical TAM engagements (architecture reviews, planning discussions) depend on TAM workload and scheduling availability, not SLA commitments.

For organisations with complex, high-velocity architectural work, the TAM relationship should be supplemented with dedicated AWS solution architect engagements, AWS Professional Services contracts, or third-party MSP support. TAMs provide strategic guidance and coordination; they are not a substitute for dedicated implementation resources. Our guide to AWS Enterprise Support vs Business Support compares what each tier actually delivers across each use case category.

AWS Enterprise Support and the EDP Relationship

Enterprise Support has a specific and important relationship with the AWS Enterprise Discount Program that enterprise buyers must understand.

EDP Mandates Enterprise Support

AWS requires that customers on an Enterprise Discount Program (EDP) maintain Enterprise Support for the duration of the commitment period. This is non-negotiable as a condition of EDP eligibility — you cannot hold an active EDP without Enterprise Support. This means EDP customers have no option to downgrade to Business Support+ during the EDP term, regardless of changes in their TAM engagement level or support utilisation.

The practical implication is that Enterprise Support costs are locked in for the EDP commitment period. The negotiation point is not whether to have Enterprise Support, but what the support commitment terms are — and whether the support level can be negotiated as part of the broader EDP terms.

Negotiating Support Within the EDP

Enterprise Support pricing is, in principle, subject to negotiation within the EDP framework. AWS sales teams have flexibility to offer discounts on support costs as part of comprehensive EDP deals, particularly for:

• Customers committing to multi-year EDP terms (three years or longer).
• Customers agreeing to AWS Marketplace minimum spend commitments that partially offset the EDP commitment.
• Customers increasing their overall EDP commitment level at renewal.
• Customers who can demonstrate that the support cost as a percentage of EDP spend is disproportionately high relative to benchmark rates for similar-sized customers.

The most effective negotiating position is to present a detailed breakdown of your Enterprise Support cost as a percentage of total AWS spend, compare it against the published tier percentages, and make the case that your actual support utilisation (cases filed, TAM hours consumed, Trusted Advisor engagement) does not justify the cost at list price. AWS will rarely volunteer a support discount but will negotiate when presented with a reasoned commercial case. See our dedicated guide on AWS Enterprise Support discount negotiation for specific tactics.

The Business Case for Enterprise Support: When It Is and Is Not Worth the Premium

Enterprise Support represents good value for some AWS customers and poor value for others. The decision framework requires honest assessment across four dimensions.

When Enterprise Support Is Worth It

Mission-critical production workloads where downtime cost exceeds $10,000 per hour. The 15-minute response time for business-critical system-down cases and the TAM's ability to escalate internally within AWS are worth the premium when the cost of slow incident response is measured in tens or hundreds of thousands of dollars.

Organisations with limited internal AWS expertise. The TAM's proactive architectural guidance, Well-Architected reviews, and access to specialist solution architects provide genuine value for organisations without mature internal cloud engineering teams. The external expertise translates directly to avoided incidents and optimised architecture decisions.

High-velocity migration and modernisation programmes. Infrastructure Event Management — available only with Enterprise Support — provides dedicated operational support for major events including cloud migrations, datacenter decommissions, and major product launches. For organisations in active migration programmes, this service alone can justify the Enterprise Support premium.

Regulated industries with security incident response requirements. The inclusion of AWS Security Incident Response (previously a paid add-on) in Enterprise Support is particularly valuable for financial services, healthcare, and government customers who require a structured incident response process with AWS involvement.

When Enterprise Support May Not Be Worth It

Organisations with sophisticated internal cloud engineering teams that rarely file support cases and manage their own architectural governance may find that Business Support+ provides adequate operational coverage at significantly lower cost. If your TAM engagement is minimal — quarterly calls and occasional architecture reviews — the value delivered does not justify a $60,000 to $200,000 annual premium over Business Support+.

Non-production and development account portfolios that are on Enterprise Support because EDP requires it but host no production workloads are paying Enterprise Support cost for capabilities they do not use. This is a common situation for enterprises that consolidate all accounts under a single EDP payer — the EDP requirement applies at the payer account level, which means all linked accounts are effectively on Enterprise Support pricing.

Organisations whose workloads are predominantly on Reserved Instances or Savings Plans will find that the support cost percentage applies to total monthly charges including RI/SP commitments, even though RI/SP purchases typically generate fewer support issues than equivalent on-demand workloads. Your RI and Savings Plans optimisation strategy affects your effective support cost.

The AWS Support Plan Negotiation Playbook

AWS support costs are negotiable, but you need the right approach, the right timing, and the right data to be effective. The following playbook reflects our experience across hundreds of AWS contract negotiations.

Step 1: Establish Your Support Cost Baseline

Before any negotiation, calculate your exact Enterprise Support cost for the past 12 months. Break this down by month, identify any spike months where the percentage calculation drove unusually high support costs, and calculate the effective annual percentage of your total AWS spend. This data forms the foundation of every negotiation argument that follows.

Step 2: Audit Your Support Utilisation

Pull the number of support cases filed in the past 12 months, categorised by severity level. Calculate the total cost per case filed. Review TAM engagement logs — how many proactive calls, architecture reviews, and event management engagements occurred. Calculate the cost per TAM interaction. This analysis typically reveals that the support cost per unit of value received is significantly higher than AWS's implicit pricing suggests.

Step 3: Identify Your Negotiation Window

The optimal time to negotiate Enterprise Support terms is either at EDP renewal (typically 60 to 90 days before the commitment period ends) or at the start of a new EDP for organisations not yet on EDP. AWS account teams have pricing flexibility in their EDP renewal conversations that they do not have mid-term. Attempting to negotiate support costs outside of an EDP renewal context is possible but significantly harder.

Step 4: Build the Commercial Case

The most effective negotiation argument combines three elements: the absolute dollar amount of support cost (which AWS may be willing to reduce to retain the overall relationship), the support cost as a percentage of total AWS spend (compared against benchmark rates for organisations of similar size), and your EDP commitment trajectory (demonstrating growth that justifies improved terms). The AWS support plan negotiation guide provides detailed tactics for each element of this commercial case.

Step 5: Request Specific Support Credits and Commitments

The ask in an AWS support negotiation is not typically a direct reduction in the tiered percentage rate. AWS is reluctant to alter the published tier structure for individual customers because it creates precedent. The more effective approach is to request:

• Support credits applied against your EDP commitment balance.
• An agreed minimum level of TAM engagement (monthly strategy calls, quarterly Well-Architected reviews, annual security review).
• Access to specialist solution architects for specific workload categories (AI/ML, security, cost optimisation) on a defined cadence.
• Infrastructure Event Management coverage for planned events in the next 12 months.
• Custom SLAs for non-critical case categories relevant to your operations.

Marketplace and EDP Interaction with Support Costs

AWS Marketplace purchases present a nuance in support cost calculations that enterprises frequently misunderstand. Marketplace charges processed through your AWS bill count toward your EDP commitment balance — but the support cost percentage calculation may or may not include Marketplace charges depending on your specific PPA terms. Our AWS Marketplace procurement strategy guide covers how Marketplace spend interacts with EDP and support cost calculations.

Some enterprises use strategic Marketplace spend to reach higher EDP discount tiers faster, which has the secondary effect of reducing the effective support cost percentage — because higher-tier EDP discounts apply to the same support cost base. This is a legitimate optimisation strategy, but it requires modelling the interaction between Marketplace commitment offsets, EDP discount thresholds, and support cost percentages before committing.

Multi-Account Architecture and Support Cost Optimisation

Enterprise AWS deployments typically involve multiple AWS accounts — business units, environments (production, development, staging), and projects. The support cost structure affects multi-account architectures in specific ways that can be optimised.

Consolidated Billing and Support Cost Pooling

Under AWS Consolidated Billing, all linked accounts within an AWS Organization contribute their monthly charges to the support cost calculation for the payer account. This means a payer account with $500,000 in monthly linked account charges pays Enterprise Support based on the total $500,000, rather than each individual account paying its own tier rate. For organisations with multiple small accounts that would individually fall below the minimum, consolidated billing typically increases the effective support cost.

Separating Non-Production Accounts

Some enterprises manage non-production accounts under separate payer accounts with Business Support+ or Developer Support, rather than consolidating them under the EDP payer account. This is structurally possible but creates operational complexity — separate billing, separate TAM relationships (or none), separate Trusted Advisor configurations. Whether the cost saving justifies the operational overhead depends on the volume and nature of non-production spend.

Third-Party Support Alternatives and MSP Supplements

Some enterprises supplement or partially replace AWS Enterprise Support with third-party managed service providers or independent AWS support specialists. The AWS third-party support alternatives guide covers this landscape in detail, but the key principle is that third-party support supplements rather than replaces native AWS support — particularly for EDP customers where Enterprise Support is contractually required.

The most common use case for third-party supplementation is depth of expertise in specific AWS service categories (container orchestration, ML infrastructure, data platform) where the TAM's generalist knowledge is insufficient for the technical complexity of the workload. Dedicated AWS MSPs can provide specialist engineering support that goes beyond what a TAM is positioned to deliver.

AWS Support Plan Comparison: Sub-Pages in This Guide

This pillar guide is supported by a set of detailed sub-pages covering specific aspects of AWS Enterprise Support:

• AWS Enterprise Support vs Business Support: Is the Premium Worth It — a detailed comparison of what each tier delivers and the decision framework for choosing between them.
• AWS Enterprise Support Discount: How to Negotiate Below List Price — the specific negotiation tactics, timing, and asks for reducing Enterprise Support costs.
• AWS TAM Value: What You Get and What to Demand — how to maximise the value of your TAM relationship and what to push for beyond the default engagement model.
• AWS Third-Party Support Alternatives to AWS Enterprise Support — when and how to supplement or replace AWS native support with MSP coverage.

Data Transfer Costs and Support Plan Strategy

One dimension of AWS Enterprise Support value that is often overlooked is its role in data transfer cost optimisation. TAMs are well-positioned to identify inter-region and egress cost inefficiencies through their visibility into your architecture and billing. Enterprises that proactively use their TAM for data transfer cost reviews often find that the TAM engagement pays for itself through identified savings alone. Our analysis of AWS data transfer and egress negotiation covers how transfer cost reduction fits within the broader EDP negotiation framework.

Ten Priority Actions for Enterprise Support Decision-Makers

1. Calculate your actual Enterprise Support cost as a percentage of total AWS spend for the trailing 12 months. Include all linked accounts in the calculation.

2. Audit TAM engagement frequency and quality in the same period. What proactive engagements occurred, and what tangible outcomes did they produce?

3. Evaluate whether Enterprise On-Ramp transition terms are being applied correctly if you are an existing On-Ramp customer approaching 2026 renewal.

4. Model the support cost impact of EDP commitment levels. Determine whether increasing your EDP commit level changes your effective support cost percentage through higher-tier discounts.

5. Assess your support case severity distribution. If the majority of your cases are General Guidance or System Impaired severity, the 15-minute response SLA of Enterprise Support may be providing no incremental value over Business Support+.

6. Build the negotiation case for your next EDP renewal using support cost benchmarks, utilisation data, and commitment trajectory.

7. Evaluate Infrastructure Event Management needs for planned events in the next 12 months. IEM is an Enterprise Support-exclusive benefit that may justify the tier independently for migration-heavy periods.

8. Review AWS Security Incident Response inclusion relative to any standalone SIR contracts you currently hold. The 2025 inclusion of SIR in Enterprise Support may eliminate a separate cost.

9. Consider third-party MSP supplementation for workload categories where TAM generalist expertise is insufficient. The combination of Enterprise Support plus targeted MSP services often delivers better technical coverage than Enterprise Support alone.

10. Engage early on EDP renewal. AWS account teams have the most flexibility at the start of the renewal process, not the end. Beginning support cost negotiation 90 days before EDP expiry gives you maximum leverage.

Real-World Example: From Standard Rates to 4.8% Blended Rate

In one engagement, a global manufacturing company with $12M annual AWS spend was paying standard Enterprise Support rates. Redress benchmarked their support costs against 40+ comparable accounts and secured a blended support rate of 4.8%, saving $420,000 annually from Year 1. The negotiation took 6 weeks.

To discuss your specific AWS Enterprise Support situation and get an independent view on negotiation opportunities at your next renewal, speak with our AWS Enterprise Support negotiation advisors.