<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Shehzad Ahmad</title>
    <description>The latest articles on DEV Community by Shehzad Ahmad (@shehzad_ahmad_153).</description>
    <link>https://dev.to/shehzad_ahmad_153</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4122766%2F5350d324-d1d8-451c-81f1-ac58c4fd24a2.png</url>
      <title>DEV Community: Shehzad Ahmad</title>
      <link>https://dev.to/shehzad_ahmad_153</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/shehzad_ahmad_153"/>
    <language>en</language>
    <item>
      <title>Building a Fully Automated CI/CD Pipeline on AWS with Docker, ECR, CodeBuild, CodePipeline and ECS Fargate</title>
      <dc:creator>Shehzad Ahmad</dc:creator>
      <pubDate>Sat, 21 Nov 2026 09:07:26 +0000</pubDate>
      <link>https://dev.to/shehzad_ahmad_153/building-a-fully-automated-cicd-pipeline-on-aws-with-docker-ecr-codebuild-codepipeline-and-ecs-189o</link>
      <guid>https://dev.to/shehzad_ahmad_153/building-a-fully-automated-cicd-pipeline-on-aws-with-docker-ecr-codebuild-codepipeline-and-ecs-189o</guid>
      <description>&lt;h2&gt;
  
  
  Introduction
&lt;/h2&gt;

&lt;p&gt;Shipping software by hand is one of the quickest ways to introduce mistakes. Someone builds an image on their laptop, pushes it to a registry, logs into a console and clicks through a deployment. It works until the day a step is skipped, a wrong tag is deployed or the one person who knows the process is on leave.&lt;/p&gt;

&lt;p&gt;Continuous Integration and Continuous Delivery (CI/CD) solves this by turning the release process into code that runs the same way every time. In this project I built a complete CI/CD pipeline on AWS that takes a change from a &lt;code&gt;git push&lt;/code&gt; to a running container on &lt;strong&gt;Amazon ECS Fargate&lt;/strong&gt;, with no manual steps in between.&lt;/p&gt;

&lt;p&gt;To keep the focus on the pipeline rather than the application, I used the classic &lt;strong&gt;2048 game&lt;/strong&gt; as the workload. It is a static web app that is easy to containerize, and it gives an instantly visible result whenever a deployment succeeds.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Credit:&lt;/strong&gt; the application source and project outline come from the &lt;a href="https://github.com/techwithlucy/ztc-projects" rel="noopener noreferrer"&gt;ZTC projects&lt;/a&gt; learning repository. The AWS setup, IAM configuration and pipeline were built and verified by me.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;At a glance&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Time: about 2 to 3 hours&lt;/li&gt;
&lt;li&gt;Cost: about $1 or less&lt;/li&gt;
&lt;li&gt;Result: every push to &lt;code&gt;main&lt;/code&gt; is built, stored in ECR and deployed to ECS automatically&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What the pipeline does
&lt;/h2&gt;

&lt;p&gt;Whenever I push code to GitHub, three things happen automatically:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Source:&lt;/strong&gt; CodePipeline detects the push and fetches the latest code from GitHub.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Build:&lt;/strong&gt; CodeBuild runs the instructions in &lt;code&gt;buildspec.yml&lt;/code&gt;. It builds a Docker image, tags it, pushes it to Amazon ECR and produces a small file called &lt;code&gt;imagedefinitions.json&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Deploy:&lt;/strong&gt; CodePipeline hands that file to Amazon ECS, which replaces the running container with the new image.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fkaz6kb2pmxoxs5eqbfo8.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fkaz6kb2pmxoxs5eqbfo8.png" alt=" " width="799" height="318"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;&lt;strong&gt;Architecture diagram of the CI/CD pipeline&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;
&lt;h2&gt;
  
  
  Tech stack and why each piece is there
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Service&lt;/th&gt;
&lt;th&gt;Role in the project&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;GitHub&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Stores the source code and triggers the pipeline on every push&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Docker + Nginx&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Packages the app so it runs identically everywhere&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Amazon ECR&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Private registry that stores the Docker images&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;AWS CodeBuild&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Managed build server that builds and pushes the image&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Amazon S3&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Holds the build artifacts passed between stages&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;AWS CodePipeline&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Orchestrates Source, Build and Deploy&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Amazon ECS (Fargate)&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Runs the container without any servers to manage&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;IAM&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Gives each service only the access it needs&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;I chose &lt;strong&gt;Fargate&lt;/strong&gt; because it removes server management completely. There are no EC2 instances to patch or scale, so the pipeline is the only moving part, which is exactly what I wanted to learn.&lt;/p&gt;
&lt;h2&gt;
  
  
  Step 1: Containerize the application
&lt;/h2&gt;

&lt;p&gt;The Dockerfile is intentionally small. It uses the official Nginx image, copies the game files into Nginx's web root and starts Nginx in the foreground so the container keeps running.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight docker"&gt;&lt;code&gt;&lt;span class="k"&gt;FROM&lt;/span&gt; nginx:latest
&lt;span class="k"&gt;COPY&lt;/span&gt; . /usr/share/nginx/html
&lt;span class="k"&gt;EXPOSE&lt;/span&gt; 80
&lt;span class="k"&gt;CMD&lt;/span&gt; &lt;span class="o"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"nginx"&lt;/span&gt;, &lt;span class="s2"&gt;"-g"&lt;/span&gt;, &lt;span class="s2"&gt;"daemon off;"&lt;/span&gt;&lt;span class="o"&gt;]&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;I built it locally first. Testing the container on my own machine before touching AWS means any problem at this stage is a Docker problem, not a cloud problem, which makes it much easier to diagnose.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;docker build -t 2048-game .
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fe3zrnz9hae03p4irq46t.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fe3zrnz9hae03p4irq46t.png" alt=" " width="799" height="438"&gt;&lt;/a&gt;&lt;br&gt;
&lt;strong&gt;&lt;em&gt;Docker image building successfully&lt;/em&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;h2&gt;
  
  
  Step 2: Store the image in Amazon ECR
&lt;/h2&gt;

&lt;p&gt;Next I created a private repository in Amazon ECR. This is where CodeBuild will later push every new version of the image, and where ECS will pull it from.&lt;/p&gt;

&lt;p&gt;To push the image I tagged it with the repository URI, authenticated Docker with a temporary ECR login token and pushed:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;docker tag 2048-game:latest &lt;span class="o"&gt;&amp;lt;&lt;/span&gt;ECR_URI&lt;span class="o"&gt;&amp;gt;&lt;/span&gt;:latest

aws ecr get-login-password --region &lt;span class="o"&gt;&amp;lt;&lt;/span&gt;your-region&lt;span class="o"&gt;&amp;gt;&lt;/span&gt; \
  &lt;span class="o"&gt;|&lt;/span&gt; docker login --username AWS --password-stdin &lt;span class="o"&gt;&amp;lt;&lt;/span&gt;ECR_URI&lt;span class="o"&gt;&amp;gt;&lt;/span&gt;

docker push &lt;span class="o"&gt;&amp;lt;&lt;/span&gt;ECR_URI&lt;span class="o"&gt;&amp;gt;&lt;/span&gt;:latest
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The image appeared in the repository straight away.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fe2dshbvxiiyj5exmxyps.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fe2dshbvxiiyj5exmxyps.png" alt=" " width="800" height="131"&gt;&lt;/a&gt;&lt;br&gt;
&lt;strong&gt;&lt;em&gt;Image stored in the ECR repository&lt;/em&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;h2&gt;
  
  
  Step 3: Deploy manually to ECS Fargate first
&lt;/h2&gt;

&lt;p&gt;Before automating anything, I deployed the container by hand. This is the most useful habit I took from the project: &lt;strong&gt;if it does not work manually, a pipeline will only automate the failure.&lt;/strong&gt; Having a known-good manual deployment also gives you something to compare against when the pipeline misbehaves.&lt;/p&gt;

&lt;p&gt;The manual deployment had four parts:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Cluster:&lt;/strong&gt; a logical group for my tasks, created with the AWS Fargate (serverless) option.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Task definition:&lt;/strong&gt; the blueprint for the container. It names the container (&lt;code&gt;2048-container&lt;/code&gt;), points to the ECR image and maps port 80 to port 80.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Service:&lt;/strong&gt; keeps the desired number of tasks (one) running and replaces any that stop. I placed it in the default VPC and enabled a public IP.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Security group:&lt;/strong&gt; allows inbound HTTP on port 80, otherwise the browser cannot reach the container.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fqzzjldwourl3vxtfskwm.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fqzzjldwourl3vxtfskwm.png" alt=" " width="799" height="233"&gt;&lt;/a&gt;&lt;br&gt;
&lt;strong&gt;&lt;em&gt;ECS cluster created successfully&lt;/em&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Once the task was running, I opened its public IP in a browser and the game loaded. That confirmed the image, the task definition, the networking and the security group were all correct.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fizuolaie3tbzhnzasvmd.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fizuolaie3tbzhnzasvmd.png" alt=" " width="800" height="429"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;&lt;strong&gt;The 2048 game served from the container on ECS&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;
&lt;h2&gt;
  
  
  Step 4: Create my own GitHub repository
&lt;/h2&gt;

&lt;p&gt;CodePipeline needs a repository I control so it can listen for pushes, so I created a new repository and pushed the project to it, along with a &lt;code&gt;buildspec.yml&lt;/code&gt; in the root.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;git init
git add .
git commit -m &lt;span class="s2"&gt;"Initial commit"&lt;/span&gt;
git remote add origin &lt;span class="o"&gt;&amp;lt;&lt;/span&gt;your-repository-url&lt;span class="o"&gt;&amp;gt;&lt;/span&gt;
git branch -M main
git push -u origin main
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fmglmxz3dlr0xxzgpc415.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fmglmxz3dlr0xxzgpc415.png" alt=" " width="800" height="342"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;&lt;strong&gt;GitHub repository with the Dockerfile, buildspec.yml and game source&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;
&lt;h2&gt;
  
  
  Step 5: Write the buildspec (the heart of CI)
&lt;/h2&gt;

&lt;p&gt;&lt;code&gt;buildspec.yml&lt;/code&gt; tells CodeBuild exactly what to do. It has three phases:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;pre_build:&lt;/strong&gt; logs in to ECR so the build can push images.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;build:&lt;/strong&gt; builds the Docker image and tags it with the ECR repository URI.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;post_build:&lt;/strong&gt; pushes the image and writes &lt;code&gt;imagedefinitions.json&lt;/code&gt;.
&lt;/li&gt;
&lt;/ul&gt;
&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight yaml"&gt;&lt;code&gt;
&lt;span class="na"&gt;version&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mf"&gt;0.2&lt;/span&gt;

&lt;span class="na"&gt;phases&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
  &lt;span class="na"&gt;pre_build&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
    &lt;span class="na"&gt;commands&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
      &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="s2"&gt;"echo Logging in to Amazon ECR..."&lt;/span&gt;
      &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="s2"&gt;"aws ecr get-login-password --region &amp;lt;your-region&amp;gt; | docker login --username AWS --password-stdin &amp;lt;ECR_URI&amp;gt;"&lt;/span&gt;

  &lt;span class="na"&gt;build&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
    &lt;span class="na"&gt;commands&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
      &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="s2"&gt;"echo Building the Docker image..."&lt;/span&gt;
      &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="s2"&gt;"docker build -t 2048-game ."&lt;/span&gt;
      &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="s2"&gt;"docker tag 2048-game:latest &amp;lt;ECR_URI&amp;gt;:latest"&lt;/span&gt;

  &lt;span class="na"&gt;post_build&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
    &lt;span class="na"&gt;commands&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
      &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="s2"&gt;"echo Pushing the Docker image to Amazon ECR..."&lt;/span&gt;
      &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="s2"&gt;"docker push &amp;lt;ECR_URI&amp;gt;:latest"&lt;/span&gt;
      &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="s2"&gt;"echo Creating imagedefinitions.json for ECS deployment..."&lt;/span&gt;
      &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="s1"&gt;'printf ''[{"name":"2048-container","imageUri":"%s"}]'' "&amp;lt;ECR_URI&amp;gt;:latest" &amp;gt; imagedefinitions.json'&lt;/span&gt;

&lt;span class="na"&gt;artifacts&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
  &lt;span class="na"&gt;files&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
    &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="s"&gt;imagedefinitions.json&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;


&lt;p&gt;The most important detail is &lt;code&gt;imagedefinitions.json&lt;/code&gt;. It is the bridge between CodeBuild and ECS: it tells the ECS deploy action &lt;strong&gt;which container to update and which image to use&lt;/strong&gt;. The &lt;code&gt;name&lt;/code&gt; value must match the container name in the task definition exactly, otherwise the Deploy stage fails.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Frsjfvdwfcrhdvsfa6rw9.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Frsjfvdwfcrhdvsfa6rw9.png" alt=" " width="800" height="235"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;&lt;strong&gt;buildspec.yml configured with my region, repository and container name&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;
&lt;h2&gt;
  
  
  Step 6: Set up permissions with IAM
&lt;/h2&gt;

&lt;p&gt;AWS services cannot act on each other by default, so CodeBuild needs an IAM role. I created &lt;code&gt;codeBuildServiceRole&lt;/code&gt; with CodeBuild as the trusted entity and attached managed policies for ECR, CodeBuild and S3.&lt;/p&gt;

&lt;p&gt;Then I added a small inline policy that lets CodeBuild update only my ECS service, rather than every service in the account:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nl"&gt;"Version"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"2012-10-17"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"Statement"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;
    &lt;span class="p"&gt;{&lt;/span&gt;
      &lt;span class="nl"&gt;"Effect"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Allow"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="nl"&gt;"Action"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"ecs:UpdateService"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"ecs:DescribeServices"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="nl"&gt;"Resource"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"&amp;lt;ECS_SERVICE_ARN&amp;gt;"&lt;/span&gt;
    &lt;span class="p"&gt;}&lt;/span&gt;
  &lt;span class="p"&gt;]&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This inline policy is a small example of &lt;strong&gt;least privilege&lt;/strong&gt;: grant the narrowest permission that gets the job done. For a production setup I would tighten the managed policies the same way (more on that below).&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 7: Create the S3 bucket and CodeBuild project
&lt;/h2&gt;

&lt;p&gt;CodeBuild produces output such as &lt;code&gt;imagedefinitions.json&lt;/code&gt;, so I created an S3 bucket to hold build artifacts. Then I created the CodeBuild project:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Source: my GitHub repository, connected through an OAuth app credential managed by CodeBuild&lt;/li&gt;
&lt;li&gt;Service role: the existing &lt;code&gt;codeBuildServiceRole&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;Build instructions: use the &lt;code&gt;buildspec.yml&lt;/code&gt; file from the repository&lt;/li&gt;
&lt;li&gt;Artifacts: stored in the S3 bucket&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Before building the pipeline I triggered a build manually. Testing each stage on its own meant that when the full pipeline ran, any failure would be easy to place. The build succeeded, the image was pushed to ECR and &lt;code&gt;imagedefinitions.json&lt;/code&gt; appeared in S3.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fqtzest3tb5xomzr3ai0q.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fqtzest3tb5xomzr3ai0q.png" alt=" " width="800" height="200"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;&lt;strong&gt;&lt;code&gt;imagedefinitions.json&lt;/code&gt; stored in the S3 artifact bucket&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;
&lt;h2&gt;
  
  
  Step 8: Connect everything with CodePipeline
&lt;/h2&gt;

&lt;p&gt;Finally I created the pipeline, &lt;code&gt;2048-game-pipeline&lt;/code&gt;, with three stages:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Stage&lt;/th&gt;
&lt;th&gt;Provider&lt;/th&gt;
&lt;th&gt;What it does&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Source&lt;/td&gt;
&lt;td&gt;GitHub (OAuth app)&lt;/td&gt;
&lt;td&gt;Starts the pipeline when &lt;code&gt;main&lt;/code&gt; changes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Build&lt;/td&gt;
&lt;td&gt;AWS CodeBuild&lt;/td&gt;
&lt;td&gt;Runs &lt;code&gt;buildspec.yml&lt;/code&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Deploy&lt;/td&gt;
&lt;td&gt;Amazon ECS&lt;/td&gt;
&lt;td&gt;Updates &lt;code&gt;2048-service&lt;/code&gt; using &lt;code&gt;imagedefinitions.json&lt;/code&gt;
&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;I skipped the optional Test stage for this project. CodePipeline created its own service role, and the first run started immediately.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F49x4ym648zrsn8yme1jb.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F49x4ym648zrsn8yme1jb.png" alt=" " width="800" height="389"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;em&gt;CodePipeline created with Source, Build and Deploy stages&lt;/em&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Each stage turned green in turn, ending with a successful deployment to ECS.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fvldseowtku9y9awp2d4m.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fvldseowtku9y9awp2d4m.png" alt=" " width="799" height="217"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;em&gt;Deploy stage succeeded&lt;/em&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;h2&gt;
  
  
  Step 9: The real test, a code change
&lt;/h2&gt;

&lt;p&gt;A pipeline only proves itself when a change flows through it untouched. I edited the heading in &lt;code&gt;index.html&lt;/code&gt; to "2048 by Me", then ran just three commands:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;git add .
git commit -m &lt;span class="s2"&gt;"Changed game name to 2048 by Me"&lt;/span&gt;
git push -u origin main
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;That was the only manual action. The push triggered the pipeline, CodeBuild built and pushed a fresh image, and ECS started a new task. The ECS console shows the old tasks stopped and the new one running: a &lt;strong&gt;rolling deployment&lt;/strong&gt; that replaces the container without me touching the console.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fxwafq92l8jbe2img4fl4.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fxwafq92l8jbe2img4fl4.png" alt=" " width="800" height="193"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;&lt;strong&gt;ECS showing the new task running and older tasks stopped&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Reloading the public IP showed the updated title.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F43vgyncevznuzx89yaeq.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F43vgyncevznuzx89yaeq.png" alt=" " width="800" height="442"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;&lt;strong&gt;The updated game live on ECS Fargate&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Common problems and how to fix them
&lt;/h2&gt;

&lt;p&gt;If you build this yourself, these are the places it most often goes wrong:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Build fails at the ECR login or push:&lt;/strong&gt; the CodeBuild role is missing ECR permissions, or the region or repository URI in &lt;code&gt;buildspec.yml&lt;/code&gt; is wrong.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Deploy stage fails:&lt;/strong&gt; the container &lt;code&gt;name&lt;/code&gt; in &lt;code&gt;imagedefinitions.json&lt;/code&gt; does not match the task definition's container name.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Site does not load on the public IP:&lt;/strong&gt; the security group does not allow inbound port 80, or the service does not have a public IP enabled.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;CodeBuild cannot update the service:&lt;/strong&gt; the inline policy's resource ARN does not match your ECS service.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Pipeline does not trigger on push:&lt;/strong&gt; the Source stage is pointing at a different repository or branch.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;In almost every case the answer was in the CodeBuild logs or the failed stage's details, so read those first.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I learned
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Automate last.&lt;/strong&gt; Get the manual deployment working, then automate it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;imagedefinitions.json&lt;/code&gt; is the contract&lt;/strong&gt; between the build and the deployment. Small mismatches here cause the most confusing failures.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;IAM is where most pipeline problems hide.&lt;/strong&gt; Understanding which service needs which permission is half the work.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Test each stage in isolation&lt;/strong&gt; before chaining them together.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Fargate keeps the focus on delivery,&lt;/strong&gt; since there are no servers to look after.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  How I would harden this for production
&lt;/h2&gt;

&lt;p&gt;This project is designed for learning. For a real workload I would:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Replace broad managed policies such as &lt;code&gt;AmazonS3FullAccess&lt;/code&gt; with &lt;strong&gt;least-privilege, resource-scoped policies&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;Pin the base image to a &lt;strong&gt;specific version&lt;/strong&gt; instead of &lt;code&gt;nginx:latest&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Tag images with the &lt;strong&gt;commit SHA&lt;/strong&gt; as well as &lt;code&gt;latest&lt;/code&gt;, so any release can be traced and rolled back.&lt;/li&gt;
&lt;li&gt;Add a &lt;strong&gt;Test stage&lt;/strong&gt; with linting and ECR image scanning before deployment.&lt;/li&gt;
&lt;li&gt;Put an &lt;strong&gt;Application Load Balancer&lt;/strong&gt; in front of the service for a stable DNS name, HTTPS and health checks.&lt;/li&gt;
&lt;li&gt;Define all of the infrastructure as code with &lt;strong&gt;Terraform or CloudFormation&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;Use a &lt;strong&gt;GitHub App connection (CodeConnections)&lt;/strong&gt; instead of the OAuth app, which AWS no longer recommends.&lt;/li&gt;
&lt;li&gt;Enable &lt;strong&gt;automatic rollback&lt;/strong&gt; and add CloudWatch alarms.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Cost and cleanup
&lt;/h2&gt;

&lt;p&gt;The whole project cost about $1 or less. To avoid ongoing charges, delete the resources when you are done: the pipeline, the CodeBuild project, the IAM roles and policies, the S3 bucket, the ECR repository, and finally the ECS service and cluster.&lt;/p&gt;

&lt;h2&gt;
  
  
  Conclusion
&lt;/h2&gt;

&lt;p&gt;A single &lt;code&gt;git push&lt;/code&gt; now takes code from my laptop to a running, containerized service on AWS, with no manual steps in between. The project gave me practical experience with the services that make up a real cloud delivery workflow and, more importantly, with how they depend on each other through IAM, artifacts and configuration.&lt;/p&gt;

&lt;p&gt;Next, I plan to rebuild the same pipeline with Terraform and add an Application Load Balancer with HTTPS.&lt;/p&gt;

&lt;p&gt;If you have built something similar or have suggestions, I would love to hear about it in the comments.&lt;/p&gt;




&lt;p&gt;&lt;strong&gt;Connect with me:&lt;/strong&gt; &lt;a href="//www.linkedin.com/in/shehzad-ahmad153"&gt;LinkedIn&lt;/a&gt; &lt;/p&gt;

</description>
      <category>aws</category>
      <category>devops</category>
      <category>docker</category>
      <category>cicd</category>
    </item>
    <item>
      <title>VPC Peering vs Transit Gateway: Which One Should You Use in AWS?</title>
      <dc:creator>Shehzad Ahmad</dc:creator>
      <pubDate>Fri, 09 Oct 2026 20:46:29 +0000</pubDate>
      <link>https://dev.to/shehzad_ahmad_153/vpc-peering-vs-transit-gateway-which-one-should-you-use-in-aws-23pn</link>
      <guid>https://dev.to/shehzad_ahmad_153/vpc-peering-vs-transit-gateway-which-one-should-you-use-in-aws-23pn</guid>
      <description>&lt;h2&gt;
  
  
  Introduction
&lt;/h2&gt;

&lt;p&gt;As your AWS footprint grows, you quickly end up with multiple VPCs: dev, staging, prod, shared services, and more. Sooner or later they need to talk to each other privately.&lt;/p&gt;

&lt;p&gt;AWS gives you two main ways to do this: &lt;strong&gt;VPC Peering&lt;/strong&gt; and &lt;strong&gt;Transit Gateway (TGW)&lt;/strong&gt;. They solve a similar problem but in very different ways. Let's break them down.&lt;/p&gt;

&lt;h2&gt;
  
  
  Quick Comparison
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;&lt;strong&gt;VPC Peering&lt;/strong&gt;&lt;/th&gt;
&lt;th&gt;&lt;strong&gt;Transit Gateway&lt;/strong&gt;&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Definition&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Direct 1-to-1 private connection between two VPCs&lt;/td&gt;
&lt;td&gt;Central hub connecting many VPCs, VPNs and on-prem networks&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Topology&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Point-to-point (mesh)&lt;/td&gt;
&lt;td&gt;Hub-and-spoke&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Transitive routing&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;Yes&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Cost&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;No hourly fee, only data transfer&lt;/td&gt;
&lt;td&gt;Per-attachment hourly fee + per-GB data processing&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Best for&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Small, simple setups&lt;/td&gt;
&lt;td&gt;Large, multi-account, hybrid setups&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  What is VPC Peering?
&lt;/h2&gt;

&lt;p&gt;VPC Peering is a networking connection between two VPCs that lets you route traffic between them using private IPv4/IPv6 addresses. Traffic stays on the AWS backbone and never touches the public internet.&lt;/p&gt;

&lt;h3&gt;
  
  
  How it works
&lt;/h3&gt;

&lt;ol&gt;
&lt;li&gt;VPC A sends a peering request to VPC B (same or different account/region).&lt;/li&gt;
&lt;li&gt;VPC B accepts the request.&lt;/li&gt;
&lt;li&gt;You add routes in &lt;strong&gt;both&lt;/strong&gt; VPCs' route tables pointing to the peer's CIDR.&lt;/li&gt;
&lt;li&gt;Security groups and NACLs must allow the traffic.&lt;/li&gt;
&lt;/ol&gt;

&lt;h3&gt;
  
  
  The big limitation: no transitive routing
&lt;/h3&gt;

&lt;p&gt;If A is peered with B, and B is peered with C, &lt;strong&gt;A cannot reach C&lt;/strong&gt; through B. You would need a separate A-C peering.&lt;/p&gt;

&lt;p&gt;For &lt;code&gt;n&lt;/code&gt; VPCs, a full mesh needs &lt;code&gt;n(n-1)/2&lt;/code&gt; connections:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;VPCs&lt;/th&gt;
&lt;th&gt;Peering connections&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;5&lt;/td&gt;
&lt;td&gt;10&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;10&lt;/td&gt;
&lt;td&gt;45&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;20&lt;/td&gt;
&lt;td&gt;190&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;This gets painful very quickly.&lt;/p&gt;

&lt;h3&gt;
  
  
  Terraform example
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight hcl"&gt;&lt;code&gt;&lt;span class="nx"&gt;resource&lt;/span&gt; &lt;span class="s2"&gt;"aws_vpc_peering_connection"&lt;/span&gt; &lt;span class="s2"&gt;"a_to_b"&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nx"&gt;vpc_id&lt;/span&gt;      &lt;span class="p"&gt;=&lt;/span&gt; &lt;span class="nx"&gt;aws_vpc&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;a&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;id&lt;/span&gt;
  &lt;span class="nx"&gt;peer_vpc_id&lt;/span&gt; &lt;span class="p"&gt;=&lt;/span&gt; &lt;span class="nx"&gt;aws_vpc&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;b&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;id&lt;/span&gt;
  &lt;span class="nx"&gt;auto_accept&lt;/span&gt; &lt;span class="p"&gt;=&lt;/span&gt; &lt;span class="kc"&gt;true&lt;/span&gt; &lt;span class="c1"&gt;# same account &amp;amp; region&lt;/span&gt;

  &lt;span class="nx"&gt;tags&lt;/span&gt; &lt;span class="p"&gt;=&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="nx"&gt;Name&lt;/span&gt; &lt;span class="p"&gt;=&lt;/span&gt; &lt;span class="s2"&gt;"vpc-a-to-vpc-b"&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;

&lt;span class="c1"&gt;# Route from A to B&lt;/span&gt;
&lt;span class="nx"&gt;resource&lt;/span&gt; &lt;span class="s2"&gt;"aws_route"&lt;/span&gt; &lt;span class="s2"&gt;"a_to_b"&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nx"&gt;route_table_id&lt;/span&gt;            &lt;span class="p"&gt;=&lt;/span&gt; &lt;span class="nx"&gt;aws_route_table&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;a&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;id&lt;/span&gt;
  &lt;span class="nx"&gt;destination_cidr_block&lt;/span&gt;    &lt;span class="p"&gt;=&lt;/span&gt; &lt;span class="nx"&gt;aws_vpc&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;b&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;cidr_block&lt;/span&gt;
  &lt;span class="nx"&gt;vpc_peering_connection_id&lt;/span&gt; &lt;span class="p"&gt;=&lt;/span&gt; &lt;span class="nx"&gt;aws_vpc_peering_connection&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;a_to_b&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;id&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;

&lt;span class="c1"&gt;# Route from B to A&lt;/span&gt;
&lt;span class="nx"&gt;resource&lt;/span&gt; &lt;span class="s2"&gt;"aws_route"&lt;/span&gt; &lt;span class="s2"&gt;"b_to_a"&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nx"&gt;route_table_id&lt;/span&gt;            &lt;span class="p"&gt;=&lt;/span&gt; &lt;span class="nx"&gt;aws_route_table&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;b&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;id&lt;/span&gt;
  &lt;span class="nx"&gt;destination_cidr_block&lt;/span&gt;    &lt;span class="p"&gt;=&lt;/span&gt; &lt;span class="nx"&gt;aws_vpc&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;a&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;cidr_block&lt;/span&gt;
  &lt;span class="nx"&gt;vpc_peering_connection_id&lt;/span&gt; &lt;span class="p"&gt;=&lt;/span&gt; &lt;span class="nx"&gt;aws_vpc_peering_connection&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;a_to_b&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;id&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  What is Transit Gateway?
&lt;/h2&gt;

&lt;p&gt;Transit Gateway is a managed, regional network hub. Instead of connecting VPCs to each other, you connect each one to the TGW. The TGW then routes traffic between all attachments.&lt;/p&gt;

&lt;h3&gt;
  
  
  How it works
&lt;/h3&gt;

&lt;ol&gt;
&lt;li&gt;Create a Transit Gateway.&lt;/li&gt;
&lt;li&gt;Create an &lt;strong&gt;attachment&lt;/strong&gt; for each VPC (and VPN / Direct Connect if needed).&lt;/li&gt;
&lt;li&gt;TGW &lt;strong&gt;route tables&lt;/strong&gt; decide which attachment can reach which.&lt;/li&gt;
&lt;li&gt;Add a route in each VPC's route table pointing the other CIDRs to the TGW.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Because routing is centralized, you get &lt;strong&gt;transitive routing&lt;/strong&gt; and can segment traffic (for example, prod can't talk to dev) using multiple TGW route tables.&lt;/p&gt;

&lt;h3&gt;
  
  
  Terraform example
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight hcl"&gt;&lt;code&gt;&lt;span class="nx"&gt;resource&lt;/span&gt; &lt;span class="s2"&gt;"aws_ec2_transit_gateway"&lt;/span&gt; &lt;span class="s2"&gt;"main"&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nx"&gt;description&lt;/span&gt;                     &lt;span class="p"&gt;=&lt;/span&gt; &lt;span class="s2"&gt;"Central hub"&lt;/span&gt;
  &lt;span class="nx"&gt;default_route_table_association&lt;/span&gt; &lt;span class="p"&gt;=&lt;/span&gt; &lt;span class="s2"&gt;"enable"&lt;/span&gt;
  &lt;span class="nx"&gt;default_route_table_propagation&lt;/span&gt; &lt;span class="p"&gt;=&lt;/span&gt; &lt;span class="s2"&gt;"enable"&lt;/span&gt;

  &lt;span class="nx"&gt;tags&lt;/span&gt; &lt;span class="p"&gt;=&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="nx"&gt;Name&lt;/span&gt; &lt;span class="p"&gt;=&lt;/span&gt; &lt;span class="s2"&gt;"main-tgw"&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;

&lt;span class="nx"&gt;resource&lt;/span&gt; &lt;span class="s2"&gt;"aws_ec2_transit_gateway_vpc_attachment"&lt;/span&gt; &lt;span class="s2"&gt;"vpc_a"&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nx"&gt;transit_gateway_id&lt;/span&gt; &lt;span class="p"&gt;=&lt;/span&gt; &lt;span class="nx"&gt;aws_ec2_transit_gateway&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;main&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;id&lt;/span&gt;
  &lt;span class="nx"&gt;vpc_id&lt;/span&gt;             &lt;span class="p"&gt;=&lt;/span&gt; &lt;span class="nx"&gt;aws_vpc&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;a&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;id&lt;/span&gt;
  &lt;span class="nx"&gt;subnet_ids&lt;/span&gt;         &lt;span class="p"&gt;=&lt;/span&gt; &lt;span class="nx"&gt;aws_subnet&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;a_private&lt;/span&gt;&lt;span class="p"&gt;[*].&lt;/span&gt;&lt;span class="nx"&gt;id&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;

&lt;span class="nx"&gt;resource&lt;/span&gt; &lt;span class="s2"&gt;"aws_ec2_transit_gateway_vpc_attachment"&lt;/span&gt; &lt;span class="s2"&gt;"vpc_b"&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nx"&gt;transit_gateway_id&lt;/span&gt; &lt;span class="p"&gt;=&lt;/span&gt; &lt;span class="nx"&gt;aws_ec2_transit_gateway&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;main&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;id&lt;/span&gt;
  &lt;span class="nx"&gt;vpc_id&lt;/span&gt;             &lt;span class="p"&gt;=&lt;/span&gt; &lt;span class="nx"&gt;aws_vpc&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;b&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;id&lt;/span&gt;
  &lt;span class="nx"&gt;subnet_ids&lt;/span&gt;         &lt;span class="p"&gt;=&lt;/span&gt; &lt;span class="nx"&gt;aws_subnet&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;b_private&lt;/span&gt;&lt;span class="p"&gt;[*].&lt;/span&gt;&lt;span class="nx"&gt;id&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;

&lt;span class="c1"&gt;# VPC A -&amp;gt; everything in 10.0.0.0/8 via TGW&lt;/span&gt;
&lt;span class="nx"&gt;resource&lt;/span&gt; &lt;span class="s2"&gt;"aws_route"&lt;/span&gt; &lt;span class="s2"&gt;"a_via_tgw"&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nx"&gt;route_table_id&lt;/span&gt;         &lt;span class="p"&gt;=&lt;/span&gt; &lt;span class="nx"&gt;aws_route_table&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;a&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;id&lt;/span&gt;
  &lt;span class="nx"&gt;destination_cidr_block&lt;/span&gt; &lt;span class="p"&gt;=&lt;/span&gt; &lt;span class="s2"&gt;"10.0.0.0/8"&lt;/span&gt;
  &lt;span class="nx"&gt;transit_gateway_id&lt;/span&gt;     &lt;span class="p"&gt;=&lt;/span&gt; &lt;span class="nx"&gt;aws_ec2_transit_gateway&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;main&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;id&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Cost Comparison
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;VPC Peering&lt;/th&gt;
&lt;th&gt;Transit Gateway&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Hourly charge&lt;/td&gt;
&lt;td&gt;None&lt;/td&gt;
&lt;td&gt;Per attachment, per hour&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Data charge&lt;/td&gt;
&lt;td&gt;Data transfer only (same-AZ traffic is free; cross-AZ and cross-region are charged)&lt;/td&gt;
&lt;td&gt;Per GB processed by the TGW&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Scales with&lt;/td&gt;
&lt;td&gt;Data volume&lt;/td&gt;
&lt;td&gt;Number of attachments + data volume&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt; Exact prices vary by region and change over time. Always check the &lt;a href="https://aws.amazon.com/transit-gateway/pricing/" rel="noopener noreferrer"&gt;official AWS pricing page&lt;/a&gt; before making a decision.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;&lt;strong&gt;Rule of thumb:&lt;/strong&gt; Peering is cheaper. TGW costs more, but it saves a lot of operational effort as you scale.&lt;/p&gt;

&lt;h2&gt;
  
  
  Which Environment Fits Which?
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Choose VPC Peering when:
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;You have only a few VPCs (roughly 2 to 5).&lt;/li&gt;
&lt;li&gt;You need the lowest cost and lowest latency.&lt;/li&gt;
&lt;li&gt;The architecture is simple and does not need transitive routing.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Choose Transit Gateway when:
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;You have many VPCs or multiple AWS accounts.&lt;/li&gt;
&lt;li&gt;You need hybrid connectivity (Site-to-Site VPN or Direct Connect).&lt;/li&gt;
&lt;li&gt;You want centralized routing, segmentation and easier operations.&lt;/li&gt;
&lt;li&gt;You plan to add inspection layers (for example a central firewall VPC).&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Gotchas to Remember
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Overlapping CIDRs&lt;/strong&gt; don't work in either option. Plan your IP ranges early.&lt;/li&gt;
&lt;li&gt;VPC Peering does &lt;strong&gt;not&lt;/strong&gt; support edge-to-edge routing (you can't use the peer's VPN or internet gateway).&lt;/li&gt;
&lt;li&gt;TGW is a &lt;strong&gt;regional&lt;/strong&gt; resource. Use TGW peering for cross-region connectivity.&lt;/li&gt;
&lt;li&gt;Remember to update &lt;strong&gt;route tables and security groups&lt;/strong&gt; on both sides. This is the most common cause of "it's not connecting".&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Conclusion
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Scenario&lt;/th&gt;
&lt;th&gt;Pick&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Small setup, tight budget&lt;/td&gt;
&lt;td&gt;VPC Peering&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Growing multi-VPC / multi-account&lt;/td&gt;
&lt;td&gt;Transit Gateway&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Hybrid cloud with on-prem&lt;/td&gt;
&lt;td&gt;Transit Gateway&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Start simple with peering, and move to Transit Gateway when managing the mesh starts hurting. Which one are you using in your project? Let me know in the comments! 👇&lt;/p&gt;

</description>
      <category>aws</category>
      <category>devops</category>
      <category>networking</category>
      <category>cloud</category>
    </item>
    <item>
      <title>Launching My First AWS EC2 Instance — A Step-by-Step Walkthrough</title>
      <dc:creator>Shehzad Ahmad</dc:creator>
      <pubDate>Fri, 25 Sep 2026 16:55:39 +0000</pubDate>
      <link>https://dev.to/shehzad_ahmad_153/launching-my-first-aws-ec2-instance-a-step-by-step-walkthrough-2h6m</link>
      <guid>https://dev.to/shehzad_ahmad_153/launching-my-first-aws-ec2-instance-a-step-by-step-walkthrough-2h6m</guid>
      <description>&lt;h2&gt;
  
  
  Introduction
&lt;/h2&gt;

&lt;p&gt;As part of my hands-on learning in cloud and cybersecurity fundamentals, I decided to launch and configure my first &lt;strong&gt;AWS EC2 instance&lt;/strong&gt; from scratch — including networking rules, storage, a bootstrap script, and remote access via SSH. This post walks through every step I took, along with the reasoning behind key configuration choices.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Instance Configuration
&lt;/h2&gt;

&lt;p&gt;I started by selecting the AMI and instance type:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;AMI:&lt;/strong&gt; Amazon Linux 2023&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Instance Type:&lt;/strong&gt; t3.micro (Free Tier eligible)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fdicgwwx26c0o06mb0zay.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fdicgwwx26c0o06mb0zay.jpg" alt=" " width="800" height="345"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Amazon Linux 2023 was chosen for its lightweight footprint and long-term AWS support, and t3.micro keeps things within Free Tier limits — ideal for learning and testing.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Storage Configuration
&lt;/h2&gt;

&lt;p&gt;I attached &lt;strong&gt;two 8 GB EBS volumes&lt;/strong&gt; to the instance for storage.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F2d0q7y6y55w3jiyome4a.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F2d0q7y6y55w3jiyome4a.jpg" alt=" " width="493" height="513"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Bootstrap Script (User Data)
&lt;/h2&gt;

&lt;p&gt;Under &lt;strong&gt;Advanced Details → User Data&lt;/strong&gt;, I added a simple script to serve a "Hello World" page automatically on launch:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="c"&gt;#!/bin/bash&lt;/span&gt;
dnf update &lt;span class="nt"&gt;-y&lt;/span&gt;
dnf &lt;span class="nb"&gt;install &lt;/span&gt;httpd &lt;span class="nt"&gt;-y&lt;/span&gt;
systemctl start httpd
systemctl &lt;span class="nb"&gt;enable &lt;/span&gt;httpd
&lt;span class="nb"&gt;echo&lt;/span&gt; &lt;span class="s2"&gt;"HELLO WORLD"&lt;/span&gt; &lt;span class="o"&gt;&amp;gt;&lt;/span&gt; /var/www/html/index.html

&lt;span class="nb"&gt;touch &lt;/span&gt;file1.txt
&lt;span class="nb"&gt;mkdir &lt;/span&gt;dir1
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fcnq87vhwibhlmrd3zctj.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fcnq87vhwibhlmrd3zctj.jpg" alt=" " width="459" height="466"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;This automates web server installation and setup so the instance is ready to serve content as soon as it boots — no manual SSH configuration needed for the basic page.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Security Group (Inbound Rules)
&lt;/h2&gt;

&lt;p&gt;This is where network access control comes in. I configured the following inbound rules:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Type&lt;/th&gt;
&lt;th&gt;Protocol&lt;/th&gt;
&lt;th&gt;Port&lt;/th&gt;
&lt;th&gt;Source&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;HTTPS&lt;/td&gt;
&lt;td&gt;TCP&lt;/td&gt;
&lt;td&gt;443&lt;/td&gt;
&lt;td&gt;0.0.0.0/0 (Anywhere)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;SSH&lt;/td&gt;
&lt;td&gt;TCP&lt;/td&gt;
&lt;td&gt;22&lt;/td&gt;
&lt;td&gt;My IP&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fi6b4stukzm3yxwmz17hg.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fi6b4stukzm3yxwmz17hg.jpg" alt=" " width="800" height="329"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Why this matters:&lt;/strong&gt; HTTPS is opened to everyone since the web page is meant to be publicly accessible, but SSH is restricted to &lt;strong&gt;My IP only&lt;/strong&gt; — this is a basic but important security practice to prevent unauthorized remote access attempts from random IPs across the internet.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Launching the Instance
&lt;/h2&gt;

&lt;p&gt;After reviewing the configuration, I launched the instance and downloaded the &lt;code&gt;.pem&lt;/code&gt; key pair for SSH authentication.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fskkpj8z9njyoolsmesxf.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fskkpj8z9njyoolsmesxf.jpg" alt=" " width="800" height="349"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  6. Connecting via SSH
&lt;/h2&gt;

&lt;p&gt;I used &lt;strong&gt;MobaXterm&lt;/strong&gt; as my SSH client. Before connecting, I set the correct permissions on the key file:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;chmod &lt;/span&gt;400 instance32.pem
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F3qvm1hfgnb99j0wc4o7o.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F3qvm1hfgnb99j0wc4o7o.jpg" alt=" " width="800" height="599"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Then connected to the instance via SSH using the public IP along with the &lt;code&gt;.pem&lt;/code&gt; private key file for authentication.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fzuvzuio5atbai4umj34y.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fzuvzuio5atbai4umj34y.jpg" alt=" " width="799" height="324"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  7. Verifying the Result
&lt;/h2&gt;

&lt;p&gt;Finally, I opened the instance's &lt;strong&gt;public IP directly over HTTPS&lt;/strong&gt; in the browser (no key file needed here — that's only required for SSH authentication) and confirmed the "Hello World" page was being served correctly.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fs00op77kwx70x01edmw7.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fs00op77kwx70x01edmw7.jpg" alt=" " width="384" height="282"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Key Takeaways
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Automating setup with &lt;strong&gt;User Data scripts&lt;/strong&gt; saves manual configuration time on boot&lt;/li&gt;
&lt;li&gt;Restricting &lt;strong&gt;SSH to a single IP&lt;/strong&gt; while keeping &lt;strong&gt;HTTP/HTTPS open&lt;/strong&gt; is a standard, practical security pattern&lt;/li&gt;
&lt;li&gt;Always set correct permissions (&lt;code&gt;chmod 400&lt;/code&gt;) on your &lt;code&gt;.pem&lt;/code&gt; key before connecting — AWS/SSH will reject overly permissive key files&lt;/li&gt;
&lt;li&gt;Free Tier resources (t3.micro, 8GB volumes) are more than enough for learning and small test deployments&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;&lt;em&gt;This was a hands-on exercise as part of my ongoing cloud and cybersecurity learning journey. Feedback and suggestions welcome!&lt;/em&gt;&lt;/p&gt;

</description>
      <category>aws</category>
      <category>cloudcomputing</category>
      <category>ec2</category>
      <category>instance</category>
    </item>
    <item>
      <title>Cloud Computing &amp; AWS: The Practical Guide I Wish I'd Had Starting Out</title>
      <dc:creator>Shehzad Ahmad</dc:creator>
      <pubDate>Sun, 13 Sep 2026 04:26:08 +0000</pubDate>
      <link>https://dev.to/shehzad_ahmad_153/cloud-computing-aws-the-practical-guide-i-wish-id-had-starting-out-3pel</link>
      <guid>https://dev.to/shehzad_ahmad_153/cloud-computing-aws-the-practical-guide-i-wish-id-had-starting-out-3pel</guid>
      <description>&lt;p&gt;Most people can explain what a website is. Almost no one can explain where it actually &lt;em&gt;lives&lt;/em&gt; — or why that matters.&lt;/p&gt;

&lt;p&gt;That's the gap cloud computing fills. And whether you're an engineer, a security professional, or someone in governance and risk trying to keep up with the technical side of the business, understanding how the cloud works isn't optional anymore. It's table stakes.&lt;/p&gt;

&lt;p&gt;This guide breaks down cloud computing and AWS from the ground up — what it is, why it matters, how it's priced, how it's structured globally, and which core services actually matter.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Here's what we'll cover:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;What cloud computing really is (beyond "someone else's computer")&lt;/li&gt;
&lt;li&gt;The advantages that make it worth the shift&lt;/li&gt;
&lt;li&gt;How AWS pricing actually works&lt;/li&gt;
&lt;li&gt;AWS's global infrastructure model&lt;/li&gt;
&lt;li&gt;The seven AWS services worth knowing cold&lt;/li&gt;
&lt;li&gt;Why this matters even if you're not an engineer&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Let's get into it.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://aws.amazon.com/what-is-cloud-computing/" class="crayons-btn crayons-btn--primary" rel="noopener noreferrer"&gt;Read AWS's official primer&lt;/a&gt;
&lt;/p&gt;

&lt;h2&gt;
  
  
  ☁️ 1. What Is Cloud Computing, Really?
&lt;/h2&gt;

&lt;p&gt;Strip away the marketing, and cloud computing is simple: &lt;strong&gt;on-demand access to computing resources over the internet&lt;/strong&gt; — compute, storage, databases, networking, software — without owning or maintaining the physical hardware behind it.&lt;/p&gt;

&lt;p&gt;That's the whole idea. Everything else is implementation detail.&lt;/p&gt;

&lt;h3&gt;
  
  
  Traditional IT vs. Cloud Computing
&lt;/h3&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Traditional IT&lt;/th&gt;
&lt;th&gt;Cloud Computing&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Buy physical servers&lt;/td&gt;
&lt;td&gt;Provision resources on demand&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Manage hardware and facilities yourself&lt;/td&gt;
&lt;td&gt;Provider manages the infrastructure&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Large upfront capital investment&lt;/td&gt;
&lt;td&gt;Pay for what you actually use&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Scaling means buying more hardware&lt;/td&gt;
&lt;td&gt;Scaling is (mostly) a few clicks&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Infrastructure lives in your building&lt;/td&gt;
&lt;td&gt;Infrastructure lives in the provider's network&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h3&gt;
  
  
  The model, in one diagram
&lt;/h3&gt;



&lt;pre data-lang="mermaid"&gt;&lt;code&gt;flowchart LR
    A[User / Business] --&amp;gt; B[Internet]
    B --&amp;gt; C[Cloud Provider]
    C --&amp;gt; D[Compute]
    C --&amp;gt; E[Storage]
    C --&amp;gt; F[Databases]
    C --&amp;gt; G[Networking]&lt;/code&gt;&lt;/pre&gt;



&lt;p&gt;You focus on the product. The provider carries the weight underneath it.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;💡 &lt;strong&gt;The real insight:&lt;/strong&gt; Cloud computing isn't "online storage." It's a completely different operating model for IT — and once you see it that way, everything else makes more sense.&lt;/p&gt;
&lt;/blockquote&gt;




&lt;h2&gt;
  
  
  🚀 2. Why Smart Organizations Keep Choosing the Cloud
&lt;/h2&gt;

&lt;h3&gt;
  
  
  💰 Cost Efficiency
&lt;/h3&gt;

&lt;p&gt;No massive upfront hardware spend. You provision what you need, when you need it. That said — cloud without cost discipline gets expensive fast. Adoption isn't the hard part. &lt;em&gt;Governance&lt;/em&gt; is.&lt;/p&gt;

&lt;h3&gt;
  
  
  📈 Real Scalability
&lt;/h3&gt;

&lt;p&gt;Picture an e-commerce brand ahead of a flash sale. On-prem, that's a hardware order placed months in advance. In the cloud, it's a capacity adjustment.&lt;/p&gt;

&lt;h3&gt;
  
  
  ⚡ Speed to Market
&lt;/h3&gt;

&lt;p&gt;Infrastructure that used to take weeks now takes minutes. That difference alone reshapes how fast teams can ship.&lt;/p&gt;

&lt;h3&gt;
  
  
  🌍 Global Reach, Built In
&lt;/h3&gt;

&lt;p&gt;Cloud providers already operate infrastructure worldwide — meaning "going global" is a configuration decision, not a construction project.&lt;/p&gt;

&lt;h3&gt;
  
  
  🛡️ Security and Resilience — With a Catch
&lt;/h3&gt;

&lt;p&gt;Cloud platforms hand you serious security tooling out of the box. But tooling isn't the same as security. &lt;strong&gt;How you configure it is what actually determines your risk.&lt;/strong&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  🔄 Flexibility to Evolve
&lt;/h3&gt;

&lt;p&gt;Business needs change. Cloud architecture can change with them, without a rip-and-replace every time.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Bottom line:&lt;/strong&gt; Cloud computing = Flexibility + Scalability + Speed + Access to capabilities most teams could never build alone.&lt;/p&gt;
&lt;/blockquote&gt;




&lt;h2&gt;
  
  
  💳 3. How AWS Pricing Actually Works
&lt;/h2&gt;

&lt;p&gt;Here's the part that trips people up: &lt;strong&gt;AWS doesn't have one price.&lt;/strong&gt; It has hundreds of pricing structures, one per service, all running on a pay-as-you-go foundation.&lt;/p&gt;

&lt;h3&gt;
  
  
  What actually drives your bill
&lt;/h3&gt;



&lt;pre data-lang="mermaid"&gt;&lt;code&gt;flowchart TD
    A[AWS Monthly Cost] --&amp;gt; B[Compute Usage]
    A --&amp;gt; C[Storage]
    A --&amp;gt; D[Database Resources]
    A --&amp;gt; E[Data Transfer]
    A --&amp;gt; F[Additional Service Usage]&lt;/code&gt;&lt;/pre&gt;



&lt;h3&gt;
  
  
  The Pricing Models Worth Knowing
&lt;/h3&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Model&lt;/th&gt;
&lt;th&gt;What It Means&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;On-Demand&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Pay as you go, no commitment&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Savings Plans&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Lower rates in exchange for a usage commitment&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Reserved Instances&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Discounts for long-term commitments on eligible services&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Spot Instances&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Cheap spare capacity — with the risk of interruption&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Free Tier&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Limited free usage for eligible services and accounts&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h3&gt;
  
  
  Before You Deploy Anything, Ask:
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;What services does this workload &lt;em&gt;actually&lt;/em&gt; need?&lt;/li&gt;
&lt;li&gt;How much compute power?&lt;/li&gt;
&lt;li&gt;How much storage?&lt;/li&gt;
&lt;li&gt;What traffic should I expect?&lt;/li&gt;
&lt;li&gt;Which Region makes sense — for latency, compliance, and cost?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The &lt;a href="https://calculator.aws/" rel="noopener noreferrer"&gt;AWS Pricing Calculator&lt;/a&gt; turns those answers into a real estimate before you spend a dollar.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;⚠️ &lt;strong&gt;The truth about cloud costs:&lt;/strong&gt; They can absolutely be efficient. They can also spiral silently if nobody's watching. Cost optimization isn't a setting — it's a habit.&lt;/p&gt;
&lt;/blockquote&gt;




&lt;h2&gt;
  
  
  🌐 4. AWS Global Infrastructure, Simplified
&lt;/h2&gt;

&lt;p&gt;Three concepts carry the entire model: &lt;strong&gt;Regions&lt;/strong&gt;, &lt;strong&gt;Availability Zones&lt;/strong&gt;, and &lt;strong&gt;Data Centers.&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;pre data-lang="mermaid"&gt;&lt;code&gt;flowchart TD
    A[AWS Global Infrastructure] --&amp;gt; B[AWS Region]
    B --&amp;gt; C[Availability Zone 1]
    B --&amp;gt; D[Availability Zone 2]
    C --&amp;gt; E[One or more Data Centers]
    D --&amp;gt; F[One or more Data Centers]&lt;/code&gt;&lt;/pre&gt;



&lt;h3&gt;
  
  
  🌍 Region
&lt;/h3&gt;

&lt;p&gt;A geographic area with multiple Availability Zones. Choosing one comes down to:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Latency to your users&lt;/li&gt;
&lt;li&gt;Service availability&lt;/li&gt;
&lt;li&gt;Data residency rules&lt;/li&gt;
&lt;li&gt;Compliance requirements&lt;/li&gt;
&lt;li&gt;Disaster recovery strategy&lt;/li&gt;
&lt;li&gt;Cost&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  🏢 Availability Zone
&lt;/h3&gt;

&lt;p&gt;An isolated location inside a Region — one or more data centers. Spread your workload across multiple Availability Zones, and a single failure stops being a catastrophe.&lt;/p&gt;

&lt;h3&gt;
  
  
  🖥️ Data Centers
&lt;/h3&gt;

&lt;p&gt;The physical layer: servers, storage, networking, power, cooling. AWS owns this. You own what you build on top of it — which brings us to shared responsibility (more below).&lt;/p&gt;

&lt;h3&gt;
  
  
  Why any of this matters
&lt;/h3&gt;

&lt;p&gt;Get this right, and you get:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Higher availability&lt;/li&gt;
&lt;li&gt;Better performance&lt;/li&gt;
&lt;li&gt;Real disaster recovery&lt;/li&gt;
&lt;li&gt;Painless geographic expansion&lt;/li&gt;
&lt;li&gt;Long-term continuity&lt;/li&gt;
&lt;/ul&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Here's the thing nobody tells beginners:&lt;/strong&gt; Regions and AZs aren't AWS certification trivia. They're the backbone of every reliable architecture decision you'll ever make.&lt;/p&gt;
&lt;/blockquote&gt;




&lt;h2&gt;
  
  
  🧩 5. The Seven AWS Services Worth Knowing Cold
&lt;/h2&gt;

&lt;p&gt;AWS has hundreds of services. You need seven to build a real foundation.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1. Amazon EC2 — Compute&lt;/strong&gt;&lt;br&gt;
Resizable virtual servers. Hosts websites, application servers, dev/test environments, enterprise workloads.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Amazon S3 — Storage&lt;/strong&gt;&lt;br&gt;
Object storage for files, backups, media, data lakes, static assets.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. Amazon RDS — Relational Databases&lt;/strong&gt;&lt;br&gt;
Managed relational databases — built for business applications, transaction processing, e-commerce.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4. Amazon VPC — Networking&lt;/strong&gt;&lt;br&gt;
Your own isolated virtual network: subnets, route tables, security groups, ACLs, gateways. This is how you segment and control access.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;5. AWS IAM — Identity and Access Management&lt;/strong&gt;&lt;br&gt;
Controls who can touch what. Non-negotiables:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Least-privilege access, always&lt;/li&gt;
&lt;li&gt;Scoped roles over broad permissions&lt;/li&gt;
&lt;li&gt;MFA enabled&lt;/li&gt;
&lt;li&gt;Regular permission reviews&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;6. AWS Lambda — Serverless Compute&lt;/strong&gt;&lt;br&gt;
Code that runs on events — no servers to manage. Built for automation, event processing, scheduled jobs.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;7. Amazon CloudWatch — Monitoring&lt;/strong&gt;&lt;br&gt;
Your eyes on the environment: metrics, logs, alerts, and the trail you need when something goes wrong.&lt;/p&gt;
&lt;h3&gt;
  
  
  At a glance
&lt;/h3&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Service&lt;/th&gt;
&lt;th&gt;Category&lt;/th&gt;
&lt;th&gt;Primary Purpose&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;EC2&lt;/td&gt;
&lt;td&gt;Compute&lt;/td&gt;
&lt;td&gt;Virtual servers&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;S3&lt;/td&gt;
&lt;td&gt;Storage&lt;/td&gt;
&lt;td&gt;Object storage&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;RDS&lt;/td&gt;
&lt;td&gt;Database&lt;/td&gt;
&lt;td&gt;Managed relational databases&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;VPC&lt;/td&gt;
&lt;td&gt;Networking&lt;/td&gt;
&lt;td&gt;Virtual network&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;IAM&lt;/td&gt;
&lt;td&gt;Security&lt;/td&gt;
&lt;td&gt;Access management&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Lambda&lt;/td&gt;
&lt;td&gt;Compute&lt;/td&gt;
&lt;td&gt;Serverless functions&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;CloudWatch&lt;/td&gt;
&lt;td&gt;Monitoring&lt;/td&gt;
&lt;td&gt;Metrics, logs, and alerts&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;


&lt;h2&gt;
  
  
  🔗 6. Where It Clicks: Services Working Together
&lt;/h2&gt;

&lt;p&gt;Individually, these services are useful. Combined, they're an architecture. Here's a simple web app:&lt;br&gt;
&lt;/p&gt;

&lt;pre data-lang="mermaid"&gt;&lt;code&gt;flowchart TD
    A[Users] --&amp;gt; B[Application]
    B --&amp;gt; C[Amazon EC2]
    C --&amp;gt; D[Amazon RDS]
    C --&amp;gt; E[Amazon S3]
    F[Amazon VPC] -.-&amp;gt; C
    G[AWS IAM] -.-&amp;gt; C
    H[Amazon CloudWatch] -.-&amp;gt; C&lt;/code&gt;&lt;/pre&gt;



&lt;p&gt;EC2 runs the app. RDS holds the data. S3 stores the files. VPC, IAM, and CloudWatch quietly do the work of keeping it secure, controlled, and observable. Production environments layer in load balancing, backups, and disaster recovery on top — but this is the core pattern behind most cloud architectures you'll encounter.&lt;/p&gt;




&lt;h2&gt;
  
  
  🛡️ 7. Why This Isn't Just an Engineering Conversation
&lt;/h2&gt;

&lt;p&gt;If you work in Governance, Risk, and Compliance, the cloud is now part of your job description whether or not it's in your title.&lt;/p&gt;

&lt;p&gt;Ask yourself:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Access&lt;/strong&gt; — Who can reach cloud resources, and how is that governed?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Data protection&lt;/strong&gt; — How is sensitive information actually secured?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Logging&lt;/strong&gt; — Can you investigate a security event when it happens?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Configuration&lt;/strong&gt; — Are resources consistently and securely set up?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Compliance&lt;/strong&gt; — Does the environment meet what regulators require?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Third-party risk&lt;/strong&gt; — Where does AWS's responsibility end and yours begin?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Continuity&lt;/strong&gt; — Can the business recover from a disruption?&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  The Shared Responsibility Model, in One Sentence
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;AWS secures the cloud. You secure what you put in it.&lt;/strong&gt;&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Cloud security was never going to be a "set it and forget it" problem. It's shared — and governance is what keeps that shared arrangement from becoming a shared liability.&lt;/p&gt;
&lt;/blockquote&gt;




&lt;h2&gt;
  
  
  🎯 The Takeaway
&lt;/h2&gt;

&lt;p&gt;Cloud computing stopped being optional a while ago. It's the operating model for modern IT — on-demand infrastructure, real scalability, faster shipping, and access to capabilities that would be out of reach for most teams to build alone.&lt;/p&gt;

&lt;p&gt;AWS is one of the biggest reasons that's true, with a service ecosystem spanning compute, storage, databases, networking, security, and monitoring.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Carry these forward:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Cloud computing is a model, not just a technology&lt;/li&gt;
&lt;li&gt;The advantages are real — but so are the trade-offs&lt;/li&gt;
&lt;li&gt;AWS pricing rewards intentional design, not guesswork&lt;/li&gt;
&lt;li&gt;Regions and Availability Zones are the backbone of reliability&lt;/li&gt;
&lt;li&gt;A handful of core services power most real-world architectures&lt;/li&gt;
&lt;li&gt;Security and compliance are everyone's job, not just engineering's&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Understanding the cloud isn't just a technical skill anymore. It's a foundation for anyone building — or protecting — modern digital infrastructure.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;💬 What's one cloud concept you had to unlearn or relearn the hard way? Drop it in the comments — I'd genuinely like to know.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;If this was useful, a ❤️, 🦄, or 🔖 helps it reach more people starting out on the same path.&lt;/p&gt;




&lt;h2&gt;
  
  
  📚 Further Reading
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://aws.amazon.com/what-is-cloud-computing/" rel="noopener noreferrer"&gt;AWS — What Is Cloud Computing?&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://aws.amazon.com/products/" rel="noopener noreferrer"&gt;AWS — Products and Services&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://aws.amazon.com/about-aws/global-infrastructure/" rel="noopener noreferrer"&gt;AWS — Global Infrastructure&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://aws.amazon.com/pricing/" rel="noopener noreferrer"&gt;AWS — Pricing&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://calculator.aws/" rel="noopener noreferrer"&gt;AWS — Pricing Calculator&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://aws.amazon.com/compliance/shared-responsibility-model/" rel="noopener noreferrer"&gt;AWS — Shared Responsibility Model&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://aws.amazon.com/architecture/well-architected/" rel="noopener noreferrer"&gt;AWS — Well-Architected Framework&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;




</description>
      <category>aws</category>
      <category>cloud</category>
      <category>beginners</category>
      <category>devops</category>
    </item>
  </channel>
</rss>
