env zero

#AskCloudQuery Try CloudQuery for free today: https://lnkd.in/egEQunKa "Which third-party vendor integrations have network access to sensitive systems and haven't had a security review in over a year?" How long would it take you to answer this question across your multi-cloud? Find out how much time you will save. Try CloudQuery today: https://lnkd.in/egEQunKa

Stop relying on stale Terraform state. Learn how to uncover hidden infrastructure drift and query your actual cloud state using SQL. By 👋 Joe Karlsson, thanks to env zero

📢 Today we’re announcing CloudQuery Insights. Cloud teams have more data than ever: CSPMs, AWS Config, CUR, Jira, ServiceNow... but no way to connect it. A single misconfigured resource can take dozens of person-hours to investigate because context is scattered across five different tools. We built CloudQuery Insights to fix that. It monitors your entire asset inventory and automatically correlates security findings, cost data, policy violations, and audit events on every resource so your team stops hunting and starts acting. Insights allow cloud teams to move faster, reduce risk, and eliminate waste in their cloud. Read the full announcement here: https://lnkd.in/gZvB6VRi

ANNOUNCEMENT: A year ago, when we launched MultiTool, we followed the traditional wisdom of launching an MVP. We found an unsolved problem in DevOps with a real market need, built a solution, and launched it as quickly as possible. But sometimes "minimum" isn't good enough. Our design partners loved MultiTool's capability, but the DX was rough. For the typical engineer, the deployment process has a ton of inertia because deployments are so load-bearing. If something goes wrong with your deployment process, the whole team suffers, so it's hard to find an internal champion willing to take on the political risk necessary for buy-in. If the tool isn't perfect, it could be painful. And perfect means mature. In short, our MVP did not deliver. That's why we rethought MultiTool from the ground up. For the past five months, I've been quietly rebuilding MultiTool in totality for our upcoming relaunch. Now, MultiTool is focused on monitoring and alerting. Unlike v1, it's a zero-config, zero installation process. Point your OTel data at our server, and get automatic 24/7/365 monitoring and alerting. Our focus is shifting from automated canary analysis, which will no longer be supported on the new platform, to combating alert fatigue. The same thresholdless metric analysis algorithm that powered the canary analysis engine now powers the new monitoring platform. Alert fatigue is a problem only made worse by the adoption of AI, as there are more services, deploying more often, with more bugs, requiring more hand-tuning. With MultiTool, there is no hand-tuning. We model your application's baseline performance and alert you whenever there's a regression, pinning down the commit and diff that caused it. Automatic root cause analysis with no config, on any codebase. I'm so excited to launch what we've built, and while all the features won't come out at once, we're moving faster and building more than ever before, and the future of Wack Incorporated shines brightly through the polychomatic glass pane of innovation.