Kategori
General

Praktek Cost Estimation (AWS)

Lab overview and objectives

This hands-on lab guides you through the steps to estimate Amazon Web Services (AWS) costs for a sample workload. The workload that you evaluate is for a three-tier web application that consists of an Application Load Balancer, an Amazon EC2 instance, and an Amazon RDS instance. The skills that you learn will help you use AWS Pricing Calculator to estimate costs for your workloads.

Web-based application diagram The preceding diagram includes a load balancer, an EC2 instance, and an RDS instance.

Objectives

After completing this lab, you will know how to do the following:

  • Estimate AWS Costs using AWS Pricing Calculator.

Task 1: Launch the AWS Pricing Calculator

In this task, you launch AWS Pricing Calculator and begin to create an estimate.

  1. Open a new web browser tab.
  2. In the address bar enter the following URL: https://calculator.aws/#/
  3. Choose Create estimate.

Task 2: Add and configure services in AWS Pricing Calculator

In this task, you use AWS Pricing Calculator to explore AWS services and create an estimate for the cost of your use case, a three-tier web application.

Add the load balancer to the estimate

  1. On the Select service page, in the Find Service search box, enter Elastic Load Balancing.
  2. In the Elastic Load Balancing card, choose Configure.
  3. In the Description section, configure the following options:
  • For Description, enter Load Balancer.
  • For Select location type, choose Region.
  • For Select region, choose US West (Oregon).
  1. For Elastic Load Balancing, turn on Application Load Balancer.
  2. In the Application Load Balancer section, choose Load Balancer in AWS Region.
  3. In the Service settings section, for Number of Application Load Balancers, enter 1.
  4. In the Load Balancer Capacity Units (LCUs) section, configure the following options:Note: The load balancer metrics that are used to estimate cost, such as processed bytes and connection duration, are typically provided by the team that developed and tested the application. These numbers vary based on the application profile.
  • Skip Processed bytes (Lambda functions as targets) because you are using EC2 instances.
  • For Processed bytes (EC2 Instances and IP addresses as targets), enter 0.36. From the dropdown list, choose GB per hour.
  • For Average number of new connections per ALB, enter 100. From the dropdown list, choose per second.
  • For Average connection duration, enter 3. From the dropdown list, choose minutes.
  • For Average number of requests per second per ALB, enter 400.
  • For Average number of rule evaluations per request, enter 20. Note: Load balancer listener rules determine how the load balancer routes requests. For example, the default rule only routes HTTP traffic on port 80 to the EC2 instances (targets).
  1. Choose Save and add service. 

Add the EC2 instance to the estimate

  1. On the Select service page, in the Find Service search box, enter EC2.
  2. In the Amazon EC2 card, choose Configure.
  3. In the Description section, configure the following options:
  • For Description, enter EC2.
  • For Select location type, choose Region.
  • For Select region, choose US West (Oregon). 
  1. In the EC2 instance specifications section, for Operating system, choose Linux.
  2. In the Workload section, configure the following options:
  • Choose Daily spike traffic.
  • Keep the settings for Workload days (Monday – Friday).
  • For Baseline, enter 1.
  • For Peak, enter 2. Note: These settings indicate that this workload requires one instance at normal times and two instances during peak usage.
  • For Duration of peak (hours,minutes), keep the default settings.
  1. In the EC2 instances section, choose t4g.small.
  2. In the Pricing strategy section, choose On-Demand.
  3. In the Amazon Elastic Block Storage (EBS) section, configure the following storage options:
  • For Storage for each EC2 instance, choose General Purpose SSD (gp3).
  • For General Purpose SSD (gp3) – IOPS, keep the default setting.
  • For General Purpose SSD (gp3) – Throughput, keep the default setting.
  • For Storage amount, enter 30. From the dropdown list, choose GB.
  1. In the Data transfer section, configure the following options:
  • For Inbound Data Transfer:
    • From the first dropdown list, choose Internet (free).
    • Enter 50.
    • From the last dropdown list choose GB per month.
  • For Outbound Data Transfer:
    • From the first dropdown list, choose Internet (0.05 USD – 0.09 USD per GB).
    • Enter 200.
    • From the last dropdown list, choose GB per month.
  1. Choose Save and add service. 

Add the RDS instance to the estimate

  1. On the Select service page, in the Find Service search box, enter RDS.
  2. In the Amazon RDS for MySQL card, choose Configure.
  3. In the Description section, configure the following options:
  • For Description, enter Database.
  • For Select location type, choose Region.
  • For Select region, choose US West (Oregon).
  1. In the MySQL instance specifications section, configure the following options:
  • For Quantity, enter 1.
  • From the dropdown list, choose db.m6g.large.
  • For Deployment option, choose Multi-AZ.
  • For Pricing model, keep the default setting.
  1. Skip the RDS Proxy section.
  2. In the Storage section, configure the following settings:
  • For Storage for each RDS instance, choose General Purpose SSD (gp2).
  • For Storage amount, enter 100. From the dropdown list, choose GB.
  1. Skip the Backup Storage and Snapshot Export sections.
  2. Choose Save and add service.

Task 3: Review and download the estimate

In this task, you review the cost estimate that the calculator generated, and you download a copy of the estimate into a comma-separated values (CSV) file. A CSV file can be opened in desktop tools such as Excel.

  1. Choose View summary.
  2. Review the overall costs that AWS Pricing Calculator generated for the services from the My Estimate page. AWS Pricing Calculator provides the total cost for the first 12 months. If needed, you can edit or delete the configuration of the services added by choosing the edit icon next to each service name.

My Estimate page The preceding screenshot is an example of the cost estimate summary.

Note: The prices found in your estimate may vary as prices occasionally change.

  1. Choose Export, and then choose CSV.
  2. In the Export My Estimate to csv dialog box, choose OK.
  3. Use your local file explorer to save the file.

Task 4: Save and share the estimate

In this task, you share your estimate with others and save it.

Commonly, estimates need to be shared with others such as managers, project team members, or even customers.

  1. Choose Share.
  2. In the Save estimate dialog box, choose Agree and continue.
  3. To copy the link for your estimate, choose Copy public link.
  4. To share the estimate, send the link to others using a communication tool such as email.Note: When you share an estimate, AWS Pricing Calculator automatically saves it and generates a URL to access it. AWS Pricing Calculator saves your estimate for 3 years.

Summary

In this lab, you created a cost estimate using AWS Pricing Calculator. You added the components that are required for a three-tier web application and defined the sizing requirements for each service. You previewed the annual cost estimate and generated a link to share the estimate with others.

Now, you know how to evaluate the potential costs of architectures before you deploy them. This helps you control your AWS costs and avoid unpleasant surprises such as unexpected or high monthly bills.

Ref : [1]