<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
    <channel>
        <title>Cloudformation - Tag - IT Guy Journals</title>
        <link>https://www.itguyjournals.com/tags/cloudformation/</link>
        <description>Cloudformation - Tag - 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>Sat, 12 Apr 2025 19:24:32 &#43;0100</lastBuildDate><atom:link href="https://www.itguyjournals.com/tags/cloudformation/" rel="self" type="application/rss+xml" /><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>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>
