Cost and licensing
At a high level, the cost of migrating a SAS workload to AWS assumes establishing a new environment on AWS. The cost includes accounting for personnel time and effort as well as provisioning computing resources and licensing software for the new environment.
SAS licenses
Selecting the appropriate size instance type for the SAS license is an important consideration. In general, SAS licensing is based on the number of physical CPUs on the host machine(s). In comparison, AWS typically specifies the number of virtual CPUs (vCPUs, or hyperthreading) for its instance types. As a rule, for the target destination, select an Amazon Elastic Compute Cloud (Amazon EC2) instance that has twice the number of vCPUs as compared to the physical CPUs in the source environment. See Optimizing CPU options in the Amazon EC2 documentation for more information about optimizing vCPU-based licensing costs.
Another consideration is the cost of running two environments (source and target) at the same time, while getting the value of only one environment. SAS offers two policies to help reduce the cost of migration efforts like this, depending on the exact circumstances involved: policy for upgrading SAS software, and policy for testing new hardware.
Policy |
Description |
Duration |
---|---|---|
Upgrading SAS software |
SAS allows all customers who are upgrading to a new production release to run two parallel copies of the licensed software (the old release and the new release) for 180 days (6 months) at no additional charge. For metered offerings, customers can run two parallel copies of the licensed software, but both will be metered for billing purposes. |
180 days |
Testing new hardware |
The following scenarios are covered by SAS evaluation paperwork and are offered free of charge for a limited test period. The standard test period for each scenario is 30 days.
|
30 days |
Note
Test machines are defined as hardware the customer is responsible for that is used to run SAS software in an evaluation environment to verify quality and accuracy of data output.
Contact your SAS account representative for more information specific to your site and license.
Cost estimates for AWS services
AWS Pricing Calculator
Note
Evaluate the ratio of vCPU to I/O bandwidth and vCPU to ephemeral storage per AWS instance type. Choose the instance that provides the best ratio of those two factors for your SAS Grid processing computing needs.
Workload sizing:
-
Small
– SAS Grid without high availability in a single Availability Zone 2x SAS Grid (i3en.6xlarge instance), 1x Metadata Server, 1x Web Server
-
Medium
– SAS Grid with high availability in a single Availability Zone 4x SAS Grid (i3en.12xlarge instance), 3x Metadata Server, 2x Web Server
-
Large
– SAS Grid with high availability in a single Availability Zone 8x SAS Grid (i3en.12xlarge instance), 3x Metadata Server, 2x Web Server