AWS Support Plans: Choosing the Right Business Assistance

This curriculum provides a comprehensive breakdown of the AWS Support ecosystem, focusing on how to select the optimal plan based on workload criticality, budget, and required technical assistance.

Prerequisites

Before starting this module, students should have a baseline understanding of:

• Cloud Fundamentals: Basic understanding of AWS Global Infrastructure (Regions/Availability Zones).
• Billing Basics: Familiarity with the AWS Management Console and how billing is generated.
• Shared Responsibility Model: Understanding that AWS manages the "Cloud" while the customer manages "in the Cloud."

Module Breakdown

Learning Objectives per Module

Module 1: Entry-Level Support

• Identify the features of the Basic Support Plan (Free).
• Determine when the Developer Plan is appropriate (non-production/testing).
• Understand response time guarantees for "System Impaired" issues.

Module 2: The Production Standard

• Evaluate the Business Support Plan as the minimum tier for production workloads.
• Analyze the shift from 12-hour response times to <1 hour for production down scenarios.
• Utilize the full suite of AWS Trusted Advisor checks.

Module 3: Enterprise Scale

• Distinguish between Enterprise On-Ramp and Enterprise support.
• Define the role of the Technical Account Manager (TAM) as a dedicated advocate.
• Identify the benefits of the AWS Concierge Support Team for billing inquiries.

Visual Anchors

Decision Flow: Selecting a Support Plan

Support Tier Response Matrix

Success Metrics

To master this curriculum, a student must be able to:

1. Correctly identify a plan based on a response time requirement (e.g., needing help in under 15 minutes).
2. Explain the difference between a "Pool of TAMs" (On-Ramp) and a "Dedicated TAM" (Enterprise).
3. Calculate cost-benefit for Infrastructure Event Management (IEM) during a product launch.
4. Differentiate between standard technical support and "Concierge" billing support.

Real-World Application

In the professional world, choosing the wrong support plan can lead to massive revenue loss.

[!IMPORTANT] If a production e-commerce site goes down on the Developer Plan, AWS is only obligated to respond within 12 business hours. On the Business Plan, that response time drops to <1 hour, 24/7.

• Scenario: A company like Netflix uses Enterprise Support because a 15-minute response time is necessary to maintain global availability.
• Scenario: A startup in the MVP phase uses the Developer Plan to keep costs low (~$29/mo) while still having a channel to ask technical questions.

Case Examples

Example 1: The E-commerce Launch

Problem: A retail company is launching its first online sale and expects 10x normal traffic. Solution: They should upgrade to at least the Business Plan to gain access to Infrastructure Event Management (IEM) (available for an additional fee) or Enterprise (where it is included) to have AWS experts help with scaling guidance.

Example 2: The Billing Dispute

Problem: An Enterprise customer has a complex multi-account structure and needs help consolidating their bill. Solution: They utilize the AWS Concierge Support Team, a specialized team included in Enterprise plans that focuses exclusively on billing and account best practices.

Formula / Concept Box

▶Click to expand: What is a TAM?

A Technical Account Manager (TAM) is your primary point of contact at AWS. They provide architectural guidance, coordinate with AWS experts, and proactively monitor your environment to ensure you are following the Well-Architected Framework.