rds

Last updated on Feb 26, 2026

---

Behind a Feature Flag

Commitment Orchestrator for RDS is currently behind a Feature Flag. Contact Harness Support to have the flag enabled for your account.

Before You Begin

To setup Commitment Orchestrator in Harness CCM, you need:

• Active CCM Connectors: You must have at least one active cloud connector set up for the cloud providers you want to categorize costs for: Set Up CCM Connectors.
• A master account with the right permissions to be added via AWS connector on which you want to enable orchestration. Select the services for which you want to enable orchestration (permissions can be limited to specific service).

Available permissions for RDS:

Action:
- 'ce:GetSavingsPlansCoverage'
- 'ce:GetReservationCoverage'
- 'ce:GetSavingsPlansUtilization'
- 'ce:GetDimensionValues'
- 'ce:GetReservationUtilization'
- 'ce:GetSavingsPlansUtilizationDetails'
- 'ce:GetCostAndUsage'
- 'organizations:ListAccounts'
- 'rds:DescribeReservedDBInstances'
- 'rds:DescribeReservedDBInstancesOfferings'
- 'rds:PurchaseReservedDBInstancesOffering'
'Resource: '*'

• For AWS RDS, only RI orchestration is supported

• Required Permissions (Read-Only): Your Harness user account must belong to a user group with the following role permissions:

Details

Required Read-Only Permissions

To enable visibility, in the master account connector, you need to add the following permissions.

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

And to enable actual orchestration, you need to add the following permissions.

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

For RDS additional permissions are required.

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

note

We have rolled out permissions for Elasticache as well. Available permissions for Elasticache:

Action:
- 'ce:GetSavingsPlansCoverage'
- 'ce:GetReservationCoverage'
- 'ce:GetSavingsPlansUtilization'
- 'ce:GetDimensionValues'
- 'ce:GetReservationUtilization'
- 'ce:GetSavingsPlansUtilizationDetails'
- 'ce:GetCostAndUsage'
- 'organizations:ListAccounts'
- 'elasticache:DescribeReservedCacheNodes'
- 'elasticache:DescribeReservedCacheNodesOfferings'
- 'elasticache:PurchaseReservedCacheNodesOffering'
Resource: '*'

---

Steps to configure:

• Go to Commitment Orchestrator > Setup Orchestrator.

Account and Service details

• Specify the cloud account and service (RDS) for which you want to enable orchestration. Currently, Commitment Orchestrator supports AWS Elastic Compute Cloud (EC2) and AWS Relational Database Service (RDS). Support for other cloud providers is in the works.

• Specify the Master Account Connector. You need to select the master account with the right permissions to be added via connector on which you want to enable orchestration. You can either select an existing connector for your master account or create one.

  Please note, even if "Commitment Orchestrator" is enabled in Connector Set Up for any other Account except for Master, it will not be visible in the connector list in Commitment Orchestrator Setup since Commitment Orchestrator requires Master Account connector.

Orchestrator Exclusions (Optional)

Commitment Orchestrator provides you with an option to exclude Accounts, Regions and Instances from the orchestration.

• Account Exclusions: You can include or exclude specific accounts from the orchestration. The accounts marked as included will be considered for RI Orchestration.

• Region Exclusions: You can include or exclude specific regions from the orchestration. All the regions are shown with their coverage and compute spend for making an informed decision

• Instance Exclusions: You can include or exclude specific instances from the orchestration.

note

The purchases will happen only at master account level and thus will be in turn applicable for child accounts as well. The exclusion list will only be considered for the compute spend calulations and actual RI/SP may be used against the instances if they are part of child accounts.

Orchestration Preferences

• Target Coverage: The maximum percentage of your compute spend that you want covered by Reserved Instances. Any remaining spend will continue to run on On-Demand. The Commitment Orchestrator automatically adjusts coverage levels based on evolving usage patterns.

• Orchestration Mode: Select how the orchestrator executes recommended commitment purchases:

  • Fully Automated: Commitment purchases are executed automatically without requiring manual approval.

  • Manual: All commitment purchases require explicit manual approval before execution, giving you complete control over the process. All the recommendations are visible in the Actions tab on the dashboard.

Review & Complete

After all the set-up steps, you can review and finalise your inputs.

---

Overview Screen

The Orchestration Setup page displays a comprehensive list of all Master Accounts with Commitment Orchestrator connector permissions. From this page, users can enable new orchestration setups and view key metrics including Last 30 Days Coverage, Savings, and the current status of each Orchestrator configuration.

---

Disable Commitment Orchestrator

To disable a Commitment Orchestrator, navigate to Cloud Cost Management > Commitment > Orchestration Setup. Click on the three ellipses for the orchestrator you want to disable > Manage Orchestration Setup > Disable.

Disabling the Commitment Orchestrator will:

• Stop all automated commitment management for the selected orchestrator

• Remove existing orchestration configurations

  

---