Official Support Channels
Type | Contact |
---|---|
Help | AWS Support Center |
Form | Create Support Case |
Web | AWS re:Post |
X | @AWSSupport |
When contacting aws support, consider the urgency of your issue.
For Non-Urgent Issues
- Choose one support channel (email is recommended)
- Wait for a response before trying other channels
- Response times: 24-48 hours for standard issues
For Urgent Issues
- Contact through multiple channels simultaneously
- Include as much relevant information as possible
- Mark emails as "URGENT" in the subject line
Priority Tip
We can escalate your case to get faster attention. Learn more about our Priority Agent service
Complete Guide to aws Support in 2025 - Best Ways to Get Help
Best Ways to Contact AWS Support
Support options vary by plan level:
- Enterprise Support
- 24/7 phone, email, and chat support
- 15-minute response for critical issues
- Dedicated Technical Account Manager
- Architectural and operational reviews
- Business Support
- 24/7 phone, email, and chat support
- 1-hour response for urgent issues
- Trusted Advisor checks
- Developer Support
- Technical support via email
- 12-24 hour response time
- Limited Trusted Advisor checks
Tips for Faster AWS Support Resolution
Follow these tips for efficient support:
- Case Information:
- Include AWS account ID and region
- List affected resources (instance IDs, etc.)
- Attach relevant CloudWatch logs
- Provide error messages and timestamps
- Business Impact:
- Clearly state production impact
- Quantify affected users/services
- Note revenue implications
- Specify urgency level
- Troubleshooting:
- Document steps already taken
- Share relevant IAM permissions
- Include architecture diagrams
- Note recent changes
Common AWS Support Issues & Solutions
Account & Billing
- Unexpected Charges: Review Cost Explorer and billing dashboard
- Account Access: Use root account recovery process
- Service Limits: Request quota increases proactively
Service Issues
- EC2 Problems: Check instance status and system logs
- Connectivity Issues: Review VPC and security groups
- Database Performance: Monitor CloudWatch metrics
Security Concerns
- Unauthorized Access: Review CloudTrail and GuardDuty
- IAM Issues: Audit permissions and roles
- DDoS Attacks: Enable Shield and WAF protection
When to Escalate Your AWS Support Case
Consider escalation in these situations:
- Production system outages
- Data loss or corruption risks
- Security breaches
- Significant performance degradation
- Business-critical service disruptions
Escalation Process
- Update case severity if situation worsens
- Contact Technical Account Manager (Enterprise)
- Request supervisor review
- Consider support plan upgrade
Support Response Times
Understanding typical response times can help set expectations and plan accordingly:
Issue Type | Expected Response Time | Best Contact Method |
---|---|---|
Enterprise Critical | 15 minutes | Phone/Chat |
Production System Down | 1 hour | Business Support |
System Impaired | 4 hours | Developer Support |
General Guidance | 24 hours | Support Center |
Basic Support | Best Effort | Documentation |
Note: Response times may vary during peak periods or holidays.
Pro Tip for Urgent aws Support
For business-critical issues affecting your payment processing, consider using our Priority Agent service. We'll help escalate your case and get faster attention from aws support. Our service has helped hundreds of businesses resolve urgent aws support issues quickly.