Account

The instance's parent environment. This corresponds to the AWS Linked Account.

Environment

The instance's parent account. This corresponds to the AWS Payer Account.

Cluster

The cluster/availability zone that corresponds to a geographic region.

System

The system name is a hyperlink that takes you to the Analysis Details page. You can access the Metrics Viewer or the Catalog Map from this page.

System ID

A unique key assigned by the public cloud vendors to identify this instance.

Overall Status

Identifies the overall status of the optimization results based on Optimization Type and potential $ Savings/Month :

Optimization Type

The recommended action for this instance. See Optimization Type Descriptions and Color-Coding for a description of each recommendation.

Recommendation Reason/Observations

The reason for the Optimization Type recommendation. Densify also provides any relevant details related to the recommendation.

Current Instance Type

Based on the data collected, the current instance type is listed.

Current Purchasing Strategy

The current purchasing strategy discovered through data collection.

Possible purchasing strategy values are:

• On-Demand—The on-demand price, with 0% RI coverage;
• Reserved—The reserved instance price, for 100% RI coverage;
• Partially Reserved—This current instance has partial reserved instance coverage (between 0% and 100%);
• "-" —no purchasing strategy is provided for terminate recommendations.

Recommended Instance Type

Based on optimization analysis, the recommended catalog instance type is listed.

Current RI Expiry Date

If Understanding the Instance Optimization Details for RDS = "Yes", then the expiry date of the reserved instance, which is currently providing coverage for this instance, is displayed.

Note: The RI expiry date is not displayed for an instance with Optimization Type = " Just Right" or "Terminate" .

Predicted Uptime (%)

When using pay-per-use pricing models, we need to know the amount of time each instance has been running to accurately estimate future costs.

The predicted uptime (%) for a cloud instance or container, is based on the percentage of hours CPU utilization data is present in the historical interval, as specified in the policy settings for the entity. For Auto Scaling groups and VM Scale Sets and Individual child instances are not taken into account.

Predicted uptime %, for new instances or containers, that started mid-way through the historical interval, is calculated from the time/date that the instance was started as opposed to the beginning of the interval, resulting in more accurate predictions for future usage.

For example, the uptime is the number of hours that have "CPU Utilization in mcores", and the range is the lesser of when the container was discovered, or the range defined in the policy. Looking at a specific container that was discovered on Jan 5th 2024, that has workload of 42 hours since that date, then the uptime % is 42 hrs/(13 days x 24 hrs/day) = 13.4%. This is the value shown in this column.

Click on the Predicted Uptime Details tab to review the uptime details for the selected instance.

Current Estimated Cost ($)

The current estimated per instance cost is determined by multiplying the on-demand, monthly price of the current instance type by predicted uptime %. i.e. current per instance list price (monthly)* predicted uptime %

See FAQs for examples of how the cost s are caculated.

Recommended Estimated Cost ($)

Recommended estimated cost is calculated based on multiplying the on-demand price of the recommended instance type by the uptime.

This column is hidden by default. You can enable it for display, as required. See Data Controls, above.

$ Savings/Month

The estimated current and recommended instance cost is used to calculate savings per month (i.e. current estimated cost - recommended estimated cost).

Effort

[Moderate|Low|Very Low|None]

This column describes the effort required to investigate and implement the Densify recommendations. Effort for each instance is calculated by rule-driven analytics based on factors (such as instance family change, storage change, data quality checks, feature changes, etc.) that can be configured in the policy settings and rule set which captures best practices.

Click on the Effort Details tab to view the factors that contribute to the effort level. See Reviewing the Workload Charts and Additional Details Tabs, below.

Implementation Method

[Manual|Self-Optimizing|-]

Specifies whether the instance with the recommended Optimization Type is configured for Self-Optimizing or Manual actioning.

The implementation method value is derived from the Self-Optimizing Automation Setup policy or from an instance Self-Optimizing Automation override, which takes precedence over the policy.

To make an instance Self-Optimizing Automation override, see Understanding the Instance Optimization Details Report. The updated implementation method value is displayed in this column after Densify analysis and the reporting database tables have been updated (i.e. after an RDB populate).

See Approving Cloud Recommendations for more information on the implementation method in the Self-Optimizing Automation workflow.

Current vCPUs

The current value for CPU allocation.

Recommended vCPUs

The recommended value for CPU allocation.

Current CPU Benchmark

The current CPU benchmark.

This column is hidden by default. You can enable it for display, as required. See Data Controls, above.

Recommended CPU Benchmark

The recommended CPU benchmark.

This column is hidden by default. You can enable it for display, as required. See Data Controls, above.

Current Memory Allocation (GB)

The current value for memory allocation.

Recommended Memory Allocation (GB)

The recommended value for memory allocation.

%CPU Usage (High)

The percentage of highest CPU workload.

%CPU Usage (Low)

The percentage of lowest CPU workload.

Active Memory Usage (%)

The percentage of active memory utilization.

Memory Usage (%)

The percentage of memory utilization.

OS

The operating system running on the instance.

Ideal CPU Allocation

The minimum CPU allocation required to not violate the policy high limits on the recommended instance.

Ideal Memory Allocation

The minimum memory allocation required to not violate the policy high limits on the recommended instance.

CPU Allocation Efficiency (%)

The allocation CPU efficiency (i.e. ideal allocation / recommended allocation) is measured in percent and shows the amount of CPU resources truly require by the workload.

Memory Allocation Efficiency (%)

The allocation memory efficiency (i.e. ideal allocation / recommended allocation) is measured in percent and shows the amount of memory resources truly require by the workload.

Instance Type Updated On

A value in this column indicates the instance type has been changed recently.

The workload for this instance, on which the recommendation is based, includes only the days of data from the indicated date to the current date. All historical data for this instance, collected prior to the indicated date is not included in the analysis. Previous data has been excluded because it was based on the previous instance type.

A blank cell indicates the current instance type has not changed and all available workload data within the range, defined by the policy, has been used to generate the recommendation.

Contact [email protected] to enable this feature. See Relearning Workload Patterns for more details.

Summary Total

On the top-right of the tabular report, the total number of Services and Savings/Month for implementing the recommendations are displayed.

The total number of instances displayed is a total of all the instances in the optimization instance type group. This number corresponds to the number in the Count column of the parent optimization opportunity tabular report.

The savings per month is a sum of all the monthly savings for each instance listed and can be negative if there are upsize or upsize to an optimal family recommendation.

Just Right

This instance is optimally sized for the workload.

This instance should be upsized to a more optimal instance family. This will improve the workload's performance and reduce risk.

If the workload can be moved to larger instance in a different family and still reduce cost, this then becomes a Modernize recommendation. e.g. t2.medium-Linux to m3.medium-Linux

This instance should be upsized to an instance within the same instance family. The hosted workload needs an instance with more CPU and\or memory resources.

e.g. r3.large to r4.xlarge, both are in the "Memory Optimized r" instance family.

This recommendation applies to ASGs only and indicates the ASG needs increase compute capacity by adjusting the maximum group size.

It may be more cost effective to use a larger instance for this ASG.

This instance should be terminated, as it is idle. An instance is determined to be idle if it has very low CPU utilization, network and disk I/O over an extended period of time. This will save you money.

This instance should be downsized to an instance belonging to an instance family that more closely suits your workload's utilization.

When you downsize, CPU and\or memory will be decreased to better suit your workloads. Utilization will improve with no impact on performance. This will save you money. e.g. d2.medium-Linux to m4.medium-Linux

This instance should be downsized to an instance within the same instance family.

As indicated above, CPU and\or memory will be decreased to better suit your workloads. Utilization will improve with no impact on performance. This will save you money. e.g. m3.large-Linux to m3.small-Linux

ThisAuto Scaling group or VM Scale Set should be downscaled to decrease the compute capacity by adjusting the minimum group size.

This instance should be modernized to an instance belonging to a more optimal instance family. The cost of the new instance type will be less than the existing cost.

Allocated resources are not being removed and moving to an instance with more current hardware, you may also benefit potential utilization and performance improvements.

When you modernize, you will not decrease performance but will decrease cost.

This instance should be modernized to an instance within the same instance family. The cost of the new instance type will be less than the existing cost and as indicated above you may also get utilization and performance improvements.

For example, moving to a new generation of the same instance family (e.g. m3.large to m4.large).