> 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/s/storage.md). # Storage The retention of retrievable data on a computer or other electronic system. Storage refers to the technologies and systems used to retain digital data for later retrieval. In cloud computing, storage services are categorized by their access patterns and data models: block storage (raw volumes attached to virtual machines), file storage (hierarchical file systems accessible over a network), and object storage (flat namespaces of key-addressable data objects). Cloud storage services include Amazon S3 and Cloudflare R2 for object storage, Amazon EBS and Azure Managed Disks for block storage, and Amazon EFS and Google Filestore for file storage. Databases (both relational and NoSQL) provide another form of structured data storage with query capabilities. In API and serverless architectures, storage choice affects application design, performance, and cost. Serverless functions typically interact with managed storage services through APIs rather than local file systems. API gateways may use key-value storage (like Cloudflare KV) for caching responses, storing configuration data, or maintaining rate limit counters. Object storage is commonly used for file uploads, static assets, and log archives accessible through API endpoints. --- # 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/s/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.