<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
    <channel>
        <title>Cloud - Category - IT Guy Journals</title>
        <link>https://www.itguyjournals.com/categories/cloud/</link>
        <description>Cloud - Category - IT Guy Journals</description>
        <generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>luka.krapic@gmail.com (Luka Krapić)</managingEditor>
            <webMaster>luka.krapic@gmail.com (Luka Krapić)</webMaster><lastBuildDate>Fri, 02 May 2025 20:59:24 &#43;0100</lastBuildDate><atom:link href="https://www.itguyjournals.com/categories/cloud/" rel="self" type="application/rss+xml" /><item>
    <title>Building a Portable FastAPI Backend for AWS Lambda and ECS Using Terraform</title>
    <link>https://www.itguyjournals.com/building-fastapi-backend-for-aws-lambda-and-ecs-using-terraform/</link>
    <pubDate>Fri, 02 May 2025 20:59:24 &#43;0100</pubDate>
    <author>Luka Krapić</author>
    <guid>https://www.itguyjournals.com/building-fastapi-backend-for-aws-lambda-and-ecs-using-terraform/</guid>
    <description><![CDATA[<p>In the <a href="../building-backend-apis-with-fastapi-on-aws-lambda" rel="">previous post</a>, we explored how to deploy a FastAPI application on AWS Lambda using an ASGI adapter. This is a great option for early-stage projects: it requires zero infrastructure management, supports rapid iteration, and scales automatically.</p>
<p>But as your application matures, Lambda’s trade-offs can become limiting:</p>
<ul>
<li><strong>Cost scaling</strong> with consistent traffic</li>
<li><strong>Compute/memory coupling</strong> and lack of vertical scaling</li>
<li><strong>Package size limits</strong> and cold starts</li>
</ul>
<p>That’s why many teams adopt a container-based workflow that can run on both <strong>Lambda (via container images)</strong> and <strong>ECS Fargate</strong>. With a little planning, you can build once and deploy to either platform with minimal friction.</p>]]></description>
</item>
<item>
    <title>Building Backend APIs with FastAPI on AWS Lambda</title>
    <link>https://www.itguyjournals.com/building-backend-apis-with-fastapi-on-aws-lambda/</link>
    <pubDate>Sat, 12 Apr 2025 19:24:32 &#43;0100</pubDate>
    <author>Luka Krapić</author>
    <guid>https://www.itguyjournals.com/building-backend-apis-with-fastapi-on-aws-lambda/</guid>
    <description><![CDATA[<p>One of the trade-offs of working in the cloud is the risk of vendor lock-in. While cloud platforms offer powerful tools and scalability, they can also tie you into their ecosystem, making it harder to pivot or migrate down the road.</p>
<p>When it comes to building backend APIs in Python, you have a few great frameworks at your disposal—<strong>Django</strong>, <strong>FastAPI</strong>, and <strong>Flask</strong>—each with its own level of complexity and opinionation. Django is feature-rich and great for full-stack apps, Flask is minimal and flexible, but <strong>FastAPI</strong> stands out as a modern, async-first framework that makes it incredibly easy to build fast, clean, and production-ready APIs.</p>]]></description>
</item>
<item>
    <title>Building Websites at Scale With Aws CloudFront and Hugo</title>
    <link>https://www.itguyjournals.com/building-websites-at-scale-with-aws-cloudfront-and-hugo/</link>
    <pubDate>Tue, 14 Jan 2025 10:34:47 &#43;0100</pubDate>
    <author>Luka Krapić</author>
    <guid>https://www.itguyjournals.com/building-websites-at-scale-with-aws-cloudfront-and-hugo/</guid>
    <description><![CDATA[<p>Building websites has become easier than ever. Numerous platforms and third-party providers now offer tools to create and host websites within minutes, complete with custom domains, analytics, and sleek graphical interfaces.</p>
<p>For straightforward websites or smaller-scale projects, these platforms can be a convenient choice. However, they often fall short when it comes to flexibility, automation, and cost-effectiveness at scale. Many lack robust CLI (Command Line Interface) support for streamlining tasks, can become expensive as your needs grow, or demand significant management effort and a steep learning curve.</p>]]></description>
</item>
<item>
    <title>Tiered Access To CloudFront Content With Self-Signed Cookies</title>
    <link>https://www.itguyjournals.com/tiered-access-to-cloudfront-content-with-self-signed-cookies/</link>
    <pubDate>Fri, 19 Jul 2024 16:56:47 &#43;0100</pubDate>
    <author>Luka Krapić</author>
    <guid>https://www.itguyjournals.com/tiered-access-to-cloudfront-content-with-self-signed-cookies/</guid>
    <description><![CDATA[<p>This blog post is a follow-up to our previous post, where we implemented tiered access to S3 data using presigned URLs.</p>
<p>In most production applications, CloudFront is used to serve static content to users.
In this post, we will explore how to implement restricted access when serving content through CloudFront.</p>
<p>You can find the complete example <a href="https://github.com/LukaK/blog-resources/tree/main/cloudfront-signed-cookies?ref=itguyjournals.com" target="_blank" rel="noopener noreffer ">here</a>.</p>
<h2 id="what-is-cloudfront">What is CloudFront?</h2>
<p>In simple terms, CloudFront is a content delivery network (CDN) managed by AWS. A CDN is a network of servers deployed close to end users, serving as a caching layer to improve content delivery speed and reliability.</p>]]></description>
</item>
<item>
    <title>Multi-Account Cloud Deployment With Terraform And Github Actions</title>
    <link>https://www.itguyjournals.com/multi-account-cloud-deployment-with-terraform-and-github-actions/</link>
    <pubDate>Wed, 26 Jun 2024 16:56:47 &#43;0100</pubDate>
    <author>Luka Krapić</author>
    <guid>https://www.itguyjournals.com/multi-account-cloud-deployment-with-terraform-and-github-actions/</guid>
    <description><![CDATA[<p>In this blog post, we will look at how to implement a multi-account deployment pipeline on AWS using GitHub Actions and Terraform.</p>
<p>We will assume that you have access to at least two AWS accounts: one to hold pipeline resources and one target account where resources will be deployed.</p>
<h2 id="architecture">Architecture</h2>
<div id="id-1"><figure><figcaption>
      <h4>Fig 1. Architecture</h4>
    </figcaption>
</figure>
</div>
<p>We will use two accounts: a pipeline account and a target account. The target account is your dev/staging/prod account. Usually, there is more than one target account in a given pipeline, but we will use one for simplicity. The same approach can be extended to an arbitrary number of target accounts.</p>]]></description>
</item>
<item>
    <title>Tiered Access To S3 Data With Presigned URLs</title>
    <link>https://www.itguyjournals.com/tiered-access-to-s3-data-with-presigned-urls/</link>
    <pubDate>Tue, 11 Jun 2024 16:56:47 &#43;0100</pubDate>
    <author>Luka Krapić</author>
    <guid>https://www.itguyjournals.com/tiered-access-to-s3-data-with-presigned-urls/</guid>
    <description><![CDATA[<p>Managing access to your Amazon S3 data is crucial for ensuring security and efficiency in your cloud architecture. You typically have three options for managing access to S3 data for client applications: using Amazon CloudFront distribution, leveraging S3 presigned URLs, or routing through backend APIs.</p>
<p>In this blog post, we will delve into S3 presigned URLs as an effective method for implementing tiered access to your S3 data. We&rsquo;ll discuss their benefits, limitations, and provide a straightforward example to illustrate their use.</p>]]></description>
</item>
</channel>
</rss>
