# Admin Dashboard Showing Problems Related to S3

**URL:** https://meta.discourse.org/t/admin-dashboard-showing-problems-related-to-s3/62106
**Category:** Bug
**Created:** [5월 4, 2017, 12:50오후 UTC](https://meta.discourse.org/t/admin-dashboard-showing-problems-related-to-s3/62106 "2017-05-04T12:50:37Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![patrickbajao](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/patrickbajao/32/120896_2.png) [@patrickbajao](https://meta.discourse.org/u/patrickbajao)
#### Post date: [5월 4, 2017, 12:50오후 UTC](https://meta.discourse.org/t/admin-dashboard-showing-problems-related-to-s3/62106/1 "2017-05-04T12:50:37Z")

</div>

Hi,

We have Discourse hosted on AWS EC2. We are also using S3 for our uploads and we enabled the `s3_use_iam_profile` site setting. We don’t have problems with S3 integration.

With that enabled, I don’t have to set the `s3_access_key_id` and `s3_secret_access_key` options anymore. But I still receive PMs saying that there are problems with my installation. On the admin dashboard, I can see a message saying that I have to set those settings but I don’t really have to because we’re already using an IAM profile.

I think that message shouldn’t show if the `s3_use_iam_profile` and `s3_upload_bucket` are set.

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [1월 18, 2018, 1:16오전 UTC](https://meta.discourse.org/t/admin-dashboard-showing-problems-related-to-s3/62106/2 "2018-01-18T01:16:54Z")

</div>

Are you still experiencing this issue?