Failed Scans and No Compliance Reports

[lucferrari]

Steps to Reproduce

My scans at cloud.prowler.com are failing. I just moved from app.prowler.com to cloud.prowler.com. Also when I go to compliance I don't see any report.

Expected behavior

see the reports and don't see failed scans. When I start the job manually it looks it work, but not the scheduled ones.

Actual Result with Screenshots or Logs

How did you install Prowler?

Cloning the repository from github.com (git clone)

Environment Resource

it's the cloud prowler, not CLI

OS used

MacOS

Prowler version

it's saas version

Pip version

n/a

Context

No response

[pedrooot]

Hey! @lucferrari you can check why the scheduled scan is failing on the details. To see this information just click on the i button, if you can give me this info I could help you better.

Also, could you delete the second photo? It contains your aws accounts ids and isn't safe to share them here.

[lucferrari]

Thanks! this is the reason: Provider aws is not connected: AWSSessionTokenExpiredError[1016]: The provided AWS Session Token is expired - An error occurred (ExpiredToken) when calling the GetCallerIdentity operation: The security token included in the request is expired

It looks like the tokens a re getting expired. Is there any other way we could connect to my accounts so this doesn't happen again? When I was using app.prowler.com I was using a cloudformation template for an IAM role... How can I do something similar here with this new version? Thank you

[MrCloudSec]

Hi @lucferrari, can you add the provider as in app.prowler.com by assuming an IAM Role? You can click this option here:

[puchy22]

Hi @lucferrari,
Just checking in — is the issue still occurring, or has it been resolved? Can we go ahead and close this issue?

Thanks!