- 最新
- 最多得票
- 最多評論
I understand your concern about the unexpected bill you've received. As someone using AWS for learning purposes, it's important to be aware that even stopped EC2 instances and other resources can still incur charges.
To address your situation:
-
First, you need to identify which services are causing the charges. Use the Cost Explorer in the AWS Billing and Cost Management console to see a breakdown of your costs by service.
-
Stopping EC2 instances doesn't completely eliminate charges. Associated resources like Elastic IP addresses or EBS volumes may continue to generate costs. You should terminate instances and delete associated resources if you're not using them.
-
For Lambda functions and CloudFormation stacks, ensure you've deleted them completely, not just disabled them.
-
Check for any other active services across all regions, such as RDS databases, S3 buckets, or Elastic Load Balancers.
-
To delete resources, go to each service's console and remove them. For EC2, terminate instances and delete associated volumes and Elastic IPs. For Lambda, delete functions. For CloudFormation, delete stacks.
Regarding the $15 pending charge, AWS doesn't typically cancel charges for services that have been used. However, you can contact AWS Support directly through the AWS Support Center. Choose the "Account and Billing Support" category when creating your case. Explain your situation as a learner, provide details about your usage, and request assistance with the billing issue.
For future use, consider setting up AWS Budgets and Billing Alarms to monitor your spending and avoid unexpected charges. Also, be sure to check the pricing of services before using them, even in a learning context.
Remember, while AWS offers some free tier services, many services incur costs even during initial usage periods. Always be vigilant about terminating resources you're not actively using to minimize unexpected charges.
Sources
High Billing fee | AWS re:Post
unexpexted Billing | AWS re:Post
unexpected billing price | AWS re:Post
相關內容
已提問 3 年前
For a learning account, here's the fastest way to get to zero ongoing charges: (1) In EC2, check 'Elastic IPs' — unattached ones charge $0.005/hour. (2) In Lambda, check 'Functions' — any scheduled Lambda that errored and is retrying will keep billing. (3) In CloudFormation, delete any stacks you created during tutorials — they often leave behind resources the tutorial doesn't mention cleaning up. (4) In CloudWatch, delete any log groups with no retention policy set. For the future: the only reliable protection is setting a Lambda reserved concurrency limit of 100 (prevents runaway invocations) and a CloudWatch alarm on EstimatedCharges at $1 routed to your actual phone via SNS → Lambda → SMS. Budget alerts to email alone are almost always seen too late.