Curriculum Overview: AWS Support Plans and Technical Resources

This curriculum provides a comprehensive deep-dive into the various support options available to AWS customers, ranging from individual developers to global enterprises. It focuses on identifying the correct support tier based on workload criticality, response time requirements, and technical guidance needs.

Prerequisites

Before beginning this module, learners should have a foundational understanding of the following:

• AWS Global Infrastructure: Basic knowledge of Regions and Availability Zones.
• The AWS Free Tier: Understanding how accounts are initially provisioned.
• Cloud Economics: A basic grasp of the "pay-as-you-go" model versus fixed monthly support costs.

Module Breakdown

Learning Objectives per Module

MOD-01: Basic Support

• Identify the services included by default (Free) for all AWS customers.
• Example: Using the AWS Health Dashboard to check if a specific service outage is affecting your region.

MOD-02: Developer Support

• Determine when to upgrade from Basic to Developer for testing purposes.
• Example: A student building a portfolio app who needs help with a specific CLI configuration error within 24 business hours.

MOD-03: Business Support

• Explain the benefits of 24/7 technical support and the "Production System Down" response time of < 1 hour.
• Example: An e-commerce site experiencing a checkout failure during a sale requiring immediate engineer intervention.

MOD-04 & MOD-05: Enterprise Levels

• Differentiate between a Technical Account Manager (TAM) pool (On-Ramp) and a Dedicated TAM (Enterprise).
• Understand the role of the Concierge Support Team for billing and account best practices.
• Example: A global bank performing a massive migration of sensitive data requiring Infrastructure Event Management (IEM) to ensure zero downtime.

Visual Anchors

Plan Selection Logic

Response Time Comparison

Success Metrics

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

1. Match Tiers to SLAs: Correctly identify that Enterprise Support offers a < 15-minute response time for business-critical system failures.
2. Identify TAM Roles: Explain that the TAM provides architectural guidance and advocacy, not just reactive troubleshooting.
3. Differentiate Trusted Advisor Access: Know that Basic/Developer get "Core" checks, while Business and above get the "Full Set" of checks (7 core checks vs. $100+ full checks).
4. Cost Justification: Explain why a company would pay $15,000/month for Enterprise support versus the $100$/month Business tier based on risk mitigation.

Real-World Application

In a career context, this knowledge is vital for Cloud Architects and FinOps Analysts:

• Scenario: A startup is moving from a prototype to a live product. The architect must recommend the Business Support plan to ensure they have 24/7 phone access if the site goes down, which the Developer plan (web-only) does not provide.
• Scenario: A large corporation is planning a "Black Friday" sale. The FinOps lead ensures they are on the Enterprise plan to leverage Infrastructure Event Management (IEM) for scaling guidance.

Examples & Scenarios

[!IMPORTANT] Choosing the wrong plan can lead to significant downtime or unnecessary costs. Always align the plan with the "Criticality" of the workload.

▶Click to expand: Key Term Definitions

• Technical Account Manager (TAM): Your primary point of contact at AWS who provides proactive guidance and helps you follow best practices. (Real-world: Like having a dedicated consultant on speed-dial).
• AWS Trusted Advisor: An online tool that provides real-time guidance to help you provision your resources following AWS best practices. (Real-world: An automated "health checkup" for your cloud environment).
• Concierge Support: A senior customer service agent specialized in billing and account assistance. (Real-world: A VIP helper for complex billing questions in large organizations).