Reusable Configusets

Typically, configsets are directly hardcoded into the CloudFormation template. Unfortunately, this makes them hard to reuse. IE: You copy and paste the configset code between CloudFormation templates.

With Lono, configsets are define separately from the template. Lono takes the configsets and adds them into your CloudFormation templates. This allows them to be reusable with different templates.


Let’s say you have two blueprints: ec2 and asg.

  • The ec2 blueprint has an Instance resource.
  • The asg blueprint has an LaunchConfiguration resource.

You can reuse the same configsets for both blueprints. Example:


configset("cfn-hup", resource: "Instance")
configset("httpd", resource: "Instance")


configset("cfn-hup", resource: "LaunchConfiguration")
configset("httpd", resource: "LaunchConfiguration")

UserData cfn-init

The UserData script for the ec2 blueprint calls cfn-init like this:

/opt/aws/bin/cfn-init -v --stack ${AWS::StackName} --resource Instance --region ${AWS::Region}

The asg blueprint’s UserData calls cfn-init like this:

/opt/aws/bin/cfn-init -v --stack ${AWS::StackName} --resource LaunchConfiguration --region ${AWS::Region}

The beauty is that you can choose whichever configsets are needed. You don’t have to copy and paste the configset into different templates. Just configure them, and lono injects them into the CloudFormation template for you.

Pro tip: Use the <- and -> arrow keys to move back and forward.

Edit this page

See a typo or an error? You can improve this page. This website is available on GitHub and contributions are encouraged and welcomed. We love pull requests from you!