Account being charged for no reason. . multiple tickets raised but still no response

You have a critical misunderstanding regarding your AWS account.

You are solely responsible for your AWS account and everything running in it. This includes starting, stopping, and managing all services as well as all costs incurred.

AWS will not and cannot turn off services in your account. This is not a limitation of the support it is a fundamental security boundary. No one outside your organization is permitted to make changes to your account.

If a service is running in your account, you are being billed for it whether you are actively using it or not. If you want a service stopped, you or someone on your team must stop it. AWS cannot do this for you under any circumstances.

Waiting for AWS to take action on your behalf will not resolve this and will only result in continued charges. This is outlined in the AWS Shared Responsibility Model and the AWS Customer Agreement, both of which govern the use of your account.

Are you getting an invoice from AWS? It should list all the services that's incurring a charge. Then depending on the service, you can choose the terminate/delete the resource. Note, common cost complains from AWS are like you might have stopped an EC2 but getting charged for EBS volumes or snapshots. Or maybe, you have S3 buckets with data in it.

Hello,

I fully understand the frustration regarding billing. Your concerns have been shared internally with our Support team for visibility.

I'd encourage you to continue to communicate through your case as our Support team is equipped with the tools to best assist: https://go.aws/support-center.

Additionally, check out our article on re:Post which includes info on how to pinpoint unexpected charges: https://repost.aws/knowledge-center/resources-unexpected-charges.

- Doug S.

I understand your frustration with unexpected charges and lack of response to your support tickets. Here are some steps you can take to address this situation:

Immediate Actions:

1. Review your AWS Cost Explorer and billing dashboard - Log into your AWS account and check the Cost Explorer to identify exactly which services are generating charges. Even "inactive" accounts can incur costs from resources that weren't properly terminated, such as EBS volumes, snapshots, Elastic IPs, or data storage.

2. Check all AWS regions - Resources may be running in regions you don't typically use. Make sure to check all regions in your account, as resources in any region will generate charges.

3. Verify your support plan - Response times vary based on your AWS Support plan. Basic support only provides account and billing support through forums and documentation. If you need faster response times for technical issues, you may need a paid support plan.

4. Use the correct support channel - For billing issues specifically, you should contact AWS Billing Support directly through the AWS Support Center in your account console, even if you have a Basic support plan. Billing inquiries typically receive responses.

5. Request a detailed billing analysis - When contacting support, specifically request a line-item breakdown of your charges and ask them to help identify any resources that should be terminated.

Important Note: Before initiating a chargeback through your bank, be aware that this could result in your AWS account being suspended or closed, and you may lose access to any data or resources in the account.

If you continue to experience no response through normal support channels, you can also try reaching out through the AWS re:Post community forum where AWS staff sometimes assist with account issues, though this should not replace formal support tickets for billing matters.