Which of the following activities may help reduce your AWS monthly costs?
Identify any Amazon EC2 instances that appear to be under-utilised and downsize (resize) them to help lower the cost of your monthly AWS bill. By default, an EC2 instance is considered under-utilised when matches the following criteria (to declare the instance under-utilised both conditions must be met): Show
This rule can help you with the following compliance standards:
This rule can help you work with the AWS Well-Architected Framework
Audit
Using AWS Console1. Sign in to the AWS Management Console. 2. Navigate to EC2 dashboard at https://console.aws.amazon.com/ec2/. 3. In the navigation panel, under INSTANCES section, choose Instances. 4. Select the EC2 instance that you want to examine. 5. Select the Monitoring tab from the dashboard bottom panel. 6. Within the CloudWatch metrics section, perform the following actions: a. Expand the CPU Utilisation (Percent) usage graph thumbnail to open the instance CPU usage details box. Inside the CloudWatch Monitoring Details dialog box, set the following parameters:
b. Once the monitoring data is loaded, verify the instance CPU usage for the last 7 days. If the average usage (percent) has been less than 30%, e.g. The selected EC2 instance qualifies as candidate for the underused instance. Click 5 to return to the dashboard.7. Now determine the EC2 instance memory utilisation by reading the 1 metric data reported by the CloudWatch agent (Perl script) installed on the selected EC2 instance (this rule assumes that the script has been successfully installed and it has returned memory usage data in the past 7 days). To verify the instance memory usage reported by the custom CloudWatch metric, perform the following actions:a. Navigate to Cloudwatch dashboard at https://console.aws.amazon.com/cloudwatch/. b. In the navigation panel, select Metrics to access your existing Cloudwatch metrics. c. Choose All metrics tab from the dashboard bottom panel, click Linux System then select InstanceId to list any custom metrics installed on your EC2 instances. d. Select the right EC2 instance from the list (see Audit section part I, step no. 4), click the Action dropdown button from the dashboard top-right menu then choose Add to dashboard option. e. On Add to dashboard dialog box, perform the following:
f. Click the Custom dropdown button from the dashboard top-right menu, select Relative then choose the 1 Weeks option to return the data recorded in the past week. g. Once the monitoring data is available within the widget, verify the instance memory usage for the last 7 days. If the average usage (percent) has been less than 30%, e.g. the selected EC2 instance qualifies as candidate for the underused instance. If the rule conditions are met, based on the usage data outlined at step no. 6 and 7, the selected AWS EC2 instance is considered 7 and can be safely downsized in order to stop incurring charges for the EC2 compute resources that you don’t use.8. Repeat steps no. 4 – 7 to verify the CPU and memory usage data available in the last 7 days for the rest of the EC2 instances provisioned in the current region. 9. Change the AWS region from the navigation bar and repeat the audit process for other regions. Using AWS CLI1. Run 8 command (OSX/Linux/UNIX) using necessary filtering to list the IDs of all active (running) EC2 instances provisioned in the selected region:
9 command (OSX/Linux/UNIX) to get the statistics recorded by AWS CloudWatch for the CPUUtilization metric representing the CPU usage of the selected EC2 instance.The following command example returns the average CPU utilization for an EC2 instance identified by the ID 0, usage data captured during a 1 time frame, using a time interval of 1 hour as the granularity for the returned datapoints:
If the average CPU usage data returned is less than 30%, the selected EC2 instance qualifies as candidate for the underused instance. 1 metric data (or whatever name you have used for your custom metric) reported by the CloudWatch script installed on the selected EC2 instance (this rule assumes that the script has been successfully installed and it has recorded memory usage data within the past 7 days).Run 9 command (OSX/Linux/UNIX) using the metric name as identifier.The following command example returns the average memory utilization for an EC2 instance identified by the ID 0, from the usage data captured by a CloudWatch metric named 1, during a 7-day time frame, using a time interval of 1 hour as the granularity for the returned data points:
If the average memory utilization data returned is less than 30%, the selected EC2 instance qualifies as candidate for the underused instance. If the usage data returned at steps no. 3 - 6 satisfy the conditions set by the rule (i.e. average CPU and memory usage less than 30%), the selected EC2 instance is considered "underutilized" and should be downsized in order to reduce your AWS EC2 usage costs.
Remediation / ResolutionOption 1: Downsize (resize) the underused EC2 instances provisioned within your AWS account. To resize any EC2 instance that is currently running in "underutilized" mode, perform the following commands:
Using AWS Console1. Sign in to the AWS Management Console. a. From the Instance Type dropdown list, select the instance type to downsize to (e.g. c4.large – see EC2 Instance Types page available at this URL to help you choose the right instance type). b. (Optional) Select EBS-optimized to enable EBS optimization or deselect EBS-optimized to disable EBS optimization. This feature provides dedicated throughput to your AWS EBS volumes for best I/O performance (additional charges apply). c. Click Apply to resize the selected instance. Using AWS CLI1. Run 6 command (OSX/Linux/UNIX) using the 7 as identifier to stop the underused EC2 instance that you want to resize (see Audit section part II to identify the right instance):
8i-0e2131e74da4fb0a2 9c5.xlarge 0c5.large` instance. If successful, no output is returned:
1 command (OSX/Linux/UNIX) to restart the EC2 instance resized at the previous step (it may take few minutes until the instance enters the running state):
0 Option 2: Override the rule check. If the selected underused EC2 instance configuration must remain unchanged (some workload scenarios can result in low resource utilization by design), you should Still Need Help?Come see why we are the #1 cloud management platform and why companies like Uber, Dickey’s BBQ Pit and Norwegian Cruise Line trust nOps to manage their cloud. Which of the following may help you to reduce your EC2 monthly costs?Utilize reserved instances or spot instances
The EC2 cost model section above highlights that utilizing reserved instances and spot instances (instead of on-demand instances) will reduce your EC2 costs by up to 75% and 90%, respectively.
What are two ways an AWS customer can reduce their monthly spend choose two?You can reduce costs by either stopping or downsizing these instances. Use AWS Instance Scheduler to automatically stop instances. Use AWS Operations Conductor to automatically resize the EC2 instances (based on the recommendations report from Cost Explorer).
How does AWS help lower costs?Cloud Financial Management with AWS. The cloud allows you to trade fixed expenses (such as data centers and physical servers) for variable expenses, and only pay for IT as you consume it. And, because of the economies of scale, the variable expenses are much lower than what you would pay to do it yourself.
Which of the following actions may reduce Amazon EBS costs?One of the easiest ways to minimize EBS costs is to identify and delete unattached volumes. After stopping or terminating EC2 Instances, the attached block volumes keep running, accruing costs. You should find the unattached EBS volumes and identify whether they are necessary or not.
|