> For the complete documentation index, see [llms.txt](https://experience-digital-transform.gitbook.io/experience-digital-transformation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://experience-digital-transform.gitbook.io/experience-digital-transformation/cloud-for-dpi/chapter-1/cloud-as-one-way-to-run-a-service.md). # Cloud as one way to run a service Cloud computing is one way to obtain and operate computing capacity and technical services. A team may use it for virtual machines, storage, managed databases, development environments, integration components, monitoring, or an entire software service. It can make certain tasks easier to obtain or operate. For example, a managed database may remove some database administration work; adjustable capacity may help a service respond to a known surge; a shared platform may give several teams a common logging or identity capability. Those possibilities do not decide whether the arrangement fits. The institution still has to define the service, control access, configure the technology, manage demand and cost, protect records, test recovery, supervise suppliers, and retain evidence. A managed component changes the boundary of the work. It does not make the public authority's obligations disappear. A capacity change illustrates the distinction. A cloud service can provide additional capacity without the authority buying equipment far in advance. The useful outcome depends on the application being able to use that capacity, on spending limits and alerts being set, and on people watching consumption. If those conditions are absent, flexible capacity may leave the service no more reliable and can make costs harder to predict. Recovery has the same character: backups, separate locations, automated deployment, and managed services can support a recovery plan, but the plan needs a recovery objective, operating access, realistic tests, and a workable service route during disruption. Cloud is therefore an operating option rather than a promise about service quality. It should be compared with retaining or improving the current service, managed hosting, a private environment, a shared platform, a software service, or redesign. The right route depends on the specific service and on the institution's practical ability to govern it. --- # 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://experience-digital-transform.gitbook.io/experience-digital-transformation/cloud-for-dpi/chapter-1/cloud-as-one-way-to-run-a-service.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.