Creating support cases and case management

In the AWS Management Console, you can create three types of customer cases in AWS Support:

• Account and billing support cases are available to all AWS customers. You can get help with billing and account questions.
• Service limit increase requests are available to all AWS customers. For more information about the default service quotas, formerly referred to as limits, see AWS service quotas in the AWS General Reference.
• Technical support cases connect you to technical support for help with service-related technical issues and, in some cases, third-party applications. If you have Basic Support, you can't create a technical support case.

Notes

• To change your support plan, see Changing AWS Support Plans.
• To close your account, see Closing an Account in the AWS Billing User Guide.
• To find common troubleshooting topics for AWS services, see Troubleshooting resources.
• If you're a customer of an AWS Partner that is part of the AWS Partner Network, and you use Resold Support, contact your AWS Partner directly for any billing related issues. AWS Support can't assist with non-technical issues for Resold Support, such as billing and account management. For more information, see the following topics:

• How AWS Partners can determine AWS Support plans in an organization
• AWS Partner-Led Support

Creating a support case

You can create a support case in the Support Center of the AWS Management Console.

Notes

• You can sign in to Support Center as the root user of your AWS account or as an AWS Identity and Access Management (IAM) user. For more information, see Manage access to AWS Support Center.
• If you can't sign in to Support Center and create a support case, you can use the Contact Us page instead. You can use this page to get help with billing and account issues.

To create a support case

1. Sign in to the AWS Support Center Console .

Tip

In the AWS Management Console, you can also choose the question mark icon ( ) and then choose Support Center.

• Account and billing
• Technical
• For service quota increases, choose Looking for service limit increases? and then follow the instructions for Creating a service quota increase.

Tip

• Error messages that you received
• Troubleshooting steps that you followed
• How you're accessing the service:

• AWS Management Console
• AWS Command Line Interface (AWS CLI)
• API operations

1. Web – Receive a reply in Support Center.
2. Chat – Start a live chat with a support agent. If you can't connect to a chat, see Troubleshooting.
3. Phone – Receive a phone call from a support agent. If you choose this option, enter the following information:

• Country or region
• Phone number
• (Optional) Extension

Notes

• The contact options that appear depend on the type of case and your support plan.
• You can choose Discard draft to clear your support case draft.

Note

If you have the Basic Support plan, the Additional contacts option isn't available. However, the Operations contact specified in the Alternate Contacts section of the My Account page receives copies of the case correspondence, but only for the specific case types of account and billing, and technical.

Describing your problem

Make your description as detailed as possible. Include relevant resource information, along with anything else that might help us understand your issue. For example, to troubleshoot performance, include timestamps and logs. For feature requests or general guidance questions, include a description of your environment and purpose. In all cases, follow the Description Guidance that appears on your case submission form.

When you provide as much detail as possible, you increase the chances that your case can be resolved quickly.

Choosing a severity

You might be inclined to always create a support case at the highest severity that your support plan allows. However, we recommend that you choose the highest severities for cases that can't be worked around or that directly affect production applications. For information about building your services so that losing single resources doesn't affect your applications, see the Building Fault-Tolerant Applications on AWS technical paper.

The following table lists the severity levels, response times, and example problems.

Notes

• You can't change the severity code for a support case after you create one. If your situation changes, work with the AWS Support agent for your support case.
• For more information about the severity level, see the AWS Support API Reference.

General guidance

You have a general development question, or you want to request a feature. (*Developer, Business, Enterprise On-Ramp, or Enterprise Support plan)

System impaired

Non-critical functions of your application are behaving abnormally, or you have a time-sensitive development question. (*Developer, Business, Enterprise On-Ramp, or Enterprise Support plan)

Production system impaired

Important functions of your application are impaired or degraded. (Business, Enterprise On-Ramp, or Enterprise Support plan)

Production system down

Your business is significantly impacted. Important functions of your application aren't available. (Business, Enterprise On-Ramp, or Enterprise Support plan)

Your business is at risk. Critical functions of your application aren't available (Enterprise Support plan). Note that this is 30 minutes for the Enterprise On-Ramp Support plan.

Response times

We make every reasonable effort to respond to your initial request within the indicated timeframe. For information about the scope of support for each AWS Support plan, see AWS Support features .

If you have a Business, Enterprise On-Ramp, or Enterprise Support plan, you have 24/7 access for technical support. *For Developer Support, response targets for support cases are calculated in business hours. Business hours are generally defined as 08:00 to 18:00 in the customer country, excluding holidays and weekends. These times can vary in countries with multiple time zones. The customer country information appears in the Contact Information section of the My Account page in the AWS Management Console.

Note

If you choose Japanese as your preferred contact language for support cases, support in Japanese may be available as follows:

• If you need customer service for non-technical support cases, or if you have a Developer Support plan and need technical support, support in Japanese is available during business hours in Japan defined as 09:00 AM to 06:00 PM Japan Standard Time (GMT+9), excluding holidays and weekends.
• If you have a Business, Enterprise On-Ramp, or Enterprise Support plan, technical support is available 24/7 in Japanese.

If you choose Chinese as your preferred contact language for support cases, support in Chinese may be available as follows:

• If you need customer service for non-technical support cases, support in Chinese is available 09:00 AM to 06:00 PM (GMT+8), excluding holidays and weekends.
• If you have a Developer Support plan, technical support in Chinese is available during business hours generally defined as 8:00 AM to 6:00 PM in your country as set in My Account , excluding holidays and weekends. These times may vary in countries with multiple time zones.
• If you have a Business, Enterprise On-Ramp, or Enterprise Support plan, technical support is available 24/7 in Chinese.

If you choose Korean as your preferred contact language for support cases, support in Korean may be available as follows:

• If you need customer service for non-technical support cases, support in Korean is available during business hours in Korea defined as 09:00 AM to 06:00 PM Korean Standard Time (GMT+9), excluding holidays and weekends.
• If you have a Developer Support plan, technical support in Korean is available during business hours generally defined as 8:00 AM to 6:00 PM in your country as set in My Account , excluding holidays and weekends. These times may vary in countries with multiple time zones.
• If you have a Business, Enterprise On-Ramp, or Enterprise Support plan, technical support is available 24/7 in Korean.