starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Add S3 IAM Role option for better security #8278

New Issue
Closed
opened 2025-12-29 20:34:39 +01:00 by adam · 2 comments
adam commented 2025-12-29 20:34:39 +01:00
Owner
Copy Link

Originally created by @princedavid-0 on GitHub (Jul 3, 2023).

NetBox version

v3.5-2.6.1

Feature type

New functionality

Proposed functionality

Currently, one can only access an S3 via IAM Users only. Are you able to add a feature for IAM Roles as they are easier to manage and refine for minimum privilege and improved security

Use case

Access and Secret Access key management is more painstaking to manage compared to roles. So the chance to limit rotation of credentials and keys is easier with IAM Role

Database changes

I don't think this will affect the database schema

External dependencies

I believe all python package required is already a part of Netbox

Originally created by @princedavid-0 on GitHub (Jul 3, 2023). ### NetBox version v3.5-2.6.1 ### Feature type New functionality ### Proposed functionality Currently, one can only access an S3 via IAM Users only. Are you able to add a feature for IAM Roles as they are easier to manage and refine for minimum privilege and improved security ### Use case Access and Secret Access key management is more painstaking to manage compared to roles. So the chance to limit rotation of credentials and keys is easier with IAM Role ### Database changes I don't think this will affect the database schema ### External dependencies I believe all python package required is already a part of Netbox
adam added the type: featurepending closure labels 2025-12-29 20:34:39 +01:00
adam closed this issue 2025-12-29 20:34:39 +01:00
adam commented 2025-12-29 20:34:40 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Oct 2, 2023):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Oct 2, 2023): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 20:34:41 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Nov 2, 2023):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Nov 2, 2023): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label pending closure type: feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#8278
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?