IAM Access Advisor Issue or Cloud Tail Bug?
Hello there,
We are having a weird situation where IAM Access Analyzer shows that the Specific IAM User has called actions on Amazon S3(Especially ListAllMyBuckets) Service on region us-east-1. But Cloud Trail doesn't show any logs. Am I missing something?
Screenshots:
I don't know which one to trust.
- 新しい順
- 投票が多い順
- コメントが多い順
It appears that the IAM user does not have access via the console, yet there are two access keys associated with the account. Notably, the second access key was utilized "yesterday." If you've been using Amazon S3, it's possible you're the owner of this IAM user. Running a simple command like aws s3 ls is adequate to register in the Access Advisor, as illustrated in the accompanying image. The "ListAllBucket" action indicates that you have the permission granted by this policy, even though it hasn't been utilized. Notably, the Access Advisor exclusively displays permissions granted to the specific IAM user in question.
This does not show that the user called ListAllMyBuckets. IAM access analyzer is showing that it ListAllMyBuckets is an allowed action but you see that it was "Not accessed in the tracking period." Do you have an example of where it shows that you have run that operation that is concerning?
We are moving away from IAM User to Instance Profile. We have done the changes two weeks ago, But we didn't deactivate the key to monitor it's usage. But currently that key is being used somewhere. As you can see from the First screenshot service "Amazon S3" was used "Yesterday" (Please check the last accessed column)
Therefore tried to search the same in CloudTrail to get more details about it. But CloudTrail has 0 entries for Yesterday for that user.
関連するコンテンツ
AWS公式更新しました 2年前
Then Cloud Trail should log aws s3 ls event right? Cloud Tail has 0 entry about that event.