Export CloudFormation

(Available at AWS accounts only)


With Cloudivize you can export selected assets to a CloudFormation JSON template.

Select assets from your account canvas by pinning those assets, click the snapshot icon (camera icon at the left-bottom) to open the snapshot view for the selected assets, you can do final touches on the snapshot by removing the groups or assets that you don’t want

to include at your export, then launch the export by from the icon


to download CloudFormation, and configure the export behavior.

Configuration options:

  • Force reference groups (even if hidden and not selected).

It will force exporting the group assets that are defined as required properties even those assets are not seen at the Canvas. Consider the case, where you have asset that refer to empty Subnet, and your view configured to “Hide Empty Groups” this subnet is not seen, but when exporting an asset that has a required property to this Subnet the export will force exporting the Subnet and refer to it at the relevant asset

  • Do not export none-regional objects. Check this option if you intend to import result template to the same AWS account

This option must be checked if you intending to import the generated template into another Region at the same account, and to avoid failure with “object already exist” errors during import. This option will allow you to generate a template that does not have the global assets (none-regional assets) and to define reference to those global assets with the appropriate asset id or arn.

Click Continue to download a JSON template with the selected assets

  • Export AMI (EC2 Images) as Mapping

When user selects EC2 Instance to export, the Instance has to have Image (AMI). With this option you decide whether Cloudivize will look for matching AMIs with the same name at all regions, or just put the AMI id from the current region as "Ref".

If this option is checked, the generated template will have the Mapping section, and will include mapping to AMIs at all regions. When there is no such AMI available at specific region, the UNAVAILABLE value will appear at the mapping, allowing the user to fill the AMI id manually while keeping the references inside the 

This option have performance impact due to the multiple quires against all regions to find the matching AMIs.


  • Export CloudFormation Template feature is not providing a ready-to-import template, it provides a very good starting point

  • You may need to change or delete some properties from the generated template according to your purpose

  • You may want to define Outputs according to your needs

  • AWS CloudFormation is not supporting all assets you may see at Cloudivize. Unsupported asset will not be exported


Export Behavior

  • When asset is selected, it is exported and references to it are defined as “Ref” properties

  • When specific asset is not selected for export, references to it can be one of two cases:

    • If the reference property is not “Required”, then the reference property will not be exported. At this case, please pay attention to hidden asset types (configured by you) and hidden groups (due to “Hide Empty Group” settings)

    • If the reference property is ”Required”, then the reference property will be defined as Parameter

  • Reference to AMI (EC2 Images) are exported as Mapping. Give it a quick review to make sure the intended image mapping at the target region is correct. When Cloudivize does not find a matching AMI at the given region, it indicates “UNAVAIABLE” at the mapping section

  • Some types always defined as Parameter, e.g. Key Pair reference, S3Bucket name and Password properties. This because Key Pair are not supported by CloudFormation but it is required, and S3Bucket name is globally unique so there is no sense to export it as is.