Skip to main content
OpenOps supports the big three cloud providers: AWS, Azure, and Google Cloud. Actions in each cloud provider’s block are implemented using the respective provider’s official APIs. You can create workflows across cloud providers if you’re using more than one of them.

​
AWS

AWS actions use the latest available AWS CLI at the time of OpenOps installation. The full list of AWS actions is as follows:
  • Build ARN: Build ARN (Amazon Resource Name) from the given parameters
  • Parse ARN: Parse information from a given ARN (Amazon Resource Name)
  • Get Price from Price Catalog: Query AWS Pricing API to get the price of a service
  • Get Account IDs: Gets the account ids for the accounts under the selected connection
  • EBS Get Volumes: Get EBS volumes that match the given criteria
  • EBS Modify Volume: Modify the given EBS volume
  • EBS Delete Volume: Delete the given EBS Volume
  • EBS Get Snapshots: Get EBS snapshots that match the given criteria
  • EBS Create Snapshot: Create a snapshot of the provided EBS Volume
  • EBS Delete Snapshot: Delete the provided EBS Snapshot
  • EC2 Get Instances: EC2 Get Instances that match the given criteria
  • EC2 Modify Instance: Modify the given EC2 instance
  • EC2 Start Instance: EC2 start a given instance
  • EC2 Stop Instance: EC2 stop a given instance
  • EC2 Terminate Instances: Terminate the provided EC2 instances
  • RDS Get Instances: Get RDS instances that match the given criteria
  • RDS Delete Instance: Delete the provided RDS Instance
  • RDS Get Snapshots: Get RDS snapshots that match the given criteria
  • RDS Create Snapshot: Create a snapshot of the provided RDS instance
  • RDS Delete Snapshot: Delete the provided RDS Snapshot
  • Tag Resources: Add tags to the given resources
  • Generate Runbook Execution Link: Generate an AWS Console link to execute an SSM Automation Runbook
  • AWS CLI: Execute AWS CLI command
Here’s an example of a step in an AWS workflow that retrieves EBS volumes. For each volume, the workflow then proceeds to determine its unit cost: A sample AWS workflow See also:

​
Azure

Azure actions use Azure CLI version 2.74.0, with the following extensions preinstalled:
  • reservation
  • resource-graph
  • costmanagement
  • billing-benefits
  • quotas
  • ssh
Dynamic extension installation is allowed. This means that if you use the Azure CLI action to run a command that is not available in the preinstalled extensions, the action installs the required extension automatically. The full list of Azure actions is as follows:
  • Azure CLI: Execute Azure CLI command
  • Get Advisor Cost Recommendations: Get Azure Advisor Cost Recommendations
  • Azure Resource Graph Query: Query Azure Resource Graph using KQL to retrieve resources across multiple subscriptions
  • Custom Azure API Call: Make a custom REST API call to Azure.
Here’s an example of a step in an Azure workflow that fetches Azure Advisor cost recommendations for a specific resource group: A sample Azure workflow See also:

​
Google Cloud

Google Cloud actions use Google Cloud SDK version 516.0.0, with beta versions of CLI commands enabled. The full list of Google Cloud actions is as follows:
  • Google Cloud CLI: Execute a Google Cloud CLI command
  • Get Recommendations: Fetch the recommendations for the selected recommenders
  • Run BigQuery SQL Query: Run a SQL query on BigQuery and return the results.
  • Custom Google Cloud API Call: Make a custom REST API call to Google Cloud.
Here’s an example of a step in a Google Cloud workflow that retrieves Google Cloud recommendations for a specific combination of a project and a recommender. The workflow then proceeds to analyze and act on each recommendation: A sample Google Cloud workflow See also:

​
Automating across multiple cloud providers

If you’re using multiple cloud providers, you can structure your workflows so that OpenOps provides automations across all of them. You can either combine actions related to multiple cloud providers in one workflow or have separate provider-specific workflows save findings to a central location, such as an OpenOps table. Using OpenOps tables, you can aggregate findings and recommendations across cloud providers into a single table, where you can track approval status or group potential savings by business unit. You can see how it works by using the three sample workflows for AWS, Azure and Google Cloud that your OpenOps instance suggests in the Overview view: These workflows collect recommendations from AWS Compute Optimizer, Azure Advisor, and Google Cloud Recommenders, respectively, and then log the recommendations to a single preconfigured Opportunities table. If you’re using multiple clouds, you can structure your workflows in a similar way.