Skip to main content

fix-plugin-aws

An AWS collector plugin for Fix.

Usage

For details on how to edit configuration, please see the documentation.

When the collector is enabled (fixworker.collector = [aws]) it will automatically collect any accounts the AWS boto3 SDK can authenticate for. By default it will check for environment variables like AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY or AWS_SESSION_TOKEN.

If Fix should assume an IAM role that role can be given via fixworker.aws.role = SomeRoleName.

The collector will scrape resources in all regions unless regions are specified using e.g. fixworker.aws.region = [us-east-1, us-west-2].

Scraping multiple accounts

If the given credentials are allowed to assume the specified role in other accounts of your AWS organisation, Fix can collect multiple accounts at the same time. To do so provide the account IDs to the fixworker.aws.account configuration.

Scraping the entire organisation

Instead of giving a list of account IDs manually you could also specify fixworker.aws.scrape_org, which will make Fix try to get the list of all accounts using the ListAccounts API.

If certain accounts are to be excluded from that list they can be specified using the fixworker.aws.scrape_exclude_account config option.

Miscellaneous Options

When collecting multiple accounts Fix by default will collect the accounts it finds in the org as well as the one it is currently authenticated as. If you do not want it to scrape the account that was used to get the list of all org accounts (e.g. your root account) you can specify fixworker.aws.dont_scrape_current.

If instead of using the current credentials you would like Fix to assume the specified role (fixworker.aws.role) even for the current account you can specify the options fixworker.aws.assume_current and fixworker.aws.dont_scrape_current. This would make it so that Fix does not scrape the current account using default credentials but instead assume the specified IAM role even for the current account.

License

See LICENSE for details.

Metadata

Release files for fixinventory-plugin-aws 4.2.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for fixinventory-plugin-aws 4.2.0
File Size Uploaded Provenance Actions
fixinventory_plugin_aws-4.2.0.tar.gz 364.8 kB Without provenance Details for fixinventory_plugin_aws-4.2.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for fixinventory-plugin-aws 4.2.0
File Interpreter ABI Platform Actions
fixinventory_plugin_aws-4.2.0-py3-none-any.whl Python 3 none any Details for fixinventory_plugin_aws-4.2.0-py3-none-any.whl

Total release size: 792.0 kB

Release files / fixinventory_plugin_aws-4.2.0.tar.gz

Download URL fixinventory_plugin_aws-4.2.0.tar.gz
Size 364.8 kB
Tags Source
SHA-256 checksum
How to use checksums
13a8e95df74f8ea387f9abc5f2d16a907b996e5e3c007cb547560f0e325ff711
BLAKE2b-256 checksum
How to use checksums
e1239fe2b40bbbed14eac5e19a94acc8f757251edd7838525ab0430ef1da09f2
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/5.1.1 CPython/3.12.7

Release files / fixinventory_plugin_aws-4.2.0-py3-none-any.whl

Download URL fixinventory_plugin_aws-4.2.0-py3-none-any.whl
Size 427.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
8f39070493b1d2ba3acc427c882b7671617be32679c262abe9e8b8faa7484b72
BLAKE2b-256 checksum
How to use checksums
629b0bda1fa1b6718caf8a5d1cb9731e95239e8dbe9c01de18b70b8871ec58aa
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/5.1.1 CPython/3.12.7

Security for fixinventory-plugin-aws 4.2.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page