Use case 14 of 21 · By Nicolas Dao

Provisioning everything

Infrastructure as code across AWS and every vendor.

My stack for this

  1. 01
    Pulumi

    Real code, S3 backend, and any Terraform provider.

Don't

  • AWS CloudFormation

    Never. YAML templates that only reach AWS. Pulumi does the same job in real code and provisions every other vendor too.

    Instead: Pulumi

Worked example: Pulumi everywhere →

The picks, in brief

What each one is, my verdict, and what it costs. Every name opens the full entry: when to use it and when not, the gotchas with their fixes, provisioning and alternatives.

  • My default Pulumi

    Infrastructure as real code. And it can use any Terraform provider, so nearly everything is provisionable from one codebase.

    Pricing: Free and open source with a self-managed S3 backend (no Pulumi Cloud fees).

Where they sit

The layers of the stack this job touches, with every tool named on this page.

Want this stack in your AWS account?

Cloudless Labs is a Sydney consultancy. We migrate on-premises systems to AWS, build serverless apps on this stack, and coach teams to ship with Claude Code and Codex.

Contact Us

For general inquiries, please contact us at:

For e-learning capabilities, please contact: