How to setup CloudQuery to build your cloud asset inventory in PostgreSQL and connect it to AWS QuickSight for visualization, monitoring and reporting.
In this blog post, we will walk you through how to setup CloudQuery to build your cloud asset inventory in PostgreSQL and connect it to AWS QuickSight for visualization, monitoring and reporting.
If it’s your first time using CloudQuery we suggest you first run it locally to get familiar with the tool, take a look at our Getting Started with AWS Guide.
If you are already familiar with CloudQuery, take a look at how to deploy it to AWS on Amazon Aurora and EKS at here.
You can connect QuickSight to a private PostgreSQL (RDS Aurora) if you are on the enterprise edition. See full walkthrough. If not, you can also make the Aurora publicly accessible but it is highly advised to only allow connections from QuickSight IP Addresses .
Click Create New Dataset and choose PostgresSQL (In this tutorial we will connect to publicly accessible RDS with authorized QuickSight IP Address) and fill-in the connection details:
Choose the table you want to visualize, in this case we will choose the
aws_resources view which you need to create to visualize all resources across all accounts and regions.
You can reuse QuickSight to export/share those dashboards as well as create alerts!
In this post we showed you how to build an open-source cloud asset inventory with CloudQuery as the ETL (Extract-Transform-Load) / data-ingestion layer and QuickSight as the visualization and monitoring platforms. This approach eliminates the yet-another-dashboard fatigue and gives you the ability to pick the best-in-class visualization tools and/or reuse your current stack.
Subscribe for monthly updatesOpen-source, product updates, blog-posts, news and more