AWS Support Response Times and Third-Party Software Help: Picking the Lowest Tier That Fits

AWS Support response times form a ladder that tightens as you pay more: Developer targets responses within 24 business hours for general guidance, Business commits to under 1 hour for a production system down, Enterprise On-Ramp cuts a business-critical system down to under 30 minutes, and Enterprise reaches under 15 minutes. The free Basic tier has no response targets at all, because it can’t open technical cases. CLF-C02 questions almost never ask you to recite these numbers directly — instead they describe a requirement (“response in about an hour if production goes down”) and ask for the lowest-cost plan that satisfies it.

The full response-time ladder

Response times are tied to case severity: when you open a case, you classify how bad the situation is, and the severity you choose determines the plan’s first-response target. Higher severities only exist on higher plans — you can’t open a “production system down” case on Developer, because Developer assumes you have no production.

Severity	Developer	Business	Enterprise On-Ramp	Enterprise
General guidance	< 24 business hrs	< 24 hrs	< 24 hrs	< 24 hrs
System impaired	< 12 business hrs	< 12 hrs	< 12 hrs	< 12 hrs
Production system impaired	—	< 4 hrs	< 4 hrs	< 4 hrs
Production system down	—	< 1 hr	< 1 hr	< 1 hr
Business-critical system down	—	—	< 30 min	< 15 min

Three structural facts make this table easy to reconstruct from memory:

1. Basic isn’t on the table. No technical cases means no response targets of any kind.
2. Developer’s targets are measured in business hours — the clock pauses nights and weekends. Every tier from Business up is measured in calendar hours, around the clock.
3. Each tier keeps everything below it and adds exactly one severity level. Business adds the two production severities; Enterprise On-Ramp adds business-critical at 30 minutes; Enterprise sharpens business-critical to 15 minutes.

The two numbers the exam leans on hardest: production system down = under 1 hour, starting at Business and business-critical system down = under 15 minutes, only at Enterprise (with On-Ramp’s 30 minutes as the middle case).

Where third-party software support begins

A separate benefit that travels with the response-time question is third-party software support: help from Cloud Support Engineers with setting up, configuring, and troubleshooting common operating systems and application stack components running on Amazon EC2 (Elastic Compute Cloud) — databases, web servers, OS issues, and similar off-the-shelf software.

This benefit starts at Business Support and continues through Enterprise On-Ramp and Enterprise. Developer offers only general guidance about AWS services themselves, and Basic offers no technical help at all. So when a scenario involves a company running commercial or open-source software on top of EC2 and wanting AWS to help troubleshoot that software — not just the underlying infrastructure — Business is the entry point.

The “lowest tier that fits” method

Nearly every support-plan scenario on the exam resolves with the same three-step procedure:

1. Extract the hard requirements. Circle phrases like “24/7,” “phone,” “production,” “response within an hour,” “third-party application,” “Technical Account Manager (TAM),” “15 minutes.”
2. Find the floor for each requirement. Each phrase maps to a minimum tier: 24/7 phone/chat → Business. Full AWS Trusted Advisor checks → Business. <1 hr production down → Business. Third-party software support → Business. Pooled TAM or <30 min business-critical → Enterprise On-Ramp. Designated TAM, Concierge Support Team, or <15 min → Enterprise.
3. Answer with the highest floor — and nothing above it. The correct plan is the maximum of the individual minimums. Scenarios reinforce this with cost language (“cannot justify,” “lowest-cost plan that still…”) or by explicitly excluding a benefit (“does not need a dedicated TAM”), which is the exam telling you not to pick the next tier up.

A worked example: a company needs a sub-hour response for production-down incidents and troubleshooting help for a third-party application on EC2, but can’t justify paying for a TAM. Requirement one’s floor is Business; requirement two’s floor is Business; the TAM exclusion caps you below Enterprise On-Ramp. Answer: Business Support, full stop.

The same logic runs downward, too. If nothing in the scenario mentions production, 24/7, or third-party software — just occasional guidance by email during work hours — the floor drops to Developer Support.

How the CLF-C02 exam tests this

• The one-hour production anchor. A revenue-generating site needs 24/7 access to Cloud Support Engineers and a guaranteed response in under one hour when production goes down, usually with “at the lowest tier” or “without a TAM” attached. Business is correct; Enterprise On-Ramp and Enterprise are the over-buy distractors.
• The third-party software entry point. A company runs a commercial application (a content-management system, an electronic health record system, a database) on EC2 and wants AWS to help troubleshoot the software itself. The question asks at which plan that help begins — Business.
• The stacked-requirements scenario. Two or three requirements are listed (fast production response + third-party help + an explicit “no TAM budget” constraint) and you must find the single cheapest plan satisfying all of them. Take the maximum floor; the exclusions exist to stop you from over-answering.
• The minutes-tier discriminator. A scenario demands a response measured in minutes for a business-critical system. Thirty minutes points to Enterprise On-Ramp; fifteen minutes points to Enterprise. Business is the trap for candidates who stopped memorizing at “1 hour.”

The ladder only sticks under time pressure — run Cloud Practitioner practice questions until each number maps to its tier on sight.

Quick reference

• Basic: no technical cases, therefore no response targets.
• Developer: <24 business hours general guidance, <12 business hours system impaired — business hours only.
• Business: adds <4 hrs production impaired and <1 hr production down, measured 24/7.
• Enterprise On-Ramp: adds business-critical system down <30 minutes.
• Enterprise: business-critical system down <15 minutes.
• Third-party software support (common OS/app-stack help on EC2) starts at Business.
• Response targets attach to the case severity you select, and higher severities only exist on higher plans.
• Exam method: map each stated requirement to its minimum tier, take the highest, and let “no TAM” / “lowest cost” language cap you there.