Skip to main content
OpenOps integrates with CloudFix to automate the retrieval and management of AWS cost optimization recommendations and the execution of their fixes.

​
Actions

OpenOps provides six actions for interacting with CloudFix: All CloudFix actions are based on the CloudFix API and require configuring a CloudFix connection with the CloudFix API URL and an API token. API tokens are created in CloudFix under Settings > API Tokens with a Reader, Resource Manager, or Runbook Manager role. The following sections describe the six actions available in the CloudFix block.

​
Get Report

Retrieves the detailed report for a specific recommendation:
  • Recommendation ID: The ID of the recommendation to get a report for

​
Get Recommendations

Retrieves recommendations from CloudFix with filtering options:
  • Status filter: Optional list of statuses: Suggested, Scheduled, Failed, Completed, Rejected, In Progress, Ready, No Longer Applicable, Resource Deleted, Resource Fixed, or Manually Fixed
  • Sort by: Scheduled At (default), Updated At, Annual Savings, or Annual Cost
  • Sort order: Descending (default) or Ascending
  • Include parameters: Whether to include recommendation parameters in the response
  • Finder fixer ID: Optional ID of a finder fixer to filter by
  • Page number: Page number for pagination, starting from 1 (defaults to 1)
  • Page limit: Maximum number of recommendations per page (defaults to 200)

​
Get Recommendations Summary

Retrieves a summary of recommendations. This action has no parameters.

​
Postpone Recommendations

Postpones recommendations until a specified date:
  • Recommendation IDs: Array of recommendation IDs to postpone
  • Postpone until: Date and time until which to postpone the recommendations, in ISO format
  • Reason: Optional reason for postponing

​
Create Change Requests

Creates change requests from recommendations so that CloudFix can execute the fixes:
  • Recommendation IDs: Array of recommendation IDs to create change requests for
  • Execute on schedule: Whether to execute the change requests on schedule

​
Custom API Call

Allows making arbitrary calls to any CloudFix API endpoint:
  • URL: Dynamic endpoint selection
  • Method: GET, POST, PATCH, PUT, DELETE, or HEAD
  • Headers: Optional (authorization auto-injected)
  • Query Parameters: Optional
  • Body: Optional JSON payload

​
Designing a workflow

A typical CloudFix workflow starts by collecting recommendations using the Get Recommendations action, then routes each one with a Condition step, for example by finder fixer ID: recommendations that need manual work become Jira issues that include the detailed report from the Get Report action, while the rest go to the resource owner for approval in Slack. Once approved, the Create Change Requests action hands the recommendation to CloudFix as a change request, and Postpone Recommendations delays the ones the owner snoozes. For the patterns behind owner mapping, approval requests, and decision tracking, see Designing Workflows with FinOps Platforms.