<?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 Dominic Kwasi Appiah on Medium]]></title>
        <description><![CDATA[Stories by Dominic Kwasi Appiah on Medium]]></description>
        <link>https://medium.com/@incoomdominic?source=rss-533dd8a1d6d8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*6JedkqmZ-3xqXd1uZHWC-g.jpeg</url>
            <title>Stories by Dominic Kwasi Appiah on Medium</title>
            <link>https://medium.com/@incoomdominic?source=rss-533dd8a1d6d8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 18:33:16 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@incoomdominic/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[Orchestrating a Multi-Container Python Flask and Redis App with Docker Compose]]></title>
            <link>https://aws.plainenglish.io/orchestrating-a-multi-container-python-flask-and-redis-app-with-docker-compose-fe214ab7e829?source=rss-533dd8a1d6d8------2</link>
            <guid isPermaLink="false">https://medium.com/p/fe214ab7e829</guid>
            <category><![CDATA[container-orchestration]]></category>
            <category><![CDATA[docker-compose]]></category>
            <category><![CDATA[containerization]]></category>
            <category><![CDATA[docker]]></category>
            <dc:creator><![CDATA[Dominic Kwasi Appiah]]></dc:creator>
            <pubDate>Fri, 19 Dec 2025 21:04:32 GMT</pubDate>
            <atom:updated>2025-12-19T21:04:32.978Z</atom:updated>
            <content:encoded><![CDATA[<p>In modern DevOps, managing multiple interconnected services is a fundamental skill. In this project, I built a scalable web application using <strong>Python Flask</strong> and <strong>Redis</strong>, orchestrated entirely through <strong>Docker Compose</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pT81oFKe_d8mQT_frHdtpQ.png" /><figcaption>Architectural Diagram</figcaption></figure><h3>🛠️ Step 1: Initializing the Environment</h3><p>I began by setting up the project directory and authenticating with Docker Hub.</p><pre>docker login<br>mkdir -p redis-docker-project/{app,docker-compose.yml}</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/732/1*E-1CfDHbXz6uBNfi5IGn7g.png" /><figcaption>docker login</figcaption></figure><h3>⚠️ The “Directory vs. File” Gotcha</h3><p>If you look closely at the command above, using {app,docker-compose.yml} inside mkdir actually created docker-compose.yml as a <strong>directory</strong>. I noticed this when trying to edit it later.</p><p>To fix this, I had to:</p><ol><li>Identify that it was a directory when the rm command failed.</li><li>Use the recursive remove command: rm -r docker-compose.yml.</li><li>Later, properly touch the file or create it via an editor.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/769/1*S6IJF4udpW_NnnUg9bpLGQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/724/1*LjrxnRMBFeBR9ISMFyLoGw.png" /><figcaption>docker-compose correction</figcaption></figure><h3>📂 Step 2: Project Structure &amp; File Creation</h3><p>A clean project structure is vital for Docker orchestration. I organized the application logic inside an app/ folder, with the orchestration file at the root.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/389/1*u1rk4_Ke20Zdor5E3ZV-Bw.png" /><figcaption>Project structure</figcaption></figure><p>I navigated into the app directory to initialize the core component files:</p><ul><li>app.py</li><li>requirement.txt</li><li>Dockerfile</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-_wyMOiXw0B-fgsLphNMPg.png" /><figcaption>touching files</figcaption></figure><h3>💻 Step 3: Developing the Application Logic</h3><p>Using the vi editor, I populated the files with the necessary code and dependencies.</p><h3>The Flask Application (app.py)</h3><p>The application connects to Redis via a host defined in our environment variables. Every time the root page is refreshed, it increments a counter in the Redis datastore.</p><pre>from flask import Flask<br>import redis<br>import os<br><br>app = Flask(__name__)<br>redis_host = os.environ.get(&quot;REDIS_HOST&quot;, &quot;redis&quot;)<br>r = redis.Redis(host=redis_host, port=6379, decode_responses=True)<br><br>@app.route(&quot;/&quot;)<br>def home():<br>    count = r.incr(&quot;visits&quot;)<br>    return f&quot;Hello! This page has been visited {count} times. Like and follow CloudDaemon&quot;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/927/1*zn5bYr1GR02UBHB1iVX44A.png" /><figcaption>app.py</figcaption></figure><h3>Dependencies (requirement.txt)</h3><p>I listed the lightweight requirements needed: flask and redis.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/669/1*a16RnOL52a_Q5OM8Sq71cQ.png" /></figure><h3>🐋 Step 4: Dockerization &amp; Orchestration</h3><p>With the code ready, I defined how the containers should be built and how they should interact.</p><h3><strong>The Dockerfile</strong></h3><p>The Dockerfile uses python:3.11-slim as a base. It sets the working directory, installs dependencies, and exposes port <strong>5000</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/535/1*BBSsyQJ3k4BNa0L1-flRjw.png" /><figcaption>Dockerfile</figcaption></figure><h3>The Docker Compose File</h3><p>The docker-compose.yml file acts as the orchestrator. It defines:</p><ul><li><strong>web service</strong>: Builds from the /app directory and maps port <strong>5000</strong>.</li><li><strong>redis service</strong>: Pulls the official <strong>Redis 7</strong> image.</li><li><strong>networking</strong>: Sets REDIS_HOST=redis so the containers can talk to each other.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/569/1*OpOVZIr51s-MeWXk1Cs9aw.png" /><figcaption>docker-compose.yml</figcaption></figure><h3>🚀 Step 5: Deployment &amp; Verification</h3><p>To bring the entire stack to life, I ran the build and up command from the project root:</p><pre>docker-compose up --build</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k2dquZ9bTfLP8tsUks8DIw.png" /><figcaption>docker-compose build</figcaption></figure><h3>Validating the Containers</h3><p>I used docker ps to verify that both the web service and the Redis datastore were active and mapped to their respective ports.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7m0x9laaC_ZEjYUy1v7g3w.png" /><figcaption>docker ps</figcaption></figure><h3>Testing the Web Service</h3><p>Navigating to 127.0.0.1:5000 confirmed the application was working and communicating with Redis.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z8P_1MqOz9s1x1oc6TC4bw.png" /><figcaption>Live webservice</figcaption></figure><h3>Inspecting the Redis Datastore</h3><p>Finally, I accessed the running Redis container using docker exec to verify the data persisted. Running GET visits via the redis-cli confirmed the visit count.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v5MKKvzOJaCsYN1NWbsusg.png" /><figcaption>redis</figcaption></figure><h3>🏁 Conclusion</h3><p>By leveraging Docker Compose, we’ve created a reproducible, isolated environment where a Python backend and a Redis database work in perfect sync. This setup handles the complexities of networking and dependency management, allowing us to focus on the code.</p><p><strong>Would you like me to help you write a “Cleanup” section explaining how to stop and remove these containers and networks safely?</strong></p><p>Do subscribe to my Youtube channel, i’ll be posting a video on this project soon: <a href="https://www.youtube.com/@Cloud_Daemon">https://www.youtube.com/@Cloud_Daemon</a></p><p>Happy Learning!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fe214ab7e829" width="1" height="1" alt=""><hr><p><a href="https://aws.plainenglish.io/orchestrating-a-multi-container-python-flask-and-redis-app-with-docker-compose-fe214ab7e829">Orchestrating a Multi-Container Python Flask and Redis App with Docker Compose</a> was originally published in <a href="https://aws.plainenglish.io/">AWS in Plain English</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building a Secure 3-Tier AWS Architecture with Terraform (Step-by-Step)]]></title>
            <link>https://aws.plainenglish.io/building-a-secure-3-tier-aws-architecture-with-terraform-step-by-step-b25b120f59b3?source=rss-533dd8a1d6d8------2</link>
            <guid isPermaLink="false">https://medium.com/p/b25b120f59b3</guid>
            <category><![CDATA[terraform]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[architecture]]></category>
            <dc:creator><![CDATA[Dominic Kwasi Appiah]]></dc:creator>
            <pubDate>Mon, 15 Dec 2025 06:27:33 GMT</pubDate>
            <atom:updated>2025-12-15T06:27:33.377Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/971/1*JnWc021XLJoFxM3UIX19Lw.png" /></figure><p>Infrastructure as Code (IaC) has become a foundational skill for cloud engineers and Terraform is one of the most powerful tools to implement it. In this post, I’ll walk through how I designed and deployed a <strong>secure, production-style 3-tier AWS architecture using Terraform</strong>, based on a real-world lab scenario and best practices.</p><p>This project demonstrates how networking, security, compute, and database layers come together in AWS — all provisioned automatically with Terraform.</p><p>📌 Project Overview</p><p>The goal of this project was to implement a <strong>3-tier architecture</strong> consisting of:</p><ul><li>A <strong>public access layer</strong> (Bastion + Web)</li><li>A <strong>private application layer</strong></li><li>A <strong>private database layer</strong></li><li>Deployed across <strong>two Availability Zones (us-east-1a and us-east-1b)</strong></li></ul><p>All resources are provisioned using Terraform, ensuring <strong>repeatability, consistency, and automation</strong>.</p><p>🧱 Architecture Summary</p><p>The architecture includes:</p><ul><li><strong>VPC</strong>: 192.168.0.0/16</li><li><strong>Public Subnet (AZ us-east-1a)</strong>: 192.168.1.0/24</li><li><strong>Private Subnet — App (AZ us-east-1a)</strong>: 192.168.2.0/24</li><li><strong>Private Subnet — DB Primary (AZ us-east-1a)</strong>: 192.168.3.0/24</li><li><strong>Private Subnet — DB Secondary (AZ us-east-1b)</strong>: 192.168.4.0/24</li></ul><p>🧩 Terraform Project Structure</p><p>To keep the code clean and maintainable, the project was split into logical Terraform files. This structure allows engineers to quickly locate and manage resources.</p><p>1. Project Variables</p><p>Configuration variables are separated for easy environment customization.</p><ul><li>variables.tf defines the variables and their types.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CC-q-9IrlAIakyFeBiPrAw.png" /><figcaption><strong>variables.tf</strong></figcaption></figure><ul><li>terraform.tfvars holds the specific values for the current deployment.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*khZSiQNwwSnXX-0SXLDiZQ.png" /><figcaption>terraform.tfvars</figcaption></figure><p>2. provider.tf - Defining AWS and Terraform Versions</p><p>This file specifies the AWS provider and the required versions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Wd7CtieM_YTnJmEQUd9UHg.png" /><figcaption>provider.tf</figcaption></figure><p>3. main.tf - VPC and Main Networking</p><p>The core network components are defined, starting with the VPC.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mWVRZTk-8DDEc0Vaznf5mQ.png" /><figcaption>main.tf</figcaption></figure><p><em>Verification in Console:</em> The VPC is provisioned and available.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aqh-w6qsAKW5I1ZqgqDZnA.png" /><figcaption>Vpc</figcaption></figure><p>4. subnet_and_routing.tf - Subnets and Route Tables</p><p>We create public and private subnets across two AZs for redundancy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vXV7tofyf54kzSPT9K_emQ.png" /><figcaption>subnet_and_routing.tf</figcaption></figure><p><em>Verification in Console:</em> The deployed subnets confirm the networking design. Note the distinct private and public subnets.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*27rKcVG42l6jjgvr6up1fw.png" /><figcaption><strong>subnets</strong></figcaption></figure><p>5. nat_and_igw.tf - NAT Gateway and Routing</p><p>A NAT Gateway is crucial for private instances to initiate outbound connections (e.g., for software updates) without being publicly accessible.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*enEZjxuaf_3PeM-qcKGkTA.png" /><figcaption>nat_and_igw.tf</figcaption></figure><p><em>Verification in Console: Elastic IP (EIP) Allocation</em> the EIP is successfully allocated and tagged for the NAT Gateway.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vSX6-rFUYhdVRu4Qp1Ymog.png" /></figure><p><em>Verification in Console:</em> The Route Tables show the explicit separation of routing. The Private RT is associated with three private subnets.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mRc5S4vWrQ-iBetctH8-rQ.png" /><figcaption><strong>RT</strong></figcaption></figure><p>🔐 Security Design (security_groups.tf)</p><p>Each tier has its own <strong>Security Group (SG)</strong>, enforced using <strong>SG-to-SG rules</strong> for least privilege. This prevents unauthorized direct access between tiers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y3KwIz-Ykia8W-dVT9aoTg.png" /><figcaption>security_groups.tf</figcaption></figure><p>Security Groups Summary</p><ul><li><strong>Bastion Host SG</strong>: SSH (22) allowed only from admin IP (admin_cidr).</li><li><strong>Web Server SG</strong>: HTTP (80) / HTTPS (443) from the internet, SSH only from Bastion SG.</li><li><strong>App Server SG</strong>: SSH from Bastion SG, data traffic only from Web SG.</li><li><strong>Database SG</strong>: MySQL (3306) only from App and Bastion SGs.</li></ul><p><em>Verification in Console:</em> The creation of the required security groups is confirmed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_5amgF9uX2CjgVXC8pTWrg.png" /><figcaption>sgs in console</figcaption></figure><p>🖥️ Compute Layer (ec2_instances.tf)</p><p>The instances are provisioned across the public and private layers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6soTtgPzVhFqzlKNB5z-oA.png" /><figcaption>ec2_instances.tf</figcaption></figure><p><em>Verification in Console:</em> All three instances (Web, App, and Bastion) are running.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*exu6-fRFuJqcdCfUnP7pwA.png" /><figcaption><strong>instances in console</strong></figcaption></figure><p><em>Verification of EBS Volumes:</em> The corresponding EBS volumes for these instances are also confirmed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Qo-xn6Xc7NbMVDcCZEpzJQ.png" /><figcaption><strong>volumes in use</strong></figcaption></figure><p>🗄️ Database Layer (rds.tf)</p><p>The database is an <strong>Amazon RDS MariaDB</strong> instance, configured as non-publicly accessible (publicly_accessible = false) and placed only in the private subnets.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*668dRGecgH0_QY9UQZDR3g.png" /><figcaption>rds.tf</figcaption></figure><p><em>Verification in Console:</em> The database instance is up and ready.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Zgla4y4KAlr7bc-Tw46gcA.png" /><figcaption><strong>database</strong></figcaption></figure><p>🚀 Deployment Workflow</p><p>The entire infrastructure is deployed using a single command sequence:</p><pre>terraform init<br>terraform plan<br>terraform apply</pre><p>Verification: The deployment finishes successfully with 43 resources added.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OHpXssAqC71IzHuLYEs_kw.png" /><figcaption>apply</figcaption></figure><p>Final Outputs (outputs.tf)</p><p>The outputs provide critical access information, such as the public IP of the Bastion Host and the private endpoint of the RDS database.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DRi5T_f_GU6TRNasf0-zzw.png" /><figcaption>outputs.tf</figcaption></figure><p><strong>OutputValueApp Private IP</strong>192.168.2.81<strong>Bastion Public IP</strong>44.223.15.66<strong>RDS Endpoint</strong>tier3-arch-mariadb.cyjrna644l9m.us-east-1.rds.amazonaws.com:3306</p><p>✅ Key Takeaways</p><p>This project successfully demonstrates the deployment of a professional, <strong>secure AWS 3-tier architecture</strong> using Terraform, highlighting:</p><ul><li><strong>Network Segmentation</strong> (Public vs. Private Subnets)</li><li><strong>Controlled Outbound Access</strong> (NAT Gateway)</li><li><strong>Principle of Least Privilege</strong> (SG-to-SG rules)</li><li><strong>Infrastructure as Code</strong> for repeatable environments</li></ul><p>🏁 Final Thoughts</p><p>By combining clean Terraform code with a well-thought-out architecture, you gain confidence in designing scalable cloud systems. This project serves as an excellent foundation for any cloud engineer.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FOEkb-hu0QcE%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fshorts%2FOEkb-hu0QcE%3Fsi%3DDRHBKuO_ziExCASh&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FOEkb-hu0QcE%2Fhq2.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/066d89d10f4175ddf8d4a1fa6509c1ea/href">https://medium.com/media/066d89d10f4175ddf8d4a1fa6509c1ea/href</a></iframe><p>Subscribe to my channel and hit the bell icon, I’ll be sharing a full tutorial video on the above soon.</p><p>Happy Learning!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b25b120f59b3" width="1" height="1" alt=""><hr><p><a href="https://aws.plainenglish.io/building-a-secure-3-tier-aws-architecture-with-terraform-step-by-step-b25b120f59b3">Building a Secure 3-Tier AWS Architecture with Terraform (Step-by-Step)</a> was originally published in <a href="https://aws.plainenglish.io/">AWS in Plain English</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Serverless Static Website with a Contact Form (S3 → API Gateway → Lambda → SES) — A Complete…]]></title>
            <link>https://aws.plainenglish.io/serverless-static-website-with-a-contact-form-s3-api-gateway-lambda-ses-a-complete-c5ea6c29a745?source=rss-533dd8a1d6d8------2</link>
            <guid isPermaLink="false">https://medium.com/p/c5ea6c29a745</guid>
            <category><![CDATA[aws-simple-email-service]]></category>
            <category><![CDATA[awsserverless]]></category>
            <category><![CDATA[api-gateway]]></category>
            <category><![CDATA[aws-lambda]]></category>
            <category><![CDATA[aws-s3]]></category>
            <dc:creator><![CDATA[Dominic Kwasi Appiah]]></dc:creator>
            <pubDate>Sat, 15 Nov 2025 15:13:11 GMT</pubDate>
            <atom:updated>2025-11-18T17:09:47.615Z</atom:updated>
            <content:encoded><![CDATA[<h3>Serverless Static Website with a Contact Form (S3 → API Gateway → Lambda → SES) A Complete, Real-World Guide</h3><p>Building a serverless contact form is one of the most common use cases for AWS yet many tutorials gloss over the parts that actually break things in production: <strong>CORS</strong>, Lambda to API Gateway wiring, IAM permissions, and SES sandbox rules.</p><blockquote><strong>S3 static website → API Gateway → Lambda → SES email delivery</strong></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/994/1*ikHDo1jtmE1Fi8osCe9Hlw.png" /></figure><h3>Architecture Overview</h3><p>The goal is to provide a robust contact form without maintaining any traditional servers.</p><ul><li>You host your static site (HTML/CSS/JS) on <strong>Amazon S3</strong>.</li><li>The contact form submits a POST /submit request to <strong>API Gateway</strong>.</li><li>API Gateway invokes an <strong>AWS Lambda function</strong> using Lambda proxy integration.</li><li>Lambda sends an email through <strong>Amazon Simple Email Service (SES)</strong>.</li><li>Lambda returns a JSON response with the necessary <strong>CORS headers</strong> so the browser accepts the successful response.</li></ul><p>This is simple, secure, and has zero servers to maintain.</p><h3>Prerequisites</h3><p>Before starting, ensure you have the following ready in your AWS account (using us-east-1 in this example):</p><ol><li><strong>AWS Permissions:</strong> Access to S3, API Gateway, Lambda, IAM, and SES.</li><li><strong>SES Verification:</strong> The <strong>sender email</strong> is verified. If your SES account is still in the sandbox, the <strong>recipient email</strong> must also be verified.</li></ol><h3>Configure the S3 Static Website</h3><h3>Create the Bucket and Policy</h3><ol><li>Go to S3 → Create bucket.</li><li>Give it a unique name (e.g., contform-s3-website-us-east-1.amazonaws.com).</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ATNkeWedDp3EM16Kn_pXJg.png" /></figure><ol><li><strong>Disable “Block all public access”</strong> (you need this for static hosting).</li><li>Apply a <strong>Bucket policy for public read access</strong> (replace the bucket name):</li></ol><pre>{<br>  &quot;Version&quot;: &quot;2012-10-17&quot;,<br>  &quot;Statement&quot;: [<br>    {<br>      &quot;Sid&quot;: &quot;PublicReadGetObject&quot;,<br>      &quot;Effect&quot;: &quot;Allow&quot;,<br>      &quot;Principal&quot;: &quot;*&quot;,<br>      &quot;Action&quot;: [&quot;s3:GetObject&quot;],<br>      &quot;Resource&quot;: [&quot;arn:aws:s3:::my-contact-site-12345/*&quot;]<br>    }<br>  ]<br>}</pre><h3>Enable Static Hosting</h3><ol><li>Go to the Bucket → <strong>Properties</strong> → <strong>Static website hosting</strong> → <strong>Enable</strong>.</li><li>Set <strong>Index document:</strong> index.html</li></ol><h3>Configure SES (Email Service)</h3><p>This step ensures you’re authorized to send emails.</p><ol><li>In SES → <strong>Verified identities</strong>, verify both the <strong>sender email</strong> (required) and the <strong>recipient email</strong> (if you are in the SES sandbox).</li><li>You will receive a verification email to the address you enter. Click the link to confirm.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*w8sgR6aoMcBu_akZETYh_g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pVb7pkGWUPwV6lRVqNYpdg.png" /></figure><h3>Create the Lambda Function</h3><p>This Python function will receive the contact for data and send the email via SES.</p><h3>Create IAM Role</h3><p>This role gives the Lambda function permission to interact with other AWS services, specifically SES and CloudWatch Logs.</p><ol><li>IAM → Roles → <strong>Create role</strong>.</li><li><strong>Trusted entity type:</strong> <strong>AWS service</strong>.</li><li><strong>Use case:</strong> Select <strong>Lambda</strong>.</li><li>In <strong>Add permissions</strong>, search for ses and select <strong>AmazonSESFullAccess</strong>.</li></ol><ul><li><em>Note: For production, use a more restrictive policy, but </em><em>AmazonSESFullAccess simplifies the initial setup.</em></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A0rsg3q9bbvBwgwHSNvIBw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oqjud8F5WXiqoWwDe83ORg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E7MEKSwtQuz__n3TvLnoGg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H0GCEB_4GZbYB_FvVmdl_w.png" /></figure><h3>Create the Lambda Function</h3><ol><li>Lambda → <strong>Create function</strong>.</li><li><strong>Name:</strong> ContactFormSender.</li><li><strong>Runtime:</strong> Python 3.11 (or latest).</li><li><strong>Execution role:</strong> Choose the IAM role you just created (lambda-ses-send-role).</li><li>Add these <strong>Environment variables</strong> to the Lambda’s configuration:</li></ol><pre>Key,Value,Description<br>SENDER_EMAIL,your verified SES sender,Email used as the source of the message.<br>RECIPIENT_EMAIL,the business owner&#39;s email,Email where the contact form submission will go.<br>SES_REGION,us-east-1,The AWS region where SES is configured.</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9zHchYdicGSUIAHvWr-cAw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QcfAL3H7qEQwIzUABDtPDA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cIqi71f5n8jY_opA36V8JQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9Pha4xUsc8Ol46Ue9nZ1KQ.png" /></figure><h3>Lambda Code (Python)</h3><p>Replace the code in lambda_function.py with the following. Pay close attention to the <strong>CORS headers</strong> in the _response function, which are crucial for the frontend</p><pre>import json<br>import boto3<br>import logging<br>import os<br>from botocore.exceptions import ClientError<br><br>logger = logging.getLogger()<br>logger.setLevel(logging.INFO)<br><br>SES_REGION = os.environ.get(&quot;SES_REGION&quot;, &quot;us-east-1&quot;)<br>SENDER = os.environ.get(&quot;SENDER_EMAIL&quot;)<br>RECIPIENT = os.environ.get(&quot;RECIPIENT_EMAIL&quot;)<br><br>ses = boto3.client(&#39;ses&#39;, region_name=SES_REGION)<br><br>def lambda_handler(event, context):<br>    logger.info(&quot;Event: %s&quot;, event)<br><br>    try:<br>        # API Gateway uses Lambda Proxy Integration, so the body is a string<br>        body = event.get(&quot;body&quot;)<br>        data = json.loads(body)<br>    except Exception:<br>        return _response(400, {&quot;error&quot;: &quot;Invalid JSON body&quot;})<br><br>    name = (data.get(&quot;name&quot;) or &quot;&quot;).strip()<br>    sender_email = (data.get(&quot;email&quot;) or &quot;&quot;).strip()<br>    message = (data.get(&quot;message&quot;) or &quot;&quot;).strip()<br><br>    if not name or not sender_email or not message:<br>        return _response(400, {&quot;error&quot;: &quot;name, email and message are required&quot;})<br><br>    subject = f&quot;Contact form submission from {name}&quot;<br>    body_text = f&quot;Name: {name}\nEmail: {sender_email}\n\nMessage:\n{message}&quot;<br><br>    try:<br>        ses.send_email(<br>            Source=SENDER,<br>            Destination={&#39;ToAddresses&#39;: [RECIPIENT]},<br>            Message={<br>                &#39;Subject&#39;: {&#39;Data&#39;: subject},<br>                &#39;Body&#39;: {&#39;Text&#39;: {&#39;Data&#39;: body_text}}<br>            },<br>            ReplyToAddresses=[sender_email]<br>        )<br>    except ClientError:<br>        logger.exception(&quot;SES send failed&quot;)<br>        return _response(500, {&quot;error&quot;: &quot;Failed to send email&quot;})<br><br>    return _response(200, {&quot;message&quot;: &quot;Email sent&quot;})<br><br>def _response(status_code, body):<br>    # For browsers (CORS): include Access-Control-Allow-Origin header<br>    # Allow site origin. The specific origin is more secure than &quot;*&quot;.<br>    return {<br>        &quot;statusCode&quot;: status_code,<br>        &quot;headers&quot;: {<br>            &quot;Content-Type&quot;: &quot;application/json&quot;,<br>            &quot;Access-Control-Allow-Origin&quot;: &quot;http://contform-s3-website-us-east-1.amazonaws.com&quot;,<br>            &quot;Access-Control-Allow-Headers&quot;: &quot;Content-Type,X-Amz-Date,Authorization,X-Api-Key,X-Amz-Security-Token&quot;,<br>            &quot;Access-Control-Allow-Methods&quot;: &quot;OPTIONS,POST&quot;<br>        },<br>        &quot;body&quot;: json.dumps(body)<br>    }</pre><p>Replace the Access-Control-Allow-Origin value with your actual S3 static website endpoint.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*335txzqfAvcssqfxqcsMOw.png" /></figure><h3>Create API Gateway (REST API)</h3><p>While HTTP API is simpler, we’ll demonstrate a <strong>REST API</strong> setup for maximum control over CORS, as shown in your images.</p><h3>Create the API</h3><ol><li>API Gateway → <strong>Create API</strong> → <strong>REST API</strong>.</li><li>Choose <strong>New API</strong>.</li><li><strong>API name:</strong> lambses.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H-Xr4Y4RrpNQqHgOqP1a3A.png" /></figure><h3>Create Resource and Method</h3><ol><li>Select the root resource (/) and <strong>Create resource</strong>.</li><li><strong>Resource Name:</strong> submit.</li><li>Select the new /submit resource and <strong>Create method</strong> → <strong>POST</strong>.</li><li><strong>Integration type:</strong> <strong>Lambda Function</strong>.</li><li><strong>Lambda Region:</strong> us-east-1.</li><li><strong>Lambda Function:</strong> ContactFormSender.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cXwZipXflBBTALrPglVEnA.png" /></figure><h3>Enable CORS on the Resource</h3><p>CORS is mandatory for the browser to allow the cross-domain request from S3 to API Gateway.</p><ol><li>Select the /submit resource.</li><li>Click <strong>Actions</strong> → <strong>Enable CORS</strong>.</li></ol><p>3. Configure the CORS settings: * <strong>Gateway responses:</strong> Check <strong>Default 4XX</strong> and <strong>Default 5XX</strong>. * <strong>Access-Control-Allow-Origin:</strong> Enter your <strong>S3 website domain exactly</strong> (e.g., http://contform-s3-website-us-east-1.amazonaws.com). * <em>Note: In production, </em><strong><em>do not</em></strong><em> use </em><em>*.</em></p><p>4. Click <strong>Save</strong>. This action automatically creates the necessary <strong>OPTIONS</strong> method for pre-flight requests.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ELvsdeOs3za9qoxgoV0xww.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0P9aDFtMFlLAVpkFfUWDqA.png" /></figure><h3>Deploy the API</h3><ol><li>Click <strong>Actions</strong> → <strong>Deploy API</strong>.</li><li><strong>Deployment stage:</strong> <strong>[New Stage]</strong></li><li><strong>Stage name:</strong> prod.</li><li>Copy the <strong>Invoke URL</strong> from the stage details you will use this in your frontend JavaScript.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H-Xr4Y4RrpNQqHgOqP1a3A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cXwZipXflBBTALrPglVEnA.png" /></figure><h3>Frontend: HTML + CSS Form</h3><p>Upload these files to your S3 bucket. Remember to replace YOUR_API_ID.execute-api.us-east-1.amazonaws.com/prod/submit with your actual <strong>Invoke URL</strong>.</p><pre>&lt;!DOCTYPE html&gt;<br>&lt;html lang=&quot;en&quot;&gt;<br>&lt;head&gt;<br>    &lt;meta charset=&quot;UTF-8&quot;&gt;<br>    &lt;meta name=&quot;viewport&quot; content=&quot;width=device-width, initial-scale=1.0&quot;&gt;<br>    &lt;title&gt;Serverless Contact Form&lt;/title&gt;<br>    &lt;link rel=&quot;stylesheet&quot; href=&quot;style.css&quot;&gt;<br>&lt;/head&gt;<br>&lt;body&gt;<br>    &lt;div class=&quot;container&quot;&gt;<br>        &lt;h1&gt;Send Us a Message&lt;/h1&gt;<br>        <br>        &lt;form id=&quot;contact-form&quot;&gt;<br>            &lt;label for=&quot;name&quot;&gt;Name&lt;/label&gt;<br>            &lt;input type=&quot;text&quot; id=&quot;name&quot; name=&quot;name&quot; required&gt;<br><br>            &lt;label for=&quot;email&quot;&gt;Email&lt;/label&gt;<br>            &lt;input type=&quot;email&quot; id=&quot;email&quot; name=&quot;email&quot; required&gt;<br><br>            &lt;label for=&quot;subject&quot;&gt;Subject&lt;/label&gt;<br>            &lt;input type=&quot;text&quot; id=&quot;subject&quot; name=&quot;subject&quot; required&gt;<br><br>            &lt;label for=&quot;message&quot;&gt;Message&lt;/label&gt;<br>            &lt;textarea id=&quot;message&quot; name=&quot;message&quot; rows=&quot;5&quot; required&gt;&lt;/textarea&gt;<br><br>            &lt;button type=&quot;submit&quot; id=&quot;submit-button&quot;&gt;Send Message&lt;/button&gt;<br><br>            &lt;p id=&quot;form-status&quot; aria-live=&quot;polite&quot;&gt;&lt;/p&gt;<br>        &lt;/form&gt;<br>    &lt;/div&gt;<br><br>    &lt;script&gt;<br>        // *** IMPORTANT: REPLACE THIS PLACEHOLDER WITH YOUR DEPLOYED API GATEWAY INVOKE URL ***<br>        const API_ENDPOINT = &#39;https://****.execute-api.us-east-1.amazonaws.com/prod/submit&#39;;<br><br>        const form = document.getElementById(&#39;contact-form&#39;);<br>        const statusMessage = document.getElementById(&#39;form-status&#39;);<br>        const submitButton = document.getElementById(&#39;submit-button&#39;);<br><br>        form.addEventListener(&#39;submit&#39;, function(event) {<br>            // Prevent the default form submission (which would refresh the page)<br>            event.preventDefault(); <br>            <br>            // Collect form data<br>            const formData = new FormData(form);<br>            const payload = {};<br>            formData.forEach((value, key) =&gt; {<br>                payload[key] = value;<br>            });<br><br>            // Show loading state<br>            statusMessage.textContent = &#39;Sending...&#39;;<br>            submitButton.disabled = true;<br><br>            fetch(API_ENDPOINT, {<br>                method: &#39;POST&#39;,<br>                headers: {<br>                    &#39;Content-Type&#39;: &#39;application/json&#39;,<br>                },<br>                body: JSON.stringify(payload) // Convert the data object to a JSON string<br>            })<br>            .then(response =&gt; {<br>                // Check for a successful response (status 200-299)<br>                if (response.ok) {<br>                    return response.json(); // Process the JSON response from Lambda/API Gateway<br>                }<br>                // Handle HTTP error responses<br>                throw new Error(`Submission failed: ${response.status} ${response.statusText}`);<br>            })<br>            .then(data =&gt; {<br>                // Success<br>                statusMessage.textContent = &#39;✅ Message sent successfully! We will be in touch soon.&#39;;<br>                form.reset(); // Clear the form fields<br>            })<br>            .catch(error =&gt; {<br>                // Error handling<br>                console.error(&#39;Error submitting form:&#39;, error);<br>                statusMessage.textContent = `❌ An error occurred: ${error.message}. Please try again.`;<br>            })<br>            .finally(() =&gt; {<br>                // Re-enable the button after process completes<br>                submitButton.disabled = false;<br>            });<br>        });<br>    &lt;/script&gt;<br>&lt;/body&gt;<br>&lt;/html&gt;<br></pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oPmUMxZAmeCeTk9l6uuCMw.png" /></figure><h3>⚠️ CORS What Breaks Most People</h3><p>If your browser returns a <strong>No &#39;Access-Control-Allow-Origin&#39; header is present…</strong> error, your CORS configuration is wrong.</p><h3>Checklist for Success</h3><ol><li><strong>API Gateway</strong> must have the <strong>OPTIONS</strong> method configured (done automatically when you click <strong>Enable CORS</strong>).</li><li><strong>Lambda</strong> must return the correct <strong>Access-Control-Allow-Origin</strong> header in its response. <strong>This is set in the Python code&#39;s </strong><strong>_response function.</strong></li><li>The <strong>Allowed origin</strong> in <em>both</em> API Gateway and Lambda <strong>must exactly match</strong> your S3 website domain (including the http:// or https://) and <strong>must not</strong> have a trailing slash.</li></ol><h3>Final Checklist Before Launch</h3><ul><li><strong>SES</strong> sender + recipient verified.</li><li><strong>Lambda</strong> IAM role includes ses:SendEmail and CloudWatch Logs permissions.</li><li><strong>API Gateway</strong> CORS enabled on the /submit resource.</li><li><strong>Lambda</strong> returns <strong>CORS headers</strong> in the response function.</li><li><strong>S3 website origin</strong> matches the <strong>Access-Control-Allow-Origin</strong> value.</li></ul><blockquote>Fun Trouble CORS messed me up like four hours straight… the joy that it eventually worked.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a4w6pLDJwkKgOWCBUWgO_Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BIcHPOVMriIKJt8TW4jVNA.png" /></figure><p><strong>Happy Troubleshooting.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c5ea6c29a745" width="1" height="1" alt=""><hr><p><a href="https://aws.plainenglish.io/serverless-static-website-with-a-contact-form-s3-api-gateway-lambda-ses-a-complete-c5ea6c29a745">Serverless Static Website with a Contact Form (S3 → API Gateway → Lambda → SES) — A Complete…</a> was originally published in <a href="https://aws.plainenglish.io/">AWS in Plain English</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Resume Hack That Beats the “5 Years Experience” Lie]]></title>
            <link>https://medium.com/@incoomdominic/the-resume-hack-that-beats-the-5-years-experience-lie-120786ba83fc?source=rss-533dd8a1d6d8------2</link>
            <guid isPermaLink="false">https://medium.com/p/120786ba83fc</guid>
            <category><![CDATA[aws-certification]]></category>
            <category><![CDATA[cloud-career-growth]]></category>
            <category><![CDATA[cloud-project]]></category>
            <category><![CDATA[cloud-careers]]></category>
            <dc:creator><![CDATA[Dominic Kwasi Appiah]]></dc:creator>
            <pubDate>Sat, 15 Nov 2025 00:11:59 GMT</pubDate>
            <atom:updated>2025-11-15T00:11:59.339Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/890/0*raErGfEWne-XKAEU" /></figure><p>Are you trying to break into Cloud Computing but feeling “under-qualified” by job descriptions? You’re not alone, and here’s the game-changing truth</p><p>Many aspiring #CloudEngineers see “3–5 years’ experience” and stop dead in their tracks. But what if those requirements are more of a wish list than a strict checklist? 🤔</p><p>Here’s the secret: Companies are looking for competence and problem-solving skills, not just clock-in time. Your foundational IT experience + targeted #AWSCertifications + robust #CloudProjects = powerful experience! Don’t self-reject if you hit 60–70% of the criteria. Apply!</p><p>⚡️ TRANSFORM YOUR RESUME &amp; GET NOTICED! ⚡️</p><p>Shift Your Narrative: Instead of “Help Desk,” think “Cloud Infrastructure Contributor.” Reframe your past responsibilities to highlight cloud-relevant tasks, even if you weren’t officially in a cloud role.</p><p>Show, Don’t Just Tell: Your portfolio projects are GOLD! 🌟 Showcase that 3-tier web app on #AWS, your #Terraform IaC automation, or that disaster recovery plan. Link your #GitHub!</p><p>Quantify Your Impact: Did you boost uptime, cut costs, or speed up deployments? Use numbers! (e.g., “reduced infra costs by 15%,” “deployment time from 4 hours to 15 minutes”).</p><p>Future-Proof: Mention certifications you’re actively pursuing (e.g., #AWSSolutionsArchitect Associate in progress). It shows initiative!</p><p>Keyword Power: Optimize your skills section with relevant #CloudComputing terms: #EC2, #S3, #RDS, #VPC, #CloudWatch, #IAM, #Lambda, #Linux, #CloudFormation, #DevOps. These bypass Applicant Tracking Systems (ATS).</p><p>Stop waiting for permission. Start building your cloud career now!</p><p>What’s one resume hack that helped you land an interview? Share below! 👇</p><p>Are you trying to break into Cloud Computing but feeling “under-qualified” by job descriptions? You’re not alone, and here’s the game-changing truth</p><p>Many aspiring #CloudEngineers see “3–5 years’ experience” and stop dead in their tracks. But what if those requirements are more of a wish list than a strict checklist? 🤔</p><p>Here’s the secret: Companies are looking for competence and problem-solving skills, not just clock-in time. Your foundational IT experience + targeted #AWSCertifications + robust #CloudProjects = powerful experience! Don’t self-reject if you hit 60–70% of the criteria. Apply!</p><p>⚡️ TRANSFORM YOUR RESUME &amp; GET NOTICED! ⚡️</p><p>Shift Your Narrative: Instead of “Help Desk,” think “Cloud Infrastructure Contributor.” Reframe your past responsibilities to highlight cloud-relevant tasks, even if you weren’t officially in a cloud role.</p><p>Show, Don’t Just Tell: Your portfolio projects are GOLD! 🌟 Showcase that 3-tier web app on #AWS, your #Terraform IaC automation, or that disaster recovery plan. Link your #GitHub!</p><p>Quantify Your Impact: Did you boost uptime, cut costs, or speed up deployments? Use numbers! (e.g., “reduced infra costs by 15%,” “deployment time from 4 hours to 15 minutes”).</p><p>Future-Proof: Mention certifications you’re actively pursuing (e.g., #AWSSolutionsArchitect Associate in progress). It shows initiative!</p><p>Keyword Power: Optimize your skills section with relevant #CloudComputing terms: #EC2, #S3, #RDS, #VPC, #CloudWatch, #IAM, #Lambda, #Linux, #CloudFormation, #DevOps. These bypass Applicant Tracking Systems (ATS).</p><p>Stop waiting for permission. Start building your cloud career now!</p><p>What’s one resume hack that helped you land an interview? Share below! 👇</p><p>#CloudCareers #AWS #Azure #GCP #TechJobs #CareerDevelopment #CloudSkills #ITCareer #JobSearch #ResumeTips #LinkedInTips #CloudCertifications</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=120786ba83fc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Architecting for Scale: A Step-by-Step Guide to Building a Three-Tier Architecture on AWS]]></title>
            <link>https://aws.plainenglish.io/architecting-for-scale-a-step-by-step-guide-to-building-a-three-tier-architecture-on-aws-0d70fc03a97d?source=rss-533dd8a1d6d8------2</link>
            <guid isPermaLink="false">https://medium.com/p/0d70fc03a97d</guid>
            <category><![CDATA[nat-gateway]]></category>
            <category><![CDATA[amazon-ec2]]></category>
            <category><![CDATA[subnet]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[aws-internet-gateway]]></category>
            <dc:creator><![CDATA[Dominic Kwasi Appiah]]></dc:creator>
            <pubDate>Thu, 13 Nov 2025 01:40:05 GMT</pubDate>
            <atom:updated>2025-11-13T01:40:05.852Z</atom:updated>
            <content:encoded><![CDATA[<p>A three-tier architecture is the backbone of almost all scalable, secure, and highly available web applications. It logically separates an application into three distinct layers: the <strong>Presentation (Web) Tier</strong>, the <strong>Application Tier</strong>, and the <strong>Data Tier</strong>.</p><p>This guide walks you through deploying this robust architecture on Amazon Web Services (AWS) using core services like <strong>Amazon VPC</strong>, <strong>Amazon EC2</strong>, and <strong>Amazon RDS</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/971/1*JnWc021XLJoFxM3UIX19Lw.png" /></figure><h3>VPC and Subnet Configuration</h3><p>We will create a custom VPC (e.g., 192.168.0.0/16) and logically divide it into a set of subnets to enforce security and availability best practices.</p><ul><li><strong>Public Subnet (e.g., </strong><strong>192.168.1.0/24):</strong> This is for resources that need direct internet access (e.g., Load Balancers, Bastion Host, Web Server).</li><li><strong>Private Application Subnet(s) (e.g., </strong><strong>192.168.2.0/24, </strong><strong>192.168.3.0/24):</strong> These host the application servers and cannot be reached directly from the internet.</li><li><strong>Private Database Subnet(s) (e.g., </strong><strong>192.168.4.0/24):</strong> These host the database and are the most restricted.</li></ul><p>Crucially, we will place subnets across <strong>two different Availability Zones (AZs)</strong> to ensure high availability and resilience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-ucLlvMSUCuzmKY-dwy7Ug.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N0y5ERAzu7eEIlK_nKfBgg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1014/1*uj5-00x7RpZHL7DxIaJk2A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-ucLlvMSUCuzmKY-dwy7Ug.png" /></figure><h3>Internet and NAT Gateways</h3><p>To enable internet access for our tiers:</p><ol><li><strong>Internet Gateway (IGW):</strong> We create an IGW and attach it to the VPC. This is the entry and exit point for internet traffic to and from the Public Subnet.</li><li><strong>NAT Gateway (NAT GW):</strong> We deploy a NAT Gateway in the <strong>Public Subnet</strong> and assign it an <strong>Elastic IP (EIP)</strong>. This allows resources in the Private Subnets (like our App Servers) to initiate outbound connections (e.g., for updates) without exposing them to incoming internet traffic.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T8Tqc8bqxH3FygcQ9hSvxg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gsuVk1ShO_IJTq5mMS4xfw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*glYAE22u5G0iFCzkSE88Kw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GsKJxfQG3rnEMrVO1v_LGw.png" /></figure><h3>Route Tables</h3><p>We then define routing rules to direct traffic:</p><ul><li><strong>Public Route Table:</strong> Associates the Public Subnet(s) and has a default route (0.0.0.0/0) pointing to the <strong>Internet Gateway</strong>.</li><li><strong>Private Route Table:</strong> Associates the Private Subnet(s) and has a default route (0.0.0.0/0) pointing to the <strong>NAT Gateway</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qrBOsL7ke5wpLLLM4TCdXQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jPRZPsN1Hpy01PrFNBPRLw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q53siyg97SOVW5sNrhOBlw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ceGKdXt_k-yf3gl7kPoz4A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w809ss6psNLC4V50R38sqQ.png" /></figure><h3>Enforcing Isolation: Security Groups</h3><p>Security Groups (SGs) act as virtual firewalls to control inbound and outbound traffic for your instances. We create four highly restrictive SGs, implementing the <strong>principle of least privilege</strong>.</p><pre>Security Group,Inbound Rules,Source<br>Bastion Host SG,SSH (Port 22),Your Public IP<br>Web Server SG,&quot;HTTP (Port 80), HTTPS (Port 443)&quot;,0.0.0.0/0 (Internet)<br>App Server SG,HTTP/S (Port 80/443),&quot;0.0.0.0/0, SSH (Port 22)&quot;<br>Database SG,MySQL/Aurora (Port 3306),App Server SG and Bastion Host SG </pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-cPXSA3yj9-RwAvRHJbC8A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rnjhWr7fHuQonkGuzLQ7Nw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dc_15SurYiKnq178xGI3Ng.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/849/1*Ek7kLJ89dQ76mP2NTTc9xQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/938/1*wxrb8gsGvCsOLt-m370H4Q.png" /></figure><h3>Deploying the Tiers: EC2 Instances and RDS</h3><p>With the network secured, we deploy the compute resources into their respective subnets.</p><h3><strong>Application and Presentation Tiers (EC2)</strong></h3><p>We launch three EC2 instances using the same base AMI (e.g., Amazon Linux 2):</p><ol><li><strong>Bastion Host:</strong> Deployed in the <strong>Public Subnet</strong>. It is a hardened access point, allowing us to securely SSH into the private instances.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4q4XGoQ2yG2rKNurHApNGw.png" /></figure><p><strong>2. Web Server (Presentation Tier):</strong> Deployed in the <strong>Public Subnet</strong>. It receives public traffic, often acting as a proxy or hosting static content. We use <strong>User Data</strong> to install and start the web server stack (e.g., Apache/PHP) on launch.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SZIGaVE9HeWx2zgH6wZ9Iw.png" /></figure><p><strong>3. App Server (Application Tier):</strong> Deployed in a <strong>Private Subnet</strong>. It contains the business logic. It’s configured to run a database client (e.g., MariaDB client) to communicate with the RDS instance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FdsjzGvLUXzQHEyMKVc8og.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E_NMc52IuoRLcZYNrfDYhA.png" /></figure><h3>Data Tier (RDS)</h3><p>The most sensitive layer is hosted by <strong>Amazon RDS</strong> for a managed database experience.</p><ol><li><strong>DB Subnet Group:</strong> First, a DB Subnet Group is created, explicitly specifying the dedicated <strong>Private Database Subnets</strong>.</li><li><strong>RDS Instance:</strong> We launch a managed database (e.g., <strong>MariaDB</strong> on the Free Tier).</li><li><strong>Configuration:</strong> The RDS instance is placed in the created <strong>DB Subnet Group</strong> and must have <strong>Public access set to No</strong> for maximum security. It is associated only with the highly restrictive <strong>Database SG</strong>.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*niqXmDc_0MriqVD70IGrwA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LgibYo1j5lXErLVDfnueDQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uN7yQED6ech3l3FF3KdmLQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CZv6qzx-K18rUa0bItRjrA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6MERurAWT5ciBH0S3ZMc1Q.png" /></figure><h3>4. Final Validation: Testing Connectivity</h3><p>The final step is to validate that the cross-tier communication works as intended, proving the architecture is functional and secure.</p><ol><li><strong>Access the Bastion Host:</strong> SSH into the Bastion Host using its Public IP.</li><li><strong>Jump to the App Server:</strong> From the Bastion Host, use its key to SSH into the <strong>App Server</strong> using the App Server’s <strong>Private IP address</strong>.</li><li><strong>Connect to the Database:</strong> From the App Server, use the MySQL client to connect to the RDS database endpoint.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/744/1*uJ4Wsyaad1FspieXax2Olg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/642/1*3qalf03jFoKaXMqV4aGddA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/766/1*Y_r_elxUvwRsAhGo3P0zJw.png" /></figure><p>Successfully connecting to the database from the App Server confirms that the networking (VPC, Subnets, Route Tables, and NAT Gateway) and security (Security Groups) are configured correctly for a secure, multi-tier deployment!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/698/1*raOU5xmhlAPxrLEVuGFl1g.png" /></figure><p><strong>Note to Reader:</strong> This architecture provides a robust, highly available, and secure foundation. For production use, consider adding an <strong>Application Load Balancer (ALB)</strong> and <strong>Auto Scaling Groups (ASGs)</strong> to the Web and App tiers for horizontal scaling and self-healing capabilities.</p><p>Happy Learning!</p><h3>A message from our Founder</h3><p><strong>Hey, </strong><a href="https://linkedin.com/in/sunilsandhu"><strong>Sunil</strong></a><strong> here.</strong> I wanted to take a moment to thank you for reading until the end and for being a part of this community.</p><p>Did you know that our team run these publications as a volunteer effort to over 3.5m monthly readers? <strong>We don’t receive any funding, we do this to support the community. ❤️</strong></p><p>If you want to show some love, please take a moment to <strong>follow me on </strong><a href="https://linkedin.com/in/sunilsandhu"><strong>LinkedIn</strong></a><strong>, </strong><a href="https://tiktok.com/@messyfounder"><strong>TikTok</strong></a>, <a href="https://instagram.com/sunilsandhu"><strong>Instagram</strong></a>. You can also subscribe to our <a href="https://newsletter.plainenglish.io/"><strong>weekly newsletter</strong></a>.</p><p>And before you go, don’t forget to <strong>clap</strong> and <strong>follow</strong> the writer️!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0d70fc03a97d" width="1" height="1" alt=""><hr><p><a href="https://aws.plainenglish.io/architecting-for-scale-a-step-by-step-guide-to-building-a-three-tier-architecture-on-aws-0d70fc03a97d">Architecting for Scale: A Step-by-Step Guide to Building a Three-Tier Architecture on AWS</a> was originally published in <a href="https://aws.plainenglish.io/">AWS in Plain English</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Architecting for Scale: A Step-by-Step Guide to Building a Three-Tier Architecture on AWS]]></title>
            <link>https://medium.com/@incoomdominic/architecting-for-scale-a-step-by-step-guide-to-building-a-three-tier-architecture-on-aws-1f285c8023da?source=rss-533dd8a1d6d8------2</link>
            <guid isPermaLink="false">https://medium.com/p/1f285c8023da</guid>
            <category><![CDATA[bastion-host]]></category>
            <category><![CDATA[aws-ec2-instance]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[subnet]]></category>
            <category><![CDATA[aws-nat-gateway]]></category>
            <dc:creator><![CDATA[Dominic Kwasi Appiah]]></dc:creator>
            <pubDate>Thu, 13 Nov 2025 00:21:56 GMT</pubDate>
            <atom:updated>2025-11-13T00:21:56.945Z</atom:updated>
            <content:encoded><![CDATA[<p>A three-tier architecture is the backbone of almost all scalable, secure, and highly available web applications. It logically separates an application into three distinct layers: the <strong>Presentation (Web) Tier</strong>, the <strong>Application Tier</strong>, and the <strong>Data Tier</strong>.</p><p>This guide walks you through deploying this robust architecture on Amazon Web Services (AWS) using core services like <strong>Amazon VPC</strong>, <strong>Amazon EC2</strong>, and <strong>Amazon RDS</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/971/1*JnWc021XLJoFxM3UIX19Lw.png" /></figure><h3>VPC and Subnet Configuration</h3><p>We will create a custom VPC (e.g., 192.168.0.0/16) and logically divide it into a set of subnets to enforce security and availability best practices.</p><ul><li><strong>Public Subnet (e.g., </strong><strong>192.168.1.0/24):</strong> This is for resources that need direct internet access (e.g., Load Balancers, Bastion Host, Web Server).</li><li><strong>Private Application Subnet(s) (e.g., </strong><strong>192.168.2.0/24, </strong><strong>192.168.3.0/24):</strong> These host the application servers and cannot be reached directly from the internet.</li><li><strong>Private Database Subnet(s) (e.g., </strong><strong>192.168.4.0/24):</strong> These host the database and are the most restricted.</li></ul><p>Crucially, we will place subnets across <strong>two different Availability Zones (AZs)</strong> to ensure high availability and resilience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-ucLlvMSUCuzmKY-dwy7Ug.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N0y5ERAzu7eEIlK_nKfBgg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1014/1*uj5-00x7RpZHL7DxIaJk2A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-ucLlvMSUCuzmKY-dwy7Ug.png" /></figure><h3>Internet and NAT Gateways</h3><p>To enable internet access for our tiers:</p><ol><li><strong>Internet Gateway (IGW):</strong> We create an IGW and attach it to the VPC. This is the entry and exit point for internet traffic to and from the Public Subnet.</li><li><strong>NAT Gateway (NAT GW):</strong> We deploy a NAT Gateway in the <strong>Public Subnet</strong> and assign it an <strong>Elastic IP (EIP)</strong>. This allows resources in the Private Subnets (like our App Servers) to initiate outbound connections (e.g., for updates) without exposing them to incoming internet traffic.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T8Tqc8bqxH3FygcQ9hSvxg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gsuVk1ShO_IJTq5mMS4xfw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*glYAE22u5G0iFCzkSE88Kw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GsKJxfQG3rnEMrVO1v_LGw.png" /></figure><h3>Route Tables</h3><p>We then define routing rules to direct traffic:</p><ul><li><strong>Public Route Table:</strong> Associates the Public Subnet(s) and has a default route (0.0.0.0/0) pointing to the <strong>Internet Gateway</strong>.</li><li><strong>Private Route Table:</strong> Associates the Private Subnet(s) and has a default route (0.0.0.0/0) pointing to the <strong>NAT Gateway</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qrBOsL7ke5wpLLLM4TCdXQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jPRZPsN1Hpy01PrFNBPRLw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q53siyg97SOVW5sNrhOBlw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ceGKdXt_k-yf3gl7kPoz4A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w809ss6psNLC4V50R38sqQ.png" /></figure><h3>Enforcing Isolation: Security Groups</h3><p>Security Groups (SGs) act as virtual firewalls to control inbound and outbound traffic for your instances. We create four highly restrictive SGs, implementing the <strong>principle of least privilege</strong>.</p><pre>Security Group,Inbound Rules,Source<br>Bastion Host SG,SSH (Port 22),Your Public IP<br>Web Server SG,&quot;HTTP (Port 80), HTTPS (Port 443)&quot;,0.0.0.0/0 (Internet)<br>App Server SG,HTTP/S (Port 80/443),&quot;0.0.0.0/0, SSH (Port 22)&quot;<br>Database SG,MySQL/Aurora (Port 3306),App Server SG and Bastion Host SG</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-cPXSA3yj9-RwAvRHJbC8A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rnjhWr7fHuQonkGuzLQ7Nw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dc_15SurYiKnq178xGI3Ng.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/849/1*Ek7kLJ89dQ76mP2NTTc9xQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/938/1*wxrb8gsGvCsOLt-m370H4Q.png" /></figure><h3>Deploying the Tiers: EC2 Instances and RDS</h3><p>With the network secured, we deploy the compute resources into their respective subnets.</p><h3>Application and Presentation Tiers (EC2)</h3><p>We launch three EC2 instances using the same base AMI (e.g., Amazon Linux 2):</p><ol><li><strong>Bastion Host:</strong> Deployed in the <strong>Public Subnet</strong>. It is a hardened access point, allowing us to securely SSH into the private instances.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4q4XGoQ2yG2rKNurHApNGw.png" /></figure><p><strong>2. Web Server (Presentation Tier):</strong> Deployed in the <strong>Public Subnet</strong>. It receives public traffic, often acting as a proxy or hosting static content. We use <strong>User Data</strong> to install and start the web server stack (e.g., Apache/PHP) on launch.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SZIGaVE9HeWx2zgH6wZ9Iw.png" /></figure><p><strong>3. App Server (Application Tier):</strong> Deployed in a <strong>Private Subnet</strong>. It contains the business logic. It’s configured to run a database client (e.g., MariaDB client) to communicate with the RDS instance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FdsjzGvLUXzQHEyMKVc8og.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*E_NMc52IuoRLcZYNrfDYhA.png" /></figure><h3>Data Tier (RDS)</h3><p>The most sensitive layer is hosted by <strong>Amazon RDS</strong> for a managed database experience.</p><ol><li><strong>DB Subnet Group:</strong> First, a DB Subnet Group is created, explicitly specifying the dedicated <strong>Private Database Subnets</strong>.</li><li><strong>RDS Instance:</strong> We launch a managed database (e.g., <strong>MariaDB</strong> on the Free Tier).</li><li><strong>Configuration:</strong> The RDS instance is placed in the created <strong>DB Subnet Group</strong> and must have <strong>Public access set to No</strong> for maximum security. It is associated only with the highly restrictive <strong>Database SG</strong>.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*niqXmDc_0MriqVD70IGrwA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LgibYo1j5lXErLVDfnueDQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uN7yQED6ech3l3FF3KdmLQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CZv6qzx-K18rUa0bItRjrA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6MERurAWT5ciBH0S3ZMc1Q.png" /></figure><h3>4. Final Validation: Testing Connectivity</h3><p>The final step is to validate that the cross-tier communication works as intended, proving the architecture is functional and secure.</p><ol><li><strong>Access the Bastion Host:</strong> SSH into the Bastion Host using its Public IP.</li><li><strong>Jump to the App Server:</strong> From the Bastion Host, use its key to SSH into the <strong>App Server</strong> using the App Server’s <strong>Private IP address</strong>.</li><li><strong>Connect to the Database:</strong> From the App Server, use the MySQL client to connect to the RDS database endpoint.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/744/1*uJ4Wsyaad1FspieXax2Olg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/642/1*3qalf03jFoKaXMqV4aGddA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/766/1*Y_r_elxUvwRsAhGo3P0zJw.png" /></figure><p>Successfully connecting to the database from the App Server confirms that the networking (VPC, Subnets, Route Tables, and NAT Gateway) and security (Security Groups) are configured correctly for a secure, multi-tier deployment!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/698/1*raOU5xmhlAPxrLEVuGFl1g.png" /></figure><p><strong>Note to Reader:</strong> This architecture provides a robust, highly available, and secure foundation. For production use, consider adding an <strong>Application Load Balancer (ALB)</strong> and <strong>Auto Scaling Groups (ASGs)</strong> to the Web and App tiers for horizontal scaling and self-healing capabilities.</p><p>Happy Learning!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1f285c8023da" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Beyond the Checklist: Cracking Cloud Interviews When You Don’t (Quite) Fit the Mold]]></title>
            <link>https://towardsaws.com/beyond-the-checklist-cracking-cloud-interviews-when-you-dont-quite-fit-the-mold-b5af18e14ae0?source=rss-533dd8a1d6d8------2</link>
            <guid isPermaLink="false">https://medium.com/p/b5af18e14ae0</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[cloud-careers]]></category>
            <dc:creator><![CDATA[Dominic Kwasi Appiah]]></dc:creator>
            <pubDate>Wed, 05 Nov 2025 14:34:52 GMT</pubDate>
            <atom:updated>2025-11-06T03:23:30.650Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/884/1*S2_rF6PxwuhSlYFw5O2-xQ.png" /></figure><p>It’s a familiar scenario for many aspiring cloud professionals: you spot a dream job posting, your heart races, and then you hit the “Requirements” section. “5+ years of AWS experience.” “Expert in Kubernetes.” “Proven track record as a Senior Cloud Architect.” Suddenly, that dream job feels like an impossible climb.</p><p>But what if I told you that most job requirements are misunderstood? What if they’re not rigid rules, but flexible guidelines?</p><p>Think about it from the hiring manager’s perspective. They’re trying to describe their ideal candidate — someone who can hit the ground running, solve complex problems, and add immediate value. When a posting demands “5 years of AWS experience,” they’re not picturing a stopwatch clicking away on a specific job title. They’re envisioning:</p><p><strong>Minimal Onboarding:</strong> A professional who doesn’t require extensive basic training.</p><p><strong>Deep Understanding: </strong>An individual who comprehends AWS services well enough to make sound architectural decisions.</p><p><strong>Self-Sufficiency:</strong> Someone capable of designing and implementing cloud solutions independently.</p><p>Essentially, they are NOT saying:</p><p>1.‘‘You must have spent exactly 60 months in a role with ‘AWS’ in the title.”</p><p>2.“We will automatically discard any application showing 4 years and 11 months of experience.”</p><p>3.“Certifications and personal projects hold no weight against ‘real’ job experience.”</p><h4>The 60–70% Rule: Your New Application Mantra</h4><p><strong>If you meet 60–70% of the listed requirements, and the role genuinely excites you, apply.</strong></p><p>Don’t let the job description be the reason you miss out on an opportunity. Your job is to present your qualifications and let the hiring team decide if you’re a good fit. Their job is to evaluate. Your job is <em>not</em> to reject yourself prematurely based on an arbitrarily strict interpretation of a wish list.</p><h3>How to Bridge the “Gap”</h3><p>So, how do you effectively present yourself when you don’t tick every box?</p><ol><li><strong>Translate Experience:</strong> Don’t just list previous roles. Detail <em>how</em> your past responsibilities (even in non-cloud roles) translate into valuable skills for a cloud environment (e.g., “Managed Linux servers” translates to “Experience with EC2 instance administration”).</li><li><strong>Showcase Certifications:</strong> AWS, Azure, GCP certifications aren’t just badges; they demonstrate foundational knowledge and a commitment to learning. Highlight them prominently.</li><li><strong>Build a Portfolio:</strong> This is your secret weapon. Deploy a simple web application using serverless technologies, automate an infrastructure setup with Terraform, or create a data pipeline in the cloud. Host these projects on GitHub and link them clearly. This proves you can <em>do</em> the work.</li><li><strong>Emphasize Soft Skills:</strong> Problem-solving, adaptability, a strong desire to learn, and teamwork are invaluable in the ever-evolving cloud landscape.</li><li><strong>Tailor Your Application:</strong> Customize your resume and cover letter for <em>each</em> application, explicitly addressing how your existing skills and projects align with the role’s actual needs, even if the “years of experience” number doesn’t match.</li></ol><p>The cloud industry is rapidly expanding, and demand for skilled professionals far outweighs the supply of those with perfectly aligned “5 years of experience” on paper. Companies are increasingly open to talent that demonstrates capability and potential, rather than just strict adherence to a checklist.</p><p>Stop self-rejecting. Start applying. Your next great cloud opportunity might just be waiting for you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b5af18e14ae0" width="1" height="1" alt=""><hr><p><a href="https://towardsaws.com/beyond-the-checklist-cracking-cloud-interviews-when-you-dont-quite-fit-the-mold-b5af18e14ae0">Beyond the Checklist: Cracking Cloud Interviews When You Don’t (Quite) Fit the Mold</a> was originally published in <a href="https://towardsaws.com/">Towards AWS</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Host a Static Website on AWS: Two Powerful Methods (S3 + CloudFront vs. AWS Amplify) — 2025]]></title>
            <link>https://aws.plainenglish.io/how-to-host-a-static-website-on-aws-two-powerful-methods-s3-cloudfront-vs-aws-amplify-2025-f84abce51fbf?source=rss-533dd8a1d6d8------2</link>
            <guid isPermaLink="false">https://medium.com/p/f84abce51fbf</guid>
            <category><![CDATA[aws-amplify]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[aws-cloudfront]]></category>
            <category><![CDATA[aws-s3]]></category>
            <dc:creator><![CDATA[Dominic Kwasi Appiah]]></dc:creator>
            <pubDate>Tue, 04 Nov 2025 11:09:39 GMT</pubDate>
            <atom:updated>2025-11-09T15:03:26.528Z</atom:updated>
            <content:encoded><![CDATA[<h3>How to Host a Static Website on AWS: Two Powerful Methods (S3 + CloudFront vs. AWS Amplify) — 2025</h3><p>In this guide, I’ll walk you through the two most popular methods of static website hosting, using screenshots from a real deployment I did recently.</p><ol><li><strong>The “Classic” Method:</strong> Manually combining <strong>S3</strong> for storage and <strong>CloudFront</strong> (a CDN) for secure, high-speed delivery. This gives you maximum control.</li><li><strong>The “Managed” Method:</strong> Using <strong>AWS Amplify</strong>, a modern, all-in-one service that handles everything from code to deployment with a built-in CI/CD pipeline.</li></ol><p>Let’s break down both.</p><h3>🛠️ Method 1: The “Classic” Build (S3 + CloudFront)</h3><p>This is the foundational method. You manually provision the storage (S3) and the delivery network (CloudFront). This is perfect for understanding exactly how the services fit together.</p><p><strong>Step 1: Create and Prep Your S3 Bucket</strong></p><p>First, we need a place to store our index.html, style.css, and other files.</p><ol><li>Create the Bucket: In the AWS Console, go to S3 and create a new bucket. Give it a unique name. In our example, we’re using portwebgh in the us-east-1 region.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fMzoqR9Ux-evgn1I_n0LRw.png" /></figure><p><strong>2.Upload Your Files:</strong> Click into your new bucket and upload your static website files from the <strong>Objects</strong> tab. At a minimum, you’ll need an index.html file.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A7bDDBbiqADNSSKA3A11Ww.png" /></figure><h3>Step 2: Configure Bucket Permissions</h3><p>This is the most critical step. We need to allow public <em>read</em> access to the objects in the bucket.</p><ol><li><strong>Turn Off “Block Public Access”:</strong> By default, S3 blocks all public access. In your bucket’s <strong>Permissions</strong> tab, <strong>Edit</strong> the “Block public access (bucket settings)” and <strong>uncheck</strong> the “Block all public access” box.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_h661NfiDLKDYRR42-DEgA.png" /></figure><p><strong>2. Apply a Public Read Bucket Policy:</strong> Still on the <strong>Permissions</strong> tab, scroll to <strong>Bucket policy</strong> and paste in a policy that allows public s3:GetObject actions. <strong>Remember to replace </strong><strong>portwebgh with your bucket&#39;s name!</strong></p><pre>{     &quot;Version&quot;: &quot;2012-10-17&quot;,     &quot;Statement&quot;: [         {             &quot;Sid&quot;: &quot;PublicReadGetObject&quot;,             &quot;Effect&quot;: &quot;Allow&quot;,             &quot;Principal&quot;: &quot;*&quot;,             &quot;Action&quot;: &quot;s3:GetObject&quot;,             &quot;Resource&quot;: &quot;arn:aws:s3:::portwebgh/*&quot;         }     ] }</pre><h3>Step 3: Enable Static Website Hosting</h3><p>Now, we tell S3 to treat this bucket as a website.</p><ol><li>Go to the <strong>Properties</strong> tab in your bucket.</li><li>Scroll down to <strong>Static website hosting</strong> and click <strong>Edit</strong>.</li><li><strong>Enable</strong> it and set your “Index document” to index.html.</li><li>After saving, S3 will give you a <strong>Bucket website endpoint</strong>. Copy this URL.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XvEwv64UPJFr2BKmgdG3Xw.png" /></figure><h3>Step 4: Create a CloudFront Distribution</h3><p>We <em>could</em> stop here, but the S3 endpoint is slow and not secure (HTTP). We’ll use CloudFront (AWS’s CDN) to fix this.</p><ol><li>Navigate to the <strong>CloudFront</strong> service.</li><li>Click <strong>Create distribution</strong>.</li><li><strong>Origin domain:</strong> Paste the S3 bucket website endpoint you copied in the last step.</li><li><strong>Viewer protocol policy:</strong> Set this to <strong>Redirect HTTP to HTTPS</strong>.</li><li><strong>Default root object:</strong> Type index.html.</li><li>Click <strong>Create distribution</strong>.</li></ol><p>It will take a few minutes to deploy. You’ll see its status as “Deploying” or “Enabled” on the dashboard. Once enabled, your site is live and securely served at the <strong>Distribution domain name</strong> (e.g., d5gp...cloudfront.net).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_JDTxLlbfpgRtaMdhkMHgw.png" /></figure><h3>🚀 Method 2: The “Managed” Alternative (AWS Amplify)</h3><p>If the steps above seem too manual, or if you’re a developer who loves a good Git-based workflow, AWS Amplify is for you. It’s an all-in-one service that handles the build, deployment, and hosting for you, automatically setting up S3 and CloudFront under the hood.</p><p><strong>Step 1: Create Your Amplify App</strong></p><p>In the AWS Amplify console, you start by creating a “new app” and connecting it to your Git provider (like GitHub, GitLab, Bitbucket, or AWS CodeCommit).</p><p>You can see our portweb app is already created and shows as &quot;Deployed.&quot;</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uc4W8vZrBDrcnDwvr5-BZA.png" /></figure><h3>Step 2: Connect &amp; Deploy Your Branch</h3><p>Amplify’s magic is its CI/CD pipeline. When you push code to a specific branch (e.g., main or staging), Amplify automatically:</p><ol><li>Detects the push.</li><li>Builds your app (if it’s a framework like React or Vue).</li><li>Deploys the static files.</li></ol><p>Here, you can see our staging branch is deployed. Amplify automatically provides a secure ...amplifyapp.com domain for every branch, which is perfect for testing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lj1-J4kYkkj_LqlR2kDEtQ.png" /></figure><h3>Step 3: Your Site is Live!</h3><p>And that’s it! You can now visit your Amplify domain, and your website is live. In the background, Amplify has automatically created an S3 bucket, configured a CloudFront distribution, and applied an HTTPS certificate. You get all the benefits of Method 1, but with a fraction of the manual setup and a built-in CI/CD pipeline.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mlTB6oHbNZdztwkfPUNHmg.png" /></figure><p>Lastly, let’s take a look at the bucket policy after the hosting off s3 for both the CloudFront and s3 and amplify with s3 as the source or origin.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MCUm97WA0nMINOTyxoU1vQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S-UtAOKc8Z-dlLs5HJ2Yzw.png" /></figure><h3>🤔 Which Method Should You Choose?</h3><p>Both methods are excellent, but they serve different needs:</p><ul><li><strong>Choose S3 + CloudFront (Method 1) if:</strong></li><li>You need granular control over every aspect of the S3 bucket policy or CloudFront cache behavior.</li><li>You are deploying files manually and <em>not</em> using a Git-based workflow.</li><li>You are learning the AWS fundamentals and want to build the infrastructure yourself.</li><li><strong>Choose AWS Amplify (Method 2) if:</strong></li><li>Your code lives in a Git repository.</li><li>You want a fast, automated CI/CD pipeline for builds and deployments.</li><li>You want features like atomic deployments, branch-based previews, and easy custom domain management.</li><li>You prefer a managed, “serverless” experience and don’t want to configure S3 or CloudFront manually.</li></ul><p><strong><em>Jump right into my YouTube channel for video tutorial for better understanding.</em></strong></p><iframe src="https://cdn.embedly.com/widgets/media.html?url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Db8ihCyObsyU&amp;type=text%2Fhtml&amp;schema=google&amp;display_name=YouTube&amp;src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fb8ihCyObsyU" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/9bd3e1f2569ebef215f961f02adc3443/href">https://medium.com/media/9bd3e1f2569ebef215f961f02adc3443/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FplGC2cK0tvM%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DplGC2cK0tvM&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FplGC2cK0tvM%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/c8393e0e03657b4e64b6ab987c403b27/href">https://medium.com/media/c8393e0e03657b4e64b6ab987c403b27/href</a></iframe><p>Happy building!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f84abce51fbf" width="1" height="1" alt=""><hr><p><a href="https://aws.plainenglish.io/how-to-host-a-static-website-on-aws-two-powerful-methods-s3-cloudfront-vs-aws-amplify-2025-f84abce51fbf">How to Host a Static Website on AWS: Two Powerful Methods (S3 + CloudFront vs. AWS Amplify) — 2025</a> was originally published in <a href="https://aws.plainenglish.io/">AWS in Plain English</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>