AWS Support Plans and Technical Resources: The Complete CLF-C02 Guide

AWS publishes an enormous library of free technical content, and the exam expects you to know that all of it lives on official AWS websites and costs nothing — no Support plan required. The foundation is AWS Documentation: per-service user guides, developer guides, API references, and tutorials. When a question asks where to find step-by-step instructions for configuring a specific service, the service documentation is the answer.

AWS Whitepapers are longer-form technical papers written by AWS and the AWS community covering architecture, security, economics, and migration. Classics include the AWS Well-Architected Framework and the Overview of AWS whitepaper. If a scenario mentions a team that wants a deep, authoritative document on a broad subject — say, security best practices across an entire environment — a whitepaper is the intended resource. Whitepapers are aimed at architects and decision makers rather than at someone debugging a single API call.

AWS Blogs are the news channel: service launch announcements, feature deep dives, customer stories, and how-to walkthroughs, organized by topic (compute, security, machine learning, and so on). When the trigger in a question is staying current with new releases or reading an informal walkthrough from AWS engineers, the answer is the AWS Blog. All three resource types are public, searchable, and free to every visitor — you do not even need an AWS account. That fact alone answers a surprising number of foundational questions: self-service technical content is never gated behind a paid Support plan.

Three named resources appear directly in the exam guide, and CLF-C02 loves to make you pick between them. AWS Prescriptive Guidance is a library of proven strategies, guides, and patterns developed by AWS experts and AWS Partners from real customer engagements. The keyword is proven: when a scenario describes a team that wants time-tested migration strategies or established patterns for adopting a technology, Prescriptive Guidance is the match.

The AWS Knowledge Center contains answers to the questions customers most frequently ask AWS Support. It is hosted on re:Post and organized by service. The trigger phrase is frequently asked or common support questions: if a user hits an error that thousands of others have hit before, the Knowledge Center likely already has the fix — no support case needed.

AWS re:Post is the official community question-and-answer service, and it replaced the old AWS Forums. Anyone can search it; posting requires a free profile. Answers come from the community, AWS experts, and AWS employees. When a question mentions asking the community, crowd-sourced answers, or a free place to get help from other AWS users, re:Post is the answer. Note that community help through re:Post is included with every account, even on the free Basic Support plan.

AWS currently offers four Support plans: Basic (free), Business Support+, Enterprise Support and Unified Operations. Each higher plan includes what the plans below it offer and adds more human expertise. The lineup changed recently: AWS is discontinuing Developer Support and Business Support on 1 January 2027 (existing customers can stay until then or move to Business Support+), and Enterprise On-Ramp customers are being moved to Enterprise Support during 2026, with that plan also ending on 1 January 2027. The current CLF-C02 exam guide already names the new lineup. You may still meet the old names in older third-party material: the role of the old entry-level and production plans is now filled by Business Support+, and the On-Ramp role by Enterprise Support. No new customer can choose a retired plan outside AWS GovCloud (US), where the older plans remain available.

Basic Support is included with every AWS account at no charge: 24/7 customer service for account and billing questions, documentation, whitepapers, community help on AWS re:Post, the core AWS Trusted Advisor checks and the AWS Health Dashboard. It does not include technical support from AWS engineers, so you cannot open a technical case on Basic.

Business Support+ is the lowest-cost plan that includes technical support, and AWS describes it as its minimum recommended plan for production workloads. It adds 24/7 access to AWS experts for technical issues, AI-assisted troubleshooting, the full set of Trusted Advisor checks, and the AWS Health API. Because it is the first plan with technical cases, it is also the cheapest choice for a team that only runs development and test workloads but occasionally needs an engineer.

Enterprise Support is AWS's recommended plan for business-critical workloads. On top of Business Support+, it adds a designated Technical Account Manager (TAM) who knows your environment and provides proactive, strategic guidance, a personalized support plan, proactive programs led by the TAM (such as AWS Well-Architected Reviews, workshops and AWS GameDays, plus help preparing for launches, migrations and peak-traffic events), and Trusted Advisor Priority: prioritized recommendations curated for you by your AWS account team. Unified Operations is the plan for mission-critical workloads that need enhanced resilience and application-specific expertise: it adds designated domain specialist engineers, 24/7 monitoring of your workloads, and incident management engineers who respond around the clock during critical incidents.

Response-time targets and price minimums are published on the AWS Support plan pages and change over time, so learn each plan by its role rather than by numbers.

Most Support-plan questions state a requirement and ask for the lowest-cost plan that meets it. Higher plans always include everything below them, so they technically satisfy the requirement too, but they are the wrong choice because they cost more. Read the requirement and stop at the first plan that has it:

• Account and billing help, at no cost → Basic
• Any technical support case, even for dev/test only → Business Support+
• 24/7 access to AWS experts for production → Business Support+
• Full Trusted Advisor check set or the AWS Health API → Business Support+
• A designated TAM, proactive strategic guidance, or Trusted Advisor Priority → Enterprise Support
• Domain specialist engineers, 24/7 workload monitoring, incident management engineers for mission-critical systems → Unified Operations

Think of each step up as adding one layer. Business Support+ is the technical-support layer: expert access around the clock, the full Trusted Advisor checks and the Health API. Enterprise Support adds the account-team layer on top, so its value is the people and curation (a designated TAM, proactive reviews, Trusted Advisor Priority) rather than anything Business Support+ already had. Unified Operations adds the operations layer: engineers who learn your specific applications and watch and manage incidents for them around the clock. Both Enterprise Support and Unified Operations include a designated TAM, so when the requirement is only the TAM, Enterprise Support is the lower-cost answer.

The AWS Support Center is the place in the AWS Management Console where you create support cases, follow and reply to their correspondence, and view your Support plan. It is the front door for all case-based help, whatever plan you are on.

Basic Support does not lock you out of the Support Center. Every account, including Basic, can open account and billing cases (for example, a question about a charge on an invoice) and service quota (service limit) increase requests. What needs a paid plan is a technical case, where you ask an AWS engineer to help with how a service is behaving. So asking for a refund on a duplicate charge, or for a higher AWS Lambda concurrency limit, costs nothing beyond the account itself, while asking why a database connection keeps timing out is a technical case and needs Business Support+ or higher. Separately, the Service Quotas console lets you request many quota increases directly.

AWS Trusted Advisor is the automated best-practice checker. It inspects your account and recommends improvements across six categories: cost optimization, performance, security, fault tolerance, service limits and operational excellence, which is how it helps you manage and monitor an environment for cost optimization. Every account, even on Basic Support, gets the core checks (all service limits checks plus a selected set of security and fault tolerance checks). The full set of checks requires Business Support+ or higher. Trusted Advisor Priority goes one step further: your AWS account team reviews and prioritizes recommendations for you, and it is available only with Enterprise Support or Unified Operations.

The AWS Health Dashboard answers a different question: not am I following best practices, but is anything happening on AWS that affects me. Its public service health view shows the general status of AWS services across Regions; your account view lists open events and upcoming scheduled maintenance that affect the specific resources in your account, with notifications and remediation guidance. It is available to every account. Amazon CloudWatch is a different tool: it reports your own metrics and alarms, not AWS operational events.

The AWS Health API returns the same account-specific events programmatically, so you can feed them into your own monitoring or ticketing systems. It requires Business Support+, Enterprise Support or Unified Operations; calls from an account on Basic Support fail with a SubscriptionRequiredException, and opening a support case does not switch it on. The pairing to remember: the dashboard is for everyone, the API comes with Business Support+ and above.

Sometimes the problem is not your account but someone else's. If you observe AWS resources being used for abusive or illegal purposes — spam originating from EC2 instances, denial-of-service attacks launched from AWS IP addresses, hosted malware or phishing sites, or intrusion attempts against your systems — the correct escalation path is the AWS Trust & Safety team. You report suspected abuse through the AWS abuse reporting form or by emailing the AWS abuse address with the source IP addresses, timestamps, and relevant logs. Trust & Safety investigates and works with the owner of the offending account.

The exam tests this as a routing question, so keep the destinations straight. Abuse of AWS resources by a third party goes to Trust & Safety, not to a regular support case and not to your account manager. A technical problem with your own workload goes to AWS Support through the Support Center. A suspected AWS service outage is checked on the AWS Health Dashboard. Security findings inside your own account are surfaced by your own tooling and Trusted Advisor.

Also worth knowing: reporting abuse requires no paid Support plan. Anyone — including people who are not AWS customers at all — can file an abuse report. If a question describes an on-premises administrator seeing attack traffic from an AWS-owned IP range, the answer is still the AWS Trust & Safety team. The one thing Trust & Safety does not do is provide security consulting for your architecture; it exists to investigate misuse of the AWS platform itself.

The other side of abuse handling is being on the receiving end. If AWS Trust & Safety sends you a notice that one of your resources, such as an S3 bucket hosting a phishing page or a compromised instance scanning other networks, is being used for abuse, the response is yours to make under the shared responsibility model: what runs on your instances is your responsibility. Investigate the resource, stop the activity (for example, remove the offending content or isolate the compromised resource, and fix how it was compromised), and reply to the notice with what you found and did. AWS does not log in and clean up your instance for you, and neither your Support plan nor a TAM changes that: a TAM can advise you, but remediation of your own resources is your job. Ignoring a notice can lead AWS to restrict the resource or the account.

Not all help comes from AWS employees. The AWS Partner Network (APN) is the global community of companies that build solutions and deliver services on AWS. The exam guide names two partner types. Independent software vendors (ISVs) build software products that run on or integrate with AWS (monitoring suites, security tools, SaaS applications) and commonly sell them through AWS Marketplace. System integrators (consulting partners) are services companies that design, migrate, build and manage customer workloads on AWS. A company with no in-house cloud skills that wants an external firm to execute its migration is looking for a system integrator.

Companies join the APN for its benefits, which the exam guide lists as partner training and certification (building the partner's AWS skills), partner events, and partner volume discounts, alongside technical enablement, go-to-market support and funding programs. Partners can also earn competencies that signal validated expertise to customers. Keep APN benefits separate from Support plan features: a designated Technical Account Manager comes from a Support plan (Enterprise Support or Unified Operations), not from joining the APN.

AWS Marketplace is the curated digital catalog where customers find, try, buy and deploy third-party software, data and services that run on AWS, such as a firewall appliance or a SaaS analytics tool, with the charges appearing on their existing AWS bill. The exam guide names cost management, governance and entitlement as examples of its key services; procurement is the buying side that ties them together:

• Procurement: buying through the AWS account with flexible options such as free trials, pay-as-you-go, contracts and private offers negotiated with a seller.
• Cost management: Marketplace charges arrive on the AWS bill, so they can be tracked and analyzed with the same billing tools as AWS usage.
• Governance: Private Marketplace lets an administrator build a curated catalog of approved Marketplace products, so employees can subscribe only to what the procurement team has allowed.
• Entitlement: purchased licenses are tracked as entitlements and can be distributed and managed across accounts with AWS License Manager.

Private Marketplace has near-twins that are easy to confuse:

Two groups of AWS's own experts round out the help landscape. AWS Professional Services is AWS's global consulting organization. Its consultants engage directly with enterprise customers — usually alongside APN partners — on large initiatives such as migrations, modernization programs, and specialized implementations. Engagements are paid, project-based, and outcome-focused. When a scenario describes an enterprise that wants AWS's own consultants embedded in a major transformation project, AWS Professional Services is the answer.

Solutions Architects (SAs) are AWS technical experts who provide architectural guidance: they help customers design well-architected workloads, review proposed designs, and recommend the right services for a use case. Unlike Professional Services, SA guidance is advisory — they help you design and decide rather than deliver a project for you. The exam contrast to remember: Professional Services works on engagements to deliver outcomes, while a Solutions Architect advises on architecture and service selection.

Do not confuse either role with the Technical Account Manager (TAM). A designated TAM is a Support plan feature that comes with Enterprise Support or Unified Operations, and acts as your ongoing advocate inside AWS: guiding operations, coordinating proactive reviews and helping you follow best practices year-round. A TAM advises; it does not log in and fix your instances or deliver projects for you. An SA helps you design, Professional Services (or a system integrator partner) helps you build, and a TAM helps you run.