Bill is too high

I understand your concern about the unexpectedly high charges for a seemingly inactive website. Even if your site only has an "under construction" page, there are several reasons why you might be incurring significant costs:

1. Running resources: AWS charges for provisioned resources, even if they're not actively serving traffic. You may have services running in the background that you're unaware of.

2. Instance type: The size and type of your EC2 instance can greatly affect costs. If you're using a larger instance than necessary for a simple static page, it could lead to higher charges.

3. Database services: If you have a database set up (like RDS or Aurora), it can contribute significantly to your bill, especially if it's a larger instance type not covered by the free tier.

4. Storage: Persistent storage like EBS volumes or S3 buckets can accumulate charges over time.

5. Free Tier expiration: If you've been using AWS for over a year, your Free Tier benefits may have expired, leading to charges for previously free services.

To address this issue:

1. Review your AWS Billing console to identify which specific services are generating costs.

2. Check for any running instances, databases, or other active services that might not be necessary.

3. Ensure you've properly terminated (not just stopped) any unused resources.

4. Consider downsizing your resources to match your current needs.

5. Set up AWS Budgets to alert you when costs approach certain thresholds.

If you're still unsure about the charges after reviewing your account, it's advisable to contact AWS Billing and Account Support for a detailed explanation of your bill. They can help identify any unexpected resource usage and potentially assist in resolving billing issues.
Sources
Hight cost of AWS | AWS re:Post
Insanely high charge for idling services | AWS re:Post
Confused Billing | AWS re:Post