Costs for the "EC-Other" item have suddenly tripled - Why?

Are you taking regular snapshots / backups of the EC2 instances. If so, those will keep piling up over time. Also, if you are have autoscaling groups that launches / terminates EC2s, make sure the detached volumes are deleted.

EC2 – Other includes charges for supporting services such as EBS volumes and snapshots, Elastic IP addresses, data transfer, and NAT gateways. Together with EC2 instances, these form the total cost of running EC2-based infrastructure.

In your case, I can’t see the detailed breakdown in above image, but one common reason for a sudden spike is data transfer. EC2 data transfer (especially inter-AZ, cross-region, or NAT-gateway egress traffic) can increase costs significantly without any visible change in the EC2 instance list.

Please check your Bills section in the AWS console . it provides a detailed charge breakdown. Compare it with the previous month to identify which service under EC2-Other is driving the increase. That will help pinpoint the exact cause and determine the next steps to resolve or contest it.

Hey,

Hope you're keeping well.

"EC2-Other" covers non-instance costs such as EBS storage, snapshots, Elastic IPs, NAT Gateway usage, and data transfer. A sudden spike often comes from increased NAT Gateway data processing or cross-AZ traffic, which can change without modifying your EC2 count. In the AWS Billing & Cost Management console, open Bills for the current month and expand the EC2-Other line to see the exact service driving the increase. Once identified, you can reduce usage or open a Support case under Account and Billing if you believe it’s incorrect. Using Cost Explorer with the “Usage Type” filter will help pinpoint trends and confirm the root cause.

Thanks and regards,
Taz

Unexpected cost increases in your AWS bill without apparent changes to your usage can be concerning. While I don't have specific information about an "EC-Other" category in AWS billing, I can provide some general guidance on investigating and addressing unexpected cost increases.

Several factors could potentially cause a sudden cost increase:

1. Recent AWS pricing changes: For example, as of February 1, 2024, AWS implemented a charge of $0.005 per IP per hour for all public IPv4 addresses, which appears under the Amazon Virtual Private Cloud service in billing.

2. Resource usage changes: Even if you didn't intentionally make changes, there might be automated processes, increased traffic, or background services consuming more resources.

3. Billing cycle changes or delayed charges from previous months that are now being reconciled.

To address this issue, I recommend:

1. Use AWS Cost Explorer to analyze your costs in detail. Look for specific resources or usage types that show increased charges.

2. Check for any resources across all AWS regions that might be running unexpectedly.

3. Review any recent AWS pricing updates that might affect your services.

To contest the charges:

1. Open a support ticket with AWS under the "Account & Billing" category. Explain the unexpected increase and request a detailed explanation of the charges.

2. AWS Support can help identify the specific resources causing the increase and may be able to provide assistance if there's been an error.

3. For future protection, set up AWS Budgets and Billing Alarms to notify you when costs exceed expected thresholds.

AWS Support is best positioned to provide specific insights into your account's billing situation and help resolve any discrepancies.
Sources
last 6 months monthly charge is under $1, this month it's over $100. However my mailer activity is down, having reduced my mailing list (email address IDs) from 5000 to 1200. | AWS re:Post
Unexpected billing | AWS re:Post
unexpected billing price | AWS re:Post
Why do I suddenly see Amazon Virtual Private Cloud in my AWS costs? | AWS re:Post