CLOUD AUDIT TOOL
Cloud Audit tool helps you to check whether the application built on AWS is following the AWS Well-Architected framework by validating it against various AWS services security requirements and the best practices. Generates report to validate the security requirements and security best practices.
Cloud Audit tool setup
The project basically uses boto client to connect to the aws services.
-
Update the session credentials in the terminal or give them through the arguments in the command line by specifying --access-key, --secret-key, and --session-token.
-
While running the program, You can specify the region name, config file path, report file path, and tags through --region, --config-path, -report-path arguments.
-
If no region is specified us-east-1 is taken as the default region, Similarly if no config file path and report path are given, the current working directory's path is taken as the default path and the audit checks are performed for the default values.
-
Tags are checked by passing as an argument --tags or updating account tags in the config.json file. Moreover, the tags passed through the argument in the command line take priority.
-
The format of the tags that are passed through the argument in the command line should be separated using commas (,).
Cloud Audit Tool Execution
Command to Run the audit tool in the command line after installing the package.
cloud-audit-tool
Arguments that can be passed
cloud-audit-tool --region {region-name} --config-path {config-path} --report-path {report-path} --access-key {access-key} --secret-key {secret-key} --session-token {session-token} --tags {tag1,tag2,..}
Final Report
The overall report is provided as a HTML document in the path specified in the report-path argument. If no path is specified report is generated in the current working directory.
Metadata
Release files for cross43 0.0.6
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 |
|---|---|---|---|---|
| cross43-0.0.6.tar.gz | 30.9 kB | Without provenance | Details for cross43-0.0.6.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cross43-0.0.6-py3-none-any.whl | Python 3 | none | any | Details for cross43-0.0.6-py3-none-any.whl |
Total release size: 84.6 kB
Release files / cross43-0.0.6.tar.gz
| Download URL | cross43-0.0.6.tar.gz |
|---|---|
| Size | 30.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7f8ad9e57775ca2fa9cd8278de5b4b08b39fe9651762238f9d203a599e677392
|
|
BLAKE2b-256 checksum How to use checksums |
a36eea5784e3e9ae1f86a487530aaff0d2ae9eb4855eb5267b73179cb41c5ca5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.6
|
Release files / cross43-0.0.6-py3-none-any.whl
| Download URL | cross43-0.0.6-py3-none-any.whl |
|---|---|
| Size | 53.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5de4e6947c40592f591bf8c1c7c654dfe688181553adca9b4c77729a4d5f5d72
|
|
BLAKE2b-256 checksum How to use checksums |
97d804d69a5937d19b64a58b5bc3b901562e05281a1fec57eb9dd8a75c38f8f3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.6
|
Security for cross43 0.0.6
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.