

# Estimate examples for services
<a name="estimate-examples"></a>

This section provides examples and tutorials that show how you can use AWS Pricing Calculator to generate estimates for certain services.

**Topics**
+ [

# Generating Amazon EC2 estimates
](ec2-estimates.md)
+ [

# Generating estimates for Windows Servers and SQL Servers on EC2
](windows-workload-estimates.md)
+ [

# Generating estimates for Windows Servers and SQL Servers on EC2 Dedicated Hosts
](windows-workload-ec2.md)
+ [

# Generating Microsoft estimates with AWS Modernization Calculator
](modernization-calculator-microsoft-workloads.md)

# Generating Amazon EC2 estimates
<a name="ec2-estimates"></a>

You can use the AWS Pricing Calculator to estimate costs for your Amazon Elastic Compute Cloud (Amazon EC2) instances. This section provides the procedure on how to generate an Amazon EC2 estimate and describes the specifications, payment options, and add-ons you can choose for your Amazon EC2 estimate.

**Topics**
+ [

## Procedure
](#ec2-estimate)
+ [

## Amazon EC2 instance specifications
](#quick-ec2-specifications)
+ [

## Payment options
](#quick-pricing-strategy)
+ [

## Amazon Elastic Block Store (EBS)
](#quick-ebs)
+ [

## Detailed monitoring costs
](#ec2-detailed-monitoring)
+ [

## Data transfer costs
](#ec2-data-estimates)
+ [

## Elastic IP costs
](#ec2-elastic)
+ [

## Additional costs
](#ec2-additional-costs)

## Procedure
<a name="ec2-estimate"></a><a name="ec2-estimates-process"></a>

**To generate an Amazon EC2 estimate**



1. Open the **Amazon EC2 estimate** page at [https://calculator.aws/\$1/createCalculator/ec2-enhancement](https://calculator.aws/#/createCalculator/ec2-enhancement) .

1. Enter the description for your Amazon EC2 estimate.

1. Choose the **Location type** and **Region** from the dropdown.

1. (Optional) Choose the parameters you want in your estimate.
   + [Amazon EC2 instance specifications](#quick-ec2-specifications)
   + [Payment options](#quick-pricing-strategy)
   + [Amazon Elastic Block Store (EBS)](#quick-ebs)
   + [Detailed monitoring costs](#ec2-detailed-monitoring)
   + [Data transfer costs](#ec2-data-estimates)
   + [Elastic IP costs](#ec2-elastic)
   + [Additional costs](#ec2-additional-costs)

1. Choose **Save and add service**.

The calculator view is preloaded with default values so you can see a starting estimate without adding or changing any information. You can change any of the values for the following parameters. Otherwise, you can also keep the defaults when they're applicable.

The Amazon EC2 instance estimate path has the following sections and parameters.

## Amazon EC2 instance specifications
<a name="quick-ec2-specifications"></a>

These settings determine the Amazon EC2 instance that AWS Pricing Calculator uses to generate an estimate for you.

**Select your tenancy**  
The default value for tenancy is `Shared Instances`.

**Select your operating system**  
The operating system on an Amazon EC2 instance. AWS Pricing Calculator generates your estimate using Amazon Machine Images (AMIs) that match the OS you choose. Choose the operating system (OS) that best matches your needs. The default value for the OS is Linux.

**Choose your instance type**  
AWS Pricing Calculator lists all available instance types. Use the search bar to filter the instances.  
**Search for an instance type by name**  
If you know the instance family or instance size that you want, it's efficient to search for the instance name. For example, you can search for a `t2.medium` instance.  
**Search for an instance type based on minimum requirements**  
Minimum requirements are most useful when you know the specifications of the instances that you want. For example, you can search either for an instance with a minimum of four vCPUs and 16 GB of memory for any network performance.  
For information about the available Amazon EC2 instance families, see [Amazon EC2 Instance Types](https://aws.amazon.com/ec2/instance-types/).

**Number of EC2 instances**  
The default value is one. AWS Pricing Calculator uses this default because it's the minimum number that you might need.

 **Workloads**   
Workloads are the usage patterns that match your Amazon EC2 usage. Choosing the workload that most closely matches what you use reduces the number of On-Demand and unused RI hours that you might purchase. It does this by covering your usage with the most appropriate combination of RIs and On-Demand Instances for you. You can define more than one workload for your estimate.  
**Constant usage**  
This workload is suitable for use cases that have a constant, predicable load. This includes use cases such as logging traffic to a website or running processes in the background.  
**Daily spike**  
This workload is best for usage patterns that peak once a day. This is suitable for scenarios where, for example, you need to run several jobs at midnight or have a morning news spike.  
**Weekly spike**  
This workload is best for patterns that peak once a week. This is suitable for scenarios such as blogs that post once a week and weekly television shows.  
**Monthly spike**  
This workload is best for traffic that spikes once a month, such as monthly invoices, payroll, or other monthly reports.

## Payment options
<a name="quick-pricing-strategy"></a>

These settings determine the pricing strategy that AWS Pricing Calculator uses to generate your estimate.

**Pricing model**  
The pricing model determines whether you're searching for a pay-as-you-use instance or an instance that you can reserve in advance. Reserving an instance isn't the same as paying for the use of an instance.

**Reservation terms**  
When you reserve a Reserved Instance (RI), you purchase a reservation for the period of your contract. Contracts can be for either one or three years.  
The default value is one year. AWS Pricing Calculator uses this default because it's the least costly option for trying out AWS.

**Payment options**  
For RIs, payment options determine when you pay for your reservation. You can pay for the entire reservation upfront, which is a hefty single-time payment but you have no monthly payments. You can pay for the RI with a partial upfront payment and a monthly payment. This gives you a smaller upfront cost but accrues monthly costs. You can also pay with no upfront payment. This means you pay only on a monthly basis. All upfront gives you the best discount, but no upfront and partial upfront spread your costs out over a greater period of time.  
The default value for the payment options is `No Upfront`. AWS Pricing Calculator uses this default because it gives you the least expensive start-up price.

**Expected utilization of EC2 instances**  
Enter the expected usage of Amazon EC2 instances. The feature is only applicable when you select the On-Demand pricing strategy.

**Spot**  
The calculator shows the historical average discount percentage for the instance chosen. You can enter a percentage discount for creating estimates.

## Amazon Elastic Block Store (EBS)
<a name="quick-ebs"></a>

These settings determine the Amazon EBS settings that AWS Pricing Calculator uses to generate an estimate for you. Amazon Elastic Block Store (Amazon EBS) is a type of storage that you can connect to your Amazon EC2 instance. You can use it to do things such as backing up your instance, creating a boot volume, or running a database on your instance. For more information about Amazon EBS, see the [Amazon Elastic Block Store documentation](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AmazonEBS.html).

**Storage volume**  
The storage volume determines what kind of storage that Amazon EBS assigns to your instance. Different types have different capabilities. For example, you can choose better I/O and faster calculations, or slower, less expensive options for your specific use cases such as boot volumes and backups.

**Storage amount**  
The storage amount determines how much storage your Amazon EBS volume has.  
The default value is `30 GB`. You can enter `0 GB` if you don't attach Amazon EBS volumes to your Amazon EC2 instance. You can also estimate additional Amazon EBS volumes by configuring and adding a standalone Amazon EBS calculator into your estimate at [https://calculator.aws/\$1/createCalculator/EBS](https://calculator.aws/#/createCalculator/EBS) .

## Detailed monitoring costs
<a name="ec2-detailed-monitoring"></a>

Your instances are turned on for basic monitoring by default. You can optionally turn on detailed monitoring. Once detailed monitoring is turned on, the Amazon EC2 console shows monitoring graphs with a one minute period for the instance. For more information, see [Detailed monitoring](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-cloudwatch-new.html).

## Data transfer costs
<a name="ec2-data-estimates"></a>

You can accrue additional costs by transferring data in and out of Amazon EC2. If you know how much data you can expect to upload or download in a month, you can add these costs to your estimate. For more information, see the [Data transfer](https://aws.amazon.com/ec2/pricing/on-demand/) section on the *On-Demand Pricing * page.

## Elastic IP costs
<a name="ec2-elastic"></a>

You can have one Elastic IP (EIP) address associated with a running instance at no charge. If you associate additional EIPs with that instance, you will be charged for each additional EIP associated with that instance per hour on a pro rata basis. A small hourly charge applies when EIPs are not associated with a running instance or when they are associated with a stopped instance or unattached network interface. For more information, see [Elastic IP Addresses](https://aws.amazon.com/ec2/pricing/on-demand/) section on the *On-Demand Pricing * page.

## Additional costs
<a name="ec2-additional-costs"></a>

You can add a custom cost to your Amazon EC2 pricing estimates. You can use this to add any placeholder costs you'd like to include in your estimates.

# Generating estimates for Windows Servers and SQL Servers on EC2
<a name="windows-workload-estimates"></a>

You can use the workload calculator in AWS Pricing Calculator to guide you on AWS tenancy qualifications for Microsoft Windows Server and SQL Server on Amazon Elastic Compute Cloud (Amazon EC2). You can use the workload calculator to estimate AWS cost using minimal information and parameters. You can generate an estimate even if you don't know the details for each parameter. This is because each parameter includes a default setting.

For options for using Microsoft software licenses on the AWS Cloud, see [Microsoft Licensing on AWS](https://aws.amazon.com/windows/resources/licensing/).

**Topics**
+ [

## Procedure
](#windows-workload-estimates-process)
+ [

## Licensing and tenancy recommendations
](#estimate-workload-tenancy)
+ [

## Configuring machine specifications
](#estimate-workload-configure)
+ [

## Pricing strategy
](#estimate-workload-pricing)
+ [

## Cost details
](#estimate-workload-cost)
+ [

# Tutorial: Generating estimates for Windows Servers and SQL Servers on EC2
](estimate-workload-tutorial.md)

## Procedure
<a name="windows-workload-estimates-process"></a>

**To generate an estimate for Windows Server and SQL Server on Amazon EC2**

1. Open AWS Pricing Calculator at [https://calculator.aws/\$1/](https://calculator.aws/#/).

1. Choose **Create estimate**.

1. Under **Windows Server and SQL Server on Amazon EC2**, choose **Configure**.

1. On the **Configure Windows Server and SQL Server on Amazon EC2** page, choose your customized settings.
   + For information about your tenancy choices, see [Licensing and tenancy recommendations](#estimate-workload-tenancy).
   + For information about how to choose your machine specifications, see [Configuring machine specifications](#estimate-workload-configure).
   + For information about how to choose your pricing strategy, see [Pricing strategy](#estimate-workload-pricing).
   + For information about how to choose your cost details, see [Cost details](#estimate-workload-cost).

1. Choose **Add to my estimate**.

For a step-by step example shows how to generate an estimate for Windows Server and SQL Server on Amazon EC2, see [Tutorial: Generating estimates for Windows Servers and SQL Servers on EC2Procedure](estimate-workload-tutorial.md).

## Licensing and tenancy recommendations
<a name="estimate-workload-tenancy"></a>

You can determine your AWS licensing and tenancy options for your workload through your choices for Windows Server and SQL Server licensing inputs. The licensing options include AWS provided licenses with License Included offerings, and your existing licenses with Bring Your Own License (BYOL) offerings for optimal cost savings. You can identify the most suitable cloud tenancy, for example, Shared tenancy or Dedicated Hosts.

The following table shows the AWS licensing and tenancy scenarios supported by AWS Pricing Calculator.


| Windows Server | SQL Server | AWS tenancy | 
| --- | --- | --- | 
| License Included | License Included | Shared tenancy | 
| License Included | BYOL | Shared tenancy or Dedicated Hosts | 
| BYOL | BYOL | Dedicated Hosts | 
| BYOL | License Included | Not supported | 

Some license and tenancy variables include the following:
+ Whether your Windows Server license was purchased before or after October 1, 2019
+ Whether your SQL Server license was purchased before or after October 1, 2019
+ Whether you want to bring your own license (BYOL), or you have active Software Assurance for SQL Server licenses

If you don’t choose a preference for Windows Server or SQL Server, the calculator assumes the Licence Included scenario that doesn't utilize the existing licenses for cost savings.

## Configuring machine specifications
<a name="estimate-workload-configure"></a>

Based on your choice of machine specification, we recommend the Amazon EC2 instance that AWS Pricing Calculator uses to generate an estimate for your cost. You can also select different instances than the one recommended, or add multiple machine specifications for a workload.

This section defines the terms mentioned in the **Configure machine specifications** section.

****Machine description****  
A description for the machine. This is generally a hostname identifier. If unknown, you can specify unique software components running on this machine—for example, `WebApp DB1` or `Webserver 1`.

****Operating system****  
You can choose an operating system with a licensing option, depending on your tenancy qualification. The default value is `Windows`.

****SQL Server edition****  
You can choose a SQL Server with licensing option, depending on your tenancy qualification. The default value is `SQL Standard`.

****Storage volumes per specification****  
You can specify the storage needs in this section. If you don't know storage needs upfront, you can remove it from the estimate using **Remove**. This section is optional.  
Instances can have either none or one or more storage volumes associated. Choose **Add new volume** to add multiple volumes to an instance.  
You can use different volume types for each volume. The calculator recommends the appropriate Amazon EBS storage type based on the optional inputs such as **IOPS** and **Throughput**.    
****Storage amount****  
You can specify your storage amount needs. The default value is 1000 GB. If only storage amount is specified, the default recommended Amazon EBS storage type is `General Purpose SSD (gp3)`.  
****IOPs****  
IOPS (input/output operations per second) is the standard unit of measurement for the maximum number of reads and writes to non-contiguous storage locations. IOPS describes performance in solid state drives (SSD), hard disk drives (HDD), and storage area networks.  
You can specify IOPs for I/O intensive workloads. AWS uses this value to potentially recommend `io2` Amazon EBS storage types.  
`io2` delivers a consistent baseline performance of up to 500 IOPS/GB to a maximum of 64,000 IOPS,. It provides up to 1,000 MB/s of throughput per volume.  
****Throughput****  
Throughput measures how many units of information a system can process in a period of time. It can refer to the number of I/O operations per second, but is typically measured in bytes per second.  
You can specify this input for throughput-intensive workloads.  
`st1` is backed by hard disk drives. It's ideal for frequently accessed, throughput-intensive workloads with large datasets and large I/O sizes. Examples include MapReduce, Kafka, and log processing.

****EC2 instance type****  
**Obtain an EC2 instance type recommendation**  
This is the default choice. Choose the number of vCPUs and memory inputs to generate an EC2 instance recommendation. Only x86 architecture instances are considered. The default vCPU value is 4, and memory is 16 GB.   
**Search for an EC2 instance type**  
You can use this option to choose different instance types than the recommended instance.  
To find an instance, search by minimum requirements or by name. Minimum requirements are the most useful when you know the specification of the instances you prefer. Instance names are useful when you know the instance family or size of the instance you prefer. For example, you can search for an instance with a minimum of 4 vCPUs and 16 GB memory, or for an m5 instance name.  
You can also search instances by using filters such as *instance category*. We recommend memory-optimized instances for database workload. You can search for them faster by using the instance category filter.

****Optimize CPU****  
You have the flexibility of specifying a custom number of vCPUs while using the same memory, storage, and bandwidth of a full sized instance. The default value is the same as the vCPU input specified for the machine specification.  
For example, a x1e.4xlarge instance currently offers 16 vCPU, by default. However, you can specify x1e.4xlarge with 4, 5, 6, 7, 8, 9,10, 12,14 Optimized vCPUs. This means BYOL customers can optimize vCPU-based licensing costs. The CPU optimized instance has the same price as the instance that iisn't optimized for CPU.

****Quantity****  
The default value is 1. This is the minimum number required.

****SQL passive node****  
A passive SQL Server node is one that's not serving SQL Server data to clients or running active SQL Server workloads. If you select this check box and you bring SQL Server 2014 and later versions to AWS with Software Assurance, you aren't required to license SQL Server on a passive node.

## Pricing strategy
<a name="estimate-workload-pricing"></a>

Your choices in the **pricing strategy** section determine the pricing strategy AWS Pricing Calculator uses to generate your estimate.

**Pricing model**  
The pricing model determines whether you're searching for a pay-as-you-use instance or an instance that you can reserve in advance. For Reserved Instance (RI) payment options, see **payment options**.  
The default value is `Standard Reserved Instances`. This is because it's the most common Amazon EC2 purchase, and it offers the flexibility with highest discount for most use cases.

**Reservation term**  
You purchase a reservation for the period of your contract when you reserve an RI. Choose either 1 or 3 years for your term. The default is set to 1 year. This is to save no costs.

**Payment options**  
Payment options determine when you pay for your RI reservation.  
**Full upfront** - You pay for the entire reservation upfront, resulting in a single payment but no monthly, recurring payments. This option provides the best discount.  
**Partial upfront** - You pay for a smaller, partial upfront fee along with monthly payments.  
**No upfront** - You only pay on a monthly basis.  
The default value is **No upfront**. It gives you the least costly start-up price.

## Cost details
<a name="estimate-workload-cost"></a>

The cost details section provides details for your workload.

**EC2 Instance costs**  
A summary of the itemized breakdown for an EC2 instance. Pause on each row to show additional information, such as instance type, operating system, SQL version, vCPU, memory, quantity, optimize CPU, and SQL passive node.

**Amazon EBS costs**  
The itemized cost breakdown for Amazon EBS.

**SQL bring your own license summary**  
A summary to clarify the number of cores for your BYOL SQL Server licenses.

# Tutorial: Generating estimates for Windows Servers and SQL Servers on EC2
<a name="estimate-workload-tutorial"></a>

This tutorial shows you how to use the Microsoft Windows Server and Microsoft SQL Server on Amazon EC2 in AWS Pricing Calculator to generate an estimate. 

## Procedure
<a name="estimate-workload-tutorial-process"></a>

**Topics**
+ [

### Step 1: Choose your AWS Region
](#estimate-workload-tutorial-region)
+ [

### Step 2: Choose your licensing and tenancy recommendation
](#estimate-workload-tutorial-step1)
+ [

### Step 3: Configure your machine specifications
](#estimate-workload-tutorial-step2)
+ [

### Step 4: Choose a pricing strategy
](#estimate-workload-tutorial-step3)
+ [

### Step 5: Review calculations and cost details
](#estimate-workload-tutorial-step4)
+ [

### Step 6: Add a Windows LI and SQL Server LI to your estimate
](#estimate-workload-tutorial-step5)

### Step 1: Choose your AWS Region
<a name="estimate-workload-tutorial-region"></a>

**To name your estimate and select your Region**

1. Open the **Configure Windows Server and SQL Server on Amazon EC2** section of AWS Pricing Calculator at [https://calculator.aws/\$1/createCalculator/EC2WinSQL](https://calculator.aws/#/createCalculator/EC2WinSQL).

1. Enter the following estimate description: `Workload_SQL_BYOL`.

1. Make sure that your location type is set to **Region**. Then, choose the Region `US East (Ohio)`.
**Note**  
All AWS resources are priced based on the Region you choose.

### Step 2: Choose your licensing and tenancy recommendation
<a name="estimate-workload-tutorial-step1"></a>

In this section, you can specify your license details to determine your cost-optimized tenancy qualifications. For more information about licensing and tenancy supported by AWS Pricing Calculator, see [Licensing and tenancy recommendations](windows-workload-estimates.md#estimate-workload-tenancy).

**To determine your licensing and tenancy recommendations for this example**

1. Open the **Configure Windows Server and SQL Server on Amazon EC2** section of AWS Pricing Calculator at [https://calculator.aws/\$1/createCalculator/EC2WinSQL](https://calculator.aws/#/createCalculator/EC2WinSQL).

1. In the **Licensing and tenancy recommendation** section, clear the **Windows Server** checkbox.

1. Under **SQL Server**, select both options.

1. Keep the default selection of the shared tenancy.

   You will notice that the recommended tenancy options are **Shared** and **Dedicated Hosts**. You can use the [Amazon EC2 Dedicated Hosts calculator](https://calculator.aws/#/EC2DedicatedHosts) to estimate Dedicated Host tenancy.

![\[Licensing and tenancy recommendation with Amazon EC2 shared tenancy selected\]](http://docs.aws.amazon.com/pricing-calculator/latest/userguide/images/t2_licensing_options_win_byol_sql.png)


### Step 3: Configure your machine specifications
<a name="estimate-workload-tutorial-step2"></a>

In this step, you can input machine specifications to configure your AWS Pricing Calculator estimate.

The following table provides an example workload scenario to show several capabilities in the AWS Pricing Calculator. You can use these values for the purpose of this tutorial.


| Host description | vCPUs | Ram | Storage (GB) | IOPS | Software | Optimize vCPUs | Quantity | Passive node count | 
| --- | --- | --- | --- | --- | --- | --- | --- | --- | 
| Server 1 | 16 | 800 | 5000 | 60000 | SQL Enterprise Edition | 16 | 10 | 5 | 
| Server 2 | 16 | 64 | 3000 | 15000 | SQL Standard Edition | 16 | 8 | 4 | 
| Server 3 | 8 | 16 | 1000 |  | SQL Web Edition | 8 | 10 | 0 | 
| Server 4 | 4 | 32 | 500 |  | Windows | N/A | 8 | N/A | 

**To specify your machine specifications for this example**

1. Open the **Configure Windows Server and SQL Server on Amazon EC2** section of AWS Pricing Calculator at [https://calculator.aws/\$1/createCalculator/EC2WinSQL](https://calculator.aws/#/createCalculator/EC2WinSQL).

1. In the **Configure machine specifications** section, choose the **Add new machine specification** button.

1. For **Machine description**, keep the name **Server 1**.

1. For **Operating system**, choose **Windows Server**.

1. For **SQL Server edition (BYOL)**, choose **SQL Server Enterprise**.

1. Under **Storage volumes per specifications**, enter the storage amount (GiB) as **5000** and **IOPS** as **60000**. 

   For more information, see [Machine specifications details](#estimate-workload-tutorial-step2-machinedetails).

1. For **Amazon EC2 instance type**, choose the **Obtain an Amazon EC2 instance type recommendation**. 

   For more information, see [Amazon EC2 instance type details](#estimate-workload-tutorial-step2-ec2details).

1. For **Optimize vCPU**, keep the optimize CPU value as `16`. 

   For more information, see [Benefits of Optimize vCPUs](#estimate-workload-tutorial-step2-optcpudetails).

1. For **Quantity**, enter **10**.

1. For number of passive instances, choose **5**. 

1. Choose **Add machine** to add more machine specification types. 

   For this tutorial, add the remaining three workloads from the example workload table.

#### Machine specifications details
<a name="estimate-workload-tutorial-step2-machinedetails"></a>

If you enter the storage size (GB) only, the calculator provides you with the most cost-effective Amazon Elastic Block Store (Amazon EBS) storage option. If you enter a value between **16000** and **64000** for IOPS, the AWS Pricing Calculator recommends the io2 EBS volume type. Anything value beyond that range, AWS Pricing Calculator recommends io2 Block Express with tiered pricing. For more information, see [Amazon EBS volume types](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-volume-types.html).

#### Amazon EC2 instance type details
<a name="estimate-workload-tutorial-step2-ec2details"></a>

You can choose **Obtain an Amazon EC2 instance type recommendation** for the server type specifications. AWS recommendations always default to the latest, cost-optimized instances for Windows Server and SQL Server workloads.

You can also choose **Search** for an Amazon EC2 instance type if you want the ability to filter the instance types. You can filter by instance category, memory, CPU, and other options.

#### Benefits of Optimize vCPUs
<a name="estimate-workload-tutorial-step2-optcpudetails"></a>

You have the flexibility to specify a custom number of vCPUs while using the same memory, storage, and bandwidth of a full-sized instance. This means that BYOL customers can optimize vCPU-based licensing costs. 

Even though the CPU optimized instance has the same price as the instance that's not optimized for CPU, it offers flexibility to choose the CPU count, so you can bring the right SQL Server license to avoid extra costs. For example, an `x1e.8xlarge` instance has 32 vCPUs by default. But you can specify `x1e.8xlarge` with Optimize CPU value to 16, 14, or 12. 

The passive SQL Server nodes allow for additional cost optimization. A passive SQL Server node doesn't serve SQL Server data or run active SQL Server workloads. If you bring SQL Server to AWS with Software Assurance, you aren’t required to license SQL Server on a passive node. 

### Step 4: Choose a pricing strategy
<a name="estimate-workload-tutorial-step3"></a>

In this step, you use the pricing strategy section in AWS Pricing Calculator to choose a pricing model.

**To choose a pricing strategy for this example**

1. Open the **Configure Windows Server and SQL Server on Amazon EC2** section of AWS Pricing Calculator at [ https://calculator.aws/\$1/createCalculator/EC2WinSQL](https://calculator.aws/#/createCalculator/EC2WinSQL).

1. In the **Choose a pricing strategy** section - under **Pricing model**, choose **Standard Reserved Instance**.

1. Under **Reservation term**, choose **1 year**.

1. Under **Payment options**, choose **No Upfront**.

**Note**  
This is a default pricing strategy that offers up to 75 percent savings over On-Demand pricing. For more information, see [Amazon EC2 pricing](https://aws.amazon.com/ec2/pricing/).

### Step 5: Review calculations and cost details
<a name="estimate-workload-tutorial-step4"></a>

At this stage in the example tutorial, you can view the breakdown your cost estimates.

**To view the calculation and cost details of this example**

1. Open the **Configure Windows Server and SQL Server on Amazon EC2** section of AWS Pricing Calculator at [ https://calculator.aws/\$1/createCalculator/EC2WinSQL](https://calculator.aws/#/createCalculator/EC2WinSQL).

1. To view the breakdown of the calculations, select the arrow next **Show calculations**.

1. The view the cost details of the EC2 instance, storage, and BYOL SQL license specifications, select the arrow next to **Cost details** section.

1. After you review the calculations and cost details of all four example workloads, choose **Save and add service**.

At this point, you successfully estimated workload costs for Windows Server License Included and SQL Server Bring Your Own License (BYOL) licensing. If want to clone your existing estimate to generate an estimate for the License Included option for an SQL Server, navigate to [Step 6: Add a Windows LI and SQL Server LI to your estimate](#estimate-workload-tutorial-step5).

### Step 6: Add a Windows LI and SQL Server LI to your estimate
<a name="estimate-workload-tutorial-step5"></a>

**To add a Windows LI and SQL Server LI to your estimate**

1. Navigate to the **My Estimate** section in AWS Pricing Calculator.

1. Select the checkbox of the service you want to duplicate. Then, choose **Duplicate**.

1. Choose the **Edit** icon on the duplicate version of the estimate.

1. For the **Estimate details** description, enter **Workload\$1LI**.

1. Keep the **Region** as is.

1. In the **Licensing and tenancy recommendation** section, keep the **Windows Server** and **SQL Server** check boxes cleared.

1. For the SQL Server section, review and adjust the machine specifications.

1. Review the new monthly cost estimate and aggregated monthly costs.

1. Choose **Update**.

On the** My Estimate** page, you can now compare the price under both the licensing options. In this example, the shared tenancy with Windows License Included and SQL Server BYOL option is approximately half of the cost of shared tenancy with Windows License Included and SQL Server License Included.

You have now completed the tutorial for using the Microsoft Windows Server and Microsoft SQL Server to generate a pricing estimate.

# Generating estimates for Windows Servers and SQL Servers on EC2 Dedicated Hosts
<a name="windows-workload-ec2"></a>

You can use the workload calculator in AWS Pricing Calculator as a guide to the AWS tenancy qualifications for Microsoft Windows Server and SQL Server on Amazon Elastic Compute Cloud (Amazon EC2). You can use the workload calculator to estimate AWS cost using minimal information or generate a rough estimate.

For options for using Microsoft software licenses on the AWS Cloud, see [Microsoft Licensing on AWS](https://aws.amazon.com/windows/resources/licensing/).

**Topics**
+ [

## Procedure
](#windows-sql-ec2-estimate)
+ [

## Licensing and tenancy recommendations
](#estimate-workload-tenancy-ec2)
+ [

## Machine specifications
](#estimate-workload-configure-ec2)
+ [

## Review dedicated hosts
](#estimate-dedicatedhost-ec2)
+ [

## Pricing strategy
](#estimate-workload-pricing-ec2)
+ [

## Cost details
](#estimate-workload-cost-ec2)
+ [

# Bulk upload instructions for Dedicated Hosts
](estimate-bulk-upload-ec2.md)

## Procedure
<a name="windows-sql-ec2-estimate"></a>

**To generate an estimate for Windows Server and SQL Server on Amazon EC2 Dedicated Hosts**

1. Open AWS Pricing Calculator at [https://calculator.aws/\$1/](https://calculator.aws/#/).

1. Choose **Create estimate**.

1. Do one of the following:
   + Under **Windows Server and SQL Server on Amazon EC2**, choose **Configure**.
   + From the **Find service** search bar, search for **Windows Server and SQL Server on Amazon EC2**. Then, choose **Configure**.

1. On the **Configure Windows Server and SQL Server on Amazon EC2** page, choose your customized settings.
   + For more information about license and tenancy options, see [Licensing and tenancy recommendations](#estimate-workload-tenancy-ec2).
   + For more information about machine specifications, see [Machine specifications](#estimate-workload-configure-ec2).
   + For more information about pricing strategy options, see [Pricing strategy](#estimate-workload-pricing-ec2).
   + For more information about reviewing dedicated hosts, see [Review dedicated hosts](#estimate-dedicatedhost-ec2).
   + For more instructions about cost details, see [Cost details](#estimate-workload-cost-ec2).
   + For instructions on how to bulk upload your machine specifications for Dedicated Hosts, see [Bulk upload instructions for Dedicated Hosts](estimate-bulk-upload-ec2.md). 

1. Choose **Save and add service** or **Save and view summary**.

## Licensing and tenancy recommendations
<a name="estimate-workload-tenancy-ec2"></a>

You can determine your AWS licensing and tenancy options for your workload through your choices for Windows Server and SQL Server licensing inputs. The licensing options include AWS provided licenses with License Included (LI) offerings. They also include your existing licenses with Bring Your Own License (BYOL) offerings for optimal cost savings. You can identify which is the most suitable cloud tenancy.

The following table shows the AWS licensing and tenancy scenarios supported by AWS Pricing Calculator.


| Windows Server | SQL Server | AWS tenancy | 
| --- | --- | --- | 
| LI | LI | Shared tenancy | 
| LI | BYOL | Shared tenancy or Dedicated Hosts | 
| BYOL | BYOL | Dedicated Hosts | 
| BYOL | LI | Not supported | 

## Machine specifications
<a name="estimate-workload-configure-ec2"></a>

Based on your choice of machine specification, we recommend that you select the Amazon EC2 instance that AWS Pricing Calculator uses to generate an estimate for your cost. You can also select another instance or instances of your choosing or add multiple machine specifications for a workload.

This section defines the terms that are mentioned in the **Configure machine specifications** section.

****Machine description****  
A description for the machine. This is generally a hostname identifier. If you don't know the hostname identifier, specify unique software components that run on this machine—for example, `WebApp DB1` or `Webserver 1`.

****Operating system****  
Depending on your tenancy qualification, you can choose an operating system with a licensing option. The default value is `Windows`.

****SQL Server edition****  
Depending on your tenancy qualification, you can choose a SQL Server with licensing option. The default value is `SQL Standard`.

****vCPU, Memory****  
Enter the number of vCPUs and memory inputs for your machine configuration. For example, 4vCPU and 8GB of memory.

****Quantity****  
The default value is 1. This is the minimum number that's required.

## Review dedicated hosts
<a name="estimate-dedicatedhost-ec2"></a>

The **Review dedicated hosts** table shows your recommended dedicated hosts instance family based on your inputs. You can see details such as host family and description, instances, license count, and used capacity (virtual cores). List count shows the license needed for a specific dedicated host.

Choose the instances to see the machines that are optimally packed within a single dedicated host.

By choosing **Download CSV**, you can download the dedicated host, instance, and license information.

## Pricing strategy
<a name="estimate-workload-pricing-ec2"></a>

Your choices in the **pricing strategy** section determine the pricing strategy that AWS Pricing Calculator uses to generate your estimate.

**Pricing model**  
The pricing model determines whether you're searching for a pay-as-you-use instance or an instance that you can reserve in advance. For Reserved Instance (RI) payment options, see **payment options**.  
The default value is `Standard Reserved Instances`. This is because it's the most common Amazon EC2 purchase, and it offers the flexibility with highest discount for most use cases.

**Reservation term**  
When you reserve an RI, you purchase a reservation for the period of your contract. For your contract term, choose 1 year or 3 years. By default, a term is 1 year. This is to save costs.

**Payment options**  
Payment options determine when you pay for your RI reservation.  
**Full upfront** - You pay for the entire reservation upfront, resulting in a single payment but no monthly, recurring payments. This option provides the best discount.  
**Partial upfront** - You pay for a smaller, partial upfront fee along with monthly payments.  
**No upfront** - You only pay on a monthly basis.  
The default value is **No upfront**. It gives you the least costly start-up price.

## Cost details
<a name="estimate-workload-cost-ec2"></a>

The cost details section provides details for your workload.

**EC2 Instance costs**  
A summary of the itemized breakdown for an EC2 instance. Pause on each row to show additional information, such as instance type, operating system, SQL version, vCPU, memory, quantity, optimize CPU, and SQL passive node.

**Amazon EBS costs**  
The itemized cost breakdown for Amazon EBS.

**SQL bring your own license summary**  
A summary to clarify the number of cores for your BYOL SQL Server licenses.

# Bulk upload instructions for Dedicated Hosts
<a name="estimate-bulk-upload-ec2"></a>

You can use bulk upload to upload your machine configuration, operating system, SQL server edition, quantity, vCPU, and memory in an excel file. Batch upload uploads this excel file to the AWS Pricing Calculator. To do this, use the provided excel template worksheet.

**To download the excel worksheet template**

1. Open AWS Pricing Calculator at [https://calculator.aws/\$1/](https://calculator.aws/#/).

1. Choose **Create estimate**.

1. Do one of the following:
   + Under **Windows Server and SQL Server on Amazon EC2**, choose **Configure**.
   + Search for **Windows Server and SQL Server on Amazon EC2** from the **Find service** search bar.

1. On the **Configure Windows Server and SQL Server on Amazon EC2** page under the **Bulk upload instructions** sections, choose **Download template**.

   For more information, see [Machine specifications](windows-workload-ec2.md#estimate-workload-configure-ec2).

1. Navigate to the downloaded file on your local machine.
**Important**  
Don't remove any columns from the template.  
Don't add any columns to the template.  
Don't change the position of the template worksheet.
**Tip**  
You can refer to the **Example** worksheet in the spreadsheet for an example data.

1. Choose **Upload file**.

1. Under the **Machine specifications** table, see the **Status** column to confirm if your template was uploaded correctly.
   + **Accepted** - The data that you entered is in the correct format. The data can be used for providing recommendations.
   + **Declined** - The data format isn't valid. You can see the upload fail reason from the same column. After you correct your file, upload again using the previous steps.

     If the declined fail reasons aren't addressed, these rows aren't included for recommendations on dedicated Hosts in the **Review dedicated hosts** table.

1. Use the Review dedicated hosts section to see details such as host family, host description, instances, license count, and used capacity. For more information, see [Review dedicated hosts](windows-workload-ec2.md#estimate-dedicatedhost-ec2).

1. Use the Dedicated Host costs section to see details for your workload.

   The costs table provides an itemized breakdown of the dedicated hosts with hourly cost, monthly cost per unit, and cost for the first twelve months included. All costs are shown in USD currency.

1. Use the **License(s) summary** section to clarify the list of licenses that you need to bring to AWS for the recommended dedicated hosts.

1. Choose **Save and add service** to save your estimate prices, and add additional services to the AWS Pricing Calculator.

# Generating Microsoft estimates with AWS Modernization Calculator
<a name="modernization-calculator-microsoft-workloads"></a>

AWS Modernization Calculator for Microsoft workloads provides a pricing estimate for modernizing your Microsoft workloads using open source and AWS cloud-native services deployed on AWS.

The calculator creates an estimate total cost of ownership for transforming your Windows and SQL server applications into a modern architecture. To use the calculator, you don't need an AWS account.

AWS Modernization Calculator for Microsoft workloads recommends modernized architecture for application patterns such as multi-tier, batch processing, CI/CD, or containerization. These recommendations are based on commonly adopted architectures by the AWS customer community. The calculator offers a reliable way to get modernization cost estimates without in-depth assessments. Using this information, you can conduct an in-depth assessment with Migration Hub Strategy Recommendations. For more information, see [What is Migration Hub Strategy Recommendations?](https://docs.aws.amazon.com/migrationhub-strategy/latest/userguide/what-is-mhub-strategy.html)

**Topics**
+ [

## Procedure
](#modernization-cal-process)
+ [

## Architecture category and pattern
](#step1-pattern)
+ [

## Architecture size
](#step2-size)
+ [

## Modernized architecture pattern
](#step3-architecture)
+ [

## AWS service configuration
](#step4-configuration)
+ [

## My Estimate
](#estimate)

## Procedure
<a name="modernization-cal-process"></a>

**To generate an estimate with AWS Modernization Calculator for Microsoft Workloads**

1. Open the AWS Modernization Calculator for Microsoft Workloads at [https://modernization.calculator.aws/microsoft/workload](https://modernization.calculator.aws/microsoft/workload).

1. In the **New estimate** section, add a description for this estimate. 

1. In the **Current application/workload location** section, choose the current location of where your application is deployed.

1. Select an **Architecture category** and an **Architecture pattern**. 

   For more information on architecture category and pattern, see [Architecture category and pattern](#step1-pattern).

1. Choose **Next**.

1. On the **Select an architecture size** page, you can select your architecture characteristics (optional) and sizing. 

   For more information, see [Architecture size](#step2-size).

1. Choose **Next**.

1. On the **Select modernized architecture pattern** page, select a modernized architecture pattern for your application. 

   For more information, see [Modernized architecture pattern](#step3-architecture).

1. Choose **Next**.

1. On the **Edit service configuration ** page, review the summary of recommendations. 

   For more information, see [AWS service configuration](#step4-configuration).

1. For an overview of your Microsoft estimate, choose **Save**. 

   For more information, see [My Estimate](#estimate)

## Architecture category and pattern
<a name="step1-pattern"></a>

You can specify the architecture category of your application by choosing from **Architecture pattern**, **Use case**, or **Custom**. The category selection provides further options to analyze your application.
+ **Architecture pattern** refers to a fundamental schema for software systems in an organization. It defines the structural composition of the program and the interactions between the elements. In most enterprises, some of the commonly found patterns include the following.
  + **Multi-tier** pattern has been a cornerstone architecture pattern for decades, and remains a popular pattern for user-facing applications. Multi-tier generally consists of a presentation tier, data tier, and logic tier. These three tiers can be hosted on the same or separate servers. This pattern provides a general framework to ensure decoupled and independently scalable application components can be separately developed, managed, and maintained.
  + **Batch processing** is the method computers periodically use to complete high-volume and repetitive data jobs. Certain data processing tasks, such as backups, filtering, and sorting, can be compute intensive and inefficient to run on individual data transactions. Instead, data systems process such tasks in batches. These tasks are processed during off-peak times such as the evening and overnight.
+ **Use case** includes grouped architecture patterns. This grouping represents a collaboration by different teams on performing tasks. Use cases are further categorized into the following.
  + **Software development** involves several steps including creating, testing, staging, and deploying software. In an organization, multiple teams collaborate as a group to create software.
  + **Container** provides a standard way to package your application's code, configurations, and dependencies into a single object. Containers share an operating system that's installed on the server and run as resource-isolated processes. This ensures quick, reliable, and consistent deployments, regardless of the environment. Containers are lightweight and provide a consistent and portable software environment for applications to run and scale virtually anywhere. Building and deploying microservices, running batch jobs for machine learning applications, and moving existing applications into the cloud are some of common use cases.
+ **Custom** category provides you with the option to build any custom architectures by selecting the relevant AWS services from the list. This is a suitable option if you're familiar with AWS services and their role in your application's architecture pattern.

## Architecture size
<a name="step2-size"></a>

This step includes a short questionnaire about the specifics of your application's architecture. All questions are optional. The calculator provides a sizing recommendation based on your answers. The default recommendation is **Small**.

If you choose to answer the questions, the calculator recommends a size. You can proceed with the recommended size or select any size that meets your business requirements.

## Modernized architecture pattern
<a name="step3-architecture"></a>

The calculator provides modernized architecture pattern options based on your inputs in preceding steps. You can download the pattern diagram to learn more.

If you see more than one option, you can choose the recommended or another pattern. If you have one recommendation without options, choose the recommended pattern to proceed to the next step.

## AWS service configuration
<a name="step4-configuration"></a>

This page provides a summary of recommendations. You can see a list of recommended AWS services. You can add or remove any service, and change the recommended settings of each service.
+ **AWS Region** has a drop-down list that you can select the Region where you want to host your modernized application from. The pricing of AWS services can differ by Region.
+ **Estimated cost** provides the total monthly cost of running a modernized application on AWS. The cost isn't intended as an actual price quote. It doesn't account for data transfer charges or any additional configurations offered by AWS services.
+ **AWS services** lists the recommended services for your modernized application. You can add or delete any service from this list. You can expand each service card to modify size and parameters for that service. You can also see the breakdown of cost for each service by expanding *Show calculation*, which is located in each service card.
+ Select **Save** to see a graphical presentation of estimate on **My Estimate** page.

## My Estimate
<a name="estimate"></a>

This page provides the estimate for your modernized application. You can do the following with this page:
+ Clone the same or add new workload to your estimate.
+ Increase or decrease the number of applications in a workload.
+ Change the recommended AWS services by editing a workload.
+ Add the cost of accessing Support to your estimate.
+ Export to an excel file or share your estimate by using a unique URL.

*If you retrieve and modify a shared estimate, you must save and share the modified version. The modifications aren't automatically added to your original estimate.*