Azure Hub n Spoke with Azure Firewall connectivity lab deployed from Terraform in Hindi

Поділитися
Вставка
  • Опубліковано 3 січ 2025
  • Azure Hub n Spoke with Azure Firewall connectivity lab deployed from Terraform in Hindi
    In this video I have shown how spoke 1 vm will use hub Firewall to connect to vm in spoke 2
    #azure #azurenetworks #azurehindi #azuretutorials

КОМЕНТАРІ •

  • @digitalentertainment4120
    @digitalentertainment4120 5 місяців тому

    As always, one more excellent video with great explaination. Thank you 🙏

  • @gaurav13851
    @gaurav13851 5 місяців тому

    Very well explained

  • @M4nishS
    @M4nishS 5 місяців тому

    Please continue terraform series

  • @MukundNarayanJha
    @MukundNarayanJha 2 місяці тому

    Excellent video. Can you please provide terraform code.

  • @sharatBhaskar
    @sharatBhaskar 3 місяці тому

    Time: 5:38, Q- what if there is a scenario where you have two 3 spokes and you want two spokes to talk with each other but not with 3rd spoke then it that case also you will need routing with firewall subnet?

    • @techonlogic
      @techonlogic  3 місяці тому

      Not really, routing thru Firewall in this case was done to allow traffic via hub vnet, there are many cases where you have direct vnet peering between spokes vnet and traffic do not go via hub or firewall,
      To answer ur question: if you want communication between two spoke via hub firewall, u wud need route table. if you don't want to connect to spoke vnet and make it isolated or only connected to hub then u don't create routes to that vnet

    • @sharatbhaskar527
      @sharatbhaskar527 3 місяці тому

      @@techonlogic so you mean even if i have gateway connected with hub vnet and there are 3 spokes then still i will need route table attached with firewall subnet and route table routes will have the configuration which spoke will talk to which spoke.
      Is that understanding correct?

    • @techonlogic
      @techonlogic  3 місяці тому

      If Spoke vnet are peered with hub vnet and not with other spoke vnet
      Then for communication between spoke vnet
      U wud need route device, here it's azure firewall
      So in order to route the next hope, we need route table to be attached to the subnet of the source spoke vnet
      Feel free to drop ur mobile no. To my email id : sourabh.chhabra777@gmail.com
      I will call n explain

  • @sopankumbhare222
    @sopankumbhare222 Місяць тому

    bro, how i can connect you,

    • @techonlogic
      @techonlogic  Місяць тому

      You can reach me at Sourabh.chhabra777@gmail.com
      Mail me and I will send you my phone number