Resoto uses a directed graph to represent your infrastructure resources as nodes and relationships between them as edges. A load balancer for example is represented as node with edges pointing to all target compute instances. The compute instance might have a volume attached, where we would see an edge between the instance node and the volume node.

Nodes represent resources, while edges define the relationship between nodes. It is often the case that a resource has multiple relationships to other resources.

Resoto has a command-line interface accessible via Resoto Shell. Commands are not executed locally, but interpreted on the server. As such, only Resoto Shell is required client-side.

Resoto offers commands like echo, tail, and jq—old friends to veteran shell users—but these commands only account for a small fraction of the possibilities in Resoto's command-line interface.

Version 2.X of Resoto Shell introduces tab completion, making the command-line interface easier to use than ever before! Press the tab key, and Resoto Shell will present you with a list of available commands:

I worked on a plugin that allows collecting DigitalOcean resources over the past few weeks, and I'm happy to announce that Resoto now has DigitalOcean support! 🌊

Resoto's search allows for resources to be selected using filters, combinators, and traversals. Search results can be combined, grouped, and aggregated.

Retrieving information about resources you have deployed in your Amazon Web Services (AWS) infrastructure means tediously navigating the AWS Management Console or using the AWS Command Line Interface. This approach works well in a single account setup, but best practice is to set up a multi-account environment. And as the number of accounts grows, navigating your infrastructure and finding resources via the Console or the CLI becomes increasingly difficult.

Furthermore, the relationships between your resources are also relevant: an EBS volume is mounted to an EC2 instance running in a VPC and reachable via an ALB load balancer, for example. Developers create resources using tools such as Terraform, CDK, or CloudFormation… or sometimes even the console or CLI. How can you see everything that is running in your cloud?