> For the complete documentation index, see [llms.txt](https://blog.gigacode.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://blog.gigacode.dev/technology/cloud-concepts.md).

# Cloud Concepts

<figure><img src="https://imgs.xkcd.com/comics/the_cloud.png" alt=""><figcaption><p>XKCD 908 - The Cloud</p></figcaption></figure>

## What will I find here?

I'll be organizing all my Cloud focused concepts here, and I expect this to be the most content rich section (at least starting out). I personally define cloud related items as really anything that isn't running on a local system, so this will include most Microsoft Online services such as Azure and 365. This section will be focused specifically on the configuration and management of cloud platforms. I expect some crossover of general development concepts, but ideally would like to have a section separately for the purely dev focused writings.


---

# 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://blog.gigacode.dev/technology/cloud-concepts.md?ask=<question>&goal=<endgoal>
```

`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.
