Insights

Below is a tutorial that walks you through the process of creating a CloudFlow from an insight.

Goal and objectives

• Goal: To create a workflow from an insight using the Migrate from gp2 to gp3 blueprint.

• Objectives: In this tutorial, you'll learn how to:

  • Check the insight data to use in the CloudFlow.

  • Interact with AWS services to check and modify EBS volumes.

  • Use filters in the flow.

  • Test an action by a dry run.

Start building

To start building it:

1. Sign in to the DoiT console, select Optimize from the top navigation bar, and then select Insights.

2. Select the Migrate from gp2 to gp3 Insight card on the main Insights page to open the insight detail page.

   Note

   CloudFlows are currently available for a subset of insights, with support for additional insights planned for future releases.

3. In Automate this insight, select Create a CloudFlow.

   

   You are taken to your draft CloudFlow blueprint.

Step 1: Configure the trigger

Add a manual trigger to the flow.

1. In the What should start your flow block, select Manually start.

   

   Tip

   Expand Complete your flow to see a list of nodes that you need to complete before you can publish this flow.

Step 2: Check the insight

An insight node determines the Migrate from gp2 to gp3 insight data to use in the CloudFlow.

1. In Service and action, check the CloudFlow has been created from the correct insight, in this case, migrateEBSGp2ToGp3.

2. In Test, select Test to ensure the CloudFlow can both process the incoming data and access it successfully. In Data out, you can confirm the correct data is moving out of this step.

   

Step 3: Describe EC2 volumes

The DescribeVolumes action allows you to retrieve information about one or more AWS EC2 volumes on your AWS account.

1. In Service and action, check the correct service and action is specified, in this case, DescribeVolumes.

2. In Parameters, select the accounts and regions whose volumes you want to migrate from gp3 to gp2.

3. In List of VolumeIds, the 2.migrateEbsGp2TGp3.volumeIds field contains the list of volume Ids that you have in your cloud environment.

   

Step 4: Filter for gp2 volumes

Filter your EBS volumes to retrieve volumes whose volume type is gp2.

1. In Data source, check the data source is 3.DescribeVolumes.

2. In Field, check the field is 3. DescribeVolumes. This field will store the filtered IDs of the gp2 volumes that you want to migrate to gp3.

3. In Filter 1, check the filter is Volumes.VolumeType = = gp2.

   

Step 5: Create snapshot

The CreateSnapshot action allows you to take a snapshot of the source volumes.

1. In Service and action, check the correct service and action is specified, in this case, CreateSnapshot.

2. In Parameters, select the accounts and regions whose EBS volumes you want to migrate from gp3 to gp2.

3. In VolumeId check the filtergp2 volumes field is specified. This field contains the output from the filter step, which lists the specific gp2 volumes that will be used to create snapshots.

   

Step 6: Modify volume

The ModifyVolume action changes the gp3 volumes to gp2 volumes.

1. In Service and action, check the correct service and action is specified, in this case, ModifyVolume.

2. In Approval, if the CloudFlow requires approval before its execution, select Require approval for this action. See Require approval.

3. In Parameters, select the accounts and regions whose EBS volumes you want to migrate from gp3 to gp2.

4. In VolumeId, check the 5. Filter to gp2 volumes.Volumes VolumeId field is specified. This field contains the unique identifiers of the EBS volumes that you want to modify.

5. In VolumeType, check that gp3 is specified.

   

Publish the CloudFlow

The last step is to publish the CloudFlow.

Once published, you can choose to Edit, Run, or Unpublish a CloudFlow on the same screen, or you can choose Close to return to the main screen.