# 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:** 11

<div class="post-metadata">

**Author:** ![phil22](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/phil22/32/248480_2.png) [@phil22](https://meta.discourse.org/u/phil22)\
**Post date:** [July 8, 2025, 2:12pm UTC](https://meta.discourse.org/t/s3-storage-with-no-public-access/251560/11 "2025-07-08T14:12:07Z")

</div>

We use the excellent [secure uploads](https://meta.discourse.org/t/secure-uploads/meta/140017/1) feature for our discourse instance, it’s working fine but it would be great if there was support for blocking all public access to the bucket.

Recently I’ve been trying to resolve all ‘AWS Foundational Security Best Practices’ issues raised by AWS Security Hub. One of these is that ‘S3 general purpose buckets should block public access’

I imagine quite a few companies are going through the same process of trying to apply the ‘AWS Foundational Security Best Practices’ and running into this issue.

Not expecting this to be prioritised any time soon but I found this thread and thought I’d add a +1 to it.

Here’s the AWS FSBP recommendation: [Security Hub CSPM controls for Amazon S3 - AWS Security Hub](https://docs.aws.amazon.com/securityhub/latest/userguide/s3-controls.html#s3-8)

---

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