anomal cost AWS

Hello.

The specifications of EC2 and RDS may not be compatible with the free tier.
For EC2, the "t2.micro" instance type is eligible for the free tier. (If "t2.micro" is not available in the region, "t3.micro" is eligible for the free tier)
For RDS, "t2.micro" with a single AZ configuration is eligible for the free tier.
https://aws.amazon.com/free/?nc1=h_ls&all-free-tier.sort-by=item.additionalFields.SortRank&all-free-tier.sort-order=asc&awsf.Free%20Tier%20Types=*all&awsf.Free%20Tier%20Categories=*all

You should also check your bill to see what items you are being charged for.
For example, if you accidentally create a backup of EC2 or RDS, you may incur storage charges.

If you are unsure of the details, we recommend that you open a case with AWS Support under "Account and billing".
Inquiries under "Account and billing" can be made free of charge.
https://docs.aws.amazon.com/awssupport/latest/user/case-management.html

Hi,

Usage Beyond Free Tier Limits: The AWS Free Tier comes with specific limits on resource usage. If your EC2 instance or RDS usage exceeds the allotted resources for the free tier, you may start incurring charges.

Data Transfer Costs: 

AWS may charge for data transfer between your EC2 instance and other AWS services or the internet. If your application has significant data transfer, it could contribute to costs.

Reserved Instances or Upgrades: 

If you have changed your EC2 instance type to a more powerful one or if you are using reserved instances, it could result in charges.

Elastic IPs: 

If you are using Elastic IP addresses, they might incur charges if they are not associated with a running instance.

RDS Instance Type or Storage: 

Similar to EC2 instances, if you are using a larger RDS instance type or have increased the storage beyond the free tier limits, it could lead to charges.

Cross-Region or Cross-AZ Data Transfer: 

If your application involves data transfer between different AWS regions or availability zones, it could incur additional costs.

To identify the specific reason for the charges, you can check your AWS Billing and Cost Management dashboard. It provides detailed information about your usage and associated costs. Look for the services that are incurring charges, and review the usage details and configurations to pinpoint the cause.

Do these have public IPv4 addresses?

Starting 1st February 2024 all public IPv4 addresses will incur a charge of $0.005 per hour, so if the instance is always-on that's $0.12 per day. You have one EC2 and one RDS instance, so that would account for $0.24 per day starting 1st February.

More details of these new charges https://aws.amazon.com/blogs/aws/new-aws-public-ipv4-address-charge-public-ip-insights/

I note that your account is in free tier, and according to that link:

The AWS Free Tier for EC2 will include 750 hours of public IPv4 address usage per month for the first 12 months, effective February 1, 2024.

This means that even as the costs continute to increase in the billing section of AWS Console, when your invoice is generated at the end of the month there will be 750 hours of "free" IPv4 applied to the final total.