CloudQuery

My main use case for CloudQuery  is to help find assets within our cloud environment.

A specific example of how I use CloudQuery  to find assets is with Prisma Cloud, where we have issues detecting all of the different assets that don't seem to be picked up by Prisma Cloud. I was using CloudQuery in order to write SQLs to find specific types of assets that weren't originally being picked up by Prisma.

I use CloudQuery whenever I have issues writing RQLs for Prisma Cloud. The SQLs to find assets are a little bit easier to write, enabling me to handle more complex queries.

I think the best feature CloudQuery offers is the AI aspect that allows you to tell it what you want, and it writes SQL for you. This really cuts down on time and effort.

The AI-generated SQL works well for my team as it gets things right most of the time. When it was first introduced, there were issues where I had to edit it, but after updates, it became very useful to the point where minimal edits were needed. If an edit was necessary, I could follow up with the AI and it would fix any mistakes automatically.

CloudQuery positively impacts my organization by helping us find assets easier. For instance, I was looking for any type of publicly accessible assets within the cloud environment and was having issues with Prisma, so CloudQuery made it easier to find those assets.

It became much easier to find assets with CloudQuery, and I noticed a lot of time saved, especially because of the AI SQL writer that does the work for us. I was spending hours trying to craft an RQL for Prisma, but I could figure out the SQL in CloudQuery in minutes.

One of the improvements that could be made to CloudQuery is the GUI. In the past, I had issues where I couldn't see all the information that would pop up at the bottom. That might be fixed by now, but I was experiencing issues with the GUI itself.

CloudQuery's AI capabilities lack governance and security features. While the AI is great for helping me craft SQLs to find assets in the environment, it does not have real security features for blocking or similar tasks. I can set up SQLs for alerting, but I find that a bit limiting.

For what it is, CloudQuery is great. The only improvement I could suggest would be to set up more alerting features, but overall it is great for what it is, and I would say it feels a little bit limiting.

I have used CloudQuery for about three to four months.

CloudQuery is very stable, and I have not had any issues.

CloudQuery's scalability seems fine. It has not had any issues when I put my environment on it.

Customer support is great. I have calls with two of the team members at CloudQuery on a semi-regular basis, and they took my feedback and implemented things very quickly. I was very impressed by the support that I received while using it.

I used CloudQuery in conjunction with Prisma Cloud. I did not fully switch; instead, I used it as an additional layer of my security.

I proceeded with a free trial, but I was not involved when it came to the cost, so I am not sure.

I do not have a business relationship with this vendor other than being a customer.

I am unsure about the money saved, but as I mentioned earlier, there was definitely a lot of time saved. I spent a couple of hours trying to craft certain RQLs in Prisma, but I could find the same asset information in CloudQuery in less than an hour, whereas Prisma took hours and hours to get things figured out.

I did not purchase CloudQuery through the AWS  marketplace; I just used it for a free trial for a few months.

Before choosing CloudQuery, I did not evaluate other options.

CloudQuery really acts as an asset inventory tool, which is great, but I find that somewhat limiting.

My advice to others looking into using CloudQuery is to know the limitations. CloudQuery is a great product for getting asset inventory of your cloud environment, at least based on my experience from a few months ago, but it is not much more than that, and it excels at what it does. I would rate this review an eight out of ten.