> For the complete documentation index, see [llms.txt](https://docs.noros.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.noros.ai/features/reservation-and-commitment-health.md). # Reservation & Commitment Health Monitor commitment utilization, coverage, and upcoming expirations across your cloud accounts. Monitor reserved instance utilization, coverage gaps, and upcoming expirations. Noros provides full visibility into your existing savings plans, reserved instances, and committed use discounts so you can ensure your commitments are working as hard as they can. Noros reads the commitments that already exist in your cloud accounts, whichever ones you have purchased directly from your provider. If you have not purchased any commitments yet, this data will be empty. Ask Noros about your commitment coverage gaps to understand where commitments could save you money. ### What Noros Can Tell You #### Savings Plans (AWS) Noros can analyze all types of AWS Savings Plans: * **Compute Savings Plans** — Flexible savings across EC2, Lambda, and ECS Fargate workloads * **Database Savings Plans** — Coverage for Aurora, RDS, DynamoDB, ElastiCache, DocumentDB, Neptune, Keyspaces, Timestream, and DMS * **CloudFront Savings Plans** — Content delivery savings with a monthly drawdown model * **SageMaker Savings Plans** — ML and AI workload savings **Try asking:** * "How are our reserved instances performing?" * "Show RI utilization across accounts" * "Which savings plans are underutilized?" #### Reserved Instances (AWS) Noros provides insight into your reserved instances across all supported services: * **RDS** — Database reserved instances * **OpenSearch** — Search and analytics reservations * **ElastiCache** — Caching layer reservations * **Redshift** — Data warehouse reservations * **DynamoDB** — Provisioned capacity reservations **Try asking:** * "Are any commitments expiring soon?" * "How much am I saving on RDS reserved instances?" * "What's my RI utilization this month?" #### Committed Use Discounts (Google Cloud) For Google Cloud environments, Noros can analyze your CUDs: * **Resource-based CUDs** — Committed discounts on specific compute resources * **Spend-based CUDs** — Flexible discounts based on overall spending **Try asking:** * "What's my CUD coverage?" * "How are my committed use discounts performing?" #### Reservations and Savings Plans (Azure) For Azure environments, Noros reads your reservations and savings plans to report utilization and coverage. {% hint style="info" %} This depends on two of the read-only roles granted during onboarding: **Reservations Reader** and **Savings Plan Reader**. If either is missing, your Azure account still connects, but commitment answers will be incomplete. See [Required Azure Permissions](/getting-started/permissions-required/required-azure-permissions.md). {% endhint %} ### Key Metrics When discussing your commitments, Noros provides context through key metrics: * **Utilization Rate** — The percentage of your commitment capacity that's being actively used * **Coverage** — How much of your eligible spend is covered by commitments * **Estimated Savings Rate (ESR)** — The effective discount rate you're achieving * **FinOps Score** — A composite score (0.0–1.0) reflecting overall commitment efficiency, where 0.7+ is healthy * **Cost per Hour** — Hourly commitment cost for trend analysis * **Savings** — Dollar amount saved compared to on-demand pricing ### FinOps Score Your FinOps Score is a composite measure of how effectively you're using your cloud commitments. Ask Noros for a quick health check: * "What's our FinOps score?" * "How efficient is our cloud spend?" * "Where can we improve our FinOps practices?" A score of **0.7 or above** is considered healthy. Scores between 0.5 and 0.7 indicate room for improvement, and scores below 0.5 suggest optimization is needed. FinOps Score is currently available for **AWS** accounts only. ### Multi-Cloud View If you have accounts connected from more than one provider, you can ask Noros about commitments for each of them. Use the account switcher to set the account you are working in. Noros can also answer across more than one connected account in a single reply. ### Example Conversations **Portfolio review:** > "How are our reserved instances performing?" > > Noros provides a summary of utilization rates, total savings, ESR, and FinOps score across all commitment types. **Identifying waste:** > "Show RI utilization across accounts" > > Noros lists utilization rates by account and highlights underperforming commitments. **Planning ahead:** > "Are any commitments expiring soon?" > > Noros lists upcoming expirations so you can plan renewals or adjustments in advance. ### Go Further with North Noros lets you monitor and analyze your commitments. North manages them for you, through North's Coverage, its commitment engine. Autobot buys commitments into your own account, on a coverage profile you choose. Flexbot is coverage North holds for you, so your usage can scale up or down without a long-term lock-in. [Learn more about upgrading →](/other/powered-by-north.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://docs.noros.ai/features/reservation-and-commitment-health.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.