An AWS Technical Account Manager (TAM) is your designated technical advisor in AWS Enterprise Support. A TAM leads Well-Architected and operational reviews, plans launches through AWS Countdown, gives FinOps guidance and brings in AWS experts when a case needs escalating. A TAM is not hands-on in your accounts. Under AWS Partner-Led Support, your TAM works for the partner, and AWS specialist TAMs support the partner.
Key Takeaways
- Only Enterprise Support and Unified Operations include a TAM. Business Support+ does not.
- A TAM plans, reviews and escalates. Engineers and AWS service teams do the fixing.
- Direct and Resold Support give you AWS’s TAM. Partner-Led Support gives you the partner’s TAM, backed by AWS specialist TAMs.
- In ASCENDING’s view, a partner TAM role should carry the same purpose and responsibilities as an AWS TAM. The difference is reach: partner TAMs are often closer to hands-on delivery, AWS TAMs to the product roadmap.
Last verified against AWS pages on 2026-10-16. AWS changes support terms, so check the linked pages before you decide.
What does an AWS TAM do?
A TAM is the person who owns your relationship with AWS Support on the technical side. AWS describes the role on its Enterprise Support page: “Your TAM leads Well-Architected Reviews, provides architectural guidance across security, reliability, performance efficiency, cost optimization, and operational excellence,” and “brings in AWS subject matter experts when needed.”
AWS’s TAM engagement page breaks the work into onboarding, an ongoing plan and a set of reviews.
Onboarding and the ongoing plan
- Onboarding. Onboarding “typically lasts 90 days.” The TAM assesses your cloud maturity and advises you across the Well-Architected pillars.
- Strategic Support Plan. “Your TAM works with you to define and refine strategic outcomes on AWS across Well-Architected pillars,” and then builds a customized support plan from them.
- Strategic Business Reviews. The TAM checks performance against those outcomes and looks for improvements.
Reviews and programs
- Advisory reviews. Operational excellence and security reviews, plus exercises that test your incident procedures against a hypothetical incident.
- Cost. FinOps practice development and Trusted Advisor recommendations.
- Events. AWS Countdown covers launches, migrations and peak traffic. The Enterprise Support page says “Your TAM works with you before events to review readiness and capacity planning, and during events to provide support.”
- Learning. Hands-on workshops, AWS GameDays and Immersion Days for your engineers.
Escalation and routing
When a support case has business impact, the TAM pulls in the right AWS specialists and service teams. The TAM then keeps the case moving. AWS’s TAM engagement page also lists AWS Trusted Advisor, which surfaces optimization recommendations, and AWS Health, which shows the availability of your AWS services and accounts.
What a TAM does not do
A TAM is not hands-on in your accounts. AWS’s Support FAQ draws the line for Support as a whole. AWS Support “does not include custom code development, software debugging, system administration tasks, or remote access to customer systems and accounts.” The TAM advises and routes. Your engineers, or a partner’s, make the changes.
Three practical limits follow from that:
- Not break-fix. A 2025 AWS Community Builders post by Danny Steenman quotes a Reddit user on this. “TAMs don’t work tickets and they don’t do break-fix,” the user wrote. That is one practitioner’s view, but it fits AWS’s own description of Support.
- Not the incident manager. You can add AWS Incident Detection and Response to Enterprise Support. Its Incident Management Engineers “provide single-threaded ownership for incidents.” The TAM does not run the incident.
- Not your application expert. Your own engineers know your code and data. See the ownership test in whether Enterprise Support is worth it.
In our view, the gap between advice and hands-on work is where partners and managed service providers often add people.
Which AWS support plans include a TAM?
Enterprise Support includes a designated TAM, and Unified Operations includes a TAM inside a designated core team. Business Support+ has no TAM. AWS reset its plans on 2025-12-02, according to the AWS News Blog.
| Plan | TAM | Critical-case response target | Starting price per month |
|---|---|---|---|
| Business Support+ | None | 30 minutes | $29 |
| Enterprise Support | Designated TAM | 15 minutes | $5,000 |
| Unified Operations | Designated TAM, plus Domain Specialist Engineers | 5 minutes | $50,000 |
Prices are the minimums on the AWS Support pricing page. The Unified Operations team is described on the Unified Operations page. Response times come from the AWS Support plans page. AWS footnotes them as targets, not guarantees. Enterprise On-Ramp, which had a TAM, is supported through 2026-12-31 and discontinued on 2027-01-01, per the AWS Support FAQ.
For every plan feature, see AWS Support plans in 2026. For the full fee formula, see what Enterprise Support costs.
Who is your TAM? Direct, Resold and Partner-Led Support
Who your TAM is depends on how you buy support. With direct or Resold Support, your TAM is AWS’s. With Partner-Led Support, your TAM is the partner’s, and AWS gives the partner access to AWS specialist TAMs.
| Direct Enterprise Support | AWS Resold Support | AWS Partner-Led Support | |
|---|---|---|---|
| Who is your TAM | AWS TAM | AWS TAM | Partner TAM |
| First line for cases | AWS Support | AWS Support | Partner |
| How cases reach AWS | Direct | Direct | The partner escalates through its own AWS entitlement |
| Who bills you | AWS | Partner | Partner |
| What varies | Nothing; AWS’s fixed offer | Billing terms | The whole offer, defined by the partner |
The AWS Resold Support page says customers “maintain a direct technical relationship with AWS Support.” The partner handles billing and non-technical questions.
The AWS Partner-Led Support page is written to the partner, not to you. It gives partners “24/7 premium access to AWS experts, including AWS specialist Technical Account Managers (TAMs).” Partners also get a 15-minute response for high-severity cases and “secure access to AWS Diagnostic Tools used by AWS Support.” Those AWS TAMs help the partner “improve customer case resolution.” An older APN blog post from 2020 adds that Partner-Led Support lets partners “define the support offerings they sell to customers, rather than doing a straight resale.”
So two TAMs are involved under Partner-Led Support. The partner’s TAM works with you. AWS’s specialist TAM works with the partner. The partner’s skills, staffing and escalation habits decide what you actually get.
In ASCENDING’s reading of AWS’s terms, Enterprise Support is mandatory in a cross-service Private Pricing Agreement (PPA). An authorized AWS partner can provide partner-led support that satisfies it. Confirm the clause with your AWS account team. See who can provide Enterprise Support under a PPA for the qualifying options, and the PPA negotiation guide for the contract.
Partner TAM vs AWS TAM: same role, different reach
When a partner’s offer includes a TAM role, the role should carry the same purpose and responsibilities as an AWS TAM. The partner TAM owns the reviews, the support plan, cost guidance and escalation, just as AWS describes. That is ASCENDING’s view as a partner that provides the role, and it is the standard to hold any partner to. In our view, what differs is where each TAM sits.
| AWS TAM | Partner TAM | |
|---|---|---|
| Purpose and responsibilities | Reviews, planning, cost guidance, escalation | The same, when the offer includes a TAM role |
| Hands-on depth | Advisory; not hands-on in your accounts | Often more hands-on delivery experience; partner engineers may work in your accounts under agreed access |
| Product roadmap (our view) | Inside AWS, with the latest insight into product features and the roadmap | Hears about the roadmap through AWS’s partner channels, at one remove |
| Escalation into AWS | Direct to service teams | Through the partner’s AWS entitlement and AWS specialist TAMs |
| Scope | AWS services | AWS services, plus the partner’s own delivery services if you buy them |
The hands-on point follows from the job. In our view, a partner TAM often comes from delivery work. The TAM can also bring in partner engineers who make changes in your accounts, if the contract grants that access. An AWS TAM gives advice and routes cases, but does not do the hands-on work.
The roadmap point runs the other way. An AWS TAM works inside AWS. AWS says its TAMs bring knowledge across technical domains “including the latest cutting-edge services.” That puts an AWS TAM closest to new features and where services are heading. It matters when a design decision depends on a feature that has not shipped yet.
Partners do not all offer the same thing, so check these in writing before you sign:
- Is the TAM a named person? How many accounts does that person cover?
- Who does hands-on work, and under what access, approval and revocation rules?
- How does a case reach AWS, and can you open AWS cases yourself? The Steenman post quotes a practitioner who warns that with some partners “you can’t open a ticket with AWS directly.”
- Which reviews and programs are included, and how often?
- Will the partner confirm in writing that its support satisfies your PPA’s Enterprise Support requirement?
The full comparison worksheet is in partner-led support vs Enterprise Support.
How to get value from your TAM
A TAM pays off when you bring your roadmap, not your tickets. This applies whether the TAM works for AWS or for a partner.
- Share a 6- to 12-month plan. The Strategic Support Plan is built from the outcomes you define with the TAM. Tell the TAM about launches, migrations and cost targets.
- Book reviews before big changes. Run a Well-Architected Review or Countdown before a launch, not after an outage.
- Use the business review to set priorities. Bring the findings from the last six months and decide what to fix next.
- Send cases through Support. Use the TAM for escalation and patterns across cases, not as a first-line help desk.
- Track what each review changed. If nothing changes after a review, the TAM is cost without value.
If no one on your team will meet the TAM regularly, the TAM-use test in whether Enterprise Support is worth it is the place to start.
What should you do next?
- Check which support plan you are on and whether it includes a TAM.
- If you buy through a partner, ask whether it is Resold or Partner-Led Support, and who your TAM is.
- Ask your TAM for a Well-Architected Review before your next major change.
- Compare partner offers row by row using the partner-led support worksheet.
ASCENDING is an authorized AWS partner and sells AWS Partner-Led Enterprise Support with a TAM role. Weigh that interest when you read this guide, and hold every partner, including us, to the checklist above.
References
- AWS Enterprise Support, AWS, retrieved 2026-10-16.
- AWS TAM engagement, AWS, retrieved 2026-10-16.
- AWS Support plans, AWS, retrieved 2026-10-16.
- AWS Support pricing, AWS, retrieved 2026-10-16.
- AWS Support FAQs, AWS, retrieved 2026-10-16.
- AWS Unified Operations, AWS, retrieved 2026-10-16.
- AWS Partner-Led Support, AWS, retrieved 2026-10-16.
- AWS Resold Support, AWS, retrieved 2026-10-16.
- New and enhanced AWS Support plans add AI capabilities to expert guidance, AWS News Blog, 2025-12-02.
- Updates to AWS Partner-Led Support for Solution Provider Partners, AWS Partner Network Blog, 2020-11-11. Older program detail; check current terms with AWS.
- What is AWS Incident Detection and Response?, AWS Incident Detection and Response User Guide, retrieved 2026-10-16.
- AWS Enterprise Support vs Partners: Which One Do You Actually Need?, Danny Steenman, AWS Community Builders, 2025-11-14, retrieved 2026-10-17.
- AWS Support plans in 2026, ASCENDING Blog.
- AWS Partner-Led Support vs AWS Enterprise Support, ASCENDING Blog.
- Is AWS Enterprise Support Worth It?, ASCENDING Blog.
FAQ — AWS Technical Account Managers
Does AWS Business Support+ include a Technical Account Manager?
No. Business Support+ gives 24/7 access to AWS experts and a 30-minute response to business-critical cases, but no designated TAM. Enterprise Support includes a designated TAM, and Unified Operations includes a TAM inside a designated core team. See AWS Support plans in 2026 for the full comparison.
Is an AWS TAM hands-on in my AWS accounts?
No. AWS's Support FAQ says AWS Support does not include custom code development, software debugging, system administration tasks or remote access to customer systems and accounts. The TAM advises and brings in AWS experts, and your engineers or a partner's engineers make the changes.
Who is my TAM under AWS Partner-Led Support?
A TAM employed by the partner. Under Partner-Led Support, AWS gives the partner access to AWS specialist TAMs, and the partner supports you. Under AWS Resold Support, by contrast, you keep a direct technical relationship with AWS Support and the partner handles billing.
Does a partner TAM do the same job as an AWS TAM?
ASCENDING's view, as a partner that provides the role, is that a partner TAM role should carry the same purpose and responsibilities as an AWS TAM: reviews, planning, cost guidance and escalation. The difference is reach. A partner TAM often brings more hands-on delivery experience, while an AWS TAM sits closer to AWS service teams and the product roadmap. AWS lets partners define their own offers, so confirm the role in writing.
Can I still open cases with AWS directly under partner-led support?
It depends on how the partner sets up your accounts, so ask before you sign. Under Partner-Led Support the partner is your first line and escalates to AWS through its own entitlement. Under AWS Resold Support you open cases with AWS Support directly.
