This KB article aims to outline the basic settings for each of these designs, providing a clear understanding of them.
The full set of settings can be downloaded as a spreadsheet attached to this page
Designer Lift and Shift_Infra Modernized values (1).xlsx
Lift and Shift/Hardware On Demand
The Lift & Shift design is engineered to provide a cloud recommendation that mirrors your current on-premises allocation. This design is typically used to ensure performance parity and a low-risk "As-Is" migration. It uses existing workload configurations and consumption data to provision One-to-one infrastructure mapping in the target environment, enabling migration without application or platform changes.
Design Logic: Cloudamize identifies the cloud instance that most closely matches the physical hardware specifications (vCPU and RAM) of the source machine. It prioritizes capacity matching over utilization optimization.
|
Pricing Plan Settings |
Setting |
Compute Tuning Settings |
Setting |
Storage Tuning Settings |
Setting |
Network Tuning Settings |
Setting |
|
Tenancy |
Shared |
CPU and Instance Family |
TRUE |
Storage Capacity Scaling |
100% |
Network Load Factor |
10% |
|
Licenses: BYOL |
FALSE |
Target Peak CPU Threshold |
80% |
Analyze Type |
3rd Standard Deviation |
Analyze Type |
2nd Standard Deviation |
|
Licenses: License Mobility through SA (For MSSQL) |
TRUE |
Analyze Type |
3rd Standard Deviation |
Max RAID Disk Numbers: |
|
|
|
|
License Optimization |
None |
Instance Family Grid |
EBS |
Unlimited |
|
|
|
|
Pricing Plan |
On-Demand |
Instance Type |
##### |
GP3 |
10 |
|
|
|
Region |
[Set on Assessment Launch] |
Workload-Based Tuning: RDS |
Enabled(not fully automatic tuning, uses predefined profile) |
GP2 |
10 |
|
|
|
Discount % |
0% |
Workload-Based Tuning: SAP |
TRUE |
ST1 |
0 |
|
|
|
Observed On-Time? |
TRUE |
|
|
SC1 |
0 |
|
|
|
On-time Hours Per Week |
FALSE |
|
|
IO1 |
Unlimited |
|
|
|
|
|
|
|
Credit-Based Storage: |
|
|
|
|
|
|
|
|
Does GP2 Consider Bucketless? |
FALSE |
|
|
|
|
|
|
|
Does SC1 Consider Bucketless? |
FALSE |
|
|
|
|
|
|
|
Does ST1 Consider Bucketless? |
FALSE |
|
|
Infrastructure Modernized/Workload OnDemand
The Modernize design is engineered for cost efficiency and resource optimization. It uses "Right-Sizing" logic to recommend cloud instances based on the actual observed utilization of the workload rather than the provisioned hardware.
Design Logic: Cloudamize analyzes the historical performance metrics of each machine and identifies the smallest possible cloud instance that can support the workload. This design typically results in a lower core count and lower projected costs by removing "zombie" or idle resources.
|
Pricing Plan Settings |
Setting |
Compute Tuning Settings |
Setting |
Storage Tuning Settings |
Setting |
Network Tuning Settings |
Setting |
|
Tenancy |
Shared |
CPU and Instance Family |
TRUE |
Storage Capacity Scaling |
100% |
Network Load Factor |
10% |
|
Licenses: BYOL |
FALSE |
Target Peak CPU Threshold |
80% |
Analyze Type |
3rd Standard Deviation |
Analyze Type |
2nd Standard Deviation |
|
Licenses: License Mobility through SA (For MSSQL) |
TRUE |
Analyze Type |
3rd Standard Deviation |
Max RAID Disk Numbers: |
|
|
|
|
License Optimization |
Optimize cost and reduce the number of cores |
Instance Family Grid |
EBS |
Unlimited |
|
|
|
|
Pricing Plan |
On-Demand |
Instance Type |
##### |
GP3 |
10 |
|
|
|
Region |
[Set on Assessment Launch] |
Workload-Based Tuning: RDS |
Enabled(not fully automatic tuning, uses predefined profile) |
GP2 |
10 |
|
|
|
Discount % |
0% |
Workload-Based Tuning: SAP |
TRUE |
ST1 |
0 |
|
|
|
Observed On-Time? |
TRUE |
|
|
SC1 |
0 |
|
|
|
On-time Hours Per Week |
FALSE |
|
|
IO1 |
Unlimited |
|
|
|
|
|
|
|
Credit-Based Storage: |
|
|
|
|
|
|
|
|
Does GP2 Consider Bucketless? |
FALSE |
|
|
|
|
|
|
|
Does SC1 Consider Bucketless? |
FALSE |
|
|
|
|
|
|
|
Does ST1 Consider Bucketless? |
FALSE |
|
|
If you have any queries, please get in touch with the helpdesk via our Helpdesk Portal or by email at helpdesk@cloudamize.com.