# Resource Recommendations - Overview

Balancing team infrastructure actions such as rightsizing or refactoring changes against infrastructure commitment savings and long-term goals can be challenging. We built the Resource Recommendation engine to help with commitment-aware rightsizing as well as to provide the flexibility to track recommendations from a number of sources — AWS Compute Optimizer, other cloud providers, and internal tools for your company.

The system can recommend EC2 sizes, Unattached EBS volumes, and other non-commitment type optimizations.

## Setting Up Compute Optimizer

### AWS

Follow the setup instructions to enable Compute Optimizer. We pull the recommendations in daily, so you should see recommendations coming into your account within the next day.

### Azure and GCP

Contact Sales at <sales@archera.ai>.

## Custom Recommendations & Syncing with External Sources

Custom recommendations can be added manually or through our API. For API access contact <sales@archera.ai>.

You can also use the API to query Recommendations and send them to your preferred system.

You can filter specific Recommendations by Segment.

## Recommendations Overview

The overview provides a breakdown of recommendations by Provider/Source as well as top recommendations by Type. When new recommendations come in they are flagged as **New** and team members can mark the stages:

* **New**
* **Reviewed**
* **Completed**

Items that are marked as complete or reviewed will show up in the Events stream for team members to review.

## Recommendations Table

Recommendations are filterable by the Segment Selector at the top of the page. From there you can do additional filtering in the search for things such as:

* Region
* Type
* Resource Family

Any field that's available in the table should return those types of recommendations.

You can select a specific recommendation and — if there are multiple options — select an option for the team to take. Choice changes are tracked and you can add notes to the recommendation.

If, for example, you have EC2 recommendations around CPU and you are more interested in Network and Memory based recommendations, mark the recommendation as not relevant and leave a note. This acts as a feedback loop for the Archera team on the relevancy of the recommendations.

## Related Resources

* [Infrastructure History - Overview](https://docs.archera.ai/help-center/user-guide/infrastructure-history)
* [Product Overview](https://docs.archera.ai/help-center/getting-started/product-overview)