infrastructure as code

And then the other one that I wanted to mention based on Marco's comment initially is that as we start building bigger or broader workflows or blueprints, the nice part is that we have this component that DBS may talk a little bit more about called the runner.

And the runner is basically an interpreter of the automation, the IAC tool that we are using for each one of the workflows.

So for example, when we use an Uber workflow, let's imagine you have eventually network, compute, plus a storage, plus software, plus all these things.

maybe one of the tools that would be beneficial for us to use is Ansible, but maybe for another one is Terraform, or maybe we need to do Helm or Python or Shell, like all these different things.

The same name, ZabSec, can be searched there.

And we regularly post blogs, our design architecture videos, uh, in some cases, uh, code also to, to, you know, make life of developers and infrastructure developers with IaC easy.

So yeah.

So you will be looking at us at our website, uh, YouTube, and LinkedIn.

... right, which is not outside the realm of possibilities, I may, in some instances, be burning those to the ground.

If they're deployed through, if they're deployed through IAC-

Right

... what does a repave cost me anyway?

Third, Pulumi 3.258 adds opt-in credential encryption.

Small change, but a useful reminder that IAC state and configuration often contain more sensitive material than teams realize.

And fourth, one AWS credential breach was reportedly noticed because the bill changed.

Unexpected egress charges became the security signal.

Terraform or IOC, infrastructure...

IAC, sorry.

IAC, infrastructure as code, is the category, and then under that category, there's Terraform, OpenTofu, and CloudFormation, and those are all just ways to define how you want your infrastructure to look, basically, in code.

So if I was real simple, I could, I could say I want an EC2 instance, which is just your basic server, virtual server running on Amazon, and then I want a database, a, a MySQL database, this version, and I could put those in code in some way, and then, like I said, version control it, or I can hit apply.

So say somebody accidentally deletes my application layer, a lot easier to replace than a data layer, of course, and, uh, I need to spin that back up real quickly, you just re-hit Terraform Apply, and it re-spins up and provisions the missing areas.

So I mean, if you're, if you're experimenting for 10 seconds and you're gonna delete it, I mean, I wouldn't commit it into version control.

Let's put it that way.

You want your version control if you're like, "I accidentally poked a hole" for 10, 10 minutes to be like, "Okay, how is this not working?" You want your version control Terraform IOC to, IAC to wipe, wipe that out the second you're done with it.