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

Deployment steps

The following is a list of the deployment steps that are used in this sample deployment

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.

PreviousList of landing zone componentsNextVPC configuration details

Last updated 2 years ago

Was this helpful?