2 posts tagged with "inventory"

"It [is] the best of times, it [is] the worst of times." Software engineers working with AWS have any cloud service imaginable at their fingertips and developer velocity could hardly be higher. But, even the most shiny of coins has two sides.

While developers can spin up compute instances, databases, and less tangible things like Lambda functions or virtual identities as they wish—at some point, someone will ask, "What is all of this?" And as they hack away in the CLI trying to get an overview of the resources in all of their AWS accounts, they will inevitably get frustrated. While Amazon has been a pioneer in cloud computing and offers the largest array of services, there are some things that aren't so ideal. Namely, API consistency.

In this post, I describe a few of the challenges and quirks with the AWS API and why we're building Resoto. (Spoiler alert: It is so that you don't have to!)

Understanding what's running in your cloud infrastructure is important for a number of reasons—for example, security, compliance, and cost.

But sometimes, the cloud feels more like a black box that you're feeding with cash, and in turn it performs the work that makes your business run.

Even those spinning up cloud resources might only be aware of their small slice of the pie. With hundreds of thousands of interconnected resources, it is really hard to know what's going on!

Cloud inventory has become a new type of technical debt, where organizations lose track of their infrastructure and how it relates to the business. Resoto helps to break open the aforementioned black box and eliminate inventory debt.