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

<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, 5:35pm UTC](https://meta.discourse.org/t/separate-s3-access-keys-for-backups-and-uploads/335479/5 "2024-11-10T17:35:40Z")

</div>

Yup. Backblaze handling of application key permissions seems to be (drastically) simpler than AWS.

A Backblaze permission key seems to have access to either a single bucket or all buckets in the owners account.

So the discourse S3 interface is just fine for AWS S3 buckets, but not quite as good for Backblaze B2 buckets.

---

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