From 703baddaa0a8fdf1b43dd03bb41ca5034ec99079 Mon Sep 17 00:00:00 2001 From: Toni de la Fuente Date: Tue, 13 Sep 2016 16:09:37 -0400 Subject: [PATCH] Updated README --- README.md | 17 ++++++++++++++--- 1 file changed, 14 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index babe043c..13827e2f 100644 --- a/README.md +++ b/README.md @@ -62,7 +62,7 @@ or for custom profile and region ``` ./prowler.sh -p custom-profile -r us-east-1 -c check11 ``` -Valid check numbers are like in the AWS CIS Benchmark guide, while 1.1 is check11 or 3.10 is check310 +Valid check numbers are like in the AWS CIS Benchmark guide, while 1.1 is check11 or 3.10 is check310 4 - For help use: @@ -78,7 +78,18 @@ USAGE: -h this help ``` +## How to fix all warnings: + Check your report and fix the issues following all specific guidelines per check in https://d0.awsstatic.com/whitepapers/compliance/AWS_CIS_Foundations_Benchmark.pdf - 4 - Check your report and fix the issues following all specific guidelines per check in https://d0.awsstatic.com/whitepapers/compliance/AWS_CIS_Foundations_Benchmark.pdf +## Screenshot - screenshot 2016-09-13 09 31 07 + screenshot 2016-09-13 16 05 42 + +## Troubleshooting + + If you are using STS token for AWS-CLI and your session is expired you probably get this error: + +``` + A client error (ExpiredToken) occurred when calling the GenerateCredentialReport operation: The security token included in the request is expired + ``` + To fix it, please renew your token by authenticating again to the AWS API.