> For the complete documentation index, see [llms.txt](https://docs.qmcloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.qmcloud.io/getting-started/deploy-the-infrastructure.md).
# Deploy the Infrastructure
Once the canvas state is saved, the following action buttons are selected in sequence to deploy the desired infrastructure:
Diagram - Deployment action buttons
Save - The save action button saves the canvas state including components, properties, and connectors
Validate – The validate action button validates the desired infrastructure (Properties and Syntax)
Plan – Confirm the desired infrastructure can be deployed (Checks dependencies and connections to the cloud provider)
Apply – Deploy the desired infrastructure
Each of the actions when competed displays a log message. The log message will indicate a success, or an error and details can be checked by selecting the appropriate log message.
Example of the log messages on the canvas:
Diagram – Logs
The following diagram depicts the completion of all the actions required for deploying the VPC and the subnets. It shows the logs section that displays the successful actions.
Diagram – Canvas, deployment sate and status
This completes the getting started section.
---
# 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://docs.qmcloud.io/getting-started/deploy-the-infrastructure.md?ask=&goal=
```
`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.