Saving plan is not being applied for 3-4 months and I am keeping billed full amount.

I understand your concern about your t4g Savings Plan showing 0% utilization despite being active. There are several common reasons why a Savings Plan might not be applying as expected. First, verify that you're running t4g instances (which are ARM-based Graviton2 instances) in the same AWS Region where you purchased the Savings Plan. Savings Plans are region-specific and won't apply to instances in other regions. Second, check that your t4g instances are actually running during the billing period - Savings Plans only apply to active usage. Third, ensure your hourly commitment amount matches or exceeds your actual t4g usage. If your instances cost less per hour than your commitment, you'll see underutilization but still get the discount on what you're using. If your usage exceeds the commitment, the excess will be billed at On-Demand rates. Fourth, confirm you're looking at the correct time period in the Cost Explorer - there can be a delay in utilization data appearing. Also, be aware that Savings Plans apply automatically in the background to eligible usage, so even if utilization shows 0%, check your actual EC2 bills to see if discounted rates are being applied. To get specific help with your account, I recommend opening a case or adding correspondence to your existing case in the AWS Support Center at https://console.aws.amazon.com/support/. The support team can review your specific account configuration, Savings Plan details, and billing to identify exactly why the plan isn't applying as expected.

Hi,

I apologize for the concern here. Reach out to our Account & Billing team through our Support Center: go.aws/support-center.

They'll be happy to take a look and see what's going on.

- Sage A.

EC2 Instance Savings Plans are region-locked and instance-family-locked, so a t4g plan won't apply to anything other than t4g instances running in the exact region you selected at purchase. After 3-4 months at 0% utilization, the most likely culprits are one of three things: your t4g instances moved to a different region than the plan covers, you switched to a different instance family (t3, m5, etc.) and those don't qualify, or if you're in an AWS Organization, Savings Plans sharing got turned off so the plan can't cover usage in other linked accounts.

Quick free check: go to Billing & Cost Management, open Savings Plans, click Inventory, select your plan, and view the utilization report. That'll show you exactly which hours had zero matching usage. Then check Cost Optimization Hub if you haven't - it'll flag the under-utilized plan directly.

Two things would help narrow this down fast: which region did you purchase the plan for, and are your t4g instances actually running in that same region? Also, are you on a standalone account or inside an AWS Organization?

I can put together a short written diagnosis with exact fix steps once I see the plan details. Happy to do that if you drop the region and account setup here.