Stack Name

You probably noticed that the stack names automatically have LONO_ENV added to the blueprint name. Example:

Command CloudFormation Stack Name
LONO_ENV=dev lono up demo demo-dev


You can customize the stack naming pattern with config.names.stack.


Lono.configure do |config|
  config.names.stack = ":APP-:ROLE-:BLUEPRINT-:ENV"

Lono expands the pattern and replaces it with actual values.


The stack name will also include LONO_APP when set. Example:

Command CloudFormation Stack Name
LONO_APP=app1 LONO_ENV=dev lono up demo app1-demo-dev

Clean Behavior

  • Lono will clean the string from consecutive dashes. IE: -- => -. This allows LONO_APP to not be set.
  • Starting and trailing dashes will be removed to keep the stack name clean.
  • Underscores are replaced by dashes since only dashes are allowed in CloudFormation stack names.


The table below covers each setting. Each option is configured in config/app.rb with config.OPTION. The config. portion is not shown for conciseness. IE: logger.level vs config.logger.level.

Name Default Description
names.stack Pattern to use for the CloudFormation stack name. See: Names Docs :APP-:ROLE-:BLUEPRINT-:ENV-:EXTRA

See Full Config Reference