The following table provides links to pricing information for each public cloud vendor. For vendors with multiple pricing models, the table explains which pricing model Commander uses to project public cloud costs.
Commander projected public cloud costs include the following:
- The various instance type costs, which typically include CPU and memory.
- Operating system cost differences (included in the instance type cost).
- Storage costs, as defined in the table below.
- Per-region pricing (where applicable).
Commander uses the key costs for supported public cloud vendors and provides a good comparison baseline. There is, however, wide variability and a large set of service offerings, so Commander doesn't cover the exhaustive list. Items like prepaid volume discounts, networking and I/O, and storage and backup costs are treated differently by the various cloud providers.
How Commander calculates public cloud instance and storage cost
Cloud Vendor | On Demand Instance Pricing | Storage Pricing |
|---|---|---|
Amazon Web Services | Amazon EC2 Pricing / Amazon EC2 Previous Generation Pricing Commander uses the individual per-region prices in EC2's "On-Demand Instances" pricing. Amazon Elastic Load Balancing Pricing . Costs vary per region. Commander uses the Elastic Load Balancer per-hour costs. Amazon RDS Pricing.Amazon RDS Previous Generation Pricing / Amazon GovCloud RDS Pricing . Costs vary per region, database type and license model. Commander uses the On Demand DB Instance costs for Single-AZ and Multi-AZ instances. | Amazon EC2 Pricing / Amazon EBS Pricing Amazon EC2 and RDS storage costs vary by region and storage type. Storage costs depend on disk size and Provisioned IOPS. Commander doesn't consider volume discounts. |
Azure | Commander uses regional US Dollar pricing as well as Azure's "Pay-as-you-go Plans". Commander supports promotional instance types available at the time of publication. | Microsoft Azure Managed Disks Pricing Microsoft Azure Unmanaged Storage Pricing Commander doesn't consider volume discounts, temporary pricing promotions on storage, or Azure Hybrid Use Benefit. Due to an Azure limitation, costs for unmanaged standard (HDD) disks are based on allocated space, rather than used space. Commander uses US Dollar pricing. |
GCP Cloud Platform | Google Compute Engine Pricing Costs vary per region. | |
IBM Cloud | IBM Cloud Virtual Server Pricing Commander uses IBM Cloud's "Public" pricing for virtual servers. As a sample, Commander uses several of IBM Cloud's resource configurations to create predefined instance types for three regions: NA South (Dallas - DAL05), Europe (Amsterdam - AMS01), and Asia-Pacific (Hong Kong - HKG02). | IBM Cloud Block Storage Pricing Commander uses IBM Cloud's "SAN Storage" pricing. |
Rackspace | Commander uses Rackspace's Infrastructure Service Level pricing. | Rackspace Block Storage Pricing Commander uses Rackspace's "Standard Volumes" pricing. |
If you have a custom public cloud price list, create a case through the Snow Support Portal to help you update the costs accordingly.
Update Public Cloud List Prices
Public cloud prices used in Commander are updated with every release. To make sure your AWS, Azure and GCP list prices are current, you can use the command workflow Update Public Cloud List Prices. This workflow will update Commander with the latest cloud list prices. The workflow checks whether your list prices are current, then updates them if necessary. You can configure this workflow to run on a recurring schedule, so that your price list is always current. Before scheduling it, you'll need to add credentials using the following procedure.
Configure credentials for the Update Public Cloud List Prices workflow
Access: | Configuration > Command Workflows |
Available to: | Commander Roles of Superuser and Enterprise Admin |
Prerequisites:
- Install the Commander Legacy API (REST API v2) and fulfill all requirements for both the API and PowerShell if you haven't already done so. For more information, see the Knowledge Base topic Download Commander PowerShell Module for REST v2.
- Create a dedicated local Commander user with a Superuser or Enterprise Admin role and access rights on AWS and/or Azure cloud accounts. This account will be used for accessing the Commander Legacy API.
To configure credentials:
- On the Configuration page, select the Update Public Cloud List Prices workflow.
- Click Edit.
- In the Command Workflow Configuration dialog, click Next to go to Steps.
- For Credentials, either
- select the REST credentials that already exist and skip the remaining steps for adding credentials (skip to step 11)
- click the Add Credentials link.
- In the Add Credentials dialog, set the Credentials Type to Username/Password.
- For the Name field, enter
REST API. - Enter the Username and Password using the credentials for the dedicated local Commander account that you created in the prerequisites part of this procedure.
- Optional: Enter a Description.
The Category will be automatically set to System Credentials.
- Click OK.
- Back in the Command Workflow Configuration dialog, click Next until you reach the Summary page.
- Click Finish to complete the command workflow configuration.
OR
You can now run and schedule the Update Public Cloud List Prices workflow. For more information, see Run command workflows.