Being billed for "EC2 - Other" - how do I find out what services I'm using and delete them?

Hello.

The prefix list itself is free to use, so I think the charge is due to something else.
In Cost Explorer, filter as in the answer to the URL below to see the breakdown of EC2 - Other charges.
After checking, you can prevent costs by deleting the resources in question.
https://repost.aws/questions/QUb7I_VMbjQAS5GyLX5rav6A/aws-cost-ec2-other#ANHm3Vhz38TFu5IodiLFcQTw

Hello,

If you want to see what has been charged under EC2-Other, go to Cost Explorer. Select the required date range, then choose Daily under Group by. Set Group by → Dimension → Usage type, and under Filters, include the service EC2-Other.

Check the attached Image for it: (/media/postImages/original/IMWhy7bbCJRKGKOe1OgtIcvg)

This will show a graph of all related usage types, including:

USW2-NatGateway-Bytes USW2-EBS:VolumeUsage.gp3 USW2-NatGateway-Hours USW2-EBS:VolumeUsage.gp2 NatGateway-Hours USW2-USE2-AWS-Out-Bytes USW2-EBS:SnapshotUsage USW2-DataTransfer-Regional-Bytes APS2-EBS:SnapshotUsage etc etc

Hi Charles,

You can also use this Knowledge Center article to find resources generating charges: Unexpected Charges.

If needed, our Support team can dive deeper: Support Center.

- Elle G.

Here's an screenshot from one of my accounts. You can use Cost Explorer, filter with service - EC2-Other, and set the dimension to API-Operation.

Hi, “EC2 – Other” charges are a common source of confusion, because they usually do not come from running EC2 instances themselves. Instead, this line item aggregates several EC2-related resources that continue to incur cost even when no instances are running.

The first step is to break down the charge in AWS Cost Explorer. Filter by Service = EC2 – Other and then group by Usage type or Region. This will tell you exactly what is generating the cost (for example: Elastic IPs, NAT Gateway hours, load balancer capacity units, EBS volumes or snapshots, or data transfer).

Managed prefix lists are not billable by themselves. AWS-managed prefix lists (such as those used by VPC endpoints or AWS services) are free, and customer-managed prefix lists are only billed if they exceed the free limits or are associated with other billable networking components. In most cases, simply seeing managed prefix lists in multiple regions is not the reason for EC2 – Other charges.

Typical causes to double-check are:

• Elastic IP addresses that are allocated but not attached to a running instance
• NAT Gateways, which incur hourly and data processing charges even if traffic is low
• Application / Network Load Balancers, which are billed based on hours and LCU usage
• EBS volumes or snapshots that remain after instances are terminated
• VPC endpoints (PrivateLink), which have hourly charges

If you want a systematic way to clean this up, go region by region and:

1. Check EC2 → Elastic IPs for unused allocations
2. Check VPC → NAT Gateways and Load Balancers
3. Check EC2 → Volumes and Snapshots
4. Review VPC Endpoints in the VPC console

Once the underlying resources are removed, the EC2 – Other charges will stop automatically. No paid AWS Support plan is required to do this—Cost Explorer and the service consoles are sufficient to identify and eliminate the source.

In short, focus on networking and storage resources, not prefix lists. EC2 – Other almost always points to something still provisioned in the background rather than a billing error.