> For the complete documentation index, see [llms.txt](https://docs.onelens.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onelens.cloud/optimize-cost-savings-and-recommendations/storage-optimization.md).
# Storage Optimization
Storage Optimization shows the cost, configuration and savings tickets for your object storage, one bucket or storage account at a time. It covers Amazon S3, Google Cloud Storage (GCS) and Azure Storage.
Go to **Optimize → Storage Optimization** and pick a provider. To switch provider later, use the dropdown next to the page title.
| Provider | Page |
| -------------------- | -------------------------- |
| Amazon S3 | S3 Optimization |
| Google Cloud Storage | GCS Optimization |
| Azure Storage | Azure Storage Optimization |
### How the GCS and Azure Storage pages work
Both pages have the same layout.
* The first tab lists every bucket or storage account with its settings and cost.
* The **Tickets** tab lists the savings tickets OneLens has raised on them.
* **Last Updated**, at the top right, shows when the data was last refreshed.
* Use **Default View** to switch saved views, the search box to find a bucket or account by name, and the date range and **Filters** to set the period and scope.
In the list, **Total Cost** is the cost for the selected date range and **Delta** is Total Cost minus **Prev Cost**. A green down arrow means cost fell and a red up arrow means it rose.
A ticket badge next to a name shows how many tickets that bucket or account has. Each ticket is one savings recommendation on one resource. You can change a ticket's **Status** and **Assigned To** directly in the table.
When you mark a ticket as resolved, it moves to **Pending Verification** while OneLens checks that the change was made. See About Achieved Savings for how verification works.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.onelens.cloud/optimize-cost-savings-and-recommendations/storage-optimization.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
