# What are "EC2-Other" AWS Costs on Cost Explorer?

## Details on Usage Costs from AWS Cost APIs

On the Archera Cost Explorer, we break out cost information as reported by the AWS APIs. Confusingly, these APIs collect a number of disparate, ancillary usage charges from EC2 into a category called "EC2-Other", which for some workloads can be large.

## What's Included

Under the "EC2-Other" umbrella the following costs are combined:

* **EBS:VolumeUsage.gp2** ($)
* **EBS:SnapshotUsage** ($)
* **CPUCredits:t2/t3** ($)
* **NatGateway-Hours** ($)
* **DataTransfer-Regional-Bytes** ($)
* **ElasticIP:IdleAddress** ($)
* **NatGateway-Bytes** ($)
* **REGION1-REGION2-AWS-Out-Bytes** ($)
* **REGION1-REGION2-AWS-In-Bytes** ($)
* **Others**

Essentially, these are the usage costs commonly associated with EC2 usage such as snapshots, CPU Credits, Data Transfer fees, etc.

## Getting Visibility

To get further details on these individual costs, you can use the Segment Explorer **"Group By"** functionality. Select **"Group By"** and change to **"Usage Type"**.

Next, select the services you want to collect information on. For example, you can look at all the Instance Type costs for a more granular breakdown.

## Related Resources

* [Why does AWS Cost Explorer Show a Cost Increase After Archera Commitment Purchases?](https://docs.archera.ai/help-center/aws-faq/cost-explorer-increase)
* [Why Not Just Use AWS Cost Explorer?](https://docs.archera.ai/help-center/aws-faq/why-not-cost-explorer)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.archera.ai/help-center/aws-faq/ec2-other-costs.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.