<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Brianmwaura on Medium]]></title>
        <description><![CDATA[Stories by Brianmwaura on Medium]]></description>
        <link>https://medium.com/@brianmwaura83?source=rss-d4f904ce5ef0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*84bw-_oYiC43M9Yw</url>
            <title>Stories by Brianmwaura on Medium</title>
            <link>https://medium.com/@brianmwaura83?source=rss-d4f904ce5ef0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 08:46:47 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@brianmwaura83/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Building B14 HUB on AWS: Designing a Secure, Cost-Conscious Cloud Foundation]]></title>
            <link>https://medium.com/@brianmwaura83/building-b14-hub-on-aws-designing-a-secure-cost-conscious-cloud-foundation-1b5e626b4da2?source=rss-d4f904ce5ef0------2</link>
            <guid isPermaLink="false">https://medium.com/p/1b5e626b4da2</guid>
            <category><![CDATA[aws-solutions-architect]]></category>
            <category><![CDATA[cloud-architecture]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Brianmwaura]]></dc:creator>
            <pubDate>Mon, 09 Nov 2026 23:38:02 GMT</pubDate>
            <atom:updated>2026-11-09T23:38:02.815Z</atom:updated>
            <content:encoded><![CDATA[<h4><em>A founder’s journey through cloud architecture, security, the AWS Well-Architected Framework, and practical infrastructure decisions.</em></h4><h3>1. The Vision Behind B14 HUB</h3><p>Every technology solution should begin with an understanding of the problem it is intended to solve.</p><p>B14 HUB is an emerging technology venture focused on digital services, technology solutions and localized agricultural order-line logistics. As the business develops, establishing a credible digital presence is an important first step.</p><p>I wanted to approach this project from two perspectives: as a founder building a business and as an IT professional developing practical cloud engineering skills.</p><p>Rather than immediately deploying infrastructure, I decided to first understand the requirements, evaluate the available AWS services and design an architecture that considers security, reliability and cost from the beginning.</p><p>This became the starting point for B14 HUB’s first AWS architecture project.</p><h3>2. Translating Business Needs into Cloud Requirements</h3><p>The initial phase focuses on a static portfolio and business website.</p><p>The website needs to:</p><ul><li>Be accessible securely over HTTPS.</li><li>Deliver website content efficiently.</li><li>Keep its underlying storage private.</li><li>Avoid unnecessary infrastructure and operational complexity.</li><li>Provide a foundation that can evolve with the business.</li></ul><p>These requirements informed the decision to use Amazon S3 for static content storage and Amazon CloudFront for content delivery.</p><p>A static website does not initially require dedicated application servers, a database or complex virtual networking infrastructure. Introducing these components without a business requirement would increase operational responsibilities and potentially introduce unnecessary costs.</p><p>The objective is simple: build what the current business requires while keeping future growth in mind.</p><h3>3. Designing the AWS Architecture</h3><p>The proposed architecture follows three main concepts: global content delivery, regional storage and a separate management and governance layer.</p><p><strong>Amazon S3 — Regional storage</strong></p><p>Amazon S3 stores the website’s static files, including HTML, CSS, JavaScript and other website assets.</p><p>The selected storage Region is af-south-1. The bucket will remain private, with public access blocked.</p><p><strong>Amazon CloudFront — Global content delivery</strong></p><p>CloudFront acts as the website’s content delivery layer. It distributes content through its global edge network, allowing visitors to retrieve cached content from locations closer to them.</p><p>For Phase 1, the website will use the default CloudFront distribution domain rather than introducing a custom domain and additional DNS configuration.</p><p><strong>Origin Access Control — Protected origin access</strong></p><p>Origin Access Control (OAC) is configured on the CloudFront S3 origin.</p><p>It enables CloudFront to sign requests to the S3 origin using AWS Signature Version 4. A restricted S3 bucket policy then allows the intended CloudFront distribution to retrieve website objects.</p><p>The architecture uses an S3 REST origin rather than the S3 static website endpoint because OAC does not support S3 website endpoints.</p><p>This design separates public content delivery from direct public access to the storage bucket.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EzJoG1z6nnHxgDzBlAS_pQ.png" /></figure><p><em>Figure 1: Proposed B14 HUB architecture showing global content delivery, regional private storage and the separate governance plane.</em></p><h3>4. Securing the Website with AWS Security Controls</h3><p>Security is a design requirement, not an additional feature to consider after deployment.</p><p>The proposed S3 configuration includes:</p><ul><li><strong>Block Public Access:</strong> prevents public bucket and object access through public access settings.</li><li><strong>Bucket owner enforced:</strong> disables ACL-based access management and establishes bucket ownership control.</li><li><strong>Restricted bucket policy:</strong> grants the CloudFront service principal s3:GetObject permission, constrained by the exact distribution ARN through the AWS:SourceArn condition.</li><li><strong>Origin Access Control:</strong> signs requests between CloudFront and the private S3 origin.</li></ul><p>IAM will support least-privilege administrative access, ensuring permissions are assigned according to operational requirements.</p><p>For visitor HTTPS, the default CloudFront domain uses CloudFront’s default certificate. A separate ACM certificate is not required for this initial configuration.</p><p>If B14 HUB introduces a custom domain in a later phase, an appropriate TLS certificate can be configured through ACM in us-east-1.</p><p>These are proposed controls. Their effectiveness must still be validated through implementation and security testing.</p><h3>5. Cost Awareness and the AWS Well-Architected Framework</h3><p>For an emerging business, infrastructure decisions must consider financial sustainability alongside technical requirements.</p><p>The architecture deliberately excludes EC2 instances, NAT Gateways, load balancers, databases and VPC networking because they are not necessary for the current static website scope.</p><p>AWS Budgets will support spending visibility and budget alerts. However, budget alerts should not be mistaken for hard spending limits.</p><p>CloudTrail will provide records of supported account activity and API events, supporting operational visibility and accountability.</p><p>It is also important to distinguish between AWS Free Tier account benefits and other CloudFront pricing plans. Eligibility, allowances and charges depend on the account, selected pricing model, Region, services and actual consumption.</p><p>Therefore, the objective is a cost-aware design, not a guaranteed zero-cost deployment.</p><p>The AWS Well-Architected Framework provides another important evaluation approach. Its six pillars are:</p><ol><li>Operational Excellence</li><li>Security</li><li>Reliability</li><li>Performance Efficiency</li><li>Cost Optimization</li><li>Sustainability</li></ol><p>Using these pillars encourages more disciplined infrastructure decisions. They help evaluate whether the proposed architecture is appropriate for the business requirements and where improvements may be necessary.</p><h3>6. Lessons Learned and the Next Implementation Phase</h3><p>One important lesson from this design process is that understanding where AWS services operate is just as important as knowing what those services do.</p><p>CloudFront is a global service, while S3 storage is regional. OAC belongs to the CloudFront origin configuration rather than being a separate resource inside an Availability Zone.</p><p>These distinctions matter because architecture diagrams should communicate actual service relationships, not simply group AWS icons together.</p><p>Another lesson is the importance of avoiding unnecessary complexity. A good architecture is not necessarily the one with the greatest number of services. It is the one that addresses the requirements with appropriate security, reliability and operational efficiency.</p><p>The next phase will move from design into implementation. Planned activities include:</p><ul><li>Creating and configuring the private S3 bucket.</li><li>Establishing the CloudFront distribution.</li><li>Configuring OAC and the S3 bucket policy.</li><li>Configuring the default root object and HTTPS viewer policy.</li><li>Uploading and validating website content.</li><li>Testing access restrictions and content delivery.</li><li>Establishing appropriate logging, monitoring and cost controls.</li></ul><p>Only after implementation and validation will it be appropriate to describe the architecture as deployed and operational.</p><h3>7. Conclusion — Building B14 HUB One Decision at a Time</h3><p>Building B14 HUB is an opportunity to connect practical business development with continuous technical learning.</p><p>This first AWS architecture exercise demonstrates the importance of making infrastructure decisions based on actual requirements rather than complexity for its own sake.</p><p>The goal is to establish a secure, cost-conscious foundation that can support the business as it grows.</p><p>The journey is still in progress. The next milestone is to move from architecture design to implementation, testing and operational validation.</p><p><strong>B14 HUB is being built one decision at a time.</strong></p><h3>Technical references</h3><ul><li><a href="https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/private-content-restricting-access-to-s3.html">AWS CloudFront — Restrict access to an Amazon S3 origin using OAC</a></li><li><a href="https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/DownloadDistValuesGeneral.html">AWS CloudFront — Distribution settings and certificates</a></li><li><a href="https://docs.aws.amazon.com/wellarchitected/latest/userguide/waf.html">AWS Well-Architected Framework</a></li><li><a href="https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/using-https-alternate-domain-names.html">AWS CloudFront — HTTPS and alternate domain names</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1b5e626b4da2" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>