- What is Amazon Web Services Support (AWS Support)?
- How are the enhanced AWS Support tiers different from Basic Support?
- What types of issues are supported?
- What level of architecture support is provided by AWS Support?
- I only use one or two services. Can I purchase support for just the one(s) I'm using?
- How many support cases can I initiate with AWS Support?
- How many users can open technical support cases?
- How quickly will you get back to me?
- How quickly will you fix my issue?
- How do I contact you?
- I'm not in the US. Can I sign up for AWS Support?
- Do you speak my language?
- How do I access Japanese Support?
- Who should use AWS Support?
- How do I offer support for my end customer's AWS-related issues?
- I use an application someone else built on Amazon Web Services. Can I use AWS Support?
- How can I get started with AWS Support?
- How much does AWS Support cost?
- Why does my AWS Support bill spike when I purchase EC2 and RDS Reserved Instances and ElasticCache Reserved Cache Nodes?
- How will I be charged and billed for my use of AWS Support?
- How do I cancel my AWS Support account?
- Can I sign up for AWS Support, receive assistance, and then cancel the subscription? If so, will I be charged a pro-rated amount?
- What is Infrastructure Event Management (IEM)?
- How does Chat support work?
- What are the best practices for fault tolerance?
- How do I configure Identity and Access Management (IAM) for support?
- How long is case history retained?
- Can I get a history of AWS Support API calls made on my account for security analysis and operational troubleshooting purposes?
- What is Support for Health Checks?
- Which AWS services provide access to support through Support for Health Checks?
- How can I get support if an EC2 instance fails the system status check?
- How can I get support if an EBS volume is stuck in attaching or has disabled I/O?
- What is the response time for my Support for Health Checks support case?
- How do I check the status of my case after it has been opened?
- Do I have to open a case for each instance that is unresponsive?
- Why must an EC2 instance fail the system status check for 20 minutes? Why not just allow customers to open a case immediately?
- Can any of my Identity and Access Management (IAM) users open a case?
- What is AWS Trusted Advisor?
- How do I access Trusted Advisor?
- What made you choose these checks/recommendations over others?
- Does AWS Trusted Advisor monitor my usage? Can Amazon see what I’m doing with AWS?
- What does AWS Trusted Advisor check?
- How does the AWS Trusted Advisor notification work?
- How does the "Recent Changes" feature work?
- How does the "Exclude Items" function work? (The "Suppress" function)
- What is an "action link"?
- How to manage the access to AWS Trusted Advisor console? What is the IAM policy?
- How do I access Trusted Advisor via API?
- How often can I refresh my Trusted Advisor result?
- What does “The check could not be completed in the allotted time” mean? How can I fix this?
- How do Trusted Advisor activities affect my Amazon CloudTrail logs?
- Which Trusted Advisor checks are available to all AWS customers?
- How do I securely control access to my AWS services and resources?
- What is Consolidated Billing?
- How can I use my AWS bill to evaluate costs?
- What are blended rates?
- Why don't I see the same figures in the Billing and Cost Management console as I see in the detailed billing report?
- How do I tell which accounts benefited from Reserved Instance pricing?
- How are credits applied across a consolidated bill?
- How do I use the AWS Billing and Cost Management console?
- How do I use Cost Explorer?
- How do I use the Amazon EC2 instance usage reports?
- How do I use the Reserved Instance utilization report?
- How do I tell if my Reserved Instances are being used?
- Can I restrict a Reserved Instance benefit to a single account/instance?
- How do I see how Reserved Instances are applied across my entire consolidated bill?
- How do I tell if and why a Reserved Instance is underutilized?
- Which accounts are charged sales tax and why?
- How do I submit an urgent limit increase request?
- How do we bill our end customers based on the detailed billing report?
AWS Support gives customers help on technical issues and additional guidance to operate their infrastructures in the cloud. Customers can choose a tier that meets their specific requirements, continuing the AWS tradition of providing the building blocks of success without bundling or long term commitments.
AWS Support is one-on-one, fast-response support from experienced technical support engineers. The service helps customers use AWS's products and features. With pay-by-the-month pricing and unlimited support cases, customers are freed from long-term commitments. Customers with operational issues or technical questions can contact a team of support engineers and receive predictable response times and personalized support.
AWS Basic Support offers all AWS customers access to our Resource Center, Service Health Dashboard, Product FAQs, Discussion Forums, and Support for Health Checks – at no additional charge. Customers who desire a deeper level of support can subscribe to AWS Support at the Developer, Business, or Enterprise level.
Customers who choose AWS Support gain one-on-one, fast-response support from AWS engineers. The service helps customers use AWS's products and features. With pay-by-the-month pricing and unlimited support cases, customers are freed from long-term commitments. Customers with operational issues or technical questions can contact a team of support engineers and receive a predictable response times and personalized support.
Your AWS Support covers development and production issues for AWS products and services, along with other key stack components.
- "How to" questions about AWS service and features
- Best practices to help you successfully integrate, deploy, and manage applications in the cloud
- Troubleshooting API and AWS SDK issues
- Troubleshooting operational or systemic problems with AWS resources
- Issues with our Management Console or other AWS tools
- Problems detected by Health Checks
- A number of third-party applications such as OS, web servers, email, databases, and storage configuration
AWS Support does not include:
- Code development
- Debugging custom software
- Performing system administration tasks
The level of architecture support provided varies by support level. Higher service levels provided progressively more support for the customer use case and application specifics.
Developer: Building Blocks
Guidance on how to use all AWS products, features, and services together. Includes guidance on best practices and generalized architectural advice.
Business: Use Case Guidance
Guidance on what AWS products, features, and services to use to best support your specific use cases. Includes guidance on optimizing AWS products and configuration to meet your specific needs.
Enterprise: Application Architecture
Consultative partnership supporting specific use cases and applications. Includes design reviews and architectural guidance. Enterprise-level customers support team includes a dedicated Technical Account Manager, and access to an AWS Solutions Architect.
No. Our Support offering covers the entire AWS service portfolio. As many of our customers are using multiple infrastructure web services together within the same application, we’ve designed AWS Support with this in mind. We’ve found that the majority of support issues, among users of multiple services, relate to how multiple services are being used together. Our goal is to support your application as seamlessly as possible.
As many as you need. Basic Support plan customers are restricted to customer support and service limit increase cases.
The Business and Enterprise support plans allow an unlimited number of users to open technical support cases (supported by AWS Identity and Access Management (IAM)). The Developer Support plan allows one user to open technical support cases. Customers with the Basic Support plan cannot open technical support cases.
Our first-contact response times are based on your chosen severity level for each case. We will use all reasonable efforts to provide responses within these time frames:
24 hours or less
24 hours or less
24 hours or less
|12 hours or less||12 hours or less||12 hours or less|
|4 hours or less||4 hours or less|
|1 hour or less||1 hour or less|
|15 minutes or less|
*Business hours are generally defined as 8:00 AM to 6:00 PM in the customer country as set in My Account console, excluding holidays and weekends. These times may vary in countries with multiple time zones.
That depends on your issue. The problems that application or service developers encounter vary widely, making it difficult to predict issue resolution times. We can say, however, that we'll work closely with you to resolve your issue as quickly as possible.
If you have a paid Support plan, you can open a web support case from Support Center. If you have Business or Enterprise-level Support, you can request that AWS contact you at any convenient phone number or start a conversation with one of our engineers via chat.
You can also see your options for contacting Support on the Contact Us page.
Support for Health Checks
Support for Health Checks monitors some of the status checks that are displayed in the Amazon EC2 console. When one of these checks does not pass, all customers have the option to open a high-severity Technical Support case. For more information, see Support for Health Checks.
Yes, AWS Support is a global organization. Any AWS customer may sign up for and use AWS Support.
AWS Support is available in English and Japanese.
To access Japanese Support, subscribers should select Japanese as their language preference from the dropdown at the top right of any AWS web page. Once your language preference is set to Japanese, all Support inquiries will be sent to our Japanese Support team.
We recommend all AWS customers use AWS Support to ensure a seamless experience leveraging AWS infrastructure services. We have created multiple tiers to fit your unique technical needs and budget.
If an issue is related to your AWS account, we'll be happy to help you. For problems with a resource provisioned under their own accounts, your customers will need to contact us directly. Due to security and privacy concerns we can only discuss specific details with the account holder of the resource in question. You many also inquire about becoming an AWS Partner, which offers different end-customer support options. For more information, see AWS Partner Network.
If the application uses resources provisioned under your AWS account, you can use AWS Support. First, we'll help you to determine whether the issue lies with an AWS resource or with the third-party application. Depending on that outcome, we'll either work to resolve your issue or let you know to contact the application developer for continued troubleshooting.
You can add AWS Support during the sign up process for any AWS product. Or simply select an AWS Support Plan.
AWS Support offers differing levels of service to align with your needs and budget, including our Developer, Business, and Enterprise Support plans. See our pricing table for more details.
When you prepay for compute needs with Amazon Elastic Compute Cloud (Amazon EC2) Reserved Instances, Amazon Relational Database Service (Amazon RDS) Reserved Instances, Amazon Redshift Reserved Instances, or Amazon ElastiCache Reserved Cache Nodes and are enrolled in a paid AWS Support plan, the one-time (upfront) charges for the prepaid resources are included in the calculation of your AWS Support charges in the month you purchase the resources. In addition, any hourly usage charges for reserved resources are included in the calculation of your AWS Support charges each month.
If you have existing reserved resources when you sign up for a Support plan, the one-time (upfront) charges for the reserved resources, prorated over the term of the reservation, are included in the price calculation for the first month of AWS Support. For example, if you purchase a three-year reserved instance on January 1 and sign up for the Business support plan on October 1 of the same year, 75% of the upfront fee you paid in January is included in the calculation of Support costs for October.
Upon signup, you will be billed a minimum monthly service charge for the current month (prorated) and the following month.
In subsequent months, you will be billed the minimum for the following month in advance. If your usage-based charges exceed the minimum monthly service charge, you'll be billed for the difference at the end of the month. End of the month bills, being dated on the first of the following month, will thus reflect both the current month's usage-based charges as well as the following month's minimum monthly service charge.
Reserved resource customers (EC2 and RDS Reserved Instances and ElastiCache Reserved Cache Nodes) should expect their prepaid amounts to be included in the usage-based component during the month they are purchased.
To cancel a paid Support plan, switch to the Basic support plan:
- Sign in to your AWS account with your root account credentials
- Go to https://console.aws.amazon.com/support/plans/home
- On the Support plans page, choose Change plan
- On the Change support plan page, select the Basic plan, and then choose Change plan
You are obligated to pay for a minimum of one month of support each time you register to receive the service. While you may see a prorated refund when you cancel the service, your account will be charged again at the end of the month to account for the minimum subscription fee. We reserve the right to refuse to provide AWS Support to any customer that frequently registers for and terminates the service.
AWS Infrastructure Event Management is a short term engagement with AWS Support, available as part of the Enterprise-level Support product offering, and available for additional purchase for Business-level Support subscribers. AWS Infrastructure Event Management will partner with your technical and project resources to gain a deep understanding of your use case and provide architectural and scaling guidance for an event. Common use case examples for AWS Event Management include advertising launches, new product launches, and infrastructure migrations to AWS.
Chat is just another way, in addition to phone or email, to gain access to Technical Support engineers. By choosing the chat support icon in the Support Center, a chat session will be initiated through your browser. This provides a real-time, one-on-one interaction with our support engineers and allows additional information and links to be shared for faster issue resolution.
Offering support via chat is new for AWS, but not for Amazon.com. We have taken the same chat capabilities currently in use by retail customers and made it available for AWS technical support. Business and Enterprise-level customers can access chat capabilities within the Support Center. Support users can also launch a chat session from an individual case or the Contact Us section of the AWS website.
Customers frequently ask us if there is anything they should be doing to prepare for a major event that could affect a single Availability Zone. Our response to this question is that customers should follow general best practices related to managing highly available deployments (e.g., having a backup strategy, distributing resources across Availability Zones). The following links provide a good starting point:
- Are you taking advantage of distributing compute resources across multiple AZs?
- How to build fault tolerant applications on AWS?
- What can I do to improve my monitoring and watch for unexpected behavior or errors?
- What are the storage best practices in EC2?
- What should I do if my instance is no longer responding?
- How do I troubleshoot instances with Failed Status Checks?
- AWS Trusted Advisor - Scan your AWS environment for optimization recommendations
For details on how you can configure your IAM users to allow/deny access to AWS Support resources, see Accessing AWS Support.
Case history information is available for 12 months after creation.
Yes. To receive a history of AWS Support API calls made on your account, you simply turn on CloudTrail in the AWS Management Console.
Note: The following calls to the AWS Support API are not recorded or delivered:
- All Trusted Advisor operations: DescribeTrustedAdvisorCheckRefreshStatuses, DescribeTrustedAdvisorCheckResult, DescribeTrustedAdvisorChecks, DescribeTrustedAdvisorCheckSummaries, RefreshTrustedAdvisorCheck
For more information, see Logging AWS Support API Calls with AWS CloudTrail.
Support for Health Checks monitors some of the status checks that are displayed in the Amazon EC2 console. When one of these checks does not pass, all customers have the option to open a high-severity Technical Support case. Support for Health Checks covers certain checks for Amazon Elastic Compute Cloud (Amazon EC2) and Amazon Elastic Block Store (Amazon EBS).
Support for Health Checks currently covers three health check scenarios: EC2 system status, EBS disabled I/O, and EBS stuck in attaching.
If an EC2 system status check fails for more than 20 minutes, a button appears that allows any AWS customer to open a case. Most of the details about your case are auto-populated, such as instance name, region, and customer information, but you can add additional context with a free-form text description.
Note: Support for Health Checks covers only the EC2 system status check, not the EC2 instance status check. For troubleshooting ideas, see Troubleshooting Instances with Failed Status Checks.
An EBS volume that has a health status of disabled I/O or is stuck in attaching displays a Troubleshoot Now button. You are presented with a number of self-remediation options that could potentially fix the problem without the need to contact support. If the EBS volume is still failing the health check after you have followed all applicable steps, choose Contact Support to open a case.
A Support for Health Checks case opened through the console is a high-severity case.
After you submit a case, the button changes from Contact Support to View Case. To view the case status, choose View Case.
You can, but you don’t need to. You can include additional context and instance names in the text description submitted with your initial case.
Most system status issues are resolved by automated processes in less than 20 minutes and do not require any action on the part of the customer. If the instance is still failing the check after 20 minutes, then opening a case brings the situation to the attention of our technical support team for assistance.
Any user can create and manage a Support case for Health Checks case using their root account credentials. IAM users associated with accounts that have a Business or Enterprise Support plan can also create and manage a Support for Health Checks case.
AWS Trusted Advisor is an application that draws upon best practices learned from AWS’s aggregated operational history of serving hundreds of thousands of AWS customers. Trusted Advisor inspects your AWS environment and makes recommendations for saving money, improving system performance, or closing security gaps.
Trusted Advisor is available in the AWS Management Console. All AWS users have access to the data for four checks. Users with Business or Enterprise-level Support can access all checks. You can access the Trusted Advisor console directly at https://console.aws.amazon.com/trustedadvisor/.
Every check was vetted for accuracy, consistency, and usefulness to our customers. We gather data and research to ensure we are making the right recommendations based on best practices and historical values. We have identified many possible checks for future implementation, and we will continue to add them over time.
Trusted Advisor respects your privacy just as all Amazon Web Services do. We will never have access to your data or the software running on your account without your consent.
Trusted Advisor includes an ever-expanding list of checks in the following four categories:
- Cost Optimization–Recommendations that can potentially save you money by highlighting unused resources and opportunities to reduce your bill.
- Security–Identification of security settings that could make your AWS solution less secure.
- Fault Tolerance–Recommendations that help increase the resiliency of your AWS solution by highlighting redundancy shortfalls, current service limits, and overutilized resources.
- Performance–Recommendations that can help to improve the speed and responsiveness of your applications.
For more information on Trusted Advisor and an up-to-date listing of checks, see Meet AWS Trusted Advisor.
The Trusted Advisor notification feature helps you stay up-to-date with your AWS resource deployment. You will be notified by weekly email when you opt in for this service, and it is totally free.
- What is in the notification? The notification email includes the summary of saving estimates and your check status, especially highlighting changes of check status.
- How do I sign up for the notification? This is an opt-in service, so do make sure to set up the notification in your dashboard. You can choose which contacts receive notification on the Preferences pane of the Trusted Advisor console.
- Who can get this notification? You can indicate up to three recipients for the weekly status updates and savings estimates.
- What language will the notification be in? The notification is available in English and Japanese.
- How often will I get notified, and when? Currently you will receive a weekly notification email, typically on Thursday or Friday, and it will reflect your resource configuration over the past week (7 days). It is in our roadmap to provide an event-triggered mailer and more flexibility.
- Can I unsubscribe from the notifications if I do not want to receive the email anymore? Yes. You can change the setting in your dashboard by clearing all the check boxes and then selecting "Save Preferences". Also, help us make this feature more relevant and better for you by using the "Feedback" button on the dashboard.
- How much does it cost? It is totally free. Get started today!
Trusted Advisor tracks the recent changes to your resource status on the console dashboard. The most recent changes over the past 30 days appear at the top to bring them to your attention. The system will track seven updates per page, and you can go to different pages to view all recent changes by clicking the forward or the backward arrow displayed on the top-right corner of the "Recent Changes" area.
If you don’t want to be notified about the status of a particular resource, you can choose to exclude (suppress) the reporting for that resource. You would normally do this after you have inspected the results of a check and decide not to make any changes to the AWS resource or setting that Trusted Advisor is flagging.
To exclude items, check the box to the left of the resource items, and then choose "Exclude". Excluded items appear in a separate view. You can restore (include) them at any time by selecting the items in the excluded items list and then choosing "Include".
The "Exclude Items" function is available only at the resource level, not at the check level. We recommend that you examine each resource alert before excluding it to make sure that you can still see the overall status of your deployment without overlooking a certain area. For an example, see AWS Trusted Advisor for Everyone in the AWS Blog.
Most items in a Trusted Advisor report have hyperlinks to the AWS Management Console, where you can take action on the Trusted Advisor recommendations. Action links are included for all services that support them.
For example, the Amazon EBS Snapshots check lists Amazon EBS volumes whose snapshots are missing or more than seven days old. In each row of the report, the volume ID is a hyperlink to that volume in the Amazon EC2 console, where you can take action to create a snapshot with just a couple of clicks.
For the Trusted Advisor console, access is controlled by IAM policies that use the trustedadvisor namespace, and access options include viewing and refreshing individual checks or categories of checks. For more information, see Controlling Access to the Trusted Advisor Console.
You can retrieve and refresh Trusted Advisor results programmatically. For more information, see About the AWS Support API.
You can refresh a check 5 minutes after it was last refreshed. You can refresh individual checks or refresh all the checks at once by choosing "Refresh All" in the top-right corner of the summary dashboard.
When you visit the Trusted Advisor dashboard, any checks that have not been refreshed in the last 24 hours are automatically refreshed; this can take a few minutes. The date and time of the last refresh is displayed to the right of the check title.
In addtion, for customers with Business or Enterprise Support plans, the Trusted Advisor data is automatically refreshed weekly.
We set a limit on the amount of time a Trusted Advisor check can spend to process a check. You can try to refresh the check again later, in case it was a one-time failure.
Each customer action in Trusted Advisor triggers an API call that is documented in your Amazon CloudTrail logs. For example, when you refresh a Trusted Advisor check, you will see a call to the relevant resources with invokedBy and userAgent values of "support.amazonaws.com". This logging incurs minimal charges (a few cents per month). Automatic refreshes also appear in CloudTrail logs.
These four Trusted Advisor checks are available to all customers at no cost: Service Limits (Performance category; details at Service Limits Check Questions) and Security Groups - Specific Ports Unrestricted, IAM Use, and MFA on Root Account (Security category). Customers can access the remaining checks by upgrading to Business or Enterprise-level Support.
The Service Health Dashboard is a good way to view the overall status of each AWS service, but provides little in terms of how the health of those services is impacting your resources. AWS Personal Health Dashboard provides a personalized view of the health of the specific services that are powering your workloads and applications. What’s more, Personal Health Dashboard proactively notifies you when AWS experiences any events that may affect you, helping provide quick visibility and guidance to help you minimize the impact of events in progress, and plan for any scheduled changes, such as AWS hardware maintenance.
You will be able to view details about the event that is impacting your environment. AWS Personal Health Dashboard will continue to update the event regularly until the event ends and provide remediation guidance.
All notifications will be available only in English. We will add support for other languages over time.
AWS Personal Health Dashboard supports API, email, and CloudWatch Events (SQS, SNS, Lambda, Kinesis). Personal Health Dashboard also supports showing alerts in AWS Management Console navigation bar.
You can navigate to the CloudWatch Events console and write custom rules to filter events of interest. These rules can be wired to targets such as SNS, SQS, Lambda or Kinesis that will be invoked when you rule pattern matches AWS Personal Health Dashboard events on the CloudWatch Events bus.
Yes. You can customize Personal Health Dashboard through setting up notification preferences for the various types of events. You can also create custom remediation actions that are triggered in response to events. Set this up by visiting the CloudWatch Events console.
AWS Personal Health Dashboard will not take any actions on your behalf on your AWS environment. It will provide you the tooling required to wire up custom actions defined by you. The Personal Health Dashboard events will be published on the CloudWatch Events channel. You can write rules to capture these events and wire them to a Lambda functions. AWS Personal Health Dashboard also provides best practices and ‘how-to’ guides that help you define your automated run-books.
Yes, you can define custom actions in Lambda, and use CloudWatch Events to trigger Lambda actions in response to events.
No. At this time running diagnostics directly inside AWS Personal Health Dashboard is not available. However, you could attach a diagnostics automation script that will be executed by Lambda when an event occurs if wired appropriately.
Yes. The AWS Personal Health Dashboard event repository will be accessible with the Health API to customers who are on Business and Enterprise Support plans. Learn more about the AWS Health API.
CloudWatch and AWS Personal Health Dashboard can coexist to provide additional value beyond what just one service can provide by itself. Where you can create CloudWatch metrics and set alarms for the services available within the console, the Personal Health Dashboard provides notifications and information regarding issues that impact the underlying AWS infrastructure.
Cloudwatch alarms will provide information typically related to a symptom without providing insight into what may be the root cause. For example, for EBS you might create metrics to monitor VolumeReadBytes, VolumeWriteBytes, VolumeReadOps, VolumeWriteOps, VolumeQueueLength, etc. When a metric breaches, you are notified but receive little to help determine if the problem is related to your application, or with perhaps with the AWS infrastructure, such as an EBS lost volume.
With AWS Personal Health Dashboard, you receive a notification with detailed information regarding the underlying issue, as well as remediation guidance that allows you to identify the root of the issue and quickly troubleshoot to resolve.
AWS Personal Health Dashboard complements CloudWatch by providing insights into operational issues caused by AWS. You could overlay Personal Health Dashboard events alongside CloudWatch metrics to draw more insight into what actually triggered the alarms. Additionally, AWS Personal Health Dashboard can inform you when CloudWatch itself is facing service issues.
Every Enterprise Support customer is entitled to one Well-Architected Review. Additional reviews may be available based on customer need.
Q: How do I get started with my Well-Architected Review?
Enterprise Support customers can contact their Technical Account Manager to initiate a Well-Architected Review.
Enterprise Support customers can contact their Technical Account Manager to initiate a Cloud Operations Review.
Each year Enterprise Support customers are entitled to receive 500 qwikLABS credits. Unused credits will expire 1 year after the day in which they are applied to the administrator account. Unused credits cannot be rolled over to the next year. Unused credits that were purchased at the 30% discount will also expire, one year after they have been applied to the administrator account.
AWS Support Business and Enterprise levels include Beta support for common operating systems and common application stack components. AWS Support engineers can assist with the setup, configuration, and troubleshooting of the following third-party platforms and applications:
Operating systems on EC2 instances:
- Ubuntu Linux
- Red Hat Enterprise Linux and Fedora
- SUSE Linux (SLES and openSUSE)
- CentOS Linux
- Microsoft Windows Server 2008
- Microsoft Windows Server 2008 R2
- Microsoft Windows Server 2012
- Microsoft Windows Server 2012 R2
- Sendmail and Postfix MTAs
- OpenVPN and RRAS
- SSH, SFTP, and FTP
- LVM and Software RAID
- Microsoft SQL Server
In the case that we are not able to resolve your issue we will collaborate with, or refer you to, the appropriate vendor support for that product. In some cases you may need to have a support relationship with the vendor to receive support from them.
AWS Support can assist with installation, configuration, and troubleshooting of third-party software on the supported list. For other more advanced topics such as performance tuning, troubleshooting of custom code or scripts, security questions, etc. it may be necessary to contact the third-party software provider directly. While AWS Support will make every effort to assist, any assistance beyond installation, configuration, and basic troubleshooting of supported third-party software will be on a best-effort basis only.
Before closing your account, be sure to back up any applications and data that you need to retain. AWS may not be able to retrieve your account data after your account is closed. After completing your backup, visit your Account Settings page and choose "Close Account". This will close your AWS account and unsubscribe you from all AWS services. You will not be able to access AWS services or launch new resources when your account is closed.
If you manage multiple AWS accounts under the same company name that you would like to close, you can contact your account representative or open an account and billing support case for assistance. If you have additional questions or requirements associated with closing your AWS accounts, your account representative or AWS Customer Service can help.
If you receive an error message when trying to close your account, you can contact your account representative or open an account and billing support case for assistance.
Usage and billing stops accruing when your account is closed. You will be billed for any usage that has accrued up until the time you closed your account, and your final charges will be billed at the beginning of the following month.
We recommend that you use AWS Identity and Access Management (IAM), which enables you to securely control access to AWS services and resources for your users. Using IAM, you can create and manage AWS users and groups and use permissions to allow and deny access to AWS resources. IAM enables security best practices by allowing you to grant unique security credentials to users and groups to specify which AWS service APIs and resources they can access.
IAM access can be revoked if a user leaves the company or project, helping to ensure that root credentials are not exposed or compromised. For security and team functionality, IAM users are essential to using the full potential of your AWS account. For more information on IAM and controlling access to your billing information, see AWS Identity and Access Management (IAM) and Controlling Access to Your Billing Information.
Consolidated Billing is a feature that allows you to consolidate payment for multiple AWS accounts in your organization by designating one of them to be the payer account.
With Consolidated Billing, you can see a combined view of AWS charges incurred by all accounts, as well as get a detailed cost report for each individual AWS accounts associated with your payer account. Consolidated Billing is offered at no additional charge and allows for all accounts under the consolidated group to be treated as one account, which assists with achieving volume discounts more rapidly.
See Pay Bills for Multiple Accounts with Consolidated Billing in the AWS Billing and Cost Management User Guide.
AWS provides a number of different ways to explore your AWS monthly bill and to allocate costs by account, resource ID, or customer-defined tags.
For a more detailed view, you can also use these resources:
- Detailed billing report with resources and tags. This report allows you to get hourly detail on all AWS usage and to view tags for specific resources as needed. The tags are fully customizable on most AWS resources, and you can add or remove tags as needed. For more information, see Understand Your Usage with Detailed Billing Reports.
- Cost Explorer. The Cost Explorer in the AWS Billing console relies on the data from the detailed billing report and provides an interactive graphical user interface for viewing and analyzing your expenditures. For more information, see Manage Your Spend Data with Cost Explorer.
For billing purposes, AWS treats all the accounts in a Consolidated Billing family as if they're one account. Blended rates appear on your bill as an average price for variable usage across an account family. This allows you to take advantage of two features that are designed to ensure that you pay the lowest available price for AWS products and services:
- Pricing tiers. Pricing tiers reward higher usage with lower unit prices for services
- Capacity reservations. Rates are discounted when you purchase some services in advance for a specific period of time.
You can always see the precise account usage, along with the unblended rates, in the detailed billing reports.
For more information, see Understanding Blended Rates in the AWS Billing and Cost Management User Guide.
The Billing and Cost Management console and the detailed billing report provide different information based on blended and unblended rates. For more information, see Understanding Blended Rates or contact us through the AWS Support Center.
The Detailed Billing Report shows the linked accounts that benefited from a Reserved Instance on your consolidated bill. The costs of the Reserved Instances can be unblended to show how the discount was distributed. Reserved Instance utilization reports also show the total cost savings (including upfront Reserved Instance costs) across a Consolidated Bill.
Promotional and service credits are shared across the entire consolidated bill. Credits are used first by the account that the credit was applied to; if additional credit remains, it is distributed based on the service usage on the other linked accounts. This means that the Billing and Cost Management console shows any linked accounts that have benefited from a credit that was applied to another linked account. Unlike credits, refunds (credit memos) are viewable only by the payer account.
For more information, see AWS Credits.
The AWS Billing and Cost Management Console is a service that you use to pay your AWS bill, monitor costs, and visualize your AWS spend. There are many ways to use this tool for your account.
For more information, see What Is AWS Billing and Cost Management?
You can use Cost Explorer to visualize patterns in your spending on AWS resources over time. You can quickly identify areas that need further inquiry, and you can see trends that you can use to understand spend and to predict future costs.
For more information, see Manage Your Spend Data with Cost Explorer.
You can use the instance usage reports to view your instance usage and cost trends. You can see your usage data in either instance hours or cost. You can choose to see hourly, daily, and monthly aggregates of your usage data. You can filter or group the report by region, Availability Zone, instance type, AWS account, platform, tenancy, purchase option, or tag. After you configure a report, you can bookmark it so that it's easy to get back to later.
For more information, see Instance Usage Report.
The Reserved Instance utilization report describes the utilization over time of each group (or bucket) of Amazon EC2 Reserved Instances that you own. Each bucket has a unique combination of region, Availability Zone, instance type, tenancy, offering type, and platform. You can specify the time range that the report covers, from a single day to weeks, months, a year, or three years.
For more information, see Reserved Instance Utilization Reports.
Three tools are available to determine Reserved Instance utilization:
- Detailed billing report. This report shows hourly detail of all charges for an account or consolidated bill. Near the bottom of the report are line items that explain Reserved Instance utilization in an aggregated format (xxx hours purchased; xxx hours used). To configure your account for this report, see Getting Set Up for Usage Reports.
- Reserved Instance utilization report. This report is accessible from the Billing and Cost Management console and shows a high-level overview of utilization. For more information, see Reserved Instance Utilization Reports.
- Billing and Cost Management console. The "Bills" pane of the console shows Reserved Instance utilization in the highest level. This view provides the least detailed view of Reserved Instance utilization.
Unfortunately, this is not supported. For billing purposes, Consolidated Billing treats all the accounts on the Consolidated Bill as one account. All accounts on a Consolidated Bill receive the hourly cost benefit of Reserved Instances purchased by any other account.
The detailed billing report shows the hourly detail of all charges on an account or consolidated bill. Near the bottom of the report, line items explain Reserved Instance utilization in an aggregated format (xxx hours purchased; xxx hours used). To configure your account for this report, see Getting Set Up for Usage Reports.
In addition to the three tools listed in How do I tell if my Reserved Instances are being used, AWS Trusted Advisor provides best practices (or checks) in four categories: Cost Optimization, Security, Fault Tolerance, and Performance. The Cost Optimization section includes a check for Amazon EC2 Reserved Instances Optimization. For more information about the Trusted Advisor check, see Reserved Instance Opimization Check Questions.
Tax is normally calculated at the linked account level. Each account must add its own tax exemption. For more information on US sales taxes and VAT taxes, see the following:
Submit limit increase requests in the AWS Support Center. Choose "Create case", select "Service Limit Increase", and then select an item from the"Limit Type" list.
We aim for a quick turnaround time with all limit increases. If your request is urgent, complete the details of the request and then select the "Phone" contact method for 24/7 service. Provide the agent with the support case ID, and we will follow up immediately with the relevant teams.
AWS does not support the billing of reseller end customers because each reseller uses unique pricing and billing structures. We do recommend that resellers not use blended rates for billing—these figures are averages and are not meant to reflect actual billed rates. The detailed billing report can show unblended costs for each account on a consolidated bill, which is more helpful for the purpose of billing end customers.