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

Additional components configuration

The following additional components were used as part of this sample deployment

PreviousFirewall configurationNextSecuring applications in AWS using Palo Alto firewall

Last updated 2 years ago

Was this helpful?

  1. Compute components include EC2 instance, security group, and security group rule. the EC2 instance is an Ubuntu server with a basic NGINX server

  2. Network load balancer, listener and target group. The target group has the EC2 instance registered to serve the web requests

  3. Internet Gateway and its associated routing components

The configuration of each of these components is beyond the scope of this document.

The deployment of the sample configuration is done via a single QMCLOUD stack and all the resources can be referenced in additional stack if required to extend the infrastructure.

QMCLOUD generates the infrastructure code automatically and can be stored in a GitHub repository if required. QMCLOUD can be integrated using REST API's with various CI/CD tools for orchestration.

The following diagram depicts the overall stack on the canvas, the configuration details (outputs from each of the components) and the code that is generated by QMCLOUD:

This completes the walk through for this sample deployment.

QMCLOUD stack on the canvas, configuration details and the associated auto generated code