Workflows are an excellent way to set up scheduled jobs based on specific conditions and actions without having to write any code. For instance, it's possible to schedule a job that checks all cloud accounts hourly, and snapshots and deletes all unattached disks. Another example is scheduling a job that checks for resources with a specific TAG and notifies or deletes the resource if the TAG value indicates that it has expired.

Workflows can be configured to take an action or just only notify when a configured condition happens in any of your cloud environments.

How to Create a Workflow

Step 1: Initiate Workflow Creation

Navigate to the Workflow tab and select 'CREATE WORKFLOW'.

Step 2: Select Environment

Begin by assigning a unique name to your workflow for easy identification. This helps in distinguishing your workflow, especially when managing multiple tasks.

Next, choose the cloud provider (Azure, GCP, or AWS) for your workflow's execution.

📘

Please note that you can select only one cloud provider per workflow.

Step 3: Specify Account and Region

Within your chosen cloud provider, select one or more accounts and regions. This step allows for broader or more targeted workflow application.

Step 4: Choose Services and Apply Filters

Before proceeding, review the list of supported actions provided by the service for your cloud provider:

AWS

Azure

GCP

Select the service(s) to which you want to apply the workflow. You must add at least one filter. For example, create a workflow for AWS EC2 instances with maximum CPU utilization ≤ 15% since their third day of launch.

When you set your filter, you can see the number of resources that Cloudchipr has found based on your filter. Click on the 'Found Resources' tab to view these resources in more detail.

Step 5: Action or Notification Selection

Choose between taking actions on filtered instances or receiving notifications.

Actions

For example, in the case of EC2, your options include deleting instances, creating AMI then deleting instance, or stopping the instances. Full list of supported actions for AWS Azure GCP.

Additional settings:

• Enable Action Notifications: Receive a detailed resource list post-action via Email, Slack, or Webhook.
• Enable Grace Period Before Actions(Beta): When enabled, actions will only be taken after a notification is sent and the grace period has expired. Users will be able to protect or backup their resources during the grace period

For instructions on configuring your preferred notification method, refer to our Integrations page.

Notify Only

Inform your teams by sending a detailed list of discovered resources. Choose a preferred method of notification from our available integrations list to streamline communication.

Additional settings:

• Always Notify: If checked, Cloudchipr will not keep track of the resources found during each run and will send notifications for the same resources every time.
  • By default, Cloudchipr will remember the resources found after each run and will only send notifications when new resources are found or actions are taken on previously discovered resources
• Set minimum threshold: Receive notifications when costs exceed the defined threshold

Step 7: Schedule Your Workflow

Set the frequency of your workflow (Hourly, Daily, Weekly, Once) and choose the desired Time Zone.

Step 8: Preview and Confirm

The final step is a preview page where you can review and confirm your selected actions and services.

After submitting this workflow will check and notify in case any instances found where MAX CPU was not more than 15% for the last 7 days.