chore(docs): solve some issues (#3868)

This commit is contained in:
Sergio Garcia
2024-04-29 10:19:37 +02:00
committed by GitHub
parent 14de3acdaa
commit 34c2128d88
3 changed files with 9 additions and 6 deletions
+1 -1
View File
@@ -27,7 +27,7 @@ Those credentials must be associated to a user or role with proper permissions t
Prowler can use your custom AWS Profile with:
```console
prowler <provider> -p/--profile <profile_name>
prowler aws -p/--profile <profile_name>
```
## Multi-Factor Authentication
+7 -4
View File
@@ -3,13 +3,13 @@
To save your report in an S3 bucket, use `-B`/`--output-bucket`.
```sh
prowler <provider> -B my-bucket
prowler aws -B my-bucket
```
If you can use a custom folder and/or filename, use `-o`/`--output-directory` and/or `-F`/`--output-filename`.
```sh
prowler <provider> \
prowler aws \
-B my-bucket \
--output-directory test-folder \
--output-filename output-filename
@@ -18,8 +18,11 @@ prowler <provider> \
By default Prowler sends HTML, JSON and CSV output formats, if you want to send a custom output format or a single one of the defaults you can specify it with the `-M`/`--output-modes` flag.
```sh
prowler <provider> -M csv -B my-bucket
prowler aws -M csv -B my-bucket
```
???+ note
In the case you do not want to use the assumed role credentials but the initial credentials to put the reports into the S3 bucket, use `-D`/`--output-bucket-no-assume` instead of `-B`/`--output-bucket`. Make sure that the used credentials have `s3:PutObject` permissions in the S3 path where the reports are going to be uploaded.
In the case you do not want to use the assumed role credentials but the initial credentials to put the reports into the S3 bucket, use `-D`/`--output-bucket-no-assume` instead of `-B`/`--output-bucket`.
???+ warning
Make sure that the used credentials have `s3:PutObject` permissions in the S3 path where the reports are going to be uploaded.