CloudQuery

Sync data from any source to any destination with CloudQuery CLI. Simple, Fast, and Extensible Data Movement

The env zero team has landed in NYC for PlatformCon. 🧪 10am: Kill the Slack queue, with Artem Artyunov in the Platform Dojo 🧠 Closing panel: the future of platform engineering, with Oved Lourie on Mainstage Stop by our booth for an EZ DOES IT hat. See you there! #PlatformCon

"Which EC2 instances are exposed to the internet AND missing critical security patches?" CloudQuery answers in seconds. No spreadsheets, no manual joins. New: try it free for 14 days. Business email, first sync, done. No sales call. cloud.cloudquery.io/auth/platform-… Watch 👇

Full writeup on why single-signal findings aren't enough: cloudquery.io/blog/introduci… Docs — supported integrations, filter options, custom Policies: cloudquery.io/docs/platform/…

Not limited to built-in sources. Define custom checks with Policies and they surface in the same Insights view — correlated against your full asset inventory. SQL-powered, built on the data you've already synced. No extra agents.

Your S3 bucket just got flagged as publicly accessible. Is it actually a problem? Without knowing it also holds PII, hasn't been accessed in 47 days, and was provisioned by a contractor — you can't tell. That's what we built CQ Insights to fix 🧵

We wrote out all five queries with full explanations, plus how to go from ad hoc investigation to automated CSPM in four weeks: cloudquery.io/blog/cloud-ope…

Same query serves triple duty: investigation tool at 2am, compliance evidence for auditors, and automated policy check on a schedule. No translation between "what I wrote to investigate" and "what runs in production." Zero language gap.

The CSPM market hit $1.64B in 2023, growing 45% YoY. Organizations keep buying more security tools. Misconfiguration rates stay flat. Something about this approach isn't working. Here's what we think is broken and how SQL fixes it. 🧵

Full implementation guide with 20+ production-ready SQL governance queries and the policy lifecycle walkthrough: cloudquery.io/blog/cloud-ope…

Start with highest-risk policies on a schedule: public S3 buckets, open security groups, unencrypted storage, IAM without MFA. Low false-positive, high-risk checks where drift creates the most damage. Get these running first, then expand.

If your governance only runs when code ships, you're blind to most infrastructure changes that actually cause incidents. Deploy-time checks cover one pathway. Console changes, config drift, and cloud provider updates bypass your pipeline entirely. 🧵