You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This page should describe the required S3 actions, so that we can write an appropriate IAM or Bucket policy instead of having to guess, or grant more permissions than is required for the application to function.
For example, it's obvious that PutObject would be required - but what about other actions like listBucket or ListMultiRegionAccessPoints?
The text was updated successfully, but these errors were encountered:
I hope the rest of this software isn't written with that sort of frame of mind. That's a very dangerous idea when talking about something intended to be exposed to the internet. Should someone compromize the installation it'll be trivial for them to locate the IAM credentials used for S3 access, so the access granted by those credentials should be as minimal as possible.
For example, said attacker could enable website hosting out of the bucket, change the bucket policy, and use it to serve out a phishing website from inside my S3 bucket.
This page should describe the required S3 actions, so that we can write an appropriate IAM or Bucket policy instead of having to guess, or grant more permissions than is required for the application to function.
For example, it's obvious that
PutObject
would be required - but what about other actions likelistBucket
orListMultiRegionAccessPoints
?The text was updated successfully, but these errors were encountered: