Calculating Projected Public Cloud Costs
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.
On Demand Instance Pricing
Amazon Web Services
Commander uses the individual per-region prices in EC2's "On-Demand Instances" pricing.
Costs vary per region. Commander uses the Elastic Load Balancer per-hour costs.
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 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.
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.
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
Costs vary per region.
Commander uses IBM SoftLayer's "Public Node" pricing for cores.
Commander uses several of IBM SoftLayer's resource configurations to create predefined instance types for three regions: Central US (Dallas - DAL01), Europe (Amsterdam - AMS01), and Asia (Hong Kong - HKG02).
Commander uses IBM SoftLayer's "SAN Storage" pricing.
Commander uses Rackspace's Infrastructure Service Level pricing.
Commander uses Rackspace's "Standard Volumes" pricing.
Note: If you have a custom public cloud price list, contact Support (firstname.lastname@example.org) to help you update the costs accordingly.
Public cloud prices used in Commander are updated with every release and are in US dollars. 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.
Configuring credentials for the Update Public Cloud List Prices workflow
Configuration > Command Workflows
Commander Roles of Superuser and Enterprise Admin
- Install REST API v2 and fulfill all requirements for REST v2 and PowerShell if you haven't already done so. For more information, see Download vCommander REST Client in the Snow Globe user community.
- 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 REST v2.
- If you're using Commander 7.0.x, you need to download the workflow from our GitHub Workflows repository and then import it. See Importing workflows and workflow modules.
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.
The Category will be automatically set to System Credentials.
You can now run and schedule the Update Public Cloud List Prices workflow. For more information, see Running Command Workflows.