Help for owners
Someone is using my AWS account and running up charges
Short answer
Unknown servers or a charge in a Region you never use usually mean someone has your access keys or password. Change the root password, turn on two-step sign-in, and disable the exposed keys before anything else. Take screenshots and do not delete anything yet, because the evidence shows how they got in.
Does this sound like your situation?
- I see servers in my AWS account that nobody on my side launched.
- The bill shows large compute charges in a Region I have never used.
- AWS emailed me about unusual activity or an exposed access key.
- New users or access keys appeared that nobody remembers creating.
- The account was fine yesterday and today the charges are many times higher.
Why does this happen?
An access key leaked
Keys are long strings that let software act as you. They leak when they are pasted into public code, shared in chat, left in an old laptop or kept inside an app that was downloaded. Anyone holding a key with wide permissions can start servers.
A password was reused or guessed
A password used on another site that was breached, with no second sign-in step, is enough to open the console. The root user is the most dangerous one because it can do everything.
Servers are started in quiet Regions
Attackers often start servers in Regions you do not use, so the usual screens look normal. Cost Explorer can group spending by Region, which makes that visible in a few clicks.
Confirmed by docs.aws.amazon.com
Nobody was watching for a spike
A budget alert warns when actual or forecast spend crosses a limit, but AWS says there can be a delay between a charge and the alert, so spend may keep rising after the alert arrives.
Confirmed by docs.aws.amazon.com
The first fix is not the last fix
Deleting the visible servers is not enough if the attacker also created users, roles or keys that let them come back. Access has to be cleaned up as well as servers.
What can I do about it today?
- Take screenshots of what you seeCapture the bill, the server list and the Regions with activity. Save any email from AWS. You will need them for the support case.
- Change the root password and turn on two-step sign-inDo this from a computer you trust. Use an authenticator app or a security key, not SMS alone if you have a choice.
- Open a support case from the affected accountSay clearly that you believe the account is compromised. A case from the account lets AWS confirm you own it and gives you a case number.
- Switch exposed keys to inactive, do not delete themIf AWS names a key, make it inactive. Inactive can be reversed, deleting cannot, and the key helps to trace how the attacker got in.
- Do not delete servers or users yetStopping the unknown servers is fine. Deleting them or the logs removes the evidence. Wait for a person who understands the account.
- Tell the people who hold keysAnyone who deployed to this account must stop using old keys. Ask them to list where those keys are stored.
When should I bring someone in?
- Your own live site or customer data runs in the same account.
- You find new users, roles or keys that you did not create.
- The charges keep growing after you changed the password.
How do I handle it?
- Contain access firstI make the exposed keys inactive, rotate the credentials that matter and check for users, roles and keys the attacker added.
- Preserve what happenedBefore removing anything I export the activity log and snapshot what must be kept, so you can show AWS what occurred.
- Remove unknown resources in every RegionI check every Region, not just the ones in use, and clean up in that order: access, then servers.
- Find the leakI look for where the key was stored: code, a build system, a laptop or a shared document. Without that, it happens again.
- Add alerts and least accessBudget alerts, two-step sign-in and keys that can only do what the app needs.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Will AWS refund the charges?
You can ask through a support case, and the decision is AWS's. I cannot promise a refund.
Should I close the account?
Not as a first step. AWS says closing the account does not remove what you owe, and the content is deleted at the end of the post-closure period. Close access, not the account.
How do I know it is not just my own developers?
Ask them. If nobody launched the servers, and especially if they sit in an unused Region, treat it as unauthorised until proven otherwise.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.