How to Open a Support Case in AWS Support Center

How to Create a Support Case in AWS Support Center

A Comprehensive DevOps Guide: Support Plans, Severity Classifications, Multi-Channel Contact & CLI Case Management

⏱️ 14 Min Read 🏷️ AWS Support Center & Troubleshooting ⚡ Level: All Cloud Engineers

Whether you are encountering unexpected latency on Amazon EC2, debugging an intermittent AWS Lambda execution timeout, or requesting an increase in your regional VPC Elastic IP limits, knowing how to create and manage support cases in AWS Support Center is a fundamental cloud operations capability.

In this visual guide, you will learn the exact steps to submit technical and billing cases, select proper severity levels for target SLAs, choose between Web, Live Chat, and Phone callback, and manage tickets using the AWS CLI.

🎯 What You Will Master

Comparing AWS Support Plans (Basic, Developer, Business, Enterprise On-Ramp, Enterprise).
Navigating the AWS Support Center dashboard.
Opening Technical vs Account/Billing vs Service Limit Increase cases.
Understanding Severity ratings and response time SLAs (from 15 min to 24 hrs).
Choosing communication channels: Web (Email), Instant Live Chat, and Immediate Phone Callback.
Querying and creating support tickets via the AWS CLI.

1. Overview of AWS Support Plans

AWS offers tiered support plans suited for different deployment scales and operational criticality:

Support Plan	Target Workload	Critical (P1) SLA	Communication Channels
Basic (Free)	Account & Billing, Service Limits, Documentation	N/A (No Tech Support)	Web Console (Billing/Quota only)
Developer	Early prototyping and testing	N/A (General guidance < 24h, System impaired < 12h)	Email (1 primary contact, Business hours)
Business	Production enterprise workloads	< 1 hour (Production Down)	24/7 Phone, Chat, & Web (Unlimited contacts)
Enterprise On-Ramp	High-scale business-critical workloads	< 30 minutes (24/7)	24/7 Phone, Chat, Web + Dedicated TAM pool
Enterprise	Mission-critical global production footprints	< 15 minutes (24/7)	24/7 Phone, Chat, Web + Dedicated Technical Account Manager (TAM)

💡 Note for Free Tier Accounts: You do not need a paid support plan to open cases for Billing Disputes, Service Quota / Limit Increases (e.g., vCPU limits), or Root Account Access issues. These categories are completely free on all AWS accounts!

2. Step-by-Step: Creating a Case in AWS Support Center

1 Open AWS Support Center

Sign in to the AWS Support Center Console (console.aws.amazon.com/support).
On the top navigation bar, you can also click the Question Mark (?) icon > Support Center.
Review your active cases, AWS Trusted Advisor checks, and AWS Health Dashboard notifications.
Click the orange Create case button.

AWS Support Center Dashboard with Create Case Button

Figure 1: AWS Support Center — Overview dashboard displaying open cases, Trusted Advisor alerts, and the 'Create case' button.

2 Select Case Type and Service Classification

Under How can we help?, select:
- Account and billing: For invoice queries, payment method issues, or Free Tier fee adjustments.
- Service limit increase: For raising regional service quotas (e.g., VPC CIDR blocks, Elastic IPs).
- Technical: For troubleshooting service errors, crashes, or connectivity drops.
Service: Select the relevant AWS service (e.g., EC2, Lambda, S3, RDS, CloudFront).
Category: Select the specific sub-topic (e.g., Linux Instance, Storage / EBS Volumes, Security Groups & Network).
Severity: Select the business impact level:
- Production system down: Core business features completely non-functional.
- Production system impaired: Significant functions impacted, but partial workaround exists.
- System impaired: Non-critical development service experiencing defects.
- General guidance: Questions regarding architecture or best practices.
Subject & Description: Enter the exact Resource ID (e.g., Instance ID i-0abcdef12345678), region, error logs, and detailed timeline.

AWS Support Center Create Case Form and Severity Selection

Figure 2: Create Case Wizard — Specifying Service (EC2), Category (Linux Instance), Severity, Subject, and Problem Description.

3 Attach Diagnostics & Choose Contact Method

Attachments: Click Upload attachments to supply system logs, EC2 serial console captures, CloudWatch error screenshots, or network packet traces (up to 3 files per upload).
Contact Method: Choose how you want AWS engineers to reach you:
- Web (Email): Asynchronous updates sent directly to your registered support email.
- Chat: Immediate live browser chat with an assigned AWS Technical Support Engineer (typically connects in < 2 minutes on Business/Enterprise plans).
- Phone: AWS automated dialer initiates an instant callback to your provided direct phone number.
Click the orange Submit button to open the case.

AWS Support Center Attachments and Contact Methods

Figure 3: Selecting Contact Methods (Web, Live Chat, Phone Callback) and uploading diagnostic log files.

3. Managing AWS Support Cases via AWS CLI

On Business or Enterprise plans, you can interact with the AWS Support API directly from your terminal or CI/CD pipelines:

# 1. Describe available service codes and categories

aws support describe-services --service-code-list "amazon-elastic-compute-cloud-linux"


# 2. Describe severity levels

aws support describe-severity-levels


# 3. Create a technical support case

aws support create-case \

  --subject "EC2 instance i-0abcdef12345678 unreachable via SSH" \

  --service-code "amazon-elastic-compute-cloud-linux" \

  --severity-code "urgent" \

  --category-code "other" \

  --communication-body "Instance unresponsive after kernel update at 10:15 UTC. Console logs attached." \

  --language "en" \

  --issue-type "technical"


# 4. List open cases

aws support describe-cases --include-resolved false --query "cases[*].[caseId,subject,status,severityCode]" --output table

4. Pro Tips for Fast Resolution by AWS Support

💡 DevOps Engineering Checklist

Always Provide Resource ARNs / IDs: Give exact IDs such as i-04a1b2c3d4e5f6789 or ARN arn:aws:iam::123456789012:role/MyDevOpsRole.
Include AWS Region: e.g., us-east-1 (N. Virginia) or eu-west-1 (Ireland).
Get Instance Console Output: Run this command to capture system boot output before submitting:
aws ec2 get-console-output --instance-id i-0abcdef12345678 --output text > console_boot.log
Use Live Chat for Urgent Cases: Live Chat is almost always faster than web tickets for immediate interactive troubleshooting.

5. Summary

By leveraging AWS Support Center effectively, specifying clear reproduction steps, and utilizing live communication channels, DevOps teams can rapidly resolve complex cloud challenges and keep production environments running with maximum reliability.