The free AWS Support plan for all customers, providing customer service for billing and account issues plus access to documentation, whitepapers, and AWS re:Post, but no guaranteed access to technical support engineers or response times.

A paid AWS Support plan aimed at development and test environments, offering business-hours email access to Cloud Support Associates and faster responses for general guidance than Basic, but not 24/7 phone or chat for production outages.

An AWS Support plan designed for production workloads, providing 24/7 access to Cloud Support Engineers via phone, chat, and email, with defined response times for issues including production system down.

The highest AWS Support tier for large, mission-critical workloads, including a Technical Account Manager, proactive reviews and guidance, and the fastest response times for critical issues.

An AWS-managed, community-driven Q&A service where customers and AWS experts ask and answer questions about AWS services, architectures, and troubleshooting.

What is Basic Support?

The free AWS Support plan for all customers, providing customer service for billing and account issues plus access to documentation, whitepapers, and AWS re:Post, but no guaranteed access to technical support engineers or response times.

What is Case severity?

A classification AWS uses for support cases, ranging from general guidance or low-severity questions to critical production system down issues, which affects target response times.

AWS Support Plans and Technical Resources — AWS Certified Cloud Practitioner (CLF-C02) Deep-Dive Exam Prep

Q: A startup is launching its first revenue-generating web application on AWS. They need 24/7 access to technical support engineers by phone or chat if the site goes down, but they are not yet at enterprise scale. Which AWS Support plan is the best fit?

Business Support. Business Support is designed for production workloads that need 24/7 access to technical support via phone, chat, and email with fast response times for production issues. Basic and Developer do not provide 24/7 phone/chat technical support. Enterprise is usually chosen by larger organizations with mission-critical, large-scale workloads and a need for a Technical Account Manager.

Big Picture: Getting Help in AWS

Two Ways to Get Help

On AWS you get help in two main ways:

Formal AWS Support plans
Self-service technical resources like docs, re:Post, and training.

Why This Matters

For the Cloud Practitioner exam and real life, you must match support plans to business needs and know when to use self-service vs opening a support case.

Shared Responsibility Reminder

The AWS shared responsibility model says: "Security and compliance are shared responsibilities between AWS and the customer." Support changes how AWS helps, not who owns what.

What We Will Cover

We will walk through each support plan, compare response times and contact methods, explore AWS technical resources, and practice choosing the right help path.

AWS Support Plans Overview (2026 Snapshot)

Five Support Plans

As of 2026 there are five main AWS Support plans: Basic, Developer, Business, Enterprise On-Ramp, and Enterprise.

Basic Support

Basic is free for all customers. It covers account and billing support plus access to docs, whitepapers, and re:Post, but no guaranteed technical engineer responses.

Developer and Business

Developer is a paid entry plan for dev/test. Business is for 24/7 production support with phone, chat, and email access to Cloud Support Engineers.

Enterprise Levels

Enterprise On-Ramp and Enterprise add higher-touch guidance, architectural reviews, and a TAM for large, mission-critical environments.

Pricing Model

Paid plans are priced as a percentage of your monthly AWS usage with minimum fees. For the exam, focus on features and use cases, not exact prices.

Response Times, Severity Levels, and Contact Methods

Severity Levels

AWS cases use severity levels: General guidance/Low, System impaired, Production system impaired, and Production system down/Critical.

Basic vs Developer

Basic has no guaranteed response times and focuses on billing/account. Developer gives business-hours email responses for guidance, not rapid outage recovery.

Business Plan Pattern

Business Support offers 24/7 phone, chat, and email with fast responses for production-down issues and defined targets for lower severities.

Enterprise Patterns

Enterprise On-Ramp and Enterprise provide the fastest responses, 24/7 channels, and strong escalation options for critical production issues.

Common Exam Trap

Only Business and above give 24/7 technical support and phone support. Developer is email-only and aimed at non-production workloads.

Matching Support Plans to Business Needs

Solo Developer

Side project, low revenue, experimenting. Needs occasional guidance and low cost. Likely fit: Developer Support or even Basic if they lean on docs and re:Post.

Startup in Beta

Beta web app with early customers. Outages hurt but are survivable. Needs 24/7 help during incidents. Fit: Business Support.

Mature SaaS Company

Thousands of customers, strict SLAs, global users. Needs fastest responses and proactive guidance. Fit: Enterprise Support.

Internal Analytics

Internal, office-hours analytics workload. Downtime is annoying but not critical. Fit: Developer Support, or Business if moving toward production.

Exam Language Cues

Mission-critical, 24/7, strict SLAs → Business/Enterprise. Testing, non-production, cost-sensitive → Developer/Basic.

What You Always Get: Self-Service Technical Resources

Docs and Whitepapers

AWS Documentation explains services and APIs; whitepapers and guides go deep on topics like security, cost, and architecture.

re:Post and Knowledge Center

AWS re:Post is a Q&A community; Knowledge Center articles are short, focused solutions written by AWS Support for common problems.

Training Ecosystem

AWS offers digital and classroom training plus labs. Your Skarp course is part of this ecosystem, focused on Cloud Practitioner prep.

Well-Architected Framework

The AWS Well-Architected Framework describes best practices for designing and running workloads and is supported by the console-based Well-Architected Tool.

Value with Any Plan

Even with Basic Support, you can solve many issues using docs, re:Post, Knowledge Center, and Well-Architected guidance before opening a case.

Thought Exercise: Self-Service or Support Case?

Exercise Setup

In each scenario, decide whether to start with self-service resources or open an AWS Support case. Focus on what is likely under your control.

Scenario A: Pricing Confusion

Unsure about EC2 pricing. First use docs and pricing pages; then open a billing case if you still need account-specific clarification.

Scenario B: 500 Errors

500 errors after a code change. First check logs, metrics, and roll back. This is likely an application issue you own under the shared responsibility model.

Scenario C: Multi-AZ Symptoms

Production app on Business Support with failures across AZs. Quickly check Service Health Dashboard, then open a high-severity support case.

Quiz 1: Support Plan Features

Test your understanding of AWS Support plan characteristics.

A startup is launching its first revenue-generating web application on AWS. They need 24/7 access to technical support engineers by phone or chat if the site goes down, but they are not yet at enterprise scale. Which AWS Support plan is the best fit?

Basic Support
Developer Support
Business Support
Enterprise Support

Show Answer

Answer: C) Business Support

Business Support is designed for production workloads that need 24/7 access to technical support via phone, chat, and email with fast response times for production issues. Basic and Developer do not provide 24/7 phone/chat technical support. Enterprise is usually chosen by larger organizations with mission-critical, large-scale workloads and a need for a Technical Account Manager.

Quiz 2: Self-Service vs AWS Support

Decide which help path makes the most sense in this scenario.

You are on the Basic Support plan. Your EC2 instance has become unreachable after you changed the security group rules. What should you do first?

Open a high-severity technical support case to ask AWS to fix your security group.
Use AWS documentation and Knowledge Center articles to troubleshoot and correct the security group configuration yourself.
Upgrade immediately to Enterprise Support so AWS can manage your security groups.
Wait to see if the issue resolves on its own because AWS will automatically roll back incorrect security group rules.

Show Answer

Answer: B) Use AWS documentation and Knowledge Center articles to troubleshoot and correct the security group configuration yourself.

Security group configuration is under your responsibility in the AWS shared responsibility model. On Basic Support, you do not have guaranteed technical troubleshooting. The correct first step is to use documentation and Knowledge Center articles to understand and fix your rules. AWS does not automatically roll back your security group changes, and upgrading to Enterprise is not required to correct your own configuration.

Enterprise Features: TAMs, Reviews, and Proactive Support

Role of the TAM

Enterprise Support includes a Technical Account Manager, a named AWS expert who knows your environment and coordinates guidance and escalations.

Proactive Reviews

Enterprise customers get proactive Well-Architected and architecture reviews, especially before major launches or migrations.

Operations Support

Enterprise-level support helps with incident management, runbooks, and escalation paths, not just reactive ticket handling.

Enterprise On-Ramp

Enterprise On-Ramp targets organizations starting large-scale production, offering some Enterprise benefits with a lower commitment.

Exam Cues

Look for phrases like dedicated TAM, proactive guidance, mission-critical global workloads, and complex multi-account setups to signal Enterprise tiers.

Key Terms and Concepts Review

Use these flashcards to reinforce your memory of AWS Support and resource concepts.

Basic Support: The free AWS Support plan for all customers, providing customer service for billing and account issues plus access to documentation, whitepapers, and AWS re:Post, but no guaranteed access to technical support engineers or response times.
Developer Support: A paid AWS Support plan aimed at development and test environments, offering business-hours email access to Cloud Support Associates and faster responses for general guidance than Basic, but not 24/7 phone or chat for production outages.
Business Support: An AWS Support plan designed for production workloads, providing 24/7 access to Cloud Support Engineers via phone, chat, and email, with defined response times for issues including production system down.
Enterprise Support: The highest AWS Support tier for large, mission-critical workloads, including a Technical Account Manager, proactive reviews and guidance, and the fastest response times for critical issues.
AWS re:Post: An AWS-managed, community-driven Q&A service where customers and AWS experts ask and answer questions about AWS services, architectures, and troubleshooting.
AWS Knowledge Center: A collection of short, focused articles written by AWS Support that explain how to resolve common issues and answer frequently asked questions.
AWS Well-Architected Framework: The AWS Well-Architected Framework describes the key concepts, design principles, and architectural best practices for designing and running workloads in the cloud.
When to open a support case: Open a support case when you face an AWS-side issue, an urgent production impact (especially on Business or Enterprise plans), or account/billing problems that cannot be resolved via documentation or self-service tools.
Self-service first mindset: Use documentation, re:Post, Knowledge Center, and monitoring/logs to troubleshoot issues that are likely in your code or configuration before escalating to AWS Support.

Putting It All Together: Decision Patterns for the Exam and Real Life

Step 1: Criticality

Classify workloads: dev/test → Basic/Developer; production with customers → Business+; mission-critical with strict SLAs → Enterprise levels.

Step 2: Features Needed

Need 24/7 phone/chat? → Business+. Need a TAM and proactive reviews? → Enterprise or Enterprise On-Ramp. Billing-only help? → Basic is enough.

Step 3: Help Path

Code/config issues → self-service first. Billing/account → billing case. AWS-side or urgent production issue → high-severity technical case (Business+).

Step 4: Cost vs Risk

Higher support tiers cost more but reduce downtime risk. For exam items, pick the lowest tier that clearly meets the stated risk and uptime needs.

Next in Your Study Path

As you take Skarp diagnostics and mocks, watch for keywords like 24/7, SLAs, or TAMs to practice applying these support-plan decision patterns.

Key Terms

AWS re:Post: An AWS-managed, community-driven Q&A service where customers and AWS experts ask and answer questions about AWS services, architectures, and troubleshooting.
Basic Support: The free AWS Support plan for all customers, providing customer service for billing and account issues plus access to documentation, whitepapers, and AWS re:Post, but no guaranteed access to technical support engineers or response times.
Case severity: A classification AWS uses for support cases, ranging from general guidance or low-severity questions to critical production system down issues, which affects target response times.
Business Support: An AWS Support plan designed for production workloads, providing 24/7 access to Cloud Support Engineers via phone, chat, and email, with defined response times for issues including production system down.
Developer Support: A paid AWS Support plan aimed at development and test environments, offering business-hours email access to Cloud Support Associates and faster responses for general guidance than Basic, but not 24/7 phone or chat for production outages.
Enterprise Support: The highest AWS Support tier for large, mission-critical workloads, including a Technical Account Manager, proactive reviews and guidance, and the fastest response times for critical issues.
AWS Knowledge Center: A collection of short, focused articles written by AWS Support that explain how to resolve common issues and answer frequently asked questions.
Enterprise On-Ramp Support: An AWS Support plan for organizations beginning to run production workloads at scale, offering higher-touch guidance and some proactive support capabilities without the full Enterprise Support commitment.
Shared responsibility model: The AWS shared responsibility model states that security and compliance are shared responsibilities between AWS and the customer, regardless of support plan.
AWS Well-Architected Framework: The AWS Well-Architected Framework describes the key concepts, design principles, and architectural best practices for designing and running workloads in the cloud.
Technical Account Manager (TAM): A named AWS expert available with Enterprise-level support tiers who knows your environment and provides ongoing guidance, coordination, and escalation management.