AWS Support Plans

Think of it as: “Car Insurance & Roadside Assistance” – Imagine you own a car (your AWS Cloud environment). You need different levels of protection and help depending on how you use the car.

• Basic Plan (The Free Manual): This is like buying a car and getting just the Owner’s Manual. If the car breaks down, you have to read the manual or search Google or Official Documents to fix it yourself. There is no mechanic to call.
• Developer Plan (Local Mechanic): You pay a small fee to have access to a mechanic via email during working hours. If you are just learning to drive or testing the car in your garage, this is enough.
• Business Plan (24/7 Service Center): You use the car for your daily job (production). You need a 24/7 helpline. If the car stops at 2 AM, someone will answer the phone and help you fix it quickly.
• Enterprise On-Ramp (Priority Lane): You have a small fleet of delivery trucks. You can’t afford delays. You get priority access to a pool of senior mechanics who know about business vehicles.
• Enterprise Plan (Personal Pit Crew): You run a Formula 1 racing team (Mission-Critical). You have a Designated Technical Account Manager (TAM) a personal chief mechanic who knows your car inside out. If a tire bursts, they are there in 15 minutes.

AWS (Amazon Web Services) doesn’t just give you servers; they offer “Support Plans” to help you when things go wrong. By default, everyone gets the Basic plan for free. As your usage grows from “just playing around” to “running a big company,” you can upgrade to get faster help and human experts.

The 5 Main Plans

1. Basic (Free):
   • For whom: Everyone.
   • What you get: Access to customer service (for billing issues) and documentation. You cannot email a technical engineer for help with a server error.
   • Key Tool: AWS Trusted Advisor (gives you automated tips, but only the 7 core checks).
2. Developer:
   • For whom: Students or developers testing new apps.
   • What you get: You can email a Cloud Support Associate during business hours.
   • Restriction: You can only ask questions about “how to use” services, not “how to design” a massive system.
3. Business:
   • For whom: Companies running live apps (Production workloads).
   • What you get: 24×7 access via phone, chat, and email to Cloud Support Engineers.
   • Key Feature: If your system goes down, they reply in less than 1 hour.
4. Enterprise On-Ramp:
   • For whom: Companies that need serious help but aren’t huge corporations yet.
   • What you get: Access to a pool of Technical Account Managers (TAMs). These are experts who proactively help you.
   • Speed: fast response times (30 mins for business-critical issues).
5. Enterprise:
   • For whom: Large corporations (Netflix, Banks) where downtime costs millions.
   • What you get: A Designated TAM (a specific person assigned to you). They meet you regularly to plan your growth.
   • Speed: 15-minute response time for critical issues.

• AWS Trusted Advisor: An automated tool that scans your cloud setup and says, “Hey, you left this door open (security risk)” or “You are paying for a server you aren’t using (cost saving).”
• AWS Personal Health Dashboard: A personalized alert system. If AWS has a power outage in the specific region where your servers are, this dashboard lights up to tell you.

DevSecOps Architect Level

For an Architect, the Support Plan is not just about “fixing breaks”; it is a strategic lever for Operational Excellence and Cost Optimization.

Key Differentiators & Architectural Value

1. Technical Account Manager (TAM):
   • Enterprise On-Ramp: Gives you access to a pool of TAMs. Good for reactive guidance.
   • Enterprise: Gives you a Designated TAM. This is a strategic partner who participates in your Well-Architected Reviews, helps with capacity planning for big events (like Black Friday), and advocates for your feature requests with AWS product teams.
2. Architectural Guidance:
   • Developer: General guidance (links to docs).
   • Business: Contextual guidance (specific to your use case).
   • Enterprise: Consultative review (deep dive into your specific application architecture).
3. Programmatic Case Management (API):
   • Available from Business tier upwards. This allows you to integrate AWS Support into your own ITSM tools (like ServiceNow or Jira). You can automatically open an AWS support case when your monitoring system detects a critical failure.
4. Identity & Access Management (IAM):
   • Architects must secure who can open support cases. You don’t want a junior dev opening a “System Down” case by accident. You can use IAM policies to restrict access to the Support Center.

• AWS Countdown: Replaces the old “Infrastructure Event Management” (IEM). It helps you plan for big launches.
  • Note: Enterprise On-Ramp gets 1 free engagement/year. Enterprise gets it included.
• AWS Incident Detection and Response: An add-on for Enterprise/Business tiers. AWS proactively monitors your workload and calls you if something breaks (5-minute response target).

—

Architect’s Response Time Matrix (SLA Targets)

—

Use Cases

• Startup (MVP Phase): Use Developer plan. You are iterating fast, bugs are expected, and you need cheap advice on how to configure services.
• E-Commerce Site (Growth Phase): Use Business plan. If your checkout page breaks, you lose money every minute. You need the < 1 hour response time.
• Banking/Healthcare (Scale Phase): Use Enterprise plan. You need the Designated TAM to ensure compliance, security reviews, and instant support during audits or crises.

Benefits

• Proactive Security: Enterprise plans include “Proactive Security Reviews” to catch vulnerabilities before hackers do.
• Cost Efficiency: Full Trusted Advisor checks (Business tier+) often find enough cost savings (idle resources) to pay for the support plan itself.
• Operational Resilience: Access to “Support Automation Workflows” helps you fix common issues (like resetting an EC2 instance) automatically.

—

Technical Challenges

1. Cost Management: Enterprise support starts at a high minimum monthly commit (e.g., $15,000/mo or % of usage), which can be a shock for smaller companies.
2. Plan Selection Friction: Moving from Business to Enterprise is a big contract change; it’s not just a button click like scaling an EC2 instance.
3. Shared Responsibility Model: AWS Support helps with the cloud infrastructure, but they will not fix your application code. Beginners often confuse “Support” with “Consulting/Coding Service.”

Cheat Sheet