Morgan Lucas

 Terraform for AWS is somewhat clearer than Terraform for Azure - easier to grasp than YAML and it's finicky formatting. After pushing some Terraform (TF) configurations live to AWS, I wondered if I could push a static webpage. Why Would You Use This? To quickly spin up the front-end for a simple webpage that might take user input after attaching it to back end services that accept and hold the data.  What Other Options Are There? I've documented hosting static webpages through Azure before on here through various methods - The process is somewhat intensive and relies strongly on interconnected systems. GitHub to host the code Azure Webapps to take the code and display it Another option would be using Netlify,  but that works best for truly single-page apps like this . It looks like it has different pages to the untrained eye, but it's only one. How Is It Done? Here, the simple webpage is hosted from a bucket. There's an index and error page. A curious aspect is the web

Hey, I have a per-small-project job - Contracted to build things in Terraform and push them to Azure to a company building out their Azure department. 80% of the time, it's pretty fun. I had to teach myself Terraform, but that's what this entire blog is about; Teaching myself things and hoping for work sometimes to make money and being employed by multiple people. You can be the next one! Anyway, what do I like about Terraform? A lot. Check out my live-post troubleshooting on a specific issue here .  TLDR? Check out the code on GitHub . There are even tiny bonuses, like bits that can be activated later. Likes:   It clearly tells you what an error is! Troubleshooting was mostly such a breeze, and since I wasn't getting [too] annoyed, I could more easily learn where the mistakes where. For instance, the first line in the main code ('provider') - the 'azurerm' part is not a random name; provider " azurerm " It's an actual thing that connects to