-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Powerpipe dashboard displaying incomplete results #305
Comments
The error in the dashboard indicates that Steampipe cannot find / resolve your AWS credentials. Are you sure it's picking up the steampipe configuration properly? |
Hi @e-gineer, I tried the following steps for setting up the credentials
Please let me know if I am missing anything else. |
How is docker involved in your setup? You mention that at the start, but not in the latest info. Are you able to run basic queries against the steampipe instance you have created? (i.e. before using powerpipe with it) |
Earlier, I utilized Docker to explore Steampipe, but currently I have install both Steampipe and Powerpipe directly on my local virtual machine (VM). |
Hi @e-gineer, Any update? |
Hi @aditivarade,
What is the error you're seeing when executing queries? |
Hi @pskrbasu, I tried to execute a simple query("select name from aws_iam_role"). Below is the error I get inspite of configuring the credentials correctly. Error: aws_account_a: operation error IAM: ListRoles, exceeded maximum number of attempts, 9, failed to sign request: failed to retrieve credentials: failed to refresh cached credentials, no EC2 IMDS role found, operation error ec2imds: GetMetadata, exceeded maximum number of attempts, 3, request send failed, Get "http://169.254.169.254/latest/meta-data/iam/security-credentials/": net/http: timeout awaiting response headers (SQLSTATE HV000) |
@aditivarade it is worth ensuring there are no stray processes left over from previous failed runs. You can list staempipe processes with Please could you give that a go then retry. |
@kaidaguerre tried listing the processes and killing them, but no luck. |
So to be clear - even a simple steampipe query is failing: |
@kaidaguerre - The issue is resolved. Appreciate the responses. |
@aditivarade can I check how this was resolved? I'm having similar issues |
Hi,
I utilized your Steampipe Docker image tailored for AWS Cloud to generate several reports. Below is a screenshot showcasing the outcomes derived from the HTML report.
Command: docker run --rm -e AWS_SECRET_ACCESS_KEY=${AWS_SECRET_ACCESS_KEY} -e AWS_REGION=${AWS_REGION}
-e AWS_ACCESS_KEY_ID=${AWS_ACCESS_KEY_ID} -e AWS_SESSION_TOKEN=${AWS_SESSION_TOKEN}
--name steampipe-compliance --mount type=bind,source="${pwd}",target=/output
steampipe-aws-compliance check all --export /output/AWS_Report.html
I've delved into the functionalities of steampipe-mod-aws-compliance and went through the process of manually installing Steampipe and Powerpipe.
When executing the "powerpipe benchmark run aws_compliance.benchmark.all_controls" command, it indicates 158 errors detected. However, I'm unable to view any additional results or the successfully passed benchmarks (OK) on the dashboard, unlike when I conduct the analysis using the docker image.
Furthermore, I haven't observed any details regarding the resources upon which the errors have been detected.
Steps I have followed to set up steampipe with powerpipe
Below are the versions installed on my Ubuntu VM
Powerpipe version (
powerpipe -v
)Powerpipe v0.1.3
Steampipe version (
steampipe -v
)Steampipe v0.22.1
a) Exported environment variables on my VM
b) Created the aws credentials file
steampipe service start
powerpipe server
powerpipe benchmark run aws_compliance.benchmark.all_controls
For your informartion I have used the same AWS user and its credentials in both the cases(steampipe docker image and steampipe with powerpipe)
Expected behavior
The PowerPipe dashboard should showcase comprehensive outcomes, including thorough details regarding the resources it has scanned through.
The text was updated successfully, but these errors were encountered: