Last active
January 13, 2022 19:52
-
-
Save ndamulelonemakh/fc77cdbc7e96bc0643baebbf3efaac49 to your computer and use it in GitHub Desktop.
Implementing web app resilience in Azure
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| #! /bin/bash | |
| # Pre-requisits | |
| # Active Azure Subscription | |
| # A virtual network resource | |
| # 2 or more vms serving the same web app | |
| # Reference: https://docs.microsoft.com/en-us/learn/modules/load-balance-web-traffic-with-application-gateway/5-exercise-create-configure-application-gateway | |
| # i.Step 1: Create a gateway subnet | |
| # ii.Step 2: Create a public Ip address with a custom FQDN | |
| # This is the endpoint that clients will use to reach your site | |
| # If you wish, you can use your own domain. See [instructions](https://docs.microsoft.com/en-us/azure/virtual-machines/custom-domain) | |
| # iii. Step 3: Create an api-gateway with default settings | |
| # iv. Step 4: Set up an HTTP listener | |
| # v. Add backend pools | |
| # v. Set up custom health endpoints for you backend pools | |
| # vi. Add URL path mappings to redirect public traffic accordingly | |
| # vii. Use your public IP address to verify that your app is llive | |
| e.g. curl http://mycustomdomain.com |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment