Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.


Log in to subscribe to topics and get notified when content changes.


A blueprint is a cloud-agnostic template for publishing a catalog item that a cloud user can use to request a stack.

What a blueprint contains

  • The set of resource blocks that the catalog item includes. For example, a resource block can contain a virtual machine, an app that runs on the VM, and information about the datacenter that the VM should run on.
  • Connections between the resources. For example, the VM has a hosts relationship with the app.
  • The operations that the user might want to perform on the resulting stack or resources. For example, the user can provision or stop a resource.
  • The operations that should happen to each resource for each of the operations. For example, to provision the catalog item, the system must provision the VM and the app that runs on the VM.
  • Attributes to use during resource operations. For example, the blueprint can list the version of the app to provision to the VM.

Ways to create a blueprint

  • Use the blueprint designer.
  • Use the Cloud Template module.
  • Import the YAML representation of an existing blueprint.
  • Based on an AWS CloudFormation template
  • Based on an Azure ARM template

Catalog items and blueprints

You publish a blueprint to generate a catalog item that is available on the service catalog. A cloud user can use the Cloud User Portal to request the catalog item.
See the following graphic for an explanation of what the user sees in the catalog, and what component of the blueprint is related to it:
  1. Applies appropriate policies to the request.
  2. Verifies that the requester has sufficient quota for the requested resources.
  3. Applies the operations and attribute settings that you configured in the blueprint.