T2 Instance Rightsizing

When rightsizing T2 instances it is important to remember that while the compute resources for T2 are burstable, and can go above the baseline, memory is static, and cannot burst. If an instance runs out of memory it may begin to swap, significantly degrading performance.

CloudHealth Rightsizing reports now will scale the CPU usage to the T2 baseline when analyzing T2 Instances. We recommend that you set the policy to evaluate for the Average CPU %, and Maximum Memory %, so the instance will not run out of memory after rightsizing.

Update to EC2 Instances Asset Report

The asset report for EC2 instances and images now reports the AMI type of virtualization and hypervisor via two new columns: Virtualization Type and Hypervisor. This can help you quickly see which virtualization type your instances are running -- Paravirtual (PV) or Hardware Virtual Machine (HVM). This may be helpful in your response to Meltdown and Spectre as you will likely want to migrate your PV machines to HVM. You can also use this metadata to create Perspective groups.

Action Required -- Update Your IAM Policy Permissions

We have added support for collecting and inventorying of Amazon Sagemaker. If you update your IAM policy using the auto-generated IAM policy in the platform, no further action is required. If you update your IAM policy manually, there are additional permissions that you need to add to your IAM policy:

• sagemaker:DescribeEndpoint

• sagemaker:DescribeEndpointConfig

• sagemaker:DescribeModel

• sagemaker:DescribeNotebookInstance

• sagemaker:DescribeTrainingJob

• sagemaker:ListEndpointConfigs

• sagemaker:ListEndpoints

• sagemaker:ListModels

• sagemaker:ListNotebookInstances

• sagemaker:ListTags

• sagemaker:ListTrainingJobs

Learn more about updating AWS account policies in this Help Center article. 

Azure Actions -- Now Generally Available 

We’re pleased to announce the general availability of Actions for Azure. Actions are available for Azure Virtual Machines (VMs) in the asset report, policies, and rightsizing reports. Available actions include:

• Start VM

• Stop and Deallocate VM

• Restart VM

• Resize VM

Note: Classic Virtual Machines will be stopped and will continue to incur charges. To deallocate Classic Virtual Machines please go to the Azure portal.

To learn more about Azure VM management using actions, read this Help Center article.

Update to Azure Virtual Machine Rightsizing

We’re excited to announce a new update to CloudHealth Rightsizing for Azure. Previously, when you created a custom rightsizing policy, it would change the scoring (battery meters) but not the recommendation savings or the recommendation. Moving forward, when you create a customized rightsizing policy, if you set the severe utilization thresholds to maximum for CPU, memory, or disk, the recommendations and associated savings will be based on maximums. If you set the severe utilization to an average, then we will evaluate and recommend downsizing based on average metrics. This gives you the flexibility to define rightsizing policies based on maximum or average CPU, memory, or disk. You can even tune these policies by your unique Perspectives.

Expansion of CloudHealth Academy Webinar Schedule

We have added new times to the webinar calendar to better accommodate our international customers. We’re now offering classes in the APAC and European timezones. To access our self-paced videos or to sign up for training classes, go to the Help Center and select CloudHealth Academy.