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

<div class="post-metadata">

**Author:** ![Walter\_Jenkins](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/walter_jenkins/32/459298_2.png) [@Walter\_Jenkins](https://meta.discourse.org/u/Walter_Jenkins)\
**Post date:** [November 10, 2024, 5:30pm UTC](https://meta.discourse.org/t/separate-s3-access-keys-for-backups-and-uploads/335479/4 "2024-11-10T17:30:19Z")

</div>

So I was able to setup an IAM user with 2 roles in AWS that allows for separate permissions for my backup and assets buckets. Each role is scoped to that bucket and has specific permissions. I believe that the backup is set to only put and not read or list. Where as the assets bucket is allowing all functions.

However this sounds like an issue with the Backblaze role specification is that correct? Seems like you can only attach a permission to 1 or all buckets and the way that it works with discourse is that they share the same permission keys?

---

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