Answers.Body: <p>My first guess would have been that the asset indexes stored in the database are out of sync since it was recently migrated to a new Volume.</p>
  
  <p>A way to fix that would be to run the "Update Asset Indexes" utility from the Control Panel.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-09-25T20:05:36.553Z
Answers.LastActivityDate: 2019-09-25T20:05:36.553Z
Answers.UserDisplayName: Brad Bell
Answers.Body: <p>It actually turns out to be an oversight on my part. It was confusing (after I manually replaced the missing assets), but in control <code>panel &gt; admin &gt; settings &gt; assets &gt; volumes</code>, I did not have the correct bucket selected for a couple of my volumes. I simply overlooked that option.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-09-25T23:16:01.727Z
Answers.LastActivityDate: 2019-09-25T23:16:01.727Z
Answers.UserDisplayName: BBaysinger
Body: <p>I migrated my images over to AWS S3 using the Amazon S3 plugin; however, now I'm seeing that the thumbnails in the CP are broken, and a <code>brokenimage</code> is displayed.</p>
  
  <p><a href="https://i.sstatic.net/neXB2.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/neXB2.png" alt="enter image description here"></a></p>
  
  <p>The full size images display fine in the CP and the front end. If I re-upload them, the thumbnails display correctly in the CP, but that's not an ideal solution.</p>
  
  <p>Is there a way to make the images display correctly in the CP without re-uploading them?</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-09-24T22:40:28.593Z
Comments.Text: Have you tried using the update asset indexes utility in the Control Panel?
Comments.UserDisplayName: Brad Bell
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-09-24T22:41:20.640Z
Comments.Text: I did not try that. Already re-uploaded everything. Agh!
Comments.UserDisplayName: BBaysinger
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-09-24T23:01:43.333Z
Comments.Text: I'm new to Craft. Think I read about that at some point. Would that likely have solved it? Feel free to post it as the answer.
Comments.UserDisplayName: BBaysinger
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-09-25T20:05:56.460Z
Comments.Text: Not sure if it would have solved it, but it's an easy first thing to try! Added an answer.
Comments.UserDisplayName: Brad Bell
Tags: <image><s3><aws>
Title: Thumbnails broken in CP after migrating images to AWS S3
ThreadText: # Thumbnails broken in CP after migrating images to AWS S3
  
  (Asked by: username_0 on 2019-09-24)
  
  I migrated my images over to AWS S3 using the Amazon S3 plugin; however, now I'm seeing that the thumbnails in the CP are broken, and a `brokenimage` is displayed.
  
  [![enter image description here](https://i.sstatic.net/neXB2.png)](https://i.sstatic.net/neXB2.png)
  
  The full size images display fine in the CP and the front end. If I re-upload them, the thumbnails display correctly in the CP, but that's not an ideal solution.
  
  Is there a way to make the images display correctly in the CP without re-uploading them?
  
  **Tags:** image, s3, aws
  
  > **Comments:**
  > **username_1**: Have you tried using the update asset indexes utility in the Control Panel?  
  > **username_0**: I did not try that. Already re-uploaded everything. Agh!  
  > **username_0**: I'm new to Craft. Think I read about that at some point. Would that likely have solved it? Feel free to post it as the answer.  
  > **username_1**: Not sure if it would have solved it, but it's an easy first thing to try! Added an answer.  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_1 on 2019-09-25. Score: 1
  
  My first guess would have been that the asset indexes stored in the database are out of sync since it was recently migrated to a new Volume.
  
  A way to fix that would be to run the "Update Asset Indexes" utility from the Control Panel.
  
  
  ---
  
  ### Answer by username_0 on 2019-09-25. Score: 1
  
  It actually turns out to be an oversight on my part. It was confusing (after I manually replaced the missing assets), but in control `panel > admin > settings > assets > volumes`, I did not have the correct bucket selected for a couple of my volumes. I simply overlooked that option.
  
  
  ---
  
  