CloudQuery deployment model and hardware requirements for AWS multi-account sync

Hi team,

We have tested CloudQuery and are happy about its capabilities. Now, I want to deploy it on our AWS for a total of 110 AWS accounts across 20+ products. I will add Azure and GCP later down the road.

What would be the best deployment model on AWS you suggest to sync frequently and keep the accounts up to date? I am also planning to use Grafana as a visualizer and PostgreSQL as the destination database.

Additionally, if possible, please suggest the hardware requirements to handle syncs smoothly.

Thanks in advance.

@upright-dogfish Thanks for the feedback, and glad testing went well. There are multiple different ways to deploy; it also depends on whether you’d like to host that in the cloud or on-prem, as well as which cloud provider you’d prefer to use. With Grafana and PostgreSQL, you can use Grafana Cloud. If the plan is to host on a cloud provider, there are managed services such as AWS Managed Grafana, and PostgreSQL can be hosted on AWS Aurora or AWS RDS.

An example with AWS, Grafana, and PostgreSQL: How to use CloudQuery with AWS, Grafana, and Postgres

A couple of resources that may help:

To echo @premium-ladybird’s point, that’s a great case study and a great architecture listed:

We also have documentation on deploying on different architectures such as Amazon ECS:

We do offer bootstrapping/help setting up CloudQuery as needed via our Support plans: CloudQuery Pricing. We also have plans to offer a fully managed version of CQ in the future—happy to chat more if that’s something you’re interested in.

Thanks, JSON and Peter. We will try the hexagon model. It looks promising. If any hiccups arise, we will get back to you. :+1: