Introduction
DoiT CloudFlow is a GenAI-powered, no-code FinOps workflow solution. It provides the automation and intelligence for you to manage FinOps processes with ease and ensure smooth operations and cost efficiency at scale.
Benefits
DoiT CloudFlow empowers you to streamline cloud operations, enhance efficiency, and achieve better cost management through automation and proactive optimization.
-
Action on FinOps recommendations. CloudFlow enables you to effectively implement FinOps recommendations, including optimizing workloads, reducing waste, and improving cost management.
-
Enhanced efficiency and collaboration. CloudFlow helps organizations optimize cloud operations, leading to cost savings and better resource utilization. It also integrates with JIRA, Slack, and other third-party project management tools to facilitate seamless collaboration within and cross teams.
-
Multicloud environments. CloudFlow supports automation and optimization across cloud providers such as AWS, Google Cloud, and Microsoft Azure. It is a unified solution for managing diverse cloud environments.
-
Proactive cost optimization. Working in conjunction with other DoiT Cloud Intelligence features such as Insights, CloudFlow can proactively surface optimization opportunities, helping identify and address inefficiencies early on.
Core capabilities
DoiT CloudFlow connects your existing IT functions with critical FinOps metrics such as cloud cost and usage, commitment plans, budgets and related monitoring, and cloud tagging standards. It benefits organizations by streamlining financial operations and decision-making with the following capabilities:
-
API-driven workflow automation. CloudFlow is integrated with AWS, Google Cloud, and DoiT APIs. It provides a unified interface where you can create no-code flows that automate repetitive cloud management tasks, such as tagging resources or approval-based deprovisioning, thereby improving operational efficiency.
-
Prescriptive blueprints. CloudFlow comes with a set of customizable blueprints to help you quickly implement best practices, ensuring cost optimization and compliance with minimal setup time.
-
Run history. CloudFlow provides a detailed run history to help teams track workflow execution, troubleshoot, and ensure compliance with audit requirements.
Key concepts
-
CloudFlow: A CloudFlow is an automated process defined by a trigger and a set of activities.
-
Node: A node is a building block of a CloudFlow. There are two types of node: trigger node and activity node.
-
Activity: An activity is a task or action to be performed in a CloudFlow, for example, running a query, sending an API request, or asking for approval. Activities are further categorized into actions, blueprints, filters, conditions, and transformers.
-
Trigger: A trigger defines the way to start a CloudFlow. You can start a CloudFlow on a custom schedule or manually from the DoiT console. See Triggers.
-
Blueprint: A CloudFlow blueprint is a prebuilt group of activities that can be embedded in another CloudFlow or serve as a template when creating a new CloudFlow.
APIs in CloudFlow
CloudFlow integrates with a wide range of AWS and Google Cloud APIs, allowing you to build API-driven workflows. When planning APIs for a CloudFlow, be aware of the following:
-
Permissions. At the basic level, CloudFlow inherits the permissions granted to DoiT when you connect your cloud accounts.
You can verify whether you have the required permissions when configuring an action node, and follow the instructions provided in the DoiT console to add additional permissions if necessary.
-
API quotas. Requests sent to AWS and Google Cloud APIs are subject to the limits and quotas of the respective providers.
Common use cases
CloudFlow is especially convenient in situations where:
-
Complex approval processes involve multiple teams.
-
Cloud resources need to be dynamically spun up or down.
-
You are seeking to enhance FinOps adoption across the organization.
Below are some common applications of CloudFlow:
-
Resource scheduling
-
Automated cloud resource tagging
-
FinOps process on autopilot
-
Execution of FinOps recommendations
-
Cost alert event handling
-
Scalable cloud governance
-
Cloud commitment management
Planning your CloudFlow
Working with DoiT CloudFlow typically involves the following stages:
-
Identify the purpose and requirements of the workflow, such as inputs, expected outputs, approval processes, and notifications.
-
Select a trigger to start the CloudFlow. For example, whether the CloudFlow runs on a schedule or is triggered manually.
-
Design the sequence of tasks in the CloudFlow. For example, whether the CloudFlow includes conditional logic, loops, or connections with external systems.
-
Define the actions for each task in the CloudFlow, such as whether a task interacts with external systems, checks conditions, or sends notifications. DoiT CloudFlow also allows you to verify the required permissions and perform a dry run test, if applicable.