- 最新
- 投票最多
- 评论最多
I've ran into a similar issue (millions of daily ReadACL and ReadObjectTagging operations) and was able to figure it out by activating AWS CloudTrail data events and analyzing the API operations. In my case it turns out the culprit was the AWS Backup plan, and I suspect in your case too, because you mention you started using it.
In my situation, it was because the bucket in question has millions of small files, making the backup process quite expensive.
It was the AWS backup. But I didn't started having this problem when I started using AWS backup, I was already using the backup when it started so I have to go through the support to figure it out, and turn out it was because of a change in the way the AWS backup works. Only the support could tell me that because that change wasn't notified to users.
I sorted the problem by changing the backup type to continuous, that way there's less things to backup.
To finish, just have in mind that I had this problem about two years ago.
I realize that the issue is very old, and I appreciate you replying after all this time. When I was investigating this problem recently, your unanswered question was the only place I found with any information relating to this and it led me in the right direction. I had to add a comment in case someone in the future bumps into the same problem. The suggestion about using continuous backups to solve this is great. Thanks.
Hi Tiago,
Sorry to hear about this experience.
You can check out our documentation for getting help with your AWS Billing and Cost Management here: https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/billing-get-answers.html.
Also, our Support team is more than happy to look into this for you. You can create a case by logging in at this page: http://go.aws/support-center.
— Aimee K.
Thanks for the answer.
The problem don't seem to be related with the billing but more with where this ReadACL and ReadObjectTagging are coming from.
Are they coming from the createPresignedRequest or getCommand in the api side of things or is the AWS backup that are trigging this?
相关内容
- AWS 官方已更新 1 年前
Having this same thing and it is killing our bill as GuardDuty as a result analyzed 150 million S3 events. Still cannot pinpoint what it is causing it
I'm experiencing the same issue (but around 2.4B requests per month). I'm struggling to find the cause but I am leaning toward AWS Backup. Tiago, were you ever able to find out the cause?