docs.vmware.com Open in urlscan Pro
2a02:26f0:6c00:196::2ef  Public Scan

Form analysis
0 forms found in the DOM

Text Content

Your session is about to expire Continue session
Your session has expired. Please login to VMware Docs again.
Hello,
Docs

All
Book

Filter by: All
All
Book

en
EnglishDeutschFrançaisEspañol日本語한국어简体中文繁體中文РусскийItalianoNederlandsPortuguês
BrasileiroDanskČeštinaPolskieSvenskaTürkçePortuguês de PortugalΕλληνικά
Tour
VMware Pages
Communities Support Downloads
MyLibrary
Login Logout
All
Book
Filter by:
All
Book

VMware Docs times
 * Hello,
 * Home

 * LANGUAGES
   
   * English
   * Deutsch
   * Français
   * Español
   * 日本語
   * 한국어
   * 简体中文
   * 繁體中文
   * Русский
   * Italiano
   * Nederlands
   * Português Brasileiro
   * Dansk
   * Čeština
   * Polskie
   * Svenska
   * Türkçe
   * Português de Portugal
   * Ελληνικά

 * VMWARE PAGES
   
   * Communities
   * Support
   * Downloads
 * MyLibrary
 * Login
 * Logout

 * VMware Aria Cost
 * Product Documentation
 * Technical Articles
 * Blogs
 * FAQ


VMware Aria Cost
Product Documentation Technical Articles Blogs FAQ
Expand All Collapse All
VMware Aria Cost Product Documentation
 * Working with Reports and Recommendations
   Working with Reports and Recommendations
   * FlexReports
     FlexReports
   * Custom Line Items
     Custom Line Items
   * Cost Reports
     Cost Reports
   * Usage Reports
     Usage Reports
   * Security Reports
     Security Reports
   * Asset Reports
     Asset Reports
   * AWS Reservation Management
     AWS Reservation Management
   * Azure Reservation Management
     Azure Reservation Management
   * AWS Rightsizing - New
     AWS Rightsizing - New
   * AWS Rightsizing - Classic
     AWS Rightsizing - Classic
   * Azure Rightsizing - New
     Azure Rightsizing - New
   * Azure Rightsizing - Classic
     Azure Rightsizing - Classic
   * GCP Rightsizing
     GCP Rightsizing
   * Data Center Rightsizing
     Data Center Rightsizing
   * Data Center Migration
     Data Center Migration
   * Savings Plan Management
     Savings Plan Management
   * Container Cost Reports
     Container Cost Reports
   * Container Usage Reports
     Container Usage Reports

Docs / VMware Aria Cost / Working with Reports and Recommendations


NEW AWS RIGHTSIZING


Add to Library
Remove from Library
RSS
Download PDF
Feedback
Edit
Review
Share
Twitter Facebook LinkedIn 微博

Updated on   06/01/2023
Selected product version:



NEW AWS RIGHTSIZING


AWS RIGHTSIZING

The new Rightsizing tool can help you use your EC2 and RDS instances more
efficiently and save money. Using Rightsizing, you can:

 * Analyze the workload patterns of your instances
 * Apply custom efficiency targets to generate recommendations for optimal
   instance sizes and to meet different application and enterprise requirements
 * Gain clear insight into your total cost saving opportunities
 * Fine-tune instance sizing based on up to two additional recommendations

Unlike the legacy Rightsizing tool, you can change efficiency targets and
instantly view updated recommendations to ensure the best fit.

To access Rightsizing, go to Recommendations > Rightsizing > Rightsizing (New).

Note- - Source instances must be active for at least 48 hours in the CloudHealth
Platform to begin generating rightsizing recommendations. - Currently, the tool
is available for the AWS and Azure cloud.


USING THE RIGHTSIZING DASHBOARD

The Rightsizing dashboard provides information about the efficiency of your
instances, displays the status of each instance and provides recommendations for
each instance.

The Efficiency Summary provides the following information:

 * Current Recommendation: the total number of recommendations available in the
   dashboard.
 * Current Monthly Price: the sum of the monthly cost for all instances. VMware
   Aria Cost considers actual usage hours to date for the whole month to
   calculate the monthly price for each current instance using on-demand hourly
   rates for the current instance type.
 * Projected Monthly Price: the monthly cost when the best fit is applied to all
   instances. If there are no recommendations, then the current instance’s
   hourly cost is used. VMware Aria Cost considers the same number of usage
   hours as the current instance and calculates the monthly price for all
   recommended instances using on-demand hourly rates for the recommended
   instance type.
 * Projected Monthly Savings: the difference between Projected Monthly Cost and
   Current Monthly Cost. This is calculated by subtracting the Projected Monthly
   Savings from the Current Monthly Cost.

You can set an efficiency target and date range to help generate targeted
recommendations. For more information about creating and using efficiency
targets, see Efficiency Targets.

You can also choose to include or exclude burstable instances in your
recommendations. Burstable instances guarantee a baseline level of CPU
performance but can also exceed the baseline level of performance to sustain a
high level of CPU performance as needed.

Click All Filters to view more filter options for your recommendations, such
availability zone, billing account, and perspective.

Click Export to download a CSV file of the recommendations.

> Using Rightsizing APIs, you can programmatically create efficiency targets and
> consume rightsizing recommendations. For more details, visit the VMware Aria
> Cost Graphql API guide.


UNDERSTAND RECOMMENDATIONS

The Recommendations table shows all instances that fit the selected filters and
that have a recommendation. You can also enable Show all recommendations to view
instances that do not currently have a recommendation.

The dashboard displays the number of instances with recommendations and their
fit:

 * Good fit: the instance meets all efficiency targets.
 * Under target: the instance is underutilized and does not meet all efficiency
   targets. VMware Aria Cost provides a recommendation to optimize the instance.
 * Over target: the instance is overutilized and exceeds one or more efficiency
   targets.
 * Undetermined fit: one or more of the metrics is above target, but one or more
   of another metric is below target, so the fit could not be determined.
 * Not enough data: there was no data available for a metric for the selected
   time period, so the fit could not be determined.

The Recommendations table also displays the following information:

 * Current Price: The current cost of the instance.
 * Recommended Price: The estimated cost of the instance after applying the most
   cost-effective recommendation.
 * Estimated Savings: The estimated monthly savings after applying the most
   cost-effective recommendation.

> Note: The prices for all instances are calculated using the list or on-demand
> prices with no discounts applied, considering the actual usage hours of
> instances.

TYPES OF RECOMMENDATIONS

There are two types of recommendations:

 * Resize: Identifies the right size candidate instance that can handle the
   usage for the current instance. Resizing recommendations can be made across
   different instance families.
   * For example, if you have an m4.xlarge instance with very low CPU and Memory
     utilization, VMware Aria Cost may recommend that you downgrade to the lower
     cost c4.large instance. VMware Aria Cost may not recommend the m4.large,
     even if it is in the same family, because it is more expensive than the
     c4.large and has memory capacity that the instance may not need.
 * Terminate: Identifies instances that have less than one percent memory and
   CPU utilization, and can likely be terminated.

If VMware Aria Cost is unable to make a recommendation for an instance, the
instance is hidden from the dashboard. You can enable Show all recommendations
to view instances that do not currently have a recommendation.

Note: No recommendations are generated in the following situations:

 * If the instance is a host tenant
 * Accelerated computing or bare metal instances
 * If the instance has no options matching the efficiency target requirements
 * If metric data is unavailable for all metrics in the selected efficiency
   target


VIEW RECOMMENDATIONS

Click an instance name to view recommendation options and metrics for that
instance. The instance details page shows monthly cost for the instance, the
primary recommendation for the instance, and compares up to two additional
recommendation options.

The Instance Metrics charts show current performance metrics and the target
efficiency range. You can use these charts to determine how your current usage
compares to the target metrics.

VIEW RECOMMENDATIONS BY ACCOUNT OR PERSPECTIVE

The Rightsizing tool also gives you an option to view recommendations grouped by
account or perspective.

In the Group By dropdown, select Account and click Update. You will see all the
recommendations grouped by account. Expand an account name to view all the
instances that fall into that specific account. Click the instance name to know
the recommendation details of the selected instance.



For grouping by Perspective, you need to select a perspective group for which
you want to view the recommendations. Once you click Update, you will see all
the recommendations grouped by perspectives. Expand a perspective name, and all
the instances associated with that specific perspective appear. Further, you can
explore recommendations details by clicking the instance name.




KUBERNETES RIGHTSIZING – NEW

The new Rightsizing tool can help you use your Kubernetes Containers more
efficiently and save money. Using Rightsizing, you can:

 * Analyze the workload patterns of your containers
 * Apply custom efficiency targets to generate recommendations for optimal
   container sizes and to meet different application and enterprise requirements

Unlike the legacy Rightsizing tool, you can change efficiency targets and
instantly view updated recommendations to ensure the best fit.

To access our new Kubernetes Rightsizing tool, go to Recommendations >
Rightsizing > Rightsizing (New).




USING THE RIGHTSIZING DASHBOARD

The Rightsizing dashboard provides information about the efficiency of your
containers, displays the status of each and provides recommendations.

The Efficiency Summary provides the following information:

 * Current CPU: the total requested compute capacity across all your containers
   (in CPU cores)
 * Recommended CPU: the total recommended compute capacity across all your
   containers (in CPU cores)
 * Current Memory: the total requested memory capacity across all your
   containers (in GB)
 * Recommended Memory: the total recommended memory capacity across all your
   containers (in GB)
 * No Change: total number of containers that do not need any change and thus,
   have no recommendations.
 * Resize: total number of containers that need to resize their CPU and/or
   Memory requests and thus, have recommendations.

You can set an efficiency target and date range to help generate targeted
recommendations. For more information about creating and using efficiency
targets, see Efficiency Targets.

Click All Filters to view more filter options for your recommendations, such as
clusters, namespaces and workload types.

Click Export to download a CSV file of the recommendations.


UNDERSTAND RECOMMENDATIONS

The Recommendations table shows all containers that fit the selected filters and
that have a recommendation. You can also enable Show all recommendations to view
containers that do not currently have a recommendation.

The dashboard displays the number of containers with recommendations and their
fit:

 * Good fit: the container meets all efficiency targets.
 * Under target: the container is underutilized and does not meet all efficiency
   targets. VMware Aria Cost provides a recommendation to optimize the
   container.
 * Over target: the container is overutilized and exceeds one or more efficiency
   targets.
 * Undetermined fit: one or more of the metrics is above target, but one or more
   of another metric is below target, so the fit could not be determined.
 * Not enough data: there was no data available for a metric for the selected
   time period, so the fit could not be determined.

The Recommendations table also displays the following information:

 * CPU Requests: the requested compute capacity for a container.
 * Memory Requests: the requested memory capacity for a container.
 * Recommended CPU Requests: the recommended compute capacity for a container
   based on applied efficiency target.
 * Recommended Memory Requests: the recommended memory capacity for a container
   based on applied efficiency target.


RESIZE RECOMMENDATIONS

Identifies the right amount of compute and/or memory requests that can handle
the usage for the current container.

If VMware Aria Cost is unable to make a recommendation for a container, it is
hidden from the dashboard. You can enable Show all recommendations to view
containers that do not currently have a recommendation.

Note:No recommendations are generated in the following situations

 * If the container has no options matching the efficiency target requirements
 * If metric data is unavailable for all metrics in the selected efficiency
   target


VIEW RECOMMENDATIONS

Click a container name to view recommendation options and metrics for that
container. The details page shows current container’s compute and memory
requests, and the recommended requests for both.

The Metrics charts show current performance metrics and the target efficiency
range. You can use these charts to determine how your current usage compares to
the target metrics.

VIEW RECOMMENDATIONS BY NAMESPACE OR CLUSTER

The Rightsizing tool also gives you an option to view recommendations grouped by
Namespace and Cluster.

In the Group By dropdown, select Namespace and click Update. You will see all
the recommendations grouped by namespaces. Expand a namespace name to view all
the containers that fall into that specific account. Click the container name to
know the recommendation details of the selected container.



Select the Cluster option from the dropdown to group recommendations by
clusters.



Note - Using Rightsizing APIs, you can programmatically create, update or delete
efficiency targets. For more details, visit the VMware Aria Cost Graphql guide.


EBS VOLUME RIGHTSIZING – NEW (BETA)



The new Rightsizing tool can help you use your EBS volumes more efficiently and
save money. Using Rightsizing, you can:

 * Analyze the workload patterns of your storage volumes
 * Apply custom efficiency targets to generate recommendations for optimal
   configuration of your volumes to meet different application and enterprise
   requirements
 * Gain clear insight into your total cost saving opportunities
 * Fine-tune volume types and/or provisioned IOPS/throughput based on up to two
   additional recommendations

Unlike the legacy Rightsizing tools, you can change efficiency targets and
instantly view updated recommendations to ensure the best fit.

To access our new EBS Rightsizing tool, go to Recommendations > Rightsizing >
Rightsizing (New).


USING THE RIGHTSIZING DASHBOARD

The Rightsizing dashboard provides information about the efficiency of your EBS
volumes, displays the status of each volume’s utilization and provides
recommendations.

The Efficiency Summary provides the following information:

 * Current Recommendation: the total number of recommendations available in the
   dashboard.
 * Current Monthly Price: the sum of the monthly cost for all volumes.
   CloudHealth considers actual usage hours (to date extrapolated for the whole
   month) to calculate the monthly price for each volume using storage, IOPS and
   throughput rates for the current volume types.
 * Projected Monthly Price: the monthly cost when the best fit is applied to all
   volumes. If there are no recommendations, then the current volume types’
   hourly cost is used. CloudHealth considers the same number of usage
   characteristics as the current EBS volume and calculates the monthly price
   for all recommended volumes using storage, IOPS and throughput rates for the
   recommended volume types.
 * Projected Monthly Savings: the difference between Projected Monthly Cost and
   Current Monthly Cost. This is calculated by subtracting the Projected Monthly
   Savings from the Current Monthly Cost.

You can set an efficiency target and date range to help generate targeted
recommendations. For more information about creating and using efficiency
targets, see Efficiency Targets.

Click All Filters to view more filter options for your recommendations, such as
billing account and sub account, volume types and availability zones.


UNDERSTAND RECOMMENDATIONS

The Recommendations table shows all EBS volumes that fit the selected filters
and that have a recommendation. You can also enable Show all recommendations to
view volumes that do not currently have a recommendation.

The dashboard displays the volume name, volume id, volume type, instance id,
volume metrics and their fit:

 * Good fit: the volume meets all efficiency targets.
 * Under target: the volume is underutilized and does not meet all efficiency
   targets. CloudHealth provides a recommendation to optimize the volume.
 * Over target: the volume is overutilized and exceeds one or more efficiency
   targets.
 * Undetermined fit: one or more of the metrics is above target, but one or more
   of another metric is below target, so the fit could not be determined.
 * Not enough data: there was no data available for a metric for the selected
   time period, so the fit could not be determined.

The Recommendations table also displays the following information:

 * Current Price: The current cost of the volume.
 * Recommended Price: The estimated cost of the volume after applying the most
   cost-effective recommendation.
 * Estimated Savings: The estimated monthly savings after applying the most
   cost-effective recommendation.


TYPES OF RECOMMENDATIONS

There are two types of recommendations:

 * Resize: Identifies the rightsize candidate volume type, provisioned IOPS,
   provisioned throughput that can handle the usage for the current volume.
   Resizing recommendations can be made across different volume types.
 * Terminate: Identifies volumes that are either severely underutilized as per
   the relevant metrics or are unattached, and can likely be terminated. Check
   the termination criteria for the AWS resources -
   * EBS Volume: ReadOps = 0 AND WriteOps = 0

If CloudHealth is unable to make a recommendation for a volume, it is hidden
from the dashboard. You can enable Show all recommendations to view volumes that
do not currently have a recommendation.

Note- No recommendations are generated in the following situations:

 * If the volume has no options matching the efficiency target requirements.
 * If metric data is unavailable for all metrics in the selected efficiency
   target


VIEW RECOMMENDATIONS

Click a volume name to view recommendation options and metrics for that volume.
The details page shows monthly cost for the volume, the primary recommendation
and provides up to two additional recommendation options.

The Metrics charts show current performance metrics and the target efficiency
range. You can use these charts to determine how your current usage compares to
the target metrics.


ELASTICACHE RIGHTSIZING – NEW (BETA)



The new Rightsizing tool can help you use your ElastiCache clusters more
efficiently and save money. Using Rightsizing, you can:

 * Analyze the workload patterns of your cache clusters
 * Apply custom efficiency targets to generate recommendations for optimal node
   sizes and to meet different application and enterprise requirements
 * Gain clear insight into your total cost saving opportunities
 * Fine-tune node sizing based on up to two additional recommendations

Unlike the legacy Rightsizing tools, you can change efficiency targets and
instantly view updated recommendations to ensure the best fit.

To access our new ElastiCache Rightsizing tool, go to Recommendations >
Rightsizing > Rightsizing (New).


USING THE RIGHTSIZING DASHBOARD

The Rightsizing dashboard provides information about the efficiency of your
Clusters, displays the status of each cluster’s utilization and provides
recommendations.

The Efficiency Summary provides the following information:

 * Current Recommendation: the total number of recommendations available in the
   dashboard.
 * Current Monthly Price: the sum of the monthly cost for all clusters.
   CloudHealth considers actual usage hours (to date extrapolated for the whole
   month) to calculate the monthly price for each cluster using on-demand hourly
   rates for the current node types.
 * Projected Monthly Price: the monthly cost when the best fit is applied to all
   clusters. If there are no recommendations, then the current node types’
   hourly cost is used. CloudHealth considers the same number of usage hours as
   the current cluster and calculates the monthly price for all recommended
   clusters using on-demand hourly rates for the recommended node types.
 * Projected Monthly Savings: the difference between Projected Monthly Cost and
   Current Monthly Cost. This is calculated by subtracting the Projected Monthly
   Savings from the Current Monthly Cost.

You can set an efficiency target and date range to help generate targeted
recommendations. For more information about creating and using efficiency
targets, see Efficiency Targets.

You can also choose to include or exclude burstable node types in your
recommendations. Burstable node types guarantee a baseline level of CPU
performance but can also exceed the baseline level of performance to sustain a
high level of CPU performance as needed.

Click All Filters to view more filter options for your recommendations, such as
billing account and sub account, perspective groups and region.


UNDERSTAND RECOMMENDATIONS

The Recommendations table shows all Elasticache clusters (redis and memcached)
that fit the selected filters and that have a recommendation. You can also
enable Show all recommendations to view clusters that do not currently have a
recommendation.

The dashboard displays the cluster name, account name, region, cache engine type
and version, node type, number of nodes, cluster metrics and their fit:

 * Good fit: the cluster meets all efficiency targets.
 * Under target: the cluster is underutilized and does not meet all efficiency
   targets. CloudHealth provides a recommendation to optimize the cluster.
 * Over target: the cluster is overutilized and exceeds one or more efficiency
   targets.
 * Undetermined fit: one or more of the metrics is above target, but one or more
   of another metric is below target, so the fit could not be determined.
 * Not enough data: there was no data available for a metric for the selected
   time period, so the fit could not be determined.

The Recommendations table also displays the following information:

 * Current Price: The current cost of the cluster.
 * Recommended Price: The estimated cost of the cluster after applying the most
   cost-effective recommendation.
 * Estimated Savings: The estimated monthly savings after applying the most
   cost-effective recommendation.

Note: The prices for all clusters are calculated using the list or on-demand
prices with no discounts applied, considering the actual usage hours.

Types of Recommendations

There are two types of recommendations:

 * Resize: Identifies the rightsize candidate node type that can handle the
   usage for the current cluster. Resizing recommendations can be made across
   different instance families.
 * Terminate: Identifies resources that are severely underutilized as per the
   relevant metrics, and can likely be terminated. Check the termination
   criteria for the AWS resources - -ElastiCache Cluster: Number of New
   Connections = 0 AND Maximum number of current connections <= 6

If CloudHealth is unable to make a recommendation for a cluster, it is hidden
from the dashboard. You can enable Show all recommendations to view clusters
that do not currently have a recommendation.

Note: No recommendations are generated in the following situations:

 * If the cluster has no options matching the efficiency target requirements.
 * If metric data is unavailable for all metrics in the selected efficiency
   target


VIEW RECOMMENDATIONS

Click a cluster name to view recommendation options and metrics for that
cluster. The details page shows monthly cost for the cluster, the primary
recommendation and provides up to two additional recommendation options.

The Metrics charts show current performance metrics and the target efficiency
range. You can use these charts to determine how your current usage compares to
the target metrics.


OPENSEARCH RIGHTSIZING – NEW

The new Rightsizing tool can help you use your OpenSearch domains more
efficiently and save money. Using Rightsizing, you can:

 * Analyze the workload patterns of your master and data nodes
 * Apply custom efficiency targets to generate recommendations for optimal node
   sizes and to meet different application and enterprise requirements
 * Gain clear insight into your total cost saving opportunities
 * Fine-tune node sizing based on up to two additional recommendations

Unlike the legacy Rightsizing tool, you can change efficiency targets and
instantly view updated recommendations to ensure the best fit.

To access our new OpenSearch Rightsizing tool, go to Recommendations >
Rightsizing > Rightsizing (New).




USING THE RIGHTSIZING DASHBOARD

The Rightsizing dashboard provides information about the efficiency of your
domains, displays the status of each set of master or data node and provides
recommendations.

The Efficiency Summary provides the following information:

 * Current Recommendation: the total number of recommendations available in the
   dashboard.
 * Current Monthly Price: the sum of the monthly cost for all domains. VMware
   Aria Cost considers actual usage hours (to date extrapolated for the whole
   month) to calculate the monthly price for each set of current master and data
   nodes using on-demand hourly rates for the current node types.
 * Projected Monthly Price: the monthly cost when the best fit is applied to all
   domains. If there are no recommendations, then the current node types’ hourly
   cost is used. VMware Aria Cost considers the same number of usage hours as
   the current domain and calculates the monthly price for all recommended
   domains using on-demand hourly rates for the recommended node types.
 * Projected Monthly Savings: the difference between Projected Monthly Cost and
   Current Monthly Cost. This is calculated by subtracting the Projected Monthly
   Savings from the Current Monthly Cost.

You can set an efficiency target and date range to help generate targeted
recommendations. For more information about creating and using efficiency
targets, see Efficiency Targets.

Click All Filters to view more filter options for your recommendations, such as
billing account and sub account, perspective groups and region.

Note - Using Rightsizing APIs, you can programmatically create efficiency
targets and consume rightsizing recommendations. For more details, visit the
VMware Aria Cost Graphql API guide.


UNDERSTAND RECOMMENDATIONS

The Recommendations table shows all sets of master and data nodes that fit the
selected filters and that have a recommendation. You can also enable Show all
recommendations to view domains that do not currently have a recommendation.

The dashboard displays the domain name, id, account name, node type, instance
type, number of instances, domain metrics and their fit:

 * Good fit: the domain meets all efficiency targets.
 * Under target: the domain is underutilized and does not meet all efficiency
   targets. VMware Aria Cost provides a recommendation to optimize the domain.
 * Over target: the domain is overutilized and exceeds one or more efficiency
   targets.
 * Undetermined fit: one or more of the metrics is above target, but one or more
   of another metric is below target, so the fit could not be determined.
 * Not enough data: there was no data available for a metric for the selected
   time period, so the fit could not be determined.

The Recommendations table also displays the following information:

 * Current Price: The current cost of the domain.
 * Recommended Price: The estimated cost of the domain after applying the most
   cost-effective recommendation.
 * Estimated Savings: The estimated monthly savings after applying the most
   cost-effective recommendation.

Note: The prices for all domains are calculated using the list or on-demand
prices with no discounts applied, considering the actual usage hours.

TYPES OF RECOMMENDATIONS

There are two types of recommendations:

 * Resize: Identifies the right size candidate node type that can handle the
   usage for the current domain. Resizing recommendations can be made across
   different instance families.
 * Terminate: Identifies resources that are severely underutilized as per the
   relevant metrics, and can likely be terminated. Check the termination
   criteria for the AWS resources -
   * OpenSearch domain: IndexRate = 0 AND SearchRate < 0.1

If VMware Aria Cost is unable to make a recommendation for a domain, it is
hidden from the dashboard. You can enable Show all recommendations to view
domains that do not currently have a recommendation.

Note: No recommendations are generated in the following situations

 * If the master or data node domain has no options matching the efficiency
   target requirements.
 * If metric data is unavailable for all metrics in the selected efficiency
   target

VIEW RECOMMENDATIONS

Click a domain name to view recommendation options and metrics for that domain.
The details page shows monthly cost for the domain, the primary recommendation
and provides up to two additional recommendation options.

The Metrics charts show current performance metrics and the target efficiency
range. You can use these charts to determine how your current usage compares to
the target metrics.

VIEW RECOMMENDATIONS BY ACCOUNT, PERSPECTIVE OR DOMAIN

The Rightsizing tool also gives you an option to view recommendations grouped by
Account, Perspective or Domain.

In the Group By dropdown, select Domain and click Update. You will see all the
recommendations grouped by Domain. Expand a domain name to view all the clusters
that fall into that specific account domain. Click the cluster name to know the
recommendation details of the selected cluster.




HOW THE NEW RIGHTSIZING TOOL MAKES EC2 RIGHTSIZING INSTANCE RECOMMENDATIONS

The following is an overview of how the rightsizing tool makes EC2 rightsizing
recommendations.


STEP 1: METRICS FOR CURRENT INSTANCE

VMware Aria Cost retrieves the following metrics for the selected date range to
determine how current instances are being utilized:

 * CPU: CPU utilization scaled to vCPUs
 * Memory: memory utilization scaled to total available memory
 * Disk: disk utilization scaled to total attached storage


STEP 2: CANDIDATE LIST

The metric ranges for the applied efficiency target are then used to build a
list of instance types that are potential candidates for recommendations based
on the following criteria:

 * Only the instance attributes included in the applied efficiency target are
   considered.
   * For example, if the applied efficiency target has ranges for CPU and Disk,
     the candidates for recommendations will be listed based on the evaluation
     of CPU and Disk metrics only. Any other available metrics are ignored.
 * The current utilization percentage for each metric is applied to instance
   types to calculate future utilization percentage assuming the same levels of
   usage.
 * The future utilization percentage of the instance type falls closer to the
   ranges specified in the applied efficiency target

If metrics for any of the current instance’s attributes are unavailable, VMware
Aria Cost ensures that the candidates have at least as much or more capacity as
that of the current instance.

Baseline performance thresholds for burstable instances are used to evaluate the
current and future utilization percentage when the burstable instance is both a
current instance and a candidate for recommendations.


STEP 3: COMPARISON AND RECOMMENDATION

Candidates are removed if the source instance and candidate instance:

 * Have different architecture
 * Have different storage types
 * Are from different regions

Note: If Recommend Burstables is checked, all burstable instance types are
included in the candidate list.

The remaining candidates are sorted from least expensive to most expensive. The
least expensive candidate is the primary recommended instance type and is marked
as the Best Fit. Two additional instance types from the sorted candidate list
are shown as alternative recommendations.


HOW THE NEW RIGHTSIZING TOOL MAKES RDS INSTANCE RIGHTSIZING RECOMMENDATIONS

The following is an overview of how the rightsizing tool makes RDS rightsizing
recommendations.

Note: The Rightsizing tool does not provide recommendations for EBS volumes
attached to RDS instances.


STEP 1: METRICS FOR CURRENT INSTANCE

VMware Aria Cost retrieves the following metrics for the selected date range to
determine how current instances are being utilized:

 * CPU: CPU utilization scaled to vCPUs
 * Freeable Memory: memory utilization scaled to total available memory


STEP 2: CANDIDATE LIST

The metric ranges for the applied efficiency target are then used to build a
list of instance types that are potential candidates for recommendations based
on the following criteria:

 * Only the instance attributes included in the applied efficiency target are
   considered.
   * For example, if the applied efficiency target has ranges for CPU, the
     candidates for recommendations will be listed based on the evaluation of
     CPU metrics only. Any other available metrics are ignored.
 * The current utilization percentage for each metric is applied to instance
   types to calculate future utilization percentage assuming the same levels of
   usage.
 * The future utilization percentage of the instance type falls closer to the
   ranges specified in the applied efficiency target

If metrics for any of the current instance’s attributes are unavailable, VMware
Aria Cost ensures that the candidates have at least as much or more capacity as
that of the current instance.

Baseline performance thresholds for burstable instances are used to evaluate the
current and future utilization percentage when the burstable instance is both a
current instance and a candidate for recommendations.


STEP 3: COMPARISON AND RECOMMENDATION

Candidates are removed if the source instance and candidate instance:

 * Do not support the same DB engine
 * Have different architecture
 * Are from different regions
 * Have different VPC only specifications
 * Have different EBS optimized specifications
 * Have maximum storage specifications less than current attached storage’s size
 * Have maximum IOPS specifications less than current attached storage’s
   provisioned IOPS

Note: If Recommend Burstables is checked, all burstable instance types are
included in the candidate list.

The remaining candidates are sorted from least expensive to most expensive. The
least expensive candidate is the primary recommended instance type and is marked
as the Best Fit. Two additional instance types from the sorted candidate list
are shown as alternative recommendations.


HOW THE NEW RIGHTSIZING TOOL MAKES EBS VOLUME RIGHTSIZING RECOMMENDATIONS

The following is an overview of how the rightsizing tool makes EBS Volume
rightsizing recommendations.


STEP 1: METRICS FOR CURRENT VOLUME

CloudHealth retrieves the following metrics for the selected date range to
determine how current volumes are being utilized:

 * IOPS: IOPS utilization scaled to available IOPS (including provisioned
   capacity)
 * Throughput: Throughput utilization scaled to total available throughput
 * Storage: Volume size in GB

Candidate List

The metric ranges for the applied efficiency target are then used to build a
list of volume types that are potential candidates for recommendations based on
the following criteria:

 * Match the total storage in GB for current and recommended volumes
 * Only the volume attributes included in the applied efficiency target are
   considered.
   * For example, if the applied efficiency target has ranges for IOPS, the
     candidates for recommendations will be listed based on the evaluation of
     IOPS only. Any other available metrics are ignored.
 * The current utilization percentage for each metric is applied to volumes to
   calculate future utilization percentage assuming the same levels of usage.
 * Select the volume types for which the future utilization percentage falls
   closer to or within the ranges specified in the applied efficiency target

If metrics for any of the current volume’s attributes are unavailable,
CloudHealth ensures that the candidates have at least as much or more capacity
as that of the current volume.


STEP 3: COMPARISON AND RECOMMENDATION

The remaining candidates are sorted from least expensive to most expensive. The
least expensive candidate is the primary recommended volume (with relevant IOPS
and throughput modifications) and is marked as the Best Fit. Two additional
volumes from the sorted candidate list are shown as alternative recommendations.


HOW THE NEW RIGHTSIZING TOOL MAKES ELASTICACHE CLUSTER RIGHTSIZING
RECOMMENDATIONS

The following is an overview of how the rightsizing tool makes ElastiCache
Cluster rightsizing recommendations.


STEP 1: METRICS FOR CURRENT CLUSTER

CloudHealth retrieves the following metrics for the selected date range to
determine how current clusters are being utilized:

 * CPU: CPU utilization scaled to vCPUs
 * Freeable Memory: Memory utilization scaled to total available memory

Candidate List

The metric ranges for the applied efficiency target are then used to build a
list of node types that are potential candidates for recommendations based on
the following criteria:

 * Only the node attributes included in the applied efficiency target are
   considered.
   * For example, if the applied efficiency target has ranges for CPU, the
     candidates for recommendations will be listed based on the evaluation of
     CPU metrics only. Any other available metrics are ignored.
 * The current utilization percentage for each metric is applied to nodes to
   calculate future utilization percentage assuming the same levels of usage.
   * The future utilization percentage of the node type falls closer to or
     within the ranges specified in the applied efficiency target

If metrics for any of the current node’s attributes are unavailable, CloudHealth
ensures that the candidates have at least as much or more capacity as that of
the current cluster.

Baseline performance thresholds for burstable node types are used to evaluate
the current and future utilization percentage whenever applicable.


STEP 3: COMPARISON AND RECOMMENDATION

Candidates are removed if the source and candidate node types:

 * Are from different regions

Note: If Recommend Burstables is checked, all relevant burstable node types are
included in the candidate list.

The remaining candidates are sorted from least expensive to most expensive. The
least expensive candidate is the primary recommended node type and is marked as
the Best Fit. Two additional node types from the sorted candidate list are shown
as alternative recommendations.


HOW THE NEW RIGHTSIZING TOOL MAKES KUBERNETES RIGHTSIZING RECOMMENDATIONS

The following is an overview of how the rightsizing tool makes Kubernetes
rightsizing recommendations.


STEP 1: METRICS FOR CURRENT CONTAINERS

VMware Aria Cost retrieves the following metrics for the selected date range to
determine how current containers are being utilized:

 * CPU: CPU utilization scaled to requested compute capacity
 * Memory: memory utilization scaled to requested memory capacity


STEP 2: CALCULATING RECOMMENDATIONS

The metric ranges for the applied efficiency target are then used to calculate
the ideal ranges or compute and memory requests so that the current usage will
fall within the performance ranges set in the applied Efficiency Target.

Only the container attributes included in the applied efficiency target are
considered.

For example, if the applied efficiency target has ranges for memory requests,
the calculations for recommendations will be based on the evaluation of memory
requests only. Any other available metrics are ignored.


HOW THE NEW RIGHTSIZING TOOL MAKES OPENSEARCH CLUSTER RIGHTSIZING
RECOMMENDATIONS

The following is an overview of how the rightsizing tool makes OpenSearch
Cluster rightsizing recommendations.


STEP 1: METRICS FOR CURRENT CLUSTER

VMware Aria Cost retrieves the following metrics for the selected date range to
determine how current clusters are being utilized:

 * CPU: CPU utilization scaled to vCPUs
 * JVM Memory: JVM memory utilization scaled to total available memory


STEP 2: CANDIDATE LIST

The metric ranges for the applied efficiency target are then used to build a
list of node types that are potential candidates for recommendations based on
the following criteria:

 * Only the node attributes included in the applied efficiency target are
   considered.
   * For example, if the applied efficiency target has ranges for CPU, the
     candidates for recommendations will be listed based on the evaluation of
     CPU metrics only. Any other available metrics are ignored.
 * The current utilization percentage for each metric is applied to nodes to
   calculate future utilization percentage assuming the same levels of usage.
   * The future utilization percentage of the node type falls closer to or
     within the ranges specified in the applied efficiency target

If metrics for any of the current node’s attributes are unavailable, VMware Aria
Cost ensures that the candidates have at least as much or more capacity as that
of the current cluster.


STEP 3: COMPARISON AND RECOMMENDATION

Candidates are removed if the source and candidate node types are from different
regions

The remaining candidates are sorted from least expensive to most expensive. The
least expensive candidate is the primary recommended node type and is marked as
the Best Fit. Two additional node types from the sorted candidate list are shown
as alternative recommendations.


EFFICIENCY TARGETS

Efficiency targets are a collection of AWS resource usage attributes and
utilization ranges that can be applied to meet application or enterprise
requirements. VMware Aria Cost’s new rightsizing report supports the following
AWS resources -

 * EC2
 * RDS
 * Kubernetes
 * OpenSearch
 * EBS Volume
 * ElastiCache

Rightsizing includes two default efficiency targets: Average Metrics and Maximum
Metrics. You can also define your own targets by creating a custom efficiency
target.


CREATE A CUSTOM EFFICIENCY TARGET

To create a custom efficiency target:

 1. From the Actions menu, select Add custom efficiency target.
 2. Provide a name for your new efficiency target.
 3. Select one or more metrics to set as a target.
 4. Select whether the metric should be defined by average performance (AVG), or
    limit the metric from going beyond a maximum value (MAX).
 5. Define the target threshold range in values.
    * For EC2 and RDS – The range is from 1 to 100.
    * For Kubernetes – The range is from 1 to 120.
    * For OpenSearch - The range is from 1 to 100.


VIEW, EDIT OR DELETE A CUSTOM EFFICIENCY TARGET

To view, edit, or delete an existing custom efficiency target:

 1. From the Actions menu, select Manage custom efficiency targets.
 2. Select the custom efficiency target from the Efficiency target dropdown.
 3. Make changes to the custom efficiency target:
    * To edit the custom efficiency target, modify any metrics and select Save.
    * To delete the custom efficiency target, select Delete.

> Using Rightsizing APIs, you can programmatically create,update or delete
> efficiency targets. For more details, visit the VMware Aria Cost Graphql API
> guide.

Previous Page
Next Page
check-circle-line exclamation-circle-line Translation Error Open MyLibrary
close-line



In this article

AWS Rightsizing

Using the Rightsizing Dashboard Understand Recommendations View Recommendations
Kubernetes Rightsizing – New

Using the Rightsizing Dashboard Understand Recommendations Resize
Recommendations View Recommendations EBS Volume Rightsizing – New (Beta)

Using the Rightsizing Dashboard Understand Recommendations Types of
Recommendations View Recommendations ElastiCache Rightsizing – New (Beta)

Using the Rightsizing Dashboard Understand Recommendations View Recommendations
OpenSearch Rightsizing – New

Using the Rightsizing Dashboard Understand Recommendations How the New
Rightsizing Tool Makes EC2 Rightsizing Instance Recommendations

Step 1: Metrics for Current Instance Step 2: Candidate List Step 3: Comparison
and Recommendation How the New Rightsizing Tool Makes RDS Instance Rightsizing
Recommendations

Step 1: Metrics for Current Instance Step 2: Candidate List Step 3: Comparison
and Recommendation How the New Rightsizing Tool Makes EBS Volume Rightsizing
Recommendations

Step 1: Metrics for Current Volume Step 3: Comparison and Recommendation How the
New Rightsizing Tool Makes ElastiCache Cluster Rightsizing Recommendations

Step 1: Metrics for Current cluster Step 3: Comparison and Recommendation How
the New Rightsizing Tool Makes Kubernetes Rightsizing Recommendations

Step 1: Metrics for Current containers Step 2: Calculating Recommendations How
the New Rightsizing Tool Makes OpenSearch Cluster Rightsizing Recommendations

Step 1: Metrics for Current Cluster Step 2: Candidate List Step 3: Comparison
and Recommendation Efficiency Targets

Create a Custom Efficiency Target View, Edit or Delete a Custom Efficiency
Target
Send Feedback
Product Download

Company

About Us Executive Leadership News & Stories Investor Relations Customer Stories
Diversity, Equity & Inclusion Environment, Social & Governance
Careers Blogs Communities Acquisitions Office Locations VMware Cloud Trust
Center COVID-19 Resources

Support

VMware Customer Connect Support Policies Product Documentation Compatibility
Guide Terms & Conditions California Transparency Act Statement
Twitter YouTube Facebook LinkedIn Contact Sales

--------------------------------------------------------------------------------

© 2023 VMware, Inc. Terms of Use Your California Privacy Rights Privacy
Accessibility Trademarks Glossary Help Feedback



SHARE

×

Anyone with the Link can view

Copy Link

Share Collection ON Share Collection OFF
Share on Social Media?

Add Note Delete Note
×
Enter Note

Cancel Submit Delete

ASK NEW QUESTION

×
exclamation-circle-line
We’re sorry, but we can’t post your question to Communities right now. Try again
later, or go directly to VMware Communities and post a question without us.
We’ll understand.
check-circle-line
Your question is posted to Communities. Wait patiently for an answer, or take a
look now!
Enter Subject
Enter Question
Product-specific community spaces are hosted in English. If you want to ask a
question in another language, visit your global community instead.
Global Communities
Relevant Tags :
Cancel Submit

CREATE A VMWARE COMMUNITIES USERNAME

×
exclamation-circle-line
We can’t create a username for you at this time. Please check that your My
VMware profile is filled out. If the problem persists, contact support.
My VMware| Support
check-circle-line
Welcome to VMware Communities!
exclamation-circle-line
Usernames can’t contain spaces or special characters. Try a username with
numbers and letters instead.

Enter Username

Username Available x Username Not Available
Cancel Create

DELETE

×
Translation Error " "?
Cancel Delete
×

Cookies Settings


WE CARE ABOUT YOUR PRIVACY

We use cookies to provide you with the best experience on our website, to
improve usability and performance and thereby improve what we offer to you. Our
website may also use third-party cookies to display advertising that is more
relevant to you. By clicking on the “Accept All” button you agree to the storing
of cookies on your device. If you close the cookie banner, only strictly
necessary cookies will be stored on your device. If you want to know more about
how we use cookies, please see our Cookie Policy.

Cookies Settings Accept All Cookies



COOKIE PREFERENCE CENTER




 * GENERAL INFORMATION ON COOKIES


 * STRICTLY NECESSARY


 * PERFORMANCE


 * FUNCTIONAL


 * ADVERTISING


 * SOCIAL MEDIA

GENERAL INFORMATION ON COOKIES

When you visit our website, we use cookies to ensure that we give you the best
experience. This information does not usually directly identify you, but it can
give you a more personalized web experience. Because we respect your right to
privacy, you can choose not to allow some types of cookies by clicking on the
different category headings to find out more and change your settings. However,
blocking some types of cookies may impact your experience on the site and the
services we are able to offer. Further information can be found in our
Cookie Policy.

STRICTLY NECESSARY

Always Active

Strictly necessary cookies are always enabled since they are essential for our
website to function. They enable core functionality such as security, network
management, and website accessibility. You can set your browser to block or
alert you about these cookies, but this may affect how the website functions.
For more information please visit www.aboutcookies.org or
www.allaboutcookies.org.

Cookies Details‎

PERFORMANCE

Performance


Performance cookies are used to analyze the user experience to improve our
website by collecting and reporting information on how you use it. They allow us
to know which pages are the most and least popular, see how visitors move around
the site, optimize our website and make it easier to navigate.

Cookies Details‎

FUNCTIONAL

Functional


Functional cookies help us keep track of your past browsing choices so we can
improve usability and customize your experience. These cookies enable the
website to remember your preferred settings, language preferences, location and
other customizable elements such as font or text size. If you do not allow these
cookies, then some or all of these services may not function properly.

Cookies Details‎

ADVERTISING

Advertising


Advertising cookies are used to send you relevant advertising and promotional
information. They may be set through our site by third parties to build a
profile of your interests and show you relevant advertisements on other sites.
These cookies do not directly store personal information, but their function is
based on uniquely identifying your browser and internet device.

Cookies Details‎

SOCIAL MEDIA

Social Media


Social media cookies are intended to facilitate the sharing of content and to
improve the user experience. These cookies can sometimes track your activities.
We do not control social media cookies and they do not allow us to gain access
to your social media accounts. Please refer to the relevant social media
platform’s privacy policies for more information.

Cookies Details‎
Back Button


COOKIE LIST

Filter Button
Consent Leg.Interest
checkbox label label
checkbox label label
checkbox label label

 * View Third Party Cookies
    * Name
      cookie name


Clear
checkbox label label
Apply Cancel
Confirm My Choices
Allow All

word word word word word word word word word word word word word word word word
word word word word word word word word word word word word word word word word
word word word word word word word word word word word word word word word word
word word word word word word word word word word word word word word word word
word word word word word word word word word word word word word word word word
word word word word word word word word word word word word word word word word
word word word word word word word word word word word word word word word word
word word word word word word word word word word word word word word word word
word word word word word word word word word word word word word word word word
word word word word word word word word word word word word word word word word
word word word word word word word word word word word word word word word word
word word word word word word word word word word word word word word word word
word word word word word word word word

mmMwWLliI0fiflO&1
mmMwWLliI0fiflO&1
mmMwWLliI0fiflO&1
mmMwWLliI0fiflO&1
mmMwWLliI0fiflO&1
mmMwWLliI0fiflO&1
mmMwWLliI0fiflO&1
word word word word word word word word word word word word word word word word
word word word word word word word word word word word word word word word word
word word word word word word word word word word word word word word word word
word word word word word word word word word word word word word word word word
word word word word word word word word word word word word word word word word
word word word word word word word word word word word word word word word word
word word word word word word word word word word word word word word word word
word word word word word word word word word word word word word word word word
word word word word word word word word word word word word word word word word
word word word word word word word word word word word word word word word word
word word word word word word word word word word word word word word word word
word word word word word word word word word word word word word word word word
word word word word word word word word

mmMwWLliI0fiflO&1
mmMwWLliI0fiflO&1
mmMwWLliI0fiflO&1
mmMwWLliI0fiflO&1
mmMwWLliI0fiflO&1
mmMwWLliI0fiflO&1
mmMwWLliI0fiflO&1