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

IAM Role-based permissions for data sources (namely S3) #10308

New Issue
Closed
opened 2025-12-29 21:29:41 +01:00 by adam · 3 comments
adam commented 2025-12-29 21:29:41 +01:00
Owner
Copy Link

Originally created by @kennedymeadows on GitHub (Sep 30, 2024).

NetBox version

v3.7.4

Feature type

Change to existing functionality

Proposed functionality

Currently, in order to add a new Amazon S3 bucket as a data source, you are required to provide an AWS access key ID and AWS secret access key. The requested change is to make these fields optional as it is possible to grant role based permissions to the server which is running Netbox to allow access to a bucket.

This is already possible for media storage via configuration.py:

# By default, uploaded media is stored on the local filesystem. Using Django-storages is also supported. Provide the
# class path of the storage driver in STORAGE_BACKEND and any configuration options in STORAGE_CONFIG. For example:
STORAGE_BACKEND = 'storages.backends.s3boto3.S3Boto3Storage'
STORAGE_CONFIG = {
    # 'AWS_ACCESS_KEY_ID': 'Key ID',
    # 'AWS_SECRET_ACCESS_KEY': 'Secret',
    'AWS_STORAGE_BUCKET_NAME': '<%= @netbox_data['s3']['bucket'] %>',
    'AWS_S3_REGION_NAME': 'us-west-2',
}

Use case

This would allow for script and report uploads for users who use role-based permissions for S3 access.

Database changes

No response

External dependencies

No response

Originally created by @kennedymeadows on GitHub (Sep 30, 2024). ### NetBox version v3.7.4 ### Feature type Change to existing functionality ### Proposed functionality Currently, in order to add a new Amazon S3 bucket as a data source, you are required to provide an AWS access key ID and AWS secret access key. The requested change is to make these fields optional as it is possible to grant role based permissions to the server which is running Netbox to allow access to a bucket. This is already possible for media storage via `configuration.py`: ``` # By default, uploaded media is stored on the local filesystem. Using Django-storages is also supported. Provide the # class path of the storage driver in STORAGE_BACKEND and any configuration options in STORAGE_CONFIG. For example: STORAGE_BACKEND = 'storages.backends.s3boto3.S3Boto3Storage' STORAGE_CONFIG = { # 'AWS_ACCESS_KEY_ID': 'Key ID', # 'AWS_SECRET_ACCESS_KEY': 'Secret', 'AWS_STORAGE_BUCKET_NAME': '<%= @netbox_data['s3']['bucket'] %>', 'AWS_S3_REGION_NAME': 'us-west-2', } ``` ### Use case This would allow for script and report uploads for users who use role-based permissions for S3 access. ### Database changes _No response_ ### External dependencies _No response_
adam closed this issue 2025-12-29 21:29:41 +01:00
adam commented 2025-12-29 21:29:42 +01:00
Author
Owner
Copy Link

@kennedymeadows commented on GitHub (Sep 30, 2024):

I should add that this has actually already been asked but there was no response. It was a pretty old issue so I created this new one for clarity: https://github.com/netbox-community/netbox/issues/13072

@kennedymeadows commented on GitHub (Sep 30, 2024): I should add that this has actually already been asked but there was no response. It was a pretty old issue so I created this new one for clarity: https://github.com/netbox-community/netbox/issues/13072
adam commented 2025-12-29 21:29:42 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (May 8, 2025):

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 (May 8, 2025): 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/main/CONTRIBUTING.md).
adam commented 2025-12-29 21:29:43 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jun 14, 2025):

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 (Jun 14, 2025): 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 complexity: medium netbox pending closure status: needs owner 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#10308
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?