# Separate S3 access keys for backups and uploads?

**URL:** <https://meta.discourse.org/t/separate-s3-access-keys-for-backups-and-uploads/335479>\
**Category:** Product Support\
**Tags:** s3\
**Created:** [November 10, 2024, 4:51pm UTC](https://meta.discourse.org/t/separate-s3-access-keys-for-backups-and-uploads/335479 "2024-11-10T16:51:27Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![wttw](https://avatars.discourse-cdn.com/v4/letter/w/3bc359/32.png) [@wttw](https://meta.discourse.org/u/wttw)\
**Post date:** [November 10, 2024, 4:51pm UTC](https://meta.discourse.org/t/separate-s3-access-keys-for-backups-and-uploads/335479/1 "2024-11-10T16:51:27Z")

</div>

I want to use separate backblaze B2 buckets for backups and uploads. I don’t want discourse to have access to any buckets other than the two it is using.

Backblaze allows creating an application key to access either a single bucket, or all buckets.

But discourse requires that uploads and backups use the same S3 credentials, as far as I can tell, so there’s no way to do that.

Is there anything I’m missing?

---

_[View the full topic](https://meta.discourse.org/t/separate-s3-access-keys-for-backups-and-uploads/335479)._