Curriculum Overview: AWS Customer Enablement and Support Services

This curriculum provides a comprehensive roadmap for understanding how AWS enables customer success through technical support, professional guidance, and a robust partner ecosystem. This topic is a critical component of the AWS Certified Cloud Practitioner (CLF-C02) exam, specifically within Domain 4: Billing, Pricing, and Support.

## Prerequisites

Before diving into Customer Enablement services, learners should possess a foundational understanding of the following:

The AWS Shared Responsibility Model: Understanding which security and operational tasks belong to AWS vs. the customer.
Basic Cloud Concepts: Familiarity with the value proposition of the cloud (agility, cost savings, elasticity).
Fundamental AWS Billing: Knowledge of how AWS accounts are created and the basic structure of the AWS Management Console.
Core AWS Services: A high-level awareness of Compute (EC2), Storage (S3), and Networking (VPC).

## Module Breakdown

Module	Topic	Difficulty	Key Focus Area
1	The AWS Support Ecosystem	Beginner	Support Center, Health Dashboards, and Trust & Safety.
2	Tiered Support Plans	Intermediate	Comparing Basic, Developer, Business, and Enterprise tiers.
3	Human-Led Enablement	Intermediate	Technical Account Managers (TAM) and Professional Services.
4	Technical Resources	Beginner	Documentation, Whitepapers, and AWS Trusted Advisor.
5	The AWS Partner Network	Intermediate	APN, Marketplace, and Third-party integrations.

## Module Objectives per Module

Module 1: The AWS Support Ecosystem

Identify the role of the AWS Support Center as a hub for managing cases.
Differentiate between the AWS Health Dashboard (service-wide status) and the Personal Health Dashboard (account-specific alerts).
Understand how to report resource abuse via the AWS Trust and Safety team.

Module 2: Tiered Support Plans

Memorize the response time SLAs for "Production System Down" and "Business Critical System Down."
Identify which plans offer 24/7 access to engineers vs. business-hours-only access.

Module 3: Human-Led Enablement

Define the role of the Technical Account Manager (TAM) as a designated advocate.
Explain the scope of AWS Professional Services for complex migrations and architectural reviews.

Module 4: Technical Resources

Locate official resources like AWS Prescriptive Guidance, Whitepapers, and re:Post.
Explain how AWS Trusted Advisor provides automated best practice checks across cost, security, and performance.

Module 5: The AWS Partner Network (APN)

Distinguish between Independent Software Vendors (ISVs) and System Integrators (SIs).
Identify the benefits of AWS Marketplace for procuring and deploying third-party software.

## Visual Anchors

AWS Support Plan Decision Logic

Loading Diagram...

The Enablement Framework

Loading Diagram...

## Success Metrics

To demonstrate mastery of this curriculum, the learner should be able to:

Categorize Support Plans: Correctly assign a support tier to a business scenario based on budget and uptime requirements.
Identify TAM Roles: Distinguish between a standard Support Engineer and a Technical Account Manager (TAM).
Navigate Documentation: Quickly identify where to find architectural best practices (e.g., Whitepapers vs. Trusted Advisor).
Recall Response Times: Identify that 15 minutes is the fastest response time available (Enterprise) for business-critical outages.
Utilize Trusted Advisor: List the 5 categories Trusted Advisor checks ( $Cost, Security, Fault Tolerance, Performance, Service Limits$ ).

## Real-World Application

In a professional setting, understanding Customer Enablement is the difference between a 48-hour outage and a 15-minute resolution.

[!IMPORTANT] A Cloud Practitioner acting as a consultant must know when to recommend the Business Plan (for production environments) vs. the Enterprise Plan (for organizations requiring strategic guidance through a TAM).

Scenario: A startup is migrating its payment gateway to AWS.

Without Enablement: They might misconfigure their VPC, leading to a security breach.
With Enablement: They use AWS Trusted Advisor to identify security gaps and engage an AWS Partner to validate their architecture, ensuring compliance and stability from Day 1.

## Examples Section: Choosing Your Support Tier

▶Click to expand: Scenario-Based Support Examples

Business Scenario	Recommended Plan	Reasoning
Individual Experimenting	Basic	No cost; access to documentation and community forums is sufficient for non-critical learning.
Early-stage Startup (Dev/Test)	Developer	Requires low-cost email support during business hours for technical questions.
E-commerce Site (Production)	Business	Requires 24/7 phone/chat access because a system outage directly impacts revenue.
Global Bank (Mission Critical)	Enterprise	Requires a dedicated TAM for proactive scaling and the fastest possible (15 min) response times.

[!TIP] Exam Hint: Remember that Basic Support includes access to Core Trusted Advisor checks and the Health Dashboard at no extra cost, but does not include technical support cases.