Rules

Rules is a CCA feature that checks the resources used in the cloud, returning recommendations for optimizing the environment.

The rules are divided into two categories: Savings and Best Practices.

How to get to Rules:

1. In the CCA side feature menu, select Rules.

1. Filters

On the home screen it possible to search for available rules:

And filter by categories:

1. Report

When you click on “Download report”, a .csv file is downloaded with details of all the rules.

1. Rules

The CCA Rules are a set of recommendations based on the services available by the provider, and are divided into the two categories mentioned above.

For each rule, it is possible to view some information:

• Monitored Accounts: Lists the number of accounts being monitored for this recommendation.

• Total Resources Found: Lists the number of resources that apply to the rule.

• Total estimated savings: Estimated cost of savings with implementation of the recommendations.

Clicking on the rule name in blue opens a detailed breakdown of the rule, showing the following information:

• Monitored accounts

• Non-compliance resources

• Total ignored resources found

• Ignored resources cost

• Total estimated savings

The system also allows you to filter by Account ID, Resource ID, or Region, as highlighted below:

Clicking on the option “Download report”, a .csv file is downloaded with details only for the selected rule.

Further down, the system presents some action options:

• By clicking the ignore icon "" you can ignore the recommendation for that selected resource. The system will display a screen to you explain the reason why you want to ignore the resource.

By describing the reason and confirming the action, clicking the checkbox, the system will enable the button to complete the action:

• In the icon next to " you can view details about the chosen resource such as resource information and Meta Data:

1. Rule settings

By clicking on the gear "", as highlighted below:

The system opens the rule configuration, where you can search for the customization you want to view.

By clicking on the "" key corresponding to the customization, it is possible to open the rule customizations, allowing you to disable the rule chosen in “Status”.

Default Settings:

In default setting, it is possible to have the configuration specified for each resource as:

• Non-compliance after: Number of days after which the resource begins to be considered non-compliant. Example: Infrequent users: after 15 days, it is considered non-compliant.

• Regions: The regions that will be listed are the regions that are being monitored.

By clicking the Edit option, you can configure the acceptable period for the resource to be considered out of compliance.

The system will prompt you to fill in the following fields:

• Filter period operator: Select from the available options

  • Less than: When you want the number of days for the resource to be considered out of compliance to be less than the specified number.

  • Greater than: When you want the number of days for the resource to be considered out of compliance to be greater than the specified number.

• Filter period days: Specify the number of days for the rule to be considered out of compliance.

By clicking the save button, the system will complete the rule compliance customization.

It is possible to add new customizations to the rule.

Clicking Add opens the customization screen, where you will need to fill in the following information:

• Filter kind: Select between the two existing filter types

  • Filter only the resources that match the filter

  • Filter only the resources that do not match the filter

• Filter key: Enter the filter key that matches the tag

• Enter the filter value: Enter the value you want to return in the filter

After entering the desired customizations, just click save, and the customization will be added to the selected rule.

Rules of Savings

1. Idle Compute Instances: Identify compute instances that are not being used. These instances may be generating unnecessary costs.

2. Bucket Without Enabled Multipart Upload Exclusion Policy: Identifies buckets without enabled multipart upload exclusion policies, which may lead to inefficient storage usage and increased costs in Oracle Cloud Infrastructure.

3. Disk Detached: Identifies persistent disks on Oracle Cloud Infrastructure that are not currently attached to any virtual machine and have remained unused for a configurable number of days. These disks may be incurring storage costs without providing operational value.

4. Bucket Without Active Infrequent Access Policy: Identifies buckets without active infrequent access policies, which can lead to inefficient storage usage and increased costs in Oracle Cloud Infrastructure.

Best Practice Rules

1. Enable Monitoring on Compute Instances: Identify compute instances that have the compute instance monitoring agent disabled. This prevents resource utilization metrics such as CPU and memory from being tracked.