Violations to EC2 Saving plans

Great question, Mark. When you commit to an EC2 Instance Savings Plan for a specific instance family like t3, the plan will not be cancelled if you create instances from a different family, such as t2. However, it's important to understand how the savings will apply in this scenario:

1. Your EC2 Instance Savings Plan for the t3 family will continue to be active and apply to any t3 instances you use in the specified region.

2. The t2 instance you create will not be covered by your t3 EC2 Instance Savings Plan. It will be charged at the regular On-Demand rate.

3. Your commitment to the t3 family remains unchanged, and you will continue to be billed for that commitment regardless of whether you fully utilize it with t3 instances.

4. The savings from your plan will only apply to the t3 instances you use, up to the amount of your hourly commitment.

It's worth noting that if you want more flexibility across instance families, you might consider a Compute Savings Plan instead. Compute Savings Plans offer slightly lower discounts but apply to EC2 instances regardless of family, size, or region, as well as to Fargate and Lambda usage.

Remember, the terms of a Savings Plan commitment can't be changed after purchase. If your usage patterns change significantly, you may want to consider purchasing additional Savings Plans to cover new types of usage rather than trying to modify existing plans.

To maximize your savings and ensure you're using the most appropriate plan for your needs, it's a good practice to regularly review your usage patterns and adjust your Savings Plan strategy accordingly.

Sources
Savings Plans types - Savings Plans
Savings Plans - Amazon EC2 Reserved Instances and Other AWS Reservation Models