resoto-plugin-aws
An AWS collector plugin for Resoto.
Usage
For details on how to edit configuration, please see the documentation.
When the collector is enabled (resotoworker.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 Resoto should assume an IAM role that role can be given via resotoworker.aws.role = SomeRoleName.
The collector will scrape resources in all regions unless regions are specified using e.g. resotoworker.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, Resoto
can collect multiple accounts at the same time. To do so provide the account IDs to the resotoworker.aws.account configuration.
Scraping the entire organisation
Instead of giving a list of account IDs manually you could also specify resotoworker.aws.scrape_org, which will make Resoto 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 resotoworker.aws.scrape_exclude_account config option.
Miscellaneous Options
When collecting multiple accounts Resoto 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 resotoworker.aws.dont_scrape_current.
If instead of using the current credentials you would like Resoto to assume the specified role (resotoworker.aws.role) even for the current account you can specify the options
resotoworker.aws.assume_current and resotoworker.aws.dont_scrape_current. This would make it so that Resoto 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.
1 maintainer
Metadata
1 maintainer
Release files for resoto-plugin-aws 3.9.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| resoto-plugin-aws-3.9.0.tar.gz | 275.7 kB | Without provenance | Details for resoto-plugin-aws-3.9.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| resoto_plugin_aws-3.9.0-py3-none-any.whl | Python 3 | none | any | Details for resoto_plugin_aws-3.9.0-py3-none-any.whl |
Total release size: 607.5 kB
Release files / resoto-plugin-aws-3.9.0.tar.gz
| Download URL | resoto-plugin-aws-3.9.0.tar.gz |
|---|---|
| Size | 275.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7f2d489e8552aa766e519df53e562e626304c67ae0ba95e6ba4423b85befeea3
|
|
BLAKE2b-256 checksum How to use checksums |
94dc8be46f890bb2bf60f59e8935e61162fd96963890a02a830b9d32416eebcc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.8
|
Release files / resoto_plugin_aws-3.9.0-py3-none-any.whl
| Download URL | resoto_plugin_aws-3.9.0-py3-none-any.whl |
|---|---|
| Size | 331.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
afad3f7fd4551e2178082ac4086bf4cea3ecc4b9d708ed25405b8e28f7b88ec0
|
|
BLAKE2b-256 checksum How to use checksums |
d40652a81f01b35aa20e50f3d5eb5ed3ee5a4f885b9858e844f48a6ffd623350
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.8
|
Security for resoto-plugin-aws 3.9.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.
