- Le plus récent
- Le plus de votes
- La plupart des commentaires
Although there is free tier in aws, it does not mean free all the time. AWS Free Tier has specific limits and conditions which you need to be clear.
If you open a support ticket in AWS support and explain your situation, they may provide you with a refund for your charges.
Although you my or may not be refunded, You may still incure charges in future if you have other services running. Since you said you are using free tier but are incurring more than 1 $ verify why were you charged. You can do that by going to Bills. Delete the resource associated with the charge. Second, set up AWS budgets and cost anomoly detection too with low threshold like .01 cents, which will help you take action proactively before you are charged high amount in future.
I understand your concern about unexpected charges on your AWS account. While AWS offers a Free Tier for many services, there are situations where you might incur charges even when using what you believe to be free services. Here are a few points to consider:
-
The Free Tier has specific limits and conditions. For example, EC2 offers 750 hours per month of a t2.micro instance (or equivalent) for 12 months. Exceeding these limits can result in charges.
-
Some resources, like Elastic IP addresses or certain types of storage, may not be covered by the Free Tier and can incur charges even when associated with a free tier instance.
-
Stopping an EC2 instance doesn't always stop all charges. Associated resources like EBS volumes may continue to incur costs.
-
Using services or resources not covered by the Free Tier, even unintentionally, can lead to charges.
Unfortunately, AWS typically does not offer refunds for used services, even if the usage was unintended. However, you can take the following steps:
-
Review your usage in the AWS Billing and Cost Management Dashboard to understand which services caused the charges.
-
Terminate or adjust any resources that are generating unexpected costs.
-
Contact AWS Support directly by creating a billing support case in your Support Center. Explain that you're a new user learning the platform and weren't aware of potential charges. While refunds aren't guaranteed, AWS Support may be able to provide guidance or, in some cases, offer a one-time courtesy credit.
-
For future protection, set up AWS Budgets and billing alerts to notify you when you're approaching Free Tier limits or incurring costs.
Remember, it's crucial to monitor your usage regularly and stay informed about which services are covered by the Free Tier to avoid unexpected charges in the future.
Sources
Unexpected AWS Charges on My Free Tier Account | AWS re:Post
Understanding unexpected charges - AWS Billing
Billing misunderstand | AWS re:Post
Contenus pertinents
- demandé il y a 2 ans
- demandé il y a 2 mois
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 7 mois
The most important thing when you see unexpected charges: go to Cost Explorer, group by 'Service', and sort by amount descending. Then look at the second-highest line item — it's almost never what you expect. The top causes of hidden charges that budget alerts miss: (1) NAT Gateway data processing fees — appear as 'Data Transfer' but can be $0.045/GB with zero warning, (2) CloudWatch log ingestion without a retention policy — grows silently, (3) Stopped EC2 instances still billing for attached EBS volumes. For any dev/learning account, the most effective protection is setting Lambda reserved concurrency to a hard cap and enabling CloudWatch cost anomaly detection with a $1 threshold. Neither of these stop charges completely, but they reduce the blast radius significantly.