- Newest
- Most votes
- Most comments
There are a few potential explanations for the inconsistencies you're seeing in your data transfer charges:
-
Timing discrepancies: The difference between Cost Explorer and the billing report could be due to how data is processed and when it becomes available in different AWS billing tools. Cost Explorer may have a slight delay in showing the most recent data.
-
Free tier usage: The AWS Free Tier typically includes 100 GB of outbound data transfer aggregated across all services. It's possible that you exhausted this limit earlier than expected, perhaps due to usage from other AWS services. The sudden jump from free tier to charged usage could occur if you hit this limit.
-
Inter-region data transfer: The charge you're seeing for data transfer between regions ($0.086 per GB) suggests that some of your traffic is moving between different AWS regions. This is typically more expensive than data transfer to the internet and is not covered by the free tier.
-
Billing granularity: AWS often bills in hourly increments, which could explain why you see charges starting precisely at midnight.
-
Public IP charges: Starting from February 2024, AWS began charging for public IPv4 addresses. This new charge could be contributing to what appears to be unexpected data transfer costs.
To address these issues and get a clearer picture of your usage:
-
Use AWS Cost Explorer with finer-grained filters to break down your usage by service, usage type, and time period.
-
Check for any resources in other regions using EC2 Global View.
-
Verify that you don't have any lingering resources like EBS volumes or snapshots from terminated instances.
-
Consider using CloudWatch to monitor your NetworkIn and NetworkOut metrics for a more detailed view of your data transfer.
-
If you're still unsure about the charges, it's best to open a support case with AWS for a detailed investigation of your account's usage and billing.
Remember that data transfer charges can be complex, especially when dealing with inter-region transfers and public IP usage. Optimizing your architecture to minimize data movement between regions and to the internet can help reduce these costs.
Sources
Data Transfer Charges | AWS re:Post
Discrepancy in Lightsail Data Transfer Out Charges Despite Below-Allowance Usage | AWS re:Post
Unexpected billing because of EC2, VPC, and Data Transfer | AWS re:Post
Hi,
Since this is of a detailed billing and pricing nature, I'd suggest opening a support case directly with our Billing Support team. You can do so via this link: Billing Support.
They have the tools and may be able to really break this down for you.
-Dino C.
Relevant content
- asked 2 years ago
- asked 2 years ago
- asked a year ago
- AWS OFFICIALUpdated 6 months ago
From the list of potential explanations, for few points below are the explanations
Time discrepency - The support team has notified me about the gap of 24 hours which it takes usually to update the records. It still doesn't make sense for the month of April, the free tier limit on the Cost and Usage Analysis > Free Tier section, for the Data Transfer seems to have reached only 92 GB and not have crossed 100GB limit as suggested by the billing report. And I don't see any cost for that as well. Even if this is a normal issue in Billing tools, it doesn't change the descrepancy in the data provided.
and 4. 100 GB is a lot to be exhausted in even 1 hour given the user and event count on my application - which I track through analytics services, which is only in 100s in a day. So I don't see how granularity affects this issue of exhausting all the resources (and mind you the usage in the report still is less than 100GB before it incuring a positive charge which is still not explained).
I checked in the EC2 global view, there is no chargeable resource present in any other region. I just have these in other regions - single VPCs, some subnets, single security groups. And that's it.
On the EC2 service Free tier page it's mentioned that this is the part of free tier - "750 hours per month of public IPv4 address regardless of instance type". Now, the only public IPV4 address I am using is the one I got with EC2 instance by default as part of this free tier.