> For the complete documentation index, see [llms.txt](https://docs.serverlessapigateway.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.serverlessapigateway.com/glossary/o/object-storage.md). # Object Storage A strategy that manages and manipulates data storage as distinct units, called objects. These objects are kept in a single storehouse and are not nested as files in a folder inside other folders. Object storage is a data storage architecture that manages data as objects rather than as files in a hierarchical directory structure or blocks on a disk. Each object includes the data itself, metadata (such as content type, creation date, and custom attributes), and a unique identifier used to retrieve it. Object storage systems are designed for massive scalability, high durability, and cost-effective storage of large amounts of unstructured data. Major object storage services include Amazon S3, Google Cloud Storage, Azure Blob Storage, and Cloudflare R2. These services provide HTTP-based APIs for uploading, downloading, and managing objects. In API architectures, object storage is commonly used to store file uploads, static assets, logs, and backups. API gateways can route file upload requests directly to object storage services, generate pre-signed URLs for secure direct uploads, or serve static content from object storage. Cloudflare R2 is notable for its zero-egress-fee pricing model, making it cost-effective for serving large files through APIs. --- # 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.serverlessapigateway.com/glossary/o/object-storage.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.