> 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/examples/deploy-aws-firewall-and-networking-with-qmcloud/list-of-landing-zone-components.md).

# List of landing zone components

1\.       VPC with three subnets (private, protected, and public). The sample deployment uses a single availability zone but ideally one should use multi-AZ deployment

2\.       An application server deployed in the private subnet (EC2 instance with NGINX)

3\.       NAT gateway to allow the app server instances to access the internet without a public IP assignment

4\.       Internet Gateway to allow access to and from the Internet

5\.       Network load Balancer for exposing an application deployed in a private subnet

6\.       Firewall in a public subnet and associated rules to control both ingress and egress traffic

7\.       The routing component controls all traffic and forces all egress and ingress traffic to be inspected by the AWS firewall

 

{% hint style="info" %}
Note – Besides the model depicted in this sample deployment, you can refer to other potential models for securing your infrastructure using AWS Firewall. The following link provides a good summary of all the potential models. We have created templates for each of the models. You can reach out to use if you a need to use and/or deploy these templates using QMCLOUD.

<https://aws.amazon.com/blogs/networking-and-content-delivery/deployment-models-for-aws-network-firewall/>
{% endhint %}


---

# 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/examples/deploy-aws-firewall-and-networking-with-qmcloud/list-of-landing-zone-components.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.