- Newest
- Most votes
- Most comments
Based on the information provided, there are several possible reasons why your images might appear to have disappeared from your S3 bucket:
-
Server-Side Encryption Issues: Your objects might have been encrypted using Server-Side Encryption with Customer-Provided Keys (SSE-C). When this happens, you need to provide the correct encryption parameters to access the files. This would explain why the files appear to be missing even though they might still exist in the bucket.
-
Object Ownership Settings: If there were changes to Object Ownership settings in your bucket, especially in cross-account scenarios, this could affect access to the objects.
-
IAM Policy or Bucket Policy Changes: Even if you believe permissions are set correctly, there might have been changes to IAM roles, policies, or bucket policies that are affecting access.
-
Bucket Region Mismatch: Ensure you're looking in the correct region (Ohio us-east-2) as mentioned in your question.
-
Accidental Deletion: Although you mentioned no developers made changes, it's worth checking CloudTrail logs to confirm no accidental deletions occurred.
To troubleshoot this issue:
- Check if you can list the objects in the bucket using the AWS Management Console or AWS CLI
- Review your bucket's encryption settings
- Check CloudTrail logs for any delete operations or policy changes
- Verify that the bucket's public access settings haven't been changed
- Ensure that the bucket policy still allows public access if that's what you intended
- Check if the objects were moved to a different prefix/folder within the bucket
If you can list the objects but can't access them, the issue is likely related to encryption or permissions. If you can't even list the objects, they might have been deleted or moved.
Sources
Files across all S3 buckets unaccessible, even from GUI | AWS re:Post
You mentioned the S3 image is no longer there. Have you checked the S3 bucket if the image is actually there or not. Are you using the correct URL (is the path and filename correct). Also, note that the url can be case sensitive.
Relevant content
- asked a year ago
- asked 3 years ago
- AWS OFFICIALUpdated 2 years ago
