# S3 Storage with no Public access

**URL:** <https://meta.discourse.org/t/s3-storage-with-no-public-access/251560>\
**Category:** Feature\
**Tags:** s3\
**Created:** [January 12, 2023, 1:46pm UTC](https://meta.discourse.org/t/s3-storage-with-no-public-access/251560 "2023-01-12T13:46:37Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![varuncjain](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/varuncjain/32/289013_2.png) [@varuncjain](https://meta.discourse.org/u/varuncjain)\
**Post date:** [January 12, 2023, 1:46pm UTC](https://meta.discourse.org/t/s3-storage-with-no-public-access/251560/1 "2023-01-12T13:46:38Z")

</div>

In our setup we are running Discourse in an AWS EKS cluster, and expect to use an S3 Bucket in the same AWS account for media storage. The EKS pod running Discourse is provided with the Kubernetes Service Account and IAM Role. The S3 Bucket has all Public access blocked, with an ACL granting only the Bucket owner (AWS account) with read/write access.

With the Discourse Site Settings of “_enabled s3 uploads_”, “_s3 use iam profile_” and “_secure media uploads_” enabled, we are able to use our setup for uploading media to Discourse Topics. However due to the checks in UploadCreator module, any Site Settings related uploads eg. logo, etc. are failing as they attempt to upload the media with the S3 API private\_acl parameter set to “false”. Would it not make sense that one “_secure media uploads_” is enabled, all content is uploaded with private\_acl set to true?

---

_[View the full topic](https://meta.discourse.org/t/s3-storage-with-no-public-access/251560)._