3 ms·

Hey! Steampipe looks great and I think the architecture you chose is very smart. Some feedback from myself: I've tried setting up steampipe with metabase to do

Hey! Steampipe looks great and I think the architecture you chose is very smart. Some feedback from myself: I've tried setting up steampipe with metabase to do some dashboarding. However, I’ve found that it mostly exposes "configuration" parameters, so to say. I couldn't find dynamic info, like S3 bucket size or autoscaling group instance count. Have I done something backwards or not noticed a table, or is that a design decision of some sort? That was half a year ago, so things might've changed since then, too.

nathanwallace 4y ago
Steampipe mostly exposes underlying APIs or data through SQL. So, "select * from aws_s3_bucket" will return bucket names, tags, policies, etc all together. But, bucket size is not a direct API so doesn't have a direct table. In some high value cases we've added tables to simplify / abstract / normalize data - for example AWS IAM policies - https://steampipe.io/blog/normalizing-aws-iam-policies-for-automated-analysis https://steampipe.io/blog/normalizing-aws-iam-policies-for-a... This example query returns the number of instances attached to an autoscaling group - https://hub.steampipe.io/plugins/turbot/aws/tables/aws_ec2_autoscaling_group#instances-information-attached-to-the-autoscaling-group https://hub.steampipe.io/plugins/turbot/aws/tables/aws_ec2_a... BTW, we recently published a Metabase integration guide - https://steampipe.io/docs/cloud/integrations/metabase https://steampipe.io/docs/cloud/integrations/metabase