Instances (EBS)

At the completion of this section, you will:

  • understand the concept and use of an Instance in FlexDeploy
  • be able to create/modify an instance
  • associate an instance to one or more environments
  • associate workflows to instances

An Instance represents a logical software technology stack running across one or more Environments.  For example, a global EBS instance maps to an Instance in FlexDeploy.  Regional EBS instances would be represented by one Instance per region.

Viewing the current list of Instances is performed by selecting Topology from the menu, and then selecting the Instances tab in the left-hand paneThere are no Instances with a new installation, so next we will create one for our global EBS instance used within this tutorial.


Click on the + in the upper right corner to create and configure a new Instance.  Enter the following required fields for the Instance.

Instance NameA descriptive name for the Instance.
Instance Code

A technical code, without any spaces.  The codes are available as variables to shell and Groovy scripts, and therefore needs to comply with their limitations. 

Click on the Environments tab.  Here we will associate the environments which host physical instances for our logical Instance.  The available Environments, which we created in the last section, are displayed in the right-hand pane.  Drag the Development, Test, QA, and Production environments into the center pane to associate them.

After associating the environments:

Click on the Workflows tab.  Here we will associate the workflows which will execute on this Instance.  Earlier we created build and deploy workflows for EBS, so now we will bind them to our Instance by dragging them from the left-hand pane into the center pane.


Use the Search filter to easily locate your workflows.

The Plugins tab shows the FlexDeploy plugins which will be executed on the Instance.  


After associating the workflows to the Instance, any plugins used by those workflows are automatically associated for you.  If you later utilize other plugin operations within these workflows you will need to explicitly associate them to the corresponding Instance(s).

Both workflows and plugin operations have properties which may have a scope of "environment instance".  This mapping allows FlexDeploy to prompt for values for them within the topology.  We will see examples of such properties in the next section.

Click Save to complete the Instance configuration.

The following macros are not currently supported in the footer:
  • style