AWS Technical Resources and Support Options (Task 4.3)

AWS Technical Resources and Support Options

Source: https://aws.amazon.com/premiumsupport/plans/

The exam tests the support-plan ladder and where free help lives. Senior engineers choose plans by RISK: what does one hour of production downtime cost the business, and which response-time tier protects it?

AWS Support Plans (Know the Ladder)

How the ladder works: every plan can open cases; the differences are WHO you reach (cloud support engineers vs a named human who knows your architecture), WHEN (business-hours email vs 24/7 phone), and HOW FAST (12–24 h vs 15 minutes for business-critical outages). Business also unlocks full Trusted Advisor checks and programmatic (IAM-scoped) case creation — the plan an automation-minded operator buys.

Real use-case: A mid-size SaaS with a revenue-critical API estimates downtime at $40k/hour. Business support's 1-hour prod-down response and 24/7 phone access cost $100+/month — the decision is not about AWS help, it is about buying an insurance policy priced at 0.003% of the insured loss.

Gotchas & interview notes: the three most-tested rules: cheapest plan with 24/7 phone → Business; dedicated TAM → Enterprise (On-Ramp gives a TAM POOL); cheapest PAID plan → Developer (business-hours EMAIL, one contact). Trusted Advisor's full checks arrive at Business, not Developer.

Trusted Advisor, Health Dashboard, Trust & Safety

• AWS Trusted Advisor: automated best-practice checks (cost, performance, security, fault tolerance, service quotas) — full checks need Business+. It INSPECTS; remediation is yours (or Config rules').
• AWS Health Dashboard (+ Health API): personalized visibility of scheduled maintenance, events, and outages affecting YOUR resources — filterable to "things I own," with an API to automate responses (e.g., drain an instance scheduled for retirement).
• AWS Trust and Safety team: where you report abuse of AWS resources (spam from an EC2 IP, phishing hosted on S3). The exam's "report abusive traffic originating from AWS" answer.
• Partners: consulting partners (system integrators like Accenture/Deloitte that design/build for you) and technology partners (ISVs building ON AWS).
• Partner benefits: training/certification paths, partner volume discounts, events (re:Invent), funding programs.
• AWS Marketplace: catalog of third-party software including cost management, governance, and entitlement/licensing — buy pre-configured AMIs/SaaS, billed through your AWS invoice.
• AWS Professional Services: AWS's own consultants (enterprise-scale engagements).
• AWS Solutions Architects: FREE presales architecture guidance available to all customers (deeper engagement on Business/Enterprise tiers).
• A hobby project crashing on weekends → Basic; use re:Post and docs
• A 5-person startup with a production SaaS and no overnight pager → Developer, upgrade when 24/7 becomes essential
• A mid-size company with a revenue-critical API → Business (24/7 phone, 1-hour prod-down response)
• A global bank with regulated workloads → Enterprise (dedicated TAM, 15-minute critical response, architecture reviews)

Real use-case: During a regional service event, a team checks the Health Dashboard (their ARNs, not the generic status page) — confirming their ELB is unaffected while a partner's is, and pre-empting customer tickets with a proactive status note.

Free Technical Resources

Real use-case: Before filing a single support case, a small team resolves 90% of its issues with Knowledge Center entries and re:Post answers (the modern forum with searchable, reputation-ranked Q&A) — free tier economics that scale with effort, not spend.

AWS Partner Network (APN) and Marketplace

• AWS Trusted Advisor: automated best-practice checks (cost, performance, security, fault tolerance, service quotas) — full checks need Business+. It INSPECTS; remediation is yours (or Config rules').
• AWS Health Dashboard (+ Health API): personalized visibility of scheduled maintenance, events, and outages affecting YOUR resources — filterable to "things I own," with an API to automate responses (e.g., drain an instance scheduled for retirement).
• AWS Trust and Safety team: where you report abuse of AWS resources (spam from an EC2 IP, phishing hosted on S3). The exam's "report abusive traffic originating from AWS" answer.
• Partners: consulting partners (system integrators like Accenture/Deloitte that design/build for you) and technology partners (ISVs building ON AWS).
• Partner benefits: training/certification paths, partner volume discounts, events (re:Invent), funding programs.
• AWS Marketplace: catalog of third-party software including cost management, governance, and entitlement/licensing — buy pre-configured AMIs/SaaS, billed through your AWS invoice.
• AWS Professional Services: AWS's own consultants (enterprise-scale engagements).
• AWS Solutions Architects: FREE presales architecture guidance available to all customers (deeper engagement on Business/Enterprise tiers).
• A hobby project crashing on weekends → Basic; use re:Post and docs
• A 5-person startup with a production SaaS and no overnight pager → Developer, upgrade when 24/7 becomes essential
• A mid-size company with a revenue-critical API → Business (24/7 phone, 1-hour prod-down response)
• A global bank with regulated workloads → Enterprise (dedicated TAM, 15-minute critical response, architecture reviews)

Real use-case: A company lacking Kubernetes expertise hires an AWS consulting partner for a 3-month EKS landing zone build, then runs it themselves — the partner's certification tier and references (visible in Partner Central) were the due diligence.

Worked Example: Picking a Plan

• AWS Trusted Advisor: automated best-practice checks (cost, performance, security, fault tolerance, service quotas) — full checks need Business+. It INSPECTS; remediation is yours (or Config rules').
• AWS Health Dashboard (+ Health API): personalized visibility of scheduled maintenance, events, and outages affecting YOUR resources — filterable to "things I own," with an API to automate responses (e.g., drain an instance scheduled for retirement).
• AWS Trust and Safety team: where you report abuse of AWS resources (spam from an EC2 IP, phishing hosted on S3). The exam's "report abusive traffic originating from AWS" answer.
• Partners: consulting partners (system integrators like Accenture/Deloitte that design/build for you) and technology partners (ISVs building ON AWS).
• Partner benefits: training/certification paths, partner volume discounts, events (re:Invent), funding programs.
• AWS Marketplace: catalog of third-party software including cost management, governance, and entitlement/licensing — buy pre-configured AMIs/SaaS, billed through your AWS invoice.
• AWS Professional Services: AWS's own consultants (enterprise-scale engagements).
• AWS Solutions Architects: FREE presales architecture guidance available to all customers (deeper engagement on Business/Enterprise tiers).
• A hobby project crashing on weekends → Basic; use re:Post and docs
• A 5-person startup with a production SaaS and no overnight pager → Developer, upgrade when 24/7 becomes essential
• A mid-size company with a revenue-critical API → Business (24/7 phone, 1-hour prod-down response)
• A global bank with regulated workloads → Enterprise (dedicated TAM, 15-minute critical response, architecture reviews)

The senior rule: buy the plan whose response time is shorter than the time it takes your own team to diagnose the failure. If your on-call can find the problem in 20 minutes, Enterprise's 15-minute response adds little; if it cannot, no plan is too expensive.