Migration – or how to optimize as you mean to go on
Migration is a highly technical process, so you require your AWS partner to be capable of building your cloud and helping you find the right pricing model because both are essential.
We shall take it as read that a poorly designed migration will have negative ramifications on performance and costs and focus on the choice of AWS contract.
The graphic below sets out the standard AWS pricing models and their respective advantages and disadvantages.
AWS Pricing Model Analysis
|
Pricing Model
|
Pros
|
Cons
|
|
On-Demand
|
No long-term commitment, flexible
|
More expensive than reserved pricing.
|
|
Reserved Instances
|
Significant savings (up to 72%).
|
Less flexibility
|
|
Savings Plans
|
Flexible savings across EC2, Lambda, and Fargate.
|
Commitment required (1 or 3 years).
|
|
Spot Instances
|
Extremely low cost (up to 90% cheaper).
|
Can be terminated by AWS at any time.
|
On-Demand is often a great “starter model” for businesses seeking to understand their cloud needs without incurring upfront costs. Once they do, it is straightforward to switch to another pricing model because the On-Demand option is highly flexible.
Whereas On-Demand lends itself well to applications that have unpredictable spikes in load, the Reserved Instances pricing model is suitable for running legacy applications that are predictable in their usage, which can be planned well in advance.
In this model, you can reserve instances for a period of one to three years at a discount of up to 72%. However, you are committed to these instances and pay for them even when you scale down.
In the Spot Instances pricing model, the situation is reversed: you bid for spare capacity on Amazon’s open market, leading to deep discounts of up to 90%. But if the capacity is not available, the Amazon EC2 Spot service can interrupt your instance, making this model suitable for businesses with advanced cloud-native development capabilities.
Amazon distinguishes various types of Savings Plans. Of these models, Compute Savings Plans are the most flexible as they can get you savings of up to 66% across EC2, Lambda, and Fargate – a serverless, pay-as-you-go computing engine. The attraction of this approach is that you benefit from discounted prices regardless of instance size, region, instance family, operating system, or tenancy.
EC2 Instance Savings Plans offer deeper savings of up to 72% in exchange for commitment to usage of individual instance families in a region. This automatically reduces your cost on the selected instance family in that region regardless of Availability Zone, size, operating system, or tenancy.
Businesses can also negotiate bespoke contracts, so-called AWS Private Pricing Agreements (PPAs), which we shall discuss in a separate section.
Your choice of contract is not set in stone. A huge aspect of AWS cost optimization is to monitor usage and potentially adjust or switch pricing models in light of your findings. The sooner you start embedding cloud control processes in your FinOps operations, the earlier you will be able to rightsize cost and consumption.
Finally, one technical aspect of migration with a bearing on AWS cost management is the development of a landing zone. The goal of a landing zone is to provide AWS users with a starting point for application or workload deployment. Landing zone accelerators allow businesses to see how costs are distributed across accounts—a hugely relevant insight that two-thirds of businesses do not currently have.