Skip to content

Latest commit

 

History

History
32 lines (20 loc) · 1.72 KB

04-AppGW.md

File metadata and controls

32 lines (20 loc) · 1.72 KB
Raw

Challenge 4: Application Gateway

< Previous Challenge - Home - Next Challenge >

Introduction

In this challenge you will integrate an Application Gateway in the design.

Description

Your security department has decided that you need to put a Web Application Firewall in front of your web workloads, and you decide to go for the Azure Application Gateway.

hubnspoke appgw

Success Criteria

  1. You have enabled SSL in the App Gateway to provide HTTPS connectivity to users accessing your site
  2. You can access the web sites in each VM in the hub and in the spokes through the Application Gateway via different URLs
  3. Can you still see the client IP in the web servers?

Related documentation

Advanced Challenges (Optional)

  • Configure SSL encryption on the App Gateway. For SSL you can use self-signed certificates or generate them with [LetsEncrypt](https://letsencrypt.org/
  • Configure end-to-end SSL (you would need a backend with SSL support). For SSL you can use self-signed certificates or generate them with LetsEncrypt
  • Make both sites (spoke1 and spoke2) reachable under the same listener, but have a different URL for each site (like https://appgw.contoso.com/spoke1 and https://appgw.contoso.com/spoke2, for example)
  • Modify the design so that the Azure Firewall inspects the web traffic, optionally while using end-to-end SSL