An AWX CR AWUS charge on your bank or credit card statement is a bill from Amazon Web Services, Amazon’s cloud computing platform. It usually means a cloud account tied to your payment method used billable services in the previous month. If you opened an AWS account at some point, log in and shut down whatever is running. If you never opened one, treat it as an unauthorized charge and dispute it with your card issuer.
What the Descriptor Means
The line item breaks into three parts. AWX identifies Amazon Web Services as the merchant, CR flags a credit-card transaction, and AWUS points to the United States billing entity. Your statement detail may also carry a nine-digit AWS invoice number next to the descriptor.
AWS is billed separately from Amazon.com retail. Logging into your shopping account will not show these charges, and Amazon customer service cannot resolve them. You need the AWS Management Console, which uses its own account and login.
Why the Charge Is Showing Up
The most common trigger is the AWS Free Tier running out. New accounts get 12 months of limited free access to certain services. Once that window closes, any resource still running switches to standard pricing automatically, with no warning beyond the terms agreed to at signup.1Amazon Web Services. AWS Free Tier Terms A test project spun up and forgotten a year ago starts costing money the day the free tier expires.
These are the resources that most often generate surprise bills:
- EC2 instances. Virtual servers bill by the hour whether anyone is using them. A single t2.micro runs about $0.0116 per hour, roughly $8.50 a month if left on around the clock. Larger instance types cost far more.2Amazon Web Services. Amazon EC2 T2 Instances
- S3 storage buckets. Charges scale with how much data you keep and how often it is accessed. Even a small bucket of forgotten files shows up as a monthly line.
- Public IPv4 addresses. Every public IP attached to an AWS resource costs $0.005 per hour, and idle Elastic IPs not attached to anything cost the same. That is about $3.60 per month per address, and it multiplies with every extra one.3Amazon Web Services. New AWS Public IPv4 Address Charge + Public IP Insights
- Data transfer out. Every account gets 100 GB of free outbound data transfer per month across services. Beyond that, per-gigabyte fees apply.4Amazon Web Services. Amazon EC2 On-Demand Pricing
Abandoned developer accounts are the usual story. Someone signs up to learn cloud computing, builds something small, moves on, and the meter keeps running quietly in the background.
Getting Into Your AWS Account
You cannot stop the charges without getting into the account. Start with the email address used at signup. Each AWS account has a unique 12-digit account ID, and it may appear in your detailed bank statement next to the charge.5Amazon Web Services. View AWS Account Identifiers – AWS Account Management If you cannot remember which email you used, search your inbox for messages from “no-reply@amazon.com” or “aws-account-confirmation.”
Once you are in, open the Billing and Cost Management console. The Bills page lists every service that contributed to the total and lets you download a PDF invoice for each billing period.6Amazon Web Services. Understanding Your Bill – AWS Billing That page tells you which resources are actually running and where the money is going. Use it as your shutdown checklist.
Lost access to the signup email? Try recovering it through your email provider first. If that fails, contact AWS account support and be ready to verify ownership with billing statements, account details, or identification.7AWS re:Post. I Don’t Have Access to the Email for My AWS Account
Shutting Down Resources So Charges Stop
Logging out does not stop billing. You have to terminate every active resource. Each service has its own shutdown process, and one thing left running keeps the charge coming.
Start with EC2. In the EC2 dashboard, select running instances and choose Terminate. This is permanent and stops hourly billing from the moment it takes effect. For S3, empty every object out of a bucket first, then delete the bucket itself. Also check the EC2 console for Elastic IP addresses and release any that are not attached to a running instance.
Do not overlook less obvious services. RDS database instances, Lambda functions with provisioned capacity, and NAT Gateways all generate charges of their own. The Bills page shows every service billed on your last invoice, so work through it line by line.
Closing the Account Completely
To shut everything down for good, go to Account Settings and initiate account closure. AWS then enters a 90-day post-closure period during which you can still sign in to view past bills and reach support. After that, the account is permanently closed and remaining resources are deleted.8Amazon Web Services. Close an AWS Account – AWS Account Management
One trap catches people every month: closing the account does not stop every charge immediately. You will still get a final bill for usage between the start of the month and the closure date. Reserved Instances and Savings Plans keep billing until their contract terms expire. AWS Marketplace subscriptions do not cancel automatically either.9AWS re:Post. Why Did I Receive a Bill After I Closed My AWS Account Cancel those before you close, or another AWX CR AWUS line will land on your statement the following month.
Setting a Budget Alert Before You Leave
If you plan to keep the account open, spend two minutes setting a spending alert so this does not repeat. AWS Budgets can fire a notification when charges cross any threshold you pick, including zero.
Open the Billing and Cost Management console, choose Budgets from the left menu, and use the simplified template to create a monthly cost budget. Set the amount to zero if you want to know the moment any charge appears, enter your email, and save. You get an alert whenever spending crosses the thresholds you defined.10AWS re:Post. How Do I Set Up a Simplified or Zero-Cost AWS Budget
If You Never Opened an AWS Account
If nothing you did explains the charge, someone may have used your payment information to open an account. Skip the AWS recovery process and go straight to your card issuer. Two federal laws cover different pieces of this situation.
For billing errors on credit card statements, the Fair Credit Billing Act gives you 60 days from when the statement containing the error was mailed to send a written dispute to your card issuer. The issuer must acknowledge the dispute within 30 days and resolve it within two billing cycles. While the investigation is open, the issuer cannot try to collect the disputed amount or report it as delinquent.11Office of the Law Revision Counsel. 15 USC 1666 – Correction of Billing Errors
For truly unauthorized use of your card, the Truth in Lending Act caps your liability at $50, and only if the card issuer met specific notification requirements beforehand.12Office of the Law Revision Counsel. 15 USC 1643 – Liability of Holder of Credit Card In practice, most major card networks offer zero-liability policies that go further than the statute, so you likely will not owe anything. Call your card issuer, give them the AWX CR AWUS descriptor and the transaction date, and ask for a chargeback. The bank will typically issue a provisional credit while it investigates.
The 60-day clock runs from when the statement is sent, not when you notice the charge. Waiting past that window weakens your position even when the charge is clearly wrong.