Skip to main content

· 6 min read
Anja Freihube

Cloud tagging strategies and policies are hailed as one of the most efficient ways to keep your cloud infrastructure controllable. But are they really?

Generally, the idea is that every piece of cloud service gets tagged (or labeled, in case of GCP) by the developers or maintainers who work with it. This could be accomplished with infrastructure-as-code (IaC) tools (such as Terraform), with a command-line interface (CLI), or in the cloud UI.

Tagging policies could require that each resource needs tags identifying the owner, cost center, product, project, and/or any other metadata. By being diligent about tagging, resources can be managed via their tags and nothing gets overlooked.

In theory, this is the correct way to manage resources; in practice, however, this hardly ever works as intended. Each tag created is a tag that requires maintenance. Tagging policies may change over time and people can make mistakes (in AWS, for example, tag keys are case sensitive). And, to properly use tagging on a greenfield cloud account is one thing; to retroactively apply tags to sprawling cloud infrastructure is quite another (especially when utilizing a multi-cloud strategy, where you'd need to repeat any operation over multiple interfaces).

· 5 min read
Nikita Melkozerov

Hello folks! A few months ago, we released Resoto Notebook, a library that makes it easy to query, visualize, and analyze Resoto data using pandas, Plotly, and Jupyter Notebooks.

Today, we'll discuss Resoto's new JupyterLite support, which allows you to use notebooks in the browser without installing and launching a Jupyter server.

Want to analyze raw infrastructure data when only platform engineers can access cloud consoles? Or count infrastructure assets without a data scientist? JupyterLite is a JupyterLab distribution that runs entirely in a web browser, and Resoto's new JupyterLite support gives you access to popular data analysis tools without the need for any additional installation steps.

· 2 min read
Nikita Melkozerov

We recently released the Resoto AWS CDK construct, which simplifies the deployment of Resoto to AWS.

We also offer a CloudFormation template, which is the easiest way to get a production-grade setup. The CDK construct is a bit more involved, but gives you more control over the setup.

The CDK construct pretty simple. All you need is a recent version of Node.js (we tested with 18.x.x) and Git. If you don't already have Node.js installed, we recommend using Node Version Manager (nvm).

· 27 min read
Lukas Lösche

In my last post, we discussed building actionable cloud infrastructure metrics and how to create metrics, export them into a time series database, and visualize them with Grafana. Today, we'll take a look at how to build an infrastructure app using Streamlit, a framework that turns data into web apps.

Sheep looking inside a black box

If you are not familiar with Python, don't worry—we're going to keep it simple! In Prerequisites, we'll go over installing Python and the coding techniques utilized in this project.

· 7 min read
Anja Freihube

"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!)

· 10 min read
Matthias Veit

Today's world of cloud computing is complex. There are many cloud providers, each with their own set of services. Getting insights out of your infrastructure requires specialized understanding of the data from each service.

Properties in different services may have different names but the same meaning, or vice versa. To interpret properties, we need to ensure that values have a defined unit of measurement and one base unit. You can see the challenge if you imagine the many ways you can specify the size of a volume, the number of CPU cores, or even timestamps.

Banner

· 12 min read
Matthias Veit

Kubernetes has dramatically improved the way we manage our workloads. It has become the de-facto standard for deploying and managing containerized applications, and is available in all major cloud providers.

A typical setup consists of distinct Kubernetes clusters for each application stage (e.g., dev, test, prod) or a cluster per tenant, and Kubernetes clusters shared between different users and teams often utilize namespaces and roles to control access. Deploying a single application to a Kubernetes cluster usually consists of tens to hundreds of resources (e.g., deployments, services, ConfigMaps, secrets, ingresses, etc.).

Even a relatively simple setup quickly becomes tedious to manage as the resource count grows. It is difficult for a human to keep track of resources, especially with user access limited to certain clusters in select namespaces.

· 13 min read
Lukas Lösche

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.

Sheep looking inside a black box

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.