AWS Billing Query

I understand your concern about the unexpected high billing charges for your AWS account. This is a common issue for those using AWS for learning purposes.

To address your situation, I recommend taking these steps:

1. Immediately review and delete any resources you're no longer using to prevent further charges.

2. Use the Cost Explorer in the Billing and Cost Management console to identify which specific resources are incurring the higher costs.

3. Be aware that even stopped EC2 instances can still generate charges through associated resources like Elastic IP addresses or EBS volumes. You may need to terminate instances completely and delete associated resources.

4. Check for active services across all regions, including Lambda functions, CloudFormation stacks, RDS databases, S3 buckets, or Elastic Load Balancers.

5. Set up AWS Budgets and Billing Alarms to monitor your spending and avoid future unexpected charges.

6. Open a support ticket with AWS under the Account & Billing category. Explain that you're using AWS for learning purposes and request assistance with the unexpected charges. AWS support may be able to help you understand the charges or potentially offer assistance.

7. For future use, always check the pricing of services before using them, even in a learning context, and be vigilant about terminating resources you're not actively using.

Remember that while AWS offers some free tier services, many have limitations and can incur costs even during initial usage periods.
Sources
unexpected billing price | AWS re:Post
Billing inquiry | AWS re:Post
High Billing fee | AWS re:Post