Toolset to render and manage AWS CloudFormation ( )
Go to file
Stefan Reimer 7841f175fd
Some checks reported errors
ZeroDownTime/CloudBender/pipeline/head Something is wrong with the build of this commit
docs: minor tweaks
2022-06-29 10:49:08 +02:00
.aws docs: minor tweaks 2022-06-29 10:49:08 +02:00
cloudbender fix: make pulumi stack sync work again, update docs 2022-06-29 10:30:25 +02:00
conf feat: add execute task, rework Dockerfile to allow podman run rootless 2022-06-27 20:51:03 +02:00
tests First release on PyPy, Makefile and License 2019-02-07 22:05:33 +00:00
.flake8 fix: code style / flake8 automation 2022-02-22 11:04:29 +01:00
.gitignore Initial checkin 2018-11-22 18:31:59 +00:00 feat: add DISABLE_SOPS 2021-10-13 13:23:31 +02:00
cloudbender.png Update logo 2020-05-27 14:05:08 +01:00
Dockerfile feat: implement version checks for extended toolchain 2022-06-28 15:30:13 +02:00
Jenkinsfile ci: disable trivy fail for now 2022-02-08 16:19:48 +01:00 First release on PyPy, Makefile and License 2019-02-07 22:05:33 +00:00
Makefile ci: migrate from setuptools to PEP517 hatchling to build 2022-06-28 13:15:45 +02:00
pyproject.toml docs: tweaks 2022-06-28 13:45:51 +02:00 docs: minor tweaks 2022-06-29 10:49:08 +02:00
requirements.txt ci: migrate from setuptools to PEP517 hatchling to build 2022-06-28 13:15:45 +02:00

Logo CloudBender


Toolset to deploy and maintain infrastructure in automated and trackable manner.
First class support for:


1a. Containerized

The command below tests the ability to run containers within containers on your local setup.
( This most likely only works on a recent Linux box/VM, which is capable of running rootless containers within containers. Requires kernel >= 5.12, Cgroups V2, podman, ... )

podman run --rm -v .:/workspace -v $HOME/.aws/config:/workspace/.aws/config podman run -q --rm echo "Rootless container inception works!"

if you get Rootless container inception works!, add an alias to your environment, eg:

alias cloudbender="podman run --rm -v .:/workspace -v $HOME/.aws/config:/home/cloudbender/.aws/config cloudbender"

and proceed with step 2)

1b. Local install

  • pip3 install -U cloudbender
  • curl -fsSL | sh (official Docs)
  • either podman or docker depending on your platform

2. Test cli

To verify that all pieces are in place run:

cloudbender version

which should get you something like:

[2022-06-28 16:06:24] CloudBender: 0.13.5
[2022-06-28 16:06:24] Pulumi: v3.34.1
[2022-06-28 16:06:24] Podman/Docker: podman version 4.1.0


Usage: cloudbender [OPTIONS] COMMAND [ARGS]...

  --debug     Turn on debug logging.
  --dir TEXT  Specify cloudbender project directory.
  --help      Show this message and exit.

  assimilate         Imports potentially existing resources into Pulumi...
  clean              Deletes all previously rendered files locally
  create-change-set  Creates a change set for an existing stack - CFN only
  create-docs        Parses all documentation fragments out of rendered...
  delete             Deletes stacks or stack groups
  execute            Executes custom Python function within an existing...
  export             Exports a Pulumi stack to repair state
  get-config         Get a config value, decrypted if secret
  outputs            Prints all stack outputs
  preview            Preview of Pulumi stack up operation
  provision          Creates or updates stacks or stack groups
  refresh            Refreshes Pulumi stack / Drift detection
  render             Renders template and its parameters - CFN only
  set-config         Sets a config value, encrypts with stack key if secret
  sync               Renders template and provisions it right away
  validate           Validates already rendered templates using cfn-lint...
  version            Displays own version and all dependencies


State management


The state for all Pulumi resources are stored on S3 in your account and in the same region as the resources being deployed. No data is send to nor shared with the official Pulumi provided APIs.

CloudBender configures Pulumi with a local, temporary workspace on the fly. This incl. the injection of various common parameters like the AWS account ID and region etc.


All state is handled by AWS Cloudformation.
The required account and region are determined by CloudBender automatically from the configuration.

Config management

  • Within the config folder each directory represents either a stack group if it has sub-directories, or an actual Cloudformation stack in case it is a leaf folder.
  • The actual configuration for each stack is hierachly merged. Lower level config files overwrite higher-level values. Complex data structures like dictionaries and arrays are deep merged.



CloudBender supports the native Pulumi secret handling. See Pulumi Docs for details.


CloudBender supports SOPS to encrypt values in any config file.

If a sops encrypted config file is detected by CloudBender, it will automatically try to decrypt the file. All required information to decrypt has to be present in the embedded sops config or set ahead of time via sops supported ENVIRONMENT variables.

SOPS support can be disabled by setting DISABLE_SOPS in order to reduce timeouts etc.