CloudQuery is an open-source, extensible framework that gives you a single-pane-of-glass to your cloud-infrastructure using SQL. Today, we are happy to announce the release of the DigitalOcean Provider for CloudQuery.
DigitalOcean is a cloud-provider that is popular both with small and larger companies. Some of DigitalOceans' advantages are its ease-of-use, flat pricing, and cheaper pricing for some services. This release brings the power of CloudQuery to DigitalOcean users, DevOps engineers and SREs, helping solve visibility, security and compliance challenges with SQL.
In this short tutorial, we will install CloudQuery and use it to fetch a DigitalOcean resources. Then, we will use SQL to get visibility into security, compliance and cost-management in DigitalOcean.
First we need to download our precompiled CloudQuery binary, we can also download it with the following brew command:
Before running CloudQuery we need to generate a
config.hcl. We won't dive into all the options available and let CloudQuery generate one for us.
Now that we have our
config.hcl ready we need to add our DigitalOcean Access Key and Spaces Access Key. We can generate our tokens in DigitalOcean's console.
CloudQuery requires us to connect to a database. Either use an existing one (we change the
dsn in the
config.hcl), or simply create a database with the following command
Finally, we can execute CloudQuery to fetch all our DigitalOcean resources, simply run the fetch command and let the magic happen.
After we finish fetching our config data we can make queries for security, compliance, cost management and other purposes.
We are going to continue to expand and maintain the DigitalOcean Provider, adding support for more current and future resources. Interested in seeing another provider? Check out Developing New Provider and/or open an issue on our GitHub.