Instructions

• The treasure hunt consists of a series of puzzles, answers to which will point you to your next clue until you ultimately reach the treasure.
• You start with clue 1 and then continue as per the answers you get to the puzzles.
• Don't start solving them sequentially you don't need to solve all of them to reach the treasure.
• There is only 1 correct way to reach the treasure (if you find a loophole please inform me, I would need to fix it). Speaking of loops, If you are struck in a loop you have probably solved one of the puzzles wrong.

Puzzles

1. The Map
2. Attacked by Bandits
3. Caveman and Equation
4. Junction
5. Delayed by Rain
6. Modern Problems require Modern solution
7. Fake coin
8. Yoda's message
9. Future Sight
10. Trust issues
11. Page not Found
12. Bus Stop
13. Horses for courses
14. Prison Break
15. Many small Shares
16. All that glitters is not gold

Any form of feedback on clarity of questions or any ambiguous solution or anything that could have made the experience better is welcome. You can reach out to me on @reetwik12 on twitter or on reetwikdas on instagram for any queries and or suggestions.

Hall of Fame

• Raj Rohit
• Pranav Machingal
• Kuldeep Singh Maurya
• Sai Dheeraj
• Sai Gopal
• Prudhvi Bikumalla
• Srija Macherla
• Asha Anil
• Ashwin K
• Smriti Verma

Complete the hunt to get your name up here.

Here we will use a VNET to securely connect our web app (published on cloud as a SaaS service) to Azure SQL/Azure Storage.  

The following things are required to get started:

1. Azure Subscription (get free Azure subscription here)

Step 1: Creating a VNET

In your Azure portal go to create resource button and select Virtual Network and fill in the necessary details.

Step 2: Connecting storage resources to VNET

Go to your virtual network's service endpoints and add a new service endpoint.

Configure the storage account to allow access to the selected network only.

For SQL Databases go to firewall settings and add a new rule allowing access from the selected VNET.

Step 3: Connecting your app service to the VNET

Go to Networking Tab of your app service and select VNET configuration and add the selected VNET.

Now access these resource from your app normally.

Here the app is securely connecting to the VNET, which in turn has the access to storage resources. If configured properly only resource deployed within the VNET or granted access to it will have access to these storage resources hence reducing the threat surface drastically as compared to the previous instance where the resources are publicly available and are only protected by a client secret.

The following things are required to get started with blogging:

1. Azure Subscription (get free azure subscription).
2. your custom domain name (get your domain from GoDaddy)

STEP 1 : Creating your blog site using Ghost on Azure
Open GitHub repository for Ghost-Azure

Fill out the required information:

• Azure Subscription from dropdown.
• Resource group in which the site will be created.
• Site name of your choice (subject to availability)

Once the deployment is successfully finished your site is deployed on azure and can be accessed via  YourSiteName.azurewebsites.net

STEP 2 : Linking your site with your custom domain name
Go to your domain provider, select your domain and click on manage DNS. You would reach a page similar to the one shown below.

You need to add the following into DNS records
1. A @ IP address of your web app.

2. CNAME * YourSiteName.azurewebsites.net
3. CNAME www YourSiteName.azurewebsites.net
4. TXT @ YourSiteName.azurewebsites.net

Now go to your Application in azure portal and then to the Scale Up tab.

Now go to the custom domain tab and add new host name

Now your custom domain is linked to your site that you hosted on azure.

STEP 3. Getting SSL certificate
We would use azure's Let's Encrypt to get SSL certificate for our site.

In your Azure Portal go to Azure Active Directory then click on App Registration tab and the begin a new Application registration.

Register this app with any name, keep application type as Web App/API and provide your custom domain for Sign on URL.

The Application ID of this App is the Client ID that would be required later in the process.

Now go to settings button in the above page and then Keys tab to generate new Keys.

Provide key description, its expiry date and the value. Save the generated key as this will be used later as client secret.

Go to the resource group containing application corresponding to the site and provide the application registered in the Azure active directory (Let's Encrypt) and provide "Contribute" access.

To do this go to resource group and then Access Control (IAM) tab.

Go to the App service and then to the extension tab and add Azure Let's Encrypt extension in it.

Open Azure Let's Encrypt extension and click on browse.

• the tenant is something like mytenantname.onmicrosoft.com, you can find out your tenant tname by hovering over the logged in used in your azure portal.
• Subscription ID is your app service's subscription ID
• Client ID and Client secret were stored by us previously in the demo.
• Resource group name and service plan resource group name is the resource group in which you had deployed the app service.

Once you fill all the details click next. You would have to verify the domain and generate certificates for your domain which will be installed automatically.