<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Walkthroughs on Adam Divall</title>
    <link>/categories/walkthroughs/</link>
    <description>Recent content in Walkthroughs on Adam Divall</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Fri, 07 Mar 2025 11:36:24 +0000</lastBuildDate>
    <atom:link href="/categories/walkthroughs/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>AWS Landing Zone Accelerator - Part 6: Security</title>
      <link>/article/step-by-step-guides/landing-zone-accelerator-part-6/</link>
      <pubDate>Fri, 07 Mar 2025 11:36:24 +0000</pubDate>
      <guid>/article/step-by-step-guides/landing-zone-accelerator-part-6/</guid>
      <description>&lt;p&gt;Welcome back to our deep dive into the AWS Landing Zone Accelerator (LZA)!&lt;/p&gt;&#xA;&lt;p&gt;In the previous five parts of this series, we&amp;rsquo;ve covered a lot of ground:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;a href=&#34;https://www.adamdivall.co.uk/article/step-by-step-guides/landing-zone-accelerator-part-1/&#34;&gt;Part 1: Introduced the LZA and its benefits for building a well-managed AWS environment&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;https://www.adamdivall.co.uk/article/step-by-step-guides/landing-zone-accelerator-part-2/&#34;&gt;Part 2: Walked through setting up your AWS Organization and creating new accounts&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;https://www.adamdivall.co.uk/article/step-by-step-guides/landing-zone-accelerator-part-3/&#34;&gt;Part 3: Explored the LZA&amp;rsquo;s global settings for standardized configurations across your AWS organization&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;https://www.adamdivall.co.uk/article/step-by-step-guides/landing-zone-accelerator-part-4/&#34;&gt;Part 4: Delved into the LZA&amp;rsquo;s network configuration, establishing a secure and scalable network foundation&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;https://www.adamdivall.co.uk/article/step-by-step-guides/landing-zone-accelerator-part-5/&#34;&gt;Part 5: Tackled Identity and Access Management (IAM), including setting up IAM Identity Center, break-glass access, and temporary elevated access.&lt;/a&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;In this sixth installment, we&amp;rsquo;ll shift our focus to a critical aspect of any well-architected cloud environment: Security. We&amp;rsquo;ll explore how the LZA helps you establish a secure baseline for your AWS workloads, but we&amp;rsquo;ll also go beyond the LZA&amp;rsquo;s default security configuration. I&amp;rsquo;ll explain the rationale behind some of our decisions to use custom solutions instead of relying solely on the LZA&amp;rsquo;s native security features, giving you a deeper understanding of how to tailor your security posture to your specific needs. Get ready to dive into the world of security best practices and learn how to fortify your AWS environment!&lt;/p&gt;</description>
    </item>
    <item>
      <title>AWS Landing Zone Accelerator - Part 5: Identity &amp; Access Management</title>
      <link>/article/step-by-step-guides/landing-zone-accelerator-part-5/</link>
      <pubDate>Mon, 03 Mar 2025 13:55:16 +0000</pubDate>
      <guid>/article/step-by-step-guides/landing-zone-accelerator-part-5/</guid>
      <description>&lt;p&gt;Welcome back to our ongoing exploration of the AWS Landing Zone Accelerator (LZA)!&lt;/p&gt;&#xA;&lt;p&gt;We&amp;rsquo;ve made some solid headway together. As you&amp;rsquo;ll recall, in &lt;a href=&#34;https://adamdivall.co.uk/article/step-by-step-guides/landing-zone-accelerator-part-1/&#34;&gt;Part 1&lt;/a&gt;, we kicked things off by introducing the LZA and highlighting its key benefits for building a robust and well-managed AWS environment. We then rolled up our sleeves in &lt;a href=&#34;https://adamdivall.co.uk/article/step-by-step-guides/landing-zone-accelerator-part-2/&#34;&gt;Part 2&lt;/a&gt;, walking through the essential steps of setting up your AWS Organization and creating those all-important new accounts. In &lt;a href=&#34;https://adamdivall.co.uk/article/step-by-step-guides/landing-zone-accelerator-part-3/&#34;&gt;Part 3&lt;/a&gt;, we delved into the LZA&amp;rsquo;s global settings, learning how to establish standardized configurations across your entire AWS organization, ensuring consistency and streamlined management. And as we just covered in &lt;a href=&#34;https://adamdivall.co.uk/article/step-by-step-guides/landing-zone-accelerator-part-4/&#34;&gt;Part 4&lt;/a&gt;, we&amp;rsquo;ve recently taken a detour into the foundational networking capabilities.&lt;/p&gt;</description>
    </item>
    <item>
      <title>AWS Landing Zone Accelerator - Part 4: Networking</title>
      <link>/article/step-by-step-guides/landing-zone-accelerator-part-4/</link>
      <pubDate>Thu, 13 Feb 2025 09:16:36 +0000</pubDate>
      <guid>/article/step-by-step-guides/landing-zone-accelerator-part-4/</guid>
      <description>&lt;p&gt;Welcome back to my deep dive into the AWS Landing Zone Accelerator (LZA)!&lt;/p&gt;&#xA;&lt;p&gt;We&amp;rsquo;ve made some good progress. In &lt;a href=&#34;https://adamdivall.co.uk/article/step-by-step-guides/landing-zone-accelerator-part-1/&#34;&gt;Part 1&lt;/a&gt;, we introduced the LZA and its benefits for building a well-managed AWS environment. &lt;a href=&#34;https://adamdivall.co.uk/article/step-by-step-guides/landing-zone-accelerator-part-2/&#34;&gt;Part 2&lt;/a&gt; walked through setting up your AWS Organisation and creating new accounts.  Then, in &lt;a href=&#34;https://adamdivall.co.uk/article/step-by-step-guides/landing-zone-accelerator-part-3/&#34;&gt;Part 3&lt;/a&gt;, we explored the LZA&amp;rsquo;s global settings, which allow for standardised configurations across your entire AWS organisation, ensuring consistency and simplified management.&lt;/p&gt;&#xA;&lt;p&gt;Now, I&amp;rsquo;m going to shift our focus to a critical aspect of any AWS environment: networking. This part of the series will delve into the network configurations provided by the LZA, exploring how it helps you establish a secure, scalable, and well-structured network foundation for your AWS workloads.&lt;/p&gt;</description>
    </item>
    <item>
      <title>AWS Landing Zone Accelerator - Part 3: Configuring Global Settings for Your Organization</title>
      <link>/article/step-by-step-guides/landing-zone-accelerator-part-3/</link>
      <pubDate>Wed, 05 Feb 2025 08:36:27 +0000</pubDate>
      <guid>/article/step-by-step-guides/landing-zone-accelerator-part-3/</guid>
      <description>&lt;p&gt;Welcome back to my deep dive into the AWS Landing Zone Accelerator (LZA)!&lt;/p&gt;&#xA;&lt;p&gt;We&amp;rsquo;ve made some good progress so far. In &lt;a href=&#34;https://adamdivall.co.uk/article/step-by-step-guides/landing-zone-accelerator-part-1/&#34;&gt;Part 1&lt;/a&gt;, we introduced the LZA and explained how it can help you build a well-managed AWS environment. In &lt;a href=&#34;https://adamdivall.co.uk/article/step-by-step-guides/landing-zone-accelerator-part-2/&#34;&gt;Part 2&lt;/a&gt;, we got hands-on and learned how to set up your AWS Organization and create new accounts.&lt;/p&gt;&#xA;&lt;p&gt;Now, in Part 3, we&amp;rsquo;re going to take a broader perspective and explore the global settings that the LZA provides. These settings let you establish standardised configurations across your entire AWS organization, ensuring consistency and simplifying management.&lt;/p&gt;</description>
    </item>
    <item>
      <title>AWS Landing Zone Accelerator - Part 2: Organizational Units and Account Configuration</title>
      <link>/article/step-by-step-guides/landing-zone-accelerator-part-2/</link>
      <pubDate>Thu, 30 Jan 2025 16:14:11 +0000</pubDate>
      <guid>/article/step-by-step-guides/landing-zone-accelerator-part-2/</guid>
      <description>&lt;p&gt;In &lt;a href=&#34;https://adamdivall.co.uk/article/step-by-step-guides/landing-zone-accelerator-part-1/&#34;&gt;Part 1&lt;/a&gt; of our AWS Landing Zone Accelerator (LZA) series, we introduced the LZA and its benefits.  Now, we&amp;rsquo;ll explore configuring OUs and other essential organizational settings, along with the process of creating AWS accounts within your LZA environment.&lt;/p&gt;&#xA;&lt;h2 id=&#34;prerequisites&#34;&gt;Prerequisites&lt;/h2&gt;&#xA;&lt;p&gt;Before we begin, ensure you have the following:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Access to the AWS Management account with the necessary permissions to modify the LZA setup.&lt;/li&gt;&#xA;&lt;li&gt;Permissions to update the LZA configuration, including editing files in the aws-accelerator-config repository.&lt;/li&gt;&#xA;&lt;li&gt;A brand-new email address for the new AWS account you&amp;rsquo;ll be creating.&lt;/li&gt;&#xA;&lt;li&gt;Git access to download and upload LZA configuration files.&lt;/li&gt;&#xA;&lt;li&gt;AWS Command Line Interface (CLI) installed and configured on your computer.&lt;/li&gt;&#xA;&lt;li&gt;The required permissions in Microsoft Entra ID to create and manage groups, and connect them to AWS IAM Identity Center for access control.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;&lt;strong&gt;Important Note:&lt;/strong&gt; I&amp;rsquo;m assuming you&amp;rsquo;ve already set up the LZA in your AWS environment by following the official guide: &lt;a href=&#34;https://docs.aws.amazon.com/solutions/latest/landing-zone-accelerator-on-aws/step-1.-launch-the-stack.html&#34;&gt;https://docs.aws.amazon.com/solutions/latest/landing-zone-accelerator-on-aws/step-1.-launch-the-stack.html&lt;/a&gt;. This means you&amp;rsquo;ve got the basic LZA structure in place.&lt;/p&gt;</description>
    </item>
    <item>
      <title>AWS Landing Zone Accelerator - Part 1: Introduction &amp; Overview</title>
      <link>/article/step-by-step-guides/landing-zone-accelerator-part-1/</link>
      <pubDate>Sun, 22 Dec 2024 11:41:46 +0000</pubDate>
      <guid>/article/step-by-step-guides/landing-zone-accelerator-part-1/</guid>
      <description>&lt;p&gt;Migrating to the cloud can feel like a giant leap into the unknown. Where do you even begin? How can you ensure your cloud environment is secure, scalable, and compliant from the get-go? The AWS Landing Zone Accelerator (LZA) is your trusted launchpad for a smooth and successful cloud journey.&lt;/p&gt;&#xA;&lt;h2 id=&#34;what-is-the-lza&#34;&gt;What is the LZA?&lt;/h2&gt;&#xA;&lt;p&gt;Think of the LZA as an open-source blueprint provided by AWS for building a well-architected, multi-account AWS environment. It&amp;rsquo;s more than just a template; it&amp;rsquo;s a framework encompassing pre-configured security controls, network configurations, and account structures, forming a robust foundation for your cloud deployments.  The LZA leverages Infrastructure as Code (IaC) principles, primarily using AWS CloudFormation, to automate the deployment and configuration of these foundational components.&lt;/p&gt;</description>
    </item>
    <item>
      <title>How to Set Up AWS CDK for Python</title>
      <link>/article/step-by-step-guides/how-to-set-up-aws-cdk-for-python/</link>
      <pubDate>Wed, 02 Oct 2024 14:07:20 +0100</pubDate>
      <guid>/article/step-by-step-guides/how-to-set-up-aws-cdk-for-python/</guid>
      <description>&lt;p&gt;In this guide, I&amp;rsquo;ll walk through setting up AWS CDK with Python, including all the required dependencies and steps, and demonstrate how to deploy a simple app that provisions an Amazon S3 bucket.&lt;/p&gt;&#xA;&lt;h2 id=&#34;what-is-the-aws-cdk&#34;&gt;What is the AWS CDK?&lt;/h2&gt;&#xA;&lt;p&gt;The AWS Cloud Development Kit (CDK) is an open-source software development framework designed to facilitate the creation and management of cloud infrastructure using familiar programming languages. Here are several important features and concepts associated with AWS CDK.:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Configuring Amazon VPC IP Address Manager (IPAM)</title>
      <link>/article/step-by-step-guides/configuring-vpc-ipam/</link>
      <pubDate>Sun, 19 Mar 2023 14:51:59 +0000</pubDate>
      <guid>/article/step-by-step-guides/configuring-vpc-ipam/</guid>
      <description>&lt;p&gt;In many enterprise environments a common challenge is to how to handle the allocation of IP CIDR blocks be that to Data Centers, Offices, Subnets so as to ensure that resources don&amp;rsquo;t end up with IP addresses that have already been assigned to resources on the Network.  Duplicate IP Addresses on the Network can cause numerous issues and AWS have previously written the following &lt;a href=&#34;https://aws.amazon.com/blogs/networking-and-content-delivery/connecting-networks-with-overlapping-ip-ranges/&#34; target=&#34;_blank&#34;&gt;blog&lt;/a&gt; that discusses several solutions to this challenge such as the use of NAT Gateways and AWS PrivateLink or a couple of more manual approaches to workaround the issue.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Customising AWS Control Tower with Account Factory Customisations</title>
      <link>/article/step-by-step-guides/customising-control-tower-with-account-factory-customisations/</link>
      <pubDate>Fri, 30 Dec 2022 15:54:49 +0000</pubDate>
      <guid>/article/step-by-step-guides/customising-control-tower-with-account-factory-customisations/</guid>
      <description>&lt;p&gt;At AWS re:Invent this year Account Factory Customisations was &lt;a href=&#34;https://aws.amazon.com/about-aws/whats-new/2022/11/aws-control-tower-account-customization/&#34; target=&#34;_blank&#34;&gt;released&lt;/a&gt;. This post will walk you through how to configure and use the new functionality as in my opinion the documentation isn&amp;rsquo;t particularly clear as to how things work and there were also issues with the implementation steps when I first implemented it.&lt;/p&gt;&#xA;&lt;h3 id=&#34;use-case&#34;&gt;Use Case&lt;/h3&gt;&#xA;&lt;p&gt;For my specific situation that I&amp;rsquo;m utilising this for I want to deploy a VPC that leverages the Amazon VPC IP Address Manager (IPAM) for obtaining an IP CIDR Range since I don&amp;rsquo;t want to have to manually enter one each time and run the risk of overlapping address space.  As part of my pre-requisties I&amp;rsquo;ve already written some automation using CloudFormation to not only setup VPC IPAM for delegated administration in my Organization, but I&amp;rsquo;ve also set up VPC IPAM so that I have seperate IPAM Pools for different regions and also different environments within those regions. This post won&amp;rsquo;t go into the details of the automation or the details of the CloudFormation Template that I&amp;rsquo;ll deploy either but how the Solution ultimately works.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Creating a Multi-Account CI/CD Pipeline with AWS CodePipeline</title>
      <link>/article/step-by-step-guides/creating-a-multi-account-pipeline-with-codepipeline/</link>
      <pubDate>Tue, 18 Oct 2022 16:44:39 +0100</pubDate>
      <guid>/article/step-by-step-guides/creating-a-multi-account-pipeline-with-codepipeline/</guid>
      <description>&lt;p&gt;Whenever I&amp;rsquo;ve tried to learn a particular service or functionality within AWS, I find the best way is to do the ClickOps approach (i.e. Good Old Point and Click in the Console).  Once I&amp;rsquo;ve figured out how to get it working via that method, I then go through the process of trying to automate it through Infrastructure as Code and in my case thats using AWS CloudFormation.&lt;/p&gt;&#xA;&lt;p&gt;One particular example of this was getting a bit more familiar with AWS CodePipeline so that I could try to automate the delivery of CloudFormation Templates across multiple AWS Accounts in a similar manner as to how you would deploy solutions in a Software Delivery Lifecycle (SDLC).  When I was learning how to do this through the management console, I found out that its not possible to do it all within the console and therefore you have to also leverage the AWS CLI for specific parts.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Customising AWS Control Tower with CfCT</title>
      <link>/article/step-by-step-guides/customising-control-tower-with-cfct/</link>
      <pubDate>Thu, 22 Sep 2022 06:57:02 +0100</pubDate>
      <guid>/article/step-by-step-guides/customising-control-tower-with-cfct/</guid>
      <description>&lt;p&gt;If you missed the previous posts on Deploying a Landing Zone with AWS Control Tower or you&amp;rsquo;ve not had much experience with the service, I&amp;rsquo;d recommend going back through and reading those firstly before continuing.&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;a href=&#34;/article/deploying-a-landing-zone-with-control-tower-part-1/&#34;&gt;Part 1 - Deploying AWS Control Tower&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;/article/deploying-a-landing-zone-with-control-tower-part-2/&#34;&gt;Part 2 - AWS Control Tower Post Configuration Tasks focusing on Organisational Structure and Guardrails&lt;/a&gt;&lt;/li&gt;&#xA;&lt;li&gt;&lt;a href=&#34;/article/deploying-a-landing-zone-with-control-tower-part-3/&#34;&gt;Part 3 - AWS Control Tower Post Configuration Tasks focusing on IAM Identity Center and Provisioning New AWS Accounts&lt;/a&gt;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;In this post, I&amp;rsquo;m going to walkthrough how you can start customising Control Tower using the &lt;a href=&#34;https://docs.aws.amazon.com/prescriptive-guidance/latest/security-reference-architecture/welcome.html&#34; target=&#34;_blank&#34;&gt;Security Reference Architecture (SRA)&lt;/a&gt;.  The SRA utilises &lt;a href=&#34;https://aws.amazon.com/solutions/implementations/customizations-for-aws-control-tower/&#34; target=&#34;_blank&#34;&gt;Customisations for Control Tower (CfCT)&lt;/a&gt; which deploys a DevOps pipeline that works with CloudFormation templates and Control Tower lifecycle events.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Deploying a Landing Zone with AWS Control Tower - Part 3</title>
      <link>/article/step-by-step-guides/deploying-a-landing-zone-with-control-tower-part-3/</link>
      <pubDate>Tue, 06 Sep 2022 15:02:04 +0100</pubDate>
      <guid>/article/step-by-step-guides/deploying-a-landing-zone-with-control-tower-part-3/</guid>
      <description>&lt;p&gt;Previously in &lt;a href=&#34;/article/deploying-a-landing-zone-with-control-tower-part-2/&#34;&gt;Part 2&lt;/a&gt; of this Walkthrough, I showed you how to create the organisational structure and enable guardrails within Control Tower.&lt;/p&gt;&#xA;&lt;p&gt;In this post, I&amp;rsquo;m going to walkthrough some of the remaining post configuration task including configuring IAM Identity Center and provisioning a new AWS Account through Account Factory.&lt;/p&gt;&#xA;&lt;h3 id=&#34;configuring-iam-identity-center-for-single-sign-on&#34;&gt;Configuring IAM Identity Center for Single Sign-On&lt;/h3&gt;&#xA;&lt;p&gt;AWS IAM Identity Center (formerly known as AWS SSO) is a service that enables you to have a single point of entry for managing resources within all of your AWS Accounts in an organisation.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Deploying a Landing Zone with AWS Control Tower - Part 2</title>
      <link>/article/step-by-step-guides/deploying-a-landing-zone-with-control-tower-part-2/</link>
      <pubDate>Mon, 05 Sep 2022 18:39:28 +0100</pubDate>
      <guid>/article/step-by-step-guides/deploying-a-landing-zone-with-control-tower-part-2/</guid>
      <description>&lt;p&gt;Previously in &lt;a href=&#34;/article/deploying-a-landing-zone-with-control-tower-part-1/&#34;&gt;Part 1&lt;/a&gt; of this Walkthrough, I touched on what a Landing Zone was and a brief background on them before going through how to launch AWS Control Tower as the foundation of a Multi-Account Architecture.&lt;/p&gt;&#xA;&lt;p&gt;In this , I&amp;rsquo;m going to walkthrough through some of the initial post configuration activities with Control Tower including setting up the organisational structure and enabling guardrails.&lt;/p&gt;&#xA;&lt;h3 id=&#34;what-has-control-tower-deployed&#34;&gt;What has Control Tower deployed?&lt;/h3&gt;&#xA;&lt;p&gt;As part of the setup, Control Tower has utilised a number of other AWS Services including:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Deploying a Landing Zone with AWS Control Tower - Part 1</title>
      <link>/article/step-by-step-guides/deploying-a-landing-zone-with-control-tower-part-1/</link>
      <pubDate>Sun, 04 Sep 2022 13:43:39 +0100</pubDate>
      <guid>/article/step-by-step-guides/deploying-a-landing-zone-with-control-tower-part-1/</guid>
      <description>&lt;p&gt;One of the first starting points for many organisations using Public Cloud is the establishment of a Landing Zone.  A Landing Zone is a well-architected, multi-account environment that&amp;rsquo;s based on security and compliance best practices..&lt;/p&gt;&#xA;&lt;p&gt;There are several reasons why organisations leverage a multi-account strategy including but not limited to:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Service Quotas:&lt;/strong&gt;  Each AWS Service typically has a number of different quotas; some of these are soft limits that can be increased by requesting an increase in the limit through a support ticket whilst others have hard limits that cannot be increased.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Limiting the Blast Radius:&lt;/strong&gt; As an AWS Account is a boundary of isolation, potential risks and threats can be contained within an account without affecting others.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Security Controls:&lt;/strong&gt; Workloads may have different complianye needs based on the Industry or the Geographical location.  Whilst there are synergies between the different compliancy frameworks, the Security Controls that are implemented to help achieve the compliance may need to be implemented in a slightly different manner or may not be required at all.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Billing Separation:&lt;/strong&gt; AWS Accounts are the only real way to separate items at a billing level e.g. Data Transfer costs.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;When I first started using AWS in 2016 there was no pre-packaged solution for a Landing Zone; there were several recommendations provided by AWS but in essence it was something that organizations had to build themselves.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Creating a Blog with Hugo and AWS Amplify</title>
      <link>/article/step-by-step-guides/creating-a-blog-with-hugo-and-aws-amplify/</link>
      <pubDate>Sun, 28 Aug 2022 16:43:50 +0100</pubDate>
      <guid>/article/step-by-step-guides/creating-a-blog-with-hugo-and-aws-amplify/</guid>
      <description>&lt;p&gt;This post is a Walkthrough Guide of how I&amp;rsquo;ve created this Blog using Hugo and AWS Amplify.&lt;/p&gt;&#xA;&lt;p&gt;I&amp;rsquo;m not a Developer by trade and therefore when determining on what to use for the Blog Software I had the following high-level requirements:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Simple to Setup &amp;amp; Configure&lt;/li&gt;&#xA;&lt;li&gt;Easy to Use &amp;amp; Maintain on an ongoing Basis&lt;/li&gt;&#xA;&lt;li&gt;Cost Effective&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;After reviewing a number of different options following a few hours of reading on Google, I settled on &lt;a href=&#34;https://gohugo.io/&#34; target=&#34;_blank&#34;&gt;Hugo&lt;/a&gt;.  What is Hugo, you may ask? Well in short, it&amp;rsquo;s a static site generator.  It allows you to create files in markdown format and using some magic it converts it into HTML.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
