QMCLOUD
  • What is QMCLOUD
  • Overview
    • Component Details
    • Security and RBAC
    • Dependencies
  • Architecture
  • Main features
  • Installation and Configuration
    • QMCLOUD SaaS
      • SaaS Registration
    • AWS Marketplace
    • Self-hosting
  • User Interface and Navigation
    • Main menu
    • Dashboard
    • General action buttons
    • Stack and Canvas
    • Stack Details
  • Getting started
    • Pre-requisites
    • Login to QMCLOUD
    • Create organization
    • Add Role
    • Add User
    • Add Components
    • Add Stack Profile
    • Add Workspace
    • Add Stack
    • Compose Infrastructure Using the Canvas
    • Add AWS Vpc
    • Add Subnets
    • Connect VPC and Subnets
    • Save Canvas State
    • Deploy the Infrastructure
  • AI Copilot
    • Example deployment using AI Copilot
    • AI Copilot pre-defined prompts
  • Additional resources
    • Explainer video
    • Short video on AI Copilot
    • Quick walkthrough videos
    • Walkthrough of deployment of AWS EKS
  • Examples
    • Deploy AWS Firewall and Networking with QMCLOUD
      • Application and landing zone components
      • List of landing zone components
      • Deployment steps
      • VPC configuration details
      • Routing configuration details
      • Firewall configuration
      • Additional components configuration
    • Securing applications in AWS using Palo Alto firewall
  • Templates
    • AWS Landing Zone
    • AWS EKS
    • Azure Web App
Powered by GitBook
On this page

Was this helpful?

  1. Examples
  2. Deploy AWS Firewall and Networking with QMCLOUD

Application and landing zone components

PreviousDeploy AWS Firewall and Networking with QMCLOUDNextList of landing zone components

Last updated 2 years ago

Was this helpful?

The sample web application deployment described in this section consists of the following:

  1. Ubuntu server with NGINX web server hosted on an EC2 instance in a private subnet

  2. Network load balancer is deployed in a protected subnet and exposes the web server to the Internet

  3. AWS firewall is deployed in the public subnet and inspects all ingress and egress traffic. the firewall rules allow only web server related traffic to the Internet (80, 443) and allows ssh connections to the web server initiated internally within the VPC

The following diagram depicts the landing zone that is used in this sample deployment:

AWS Landing Zone Components