Savings Plan suggestion from m4 to r5 instance family

Unfortunately, it's not possible to directly transfer or modify an existing Savings Plan from one instance family (like m4) to another (like r5). Savings Plans are commitments to a specific instance family or compute usage, and they cannot be changed after purchase. However, there are a few options you can consider to manage this transition:

1. If you have an EC2 Instance Savings Plan for m4 instances: You'll need to continue using this plan for m4 instances until it expires. For your new r5 instances, you have two choices: a) Run them at On-Demand prices until your current plan expires. b) Purchase a new Savings Plan specifically for r5 instances.

2. If you have a Compute Savings Plan: This is more flexible and can automatically apply to your new r5 instances without any changes needed. Compute Savings Plans apply across different instance families, sizes, regions, and even to services like Fargate and Lambda.

For the most cost-effective solution moving forward, you might want to consider purchasing a Compute Savings Plan for your future needs. Compute Savings Plans offer up to 66% savings compared to On-Demand pricing and provide the flexibility to change instance families (like moving from m4 to r5) without any manual intervention.

Remember, your existing Savings Plan will continue to apply to any m4 instances you're still running. For optimal cost management, you can:

1. Continue using m4 instances where possible to utilize your current Savings Plan.
2. Gradually transition to r5 instances as needed.
3. Consider purchasing a new Compute Savings Plan to cover your growing r5 usage.

It's also a good practice to regularly review your usage patterns and adjust your Savings Plan strategy accordingly to maximize your savings as your infrastructure needs evolve.

Sources
EC2 Instance Savings Plan VS Flexible reserved instance | AWS re:Post
Violations to EC2 Saving plans | AWS re:Post
Savings Plans - Amazon EC2 Reserved Instances and Other AWS Reservation Models

Hi, When transitioning from m4 to r5 instances while having an existing Savings Plan, it's important to understand that AWS Savings Plans cannot be modified, transferred, or canceled once purchased. You must continue paying for your existing m4 Savings Plan commitment until its term ends. For the new r5 instances, you'll need to purchase a separate Savings Plan. The recommended approach is to maintain your existing m4 Savings Plan till it ends and simultaneously purchase a new plan specifically for r5 instances. Consider opting for a Compute Savings Plan instead of an Instance Savings Plan for future purchases, as it offers more flexibility across instance families. Before committing to a new plan, use AWS Cost Explorer to analyze your usage patterns and determine optimal coverage. Start with a smaller commitment for r5 instances and adjust based on actual usage. To manage costs effectively, consider partial upfront payment options and regularly monitor the utilization of both plans. This dual-plan approach, while not ideal, is currently the best way to manage the transition between instance families while maintaining cost savings.

For detailed guidance on Savings Plans management, refer to AWS documentation at https://docs.aws.amazon.com/savingsplans/latest/userguide/what-is-savings-plans.html.