# Deployment steps 1\. Define your credential using a stack profile (Example AWS Key, Secret, and the Region) 2\. Create a stack (unit of infrastructure) and select AWS as the cloud provider 3\. Compose your desired infrastructure using the stack canvas (Drag and Drop from the list of components organized by categories) 4\. Add all the components listed in this document. It may be relatively easier to compose using a modular approach. For example, in the first iteration you can compose only the VPC, subnets and the routing components. Alternately, you can break down the desired component into individual stacks as opposed to all-in-one stack 5\. Define the required properties for each of the components. This is where a template assists in reusability where you are required to define only the minimum properties from a full ist of properties that are pre-defined in a template 6\. Use the auto connections feature to let QMCLOUD connect all the required components thus defining the dependencies (Example a subnet needs to know which VPC it will be deployed into) 7\. Save, validate, and deploy the infrastructure Note: Refer to the next section for configuration details for each of the components. --- # Agent Instructions: 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: ``` GET https://docs.qmcloud.io/examples/deploy-aws-firewall-and-networking-with-qmcloud/deployment-steps.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.