AWS S3 and Config keep charging me
So i have this first aws account that i am not using since August 2023.
All EC2, S3, and all other configuration that i explored and tested were all deleted but i noticed that S3 and AWS Config still charges me up to now.
As i checked, there are no existing buckets and configs in the console. As i dig deeper i saw this detailed bills but i cannot find any config in the console.
Can someone help me find this configs to stop aws charging me. Thanks
- Newest
- Most votes
- Most comments
Hello.
As you can see from the invoice image, API requests to S3 (List, Post, etc.) are charged as fees.
I'm guessing that AWS Config is probably enabled and recording S3 settings, etc.
Therefore, please try disabling the AWS Config recorder by following the steps in the document below.
https://docs.aws.amazon.com/config/latest/developerguide/stop-start-recorder.html
I checked your provided documents and at least tried them, but i cannot find the settings in the navigation plane in the AWS Config.
To add i don't have any existing aws config and S3 bucket on my account.
Relevant content
- Accepted Answerasked 9 months ago
- asked 2 months ago
AWS OFFICIALUpdated 2 years ago- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
I checked your provided documents and at least tried them, but i cannot find the settings in the navigation plane in the AWS Config.
To add i don't have any existing aws config and S3 bucket on my account.
Please see below for screenshots.
Is there nothing when I check AWS Config in the "us-east-1" region?
No existing item on AWS Config in that region. I will also post the screenshot below
It certainly looks like it's not set. We recommend contacting AWS Support for this by opening a case under "Account and billing". https://docs.aws.amazon.com/awssupport/latest/user/case-management.html
This has been resolve. I created a support ticket and aws support trace all of our aws account. What i missed and did not check are the member accounts and deleted the remaining resources. That solved my issue. Thank you for your inputs and recommendations.