Hight cost of AWS

I understand your concern about the unexpected high cost and depletion of your AWS credits. This situation can be frustrating, especially when you believe your website wasn't live. Here are some possible explanations and steps you can take:

1. Check your AWS account activity: Even if your website wasn't live, you may have had resources running in the background. AWS charges for resources that are provisioned, regardless of whether they're actively serving traffic.

2. Review your billing details: Use the AWS Cost Explorer or check your detailed billing statement to identify which specific services consumed your credits. This will give you a breakdown of where the charges came from.

3. Look for unexpected or forgotten resources: Sometimes, developers forget to terminate test environments or leave resources running unintentionally. Check for any EC2 instances, databases, or other services that might be active.

4. Verify your Free Tier usage: If you were relying on Free Tier services, ensure you didn't exceed the limits, as this can lead to unexpected charges.

5. Set up billing alerts: For future protection, configure AWS Budgets to alert you when your costs or credit usage approaches certain thresholds.

6. Contact AWS Support: If you're unable to identify the cause of the high charges or believe there's an error, reach out to AWS Billing and Account Support. They can provide a detailed explanation of the charges and potentially assist with resolving any issues.

Remember, AWS credits are consumed based on your usage of AWS services. It's crucial to regularly monitor your account activity and shut down any unnecessary resources to avoid unexpected costs.
Sources
unexpected billing price | AWS re:Post
High Billing fee | AWS re:Post
AWS Credit Usage | AWS re:Post