Skip to main content

Commitment Orchestrator for RDS

Commitment Orchestrator for RDS helps you optimize your Amazon RDS (Relational Database Service) costs by automatically managing your Reserved Instance (RI) commitments. It analyzes your RDS usage patterns and recommends the most cost-effective combination of Reserved Instances.

Key Features​

  • Automated RI Management: Automatically purchases and exchanges RDS Reserved Instances based on your usage patterns
  • Multi-Account Support: Manages RDS commitments across all your AWS accounts from a single master account
  • Smart Coverage Optimization: Intelligently determines the optimal coverage percentage for your RDS instances
  • Flexible Instance Family Support: Supports various RDS instance families and database engines

Prerequisites​

Before setting up Commitment Orchestrator for RDS, ensure you have:

  1. A Harness account with CCM module enabled
  2. AWS master account with appropriate permissions

Steps to configure:​

Permissions For Visibility​

"ec2:DescribeReservedInstancesOfferings",
"ce:GetSavingsPlansUtilization",
"ce:GetReservationUtilization",
"ec2:DescribeInstanceTypeOfferings",
"ce:GetDimensionValues",
"ce:GetSavingsPlansUtilizationDetails",
"ec2:DescribeReservedInstances",
"ce:GetReservationCoverage",
"ce:GetSavingsPlansCoverage",
"savingsplans:DescribeSavingsPlans",
"organizations:DescribeOrganization"
"ce:GetCostAndUsage"

Permissions for Orchestration​

"ec2:PurchaseReservedInstancesOffering",
"ec2:GetReservedInstancesExchangeQuote",
"ec2:DescribeInstanceTypeOfferings",              
"ec2:AcceptReservedInstancesExchangeQuote",              
"ec2:DescribeReservedInstancesModifications",   
"ec2:ModifyReservedInstances",
"ce:GetCostAndUsage",
"savingsplans:DescribeSavingsPlansOfferings",
"savingsplans:CreateSavingsPlan"

Permissions for RDS​

"rds:PurchaseReservedDBInstancesOffering",
"rds:DescribeReservedDBInstancesOfferings",
"pricing:GetProducts"

Native User Approval​

With this feature, users can approve the recommendations generated by the orchestrator. This feature enhances the functionality of the orchestrator by enabling user actions such as approval or rejection of recommendations generated by the engine.

Supported actions:​

The Commitment Orchestrator supports six action states currently:

  • APPROVED: You can approve the recommendation, allowing the action to proceed.
  • REJECTED: You can choose to reject the recommendation, preventing the action from taking place.
  • APPROVAL_PENDING: The action is pending approval by the user. This is the default state for all recommendations and any pending actions will expire in 24 hours.
  • EXPIRED: The recommended action has expired.
  • ERROR: The approval process encounters an error.
  • COMPLETED: The approved recommendation has been successfully completed.

Action Center UI​

In the Action Center UI, you can:

  • View a list of all recommendations generated by the engine, categorized by day and recommendation type.
  • Approve or reject recommendations individually, in subsets, or all at once.
  • Perform actions on different master accounts and regions.
info

You can change and select the mode (either automatic approval or manual approval) during the setup flow.