Toolset to render and manage AWS CloudFormation ( )
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Stefan Reimer 962ef05714 fix: ensure Jinja2 version >=3 4 weeks ago
cloudbender fix: support Jinja2 >= 3.1 4 weeks ago
tests First release on PyPy, Makefile and License 3 years ago
.flake8 fix: code style / flake8 automation 3 months ago
.gitignore Initial checkin 4 years ago feat: add DISABLE_SOPS 7 months ago
Dockerfile fix: Revert Python to V3.8 4 weeks ago
Jenkinsfile ci: disable trivy fail for now 3 months ago First release on PyPy, Makefile and License 3 years ago
Makefile fix: migrate to new Jinja2 V3 context decorator 4 weeks ago chore: some more docs 6 months ago
cloudbender.png Update logo 2 years ago
dev-requirements.txt feat: Enabled Jinja2 V3 support 4 months ago
requirements.txt fix: ensure Jinja2 version >=3 4 weeks ago
setup.cfg ci: use version number from Git tag 3 months ago fix: ensure Jinja2 version >=3 4 weeks ago

Logo CloudBender


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


$ pip install cloudbender

State management


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


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.


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

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

  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
  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...

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.



Secrets handling


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


CloudBender supports SOPS to encrypt values in any config yaml file since version 0.8.1

If a sops encrypted config file is detected CloudBender will automatically try to decrypt the file during execution.
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.