- 新しい順
- 投票が多い順
- コメントが多い順
Hi Umar,
Could you check the concept of the charge on the AWS Billing dashboard? That will give us a clue to understand where those $3 come from.
While you've been careful to use only free tier resources, there are a few reasons why you might still see a small charge on your AWS account:
-
Not all components of your setup may be covered by the free tier. For example, while EC2 instances might be free, associated resources like Elastic IP addresses or certain types of storage could incur charges.
-
The Application Load Balancer (ALB) is typically not included in the free tier and can result in charges.
-
Even if you delete resources before logging off, there might be pro-rated charges for the time they were active.
-
Some services may have usage limits within the free tier, and exceeding these limits, even slightly, can result in charges.
To address this issue:
-
Review your detailed billing statement in the AWS Billing and Cost Management Dashboard to identify which specific services are generating charges.
-
Double-check that all resources, including associated components like EBS volumes or Elastic IPs, are fully terminated and not just stopped.
-
Be aware that while EC2 instances might be free tier eligible, other components of your architecture (like the load balancer) may not be.
-
Set up AWS Budgets and billing alerts to notify you when you're approaching free tier limits or starting to incur costs.
If you believe the charges are in error or you need further clarification, you can open a support case with AWS Billing Support. They can provide a detailed breakdown of the charges and potentially offer guidance or, in some cases, a one-time courtesy credit if you're a new user who unintentionally incurred charges while learning.
Sources
Charged for AWS despite using Free tier | AWS re:Post
Questions about the AWS free tier | AWS re:Post
Aws charging me for services | AWS re:Post
Hello,
Sorry for any confusion with this. Here's an article to help you pin down unexpected charges: http://go.aws/resources-unexpected-charges. There is also this resource to help you avoid them in the future: https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/avoid-charges-after-free-tier.html.
Feel free to open a support case with our Billing team for additional help or guidance: http://go.aws/support-center.
— Ann D.
関連するコンテンツ
- 質問済み 1年前
I figured out It was a NAT Gateway that I forgot to delete. This is so frustrating you never know what you leave even for learning purposes. I have imposed a zero-budget now, hopefully I should know when something like this happens.