Visual overview
Health supplies relevant event context, Trusted Advisor evaluates best practices, and Support provides assistance according to plan.
Technical reference
Support entitlements change over time. Learn the service boundary and escalation model, then verify the current plan matrix for commercial or response-time specifics.
AWS documentation lists these as the main current options in August 2026, alongside announced transitions from legacy plans.
Basic includes documentation and baseline support resources but does not provide the full paid technical-support operating model.
Findings can expose cost, performance, security, resilience, or quota opportunities; entitlement depth depends on current Support packaging.
Health is event context, not a replacement for Trusted Advisor optimization checks or a technical support case.
AWS currently documents a designated TAM with Enterprise Support; higher-end support value should be assessed against workload criticality.
Service limits and capabilities can change. Values shown here reflect the current AWS documentation; use the linked official sources below as the source of truth.
Support is part of workload economics when downtime and expertise have value
AWS Support plans change access to technical assistance, response objectives, proactive guidance, automation, and expert relationships. The right plan is therefore not selected only by monthly fee: a production or mission-critical workload can justify paid support because response speed, access to experts, and proactive operational assistance reduce business risk. Basic Support remains included for all customers for account and billing help, documentation, health information, and other documented baseline capabilities.
As of August 2026, AWS documentation lists Basic, Business Support+, Enterprise Support, and Unified Operations as the current main support choices. AWS has also announced January 1, 2027 end-of-support transitions for legacy Developer Support, Business Support, and Enterprise On-Ramp outside the documented GovCloud exception. This area changes, so certification study should prioritize capability differences and verify the current plan table rather than memorizing an aging list.
Trusted Advisor recommends; it does not replace operational ownership
AWS Trusted Advisor inspects an AWS environment against AWS best-practice checks and surfaces recommendations across areas including cost optimization, performance, resilience/fault tolerance, security, and service limits or quotas according to current check organization and plan access. A cost recommendation can identify waste or an optimization opportunity, but the customer still decides whether the recommendation fits workload requirements and change risk.
Access depth depends on the support relationship. AWS currently provides a core set of guidance with Basic Support and broader Trusted Advisor capabilities with paid plans, while some advanced Trusted Advisor access can also be offered separately. Because check coverage and packaging evolve, treat Trusted Advisor as the recommendation service and the Support plan as the entitlement/context layer rather than memorizing a fixed count of checks.
AWS Health, Support, and Trusted Advisor answer different questions
AWS Health provides account- and resource-relevant service health information; AWS Support provides access to support processes and expertise according to plan; Trusted Advisor evaluates the environment against best-practice checks. They can appear together in an operational workflow without being substitutes. An account-specific AWS service event belongs to Health, an architecture optimization check to Trusted Advisor, and a production incident requiring AWS engineering assistance to Support.
Enterprise and mission-critical support tiers add value through deeper expert and proactive operating models. For example, AWS currently documents a designated Technical Account Manager with Enterprise Support and more intensive application-specific operations under Unified Operations. Financial evaluation should compare this capability with the expected business impact of incidents, not just with infrastructure spend.
Key takeaways
- 01
AWS Support plan choice is a business-risk and expertise decision, not only a price comparison.
- 02
Trusted Advisor evaluates an environment and recommends improvements; customers still own implementation decisions.
- 03
AWS Health reports relevant service/account events, while Support manages assistance and Trusted Advisor provides best-practice findings.
- 04
Support plan names and entitlements are changing in 2026–2027, so current AWS documentation should override memorized legacy tier lists.
- 05
Enterprise-level support adds expert and proactive capabilities whose value depends on workload criticality.
Official AWS sources
Use these primary AWS resources for the source material behind this article and for deeper reference.