<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Aws on Simple Enough Blog</title><link>https://blog.dev.simpleenough.net/tags/aws/</link><description>Recent content in Aws on Simple Enough Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 24 Jun 2026 10:00:00 +0200</lastBuildDate><atom:link href="https://blog.dev.simpleenough.net/tags/aws/index.xml" rel="self" type="application/rss+xml"/><item><title>The Invisible Part of the Iceberg: AWS Security Hub</title><link>https://blog.dev.simpleenough.net/blog/securityhubiceberg/</link><pubDate>Wed, 24 Jun 2026 10:00:00 +0200</pubDate><guid>https://blog.dev.simpleenough.net/blog/securityhubiceberg/</guid><description>&lt;p>When we talk about security on AWS, we first think of the visible services: GuardDuty detecting threats, Macie watching sensitive data, Inspector scanning vulnerabilities. These are the tips of the iceberg poking above the water. But beneath the surface lies a far larger mass: hundreds of scattered &lt;em>findings&lt;/em>, compliance rules to follow, multiple accounts to correlate. &lt;strong>AWS Security Hub&lt;/strong> is precisely the service that makes that invisible part usable, by gathering it into a single view.&lt;/p></description></item><item><title>EC2 Checklist: 7 Things to Do After Launching an Instance</title><link>https://blog.dev.simpleenough.net/blog/ec2_checklist/</link><pubDate>Wed, 20 May 2026 19:30:00 +0100</pubDate><guid>https://blog.dev.simpleenough.net/blog/ec2_checklist/</guid><description>&lt;h1 id="ec2-checklist-7-things-to-do-after-launching-an-instance" class="heading">EC2 Checklist: 7 Things to Do After Launching an Instance&lt;a href="#ec2-checklist-7-things-to-do-after-launching-an-instance" aria-labelledby="ec2-checklist-7-things-to-do-after-launching-an-instance">
&lt;!-- &lt;i class="fas fa-link anchor">&lt;/i> -->
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512">&lt;use href="#fas-link">&lt;/use>&lt;/svg>&amp;nbsp;
 &lt;/a>
&lt;/h1>
&lt;p>Launching an EC2 instance is easy.&lt;/p>
&lt;p>A few clicks in the AWS Console, and your machine is running.&lt;/p>
&lt;p>In reality, however, &lt;strong>a launched instance is not a production-ready instance&lt;/strong>.&lt;/p>
&lt;p>Many production incidents stem from small details that were overlooked immediately after launch:&lt;/p>
&lt;ul>
&lt;li>Misconfigured security groups&lt;/li>
&lt;li>No backups&lt;/li>
&lt;li>No monitoring&lt;/li>
&lt;li>Missing IAM role&lt;/li>
&lt;li>Poor SSH configuration&lt;/li>
&lt;li>Insufficient storage&lt;/li>
&lt;li>Missing tags&lt;/li>
&lt;/ul>
&lt;p>Here is a simple and practical checklist of &lt;strong>7 things you should verify immediately after launching an EC2 instance&lt;/strong>.&lt;/p></description></item><item><title>How to create a security group that allows only traffic coming from CloudFront?</title><link>https://blog.dev.simpleenough.net/blog/gs_cloudfront/</link><pubDate>Tue, 14 Apr 2026 17:52:00 +0100</pubDate><guid>https://blog.dev.simpleenough.net/blog/gs_cloudfront/</guid><description>&lt;h1 id="how-to-create-a-security-group-that-allows-only-traffic-coming-from-cloudfront" class="heading">How to create a security group that allows only traffic coming from CloudFront?&lt;a href="#how-to-create-a-security-group-that-allows-only-traffic-coming-from-cloudfront" aria-labelledby="how-to-create-a-security-group-that-allows-only-traffic-coming-from-cloudfront">
&lt;!-- &lt;i class="fas fa-link anchor">&lt;/i> -->
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512">&lt;use href="#fas-link">&lt;/use>&lt;/svg>&amp;nbsp;
 &lt;/a>
&lt;/h1>




&lt;h2 id="why-this-question-keeps-coming-back" class="heading">Why this question keeps coming back&lt;a href="#why-this-question-keeps-coming-back" aria-labelledby="why-this-question-keeps-coming-back">
&lt;!-- &lt;i class="fas fa-link anchor">&lt;/i> -->
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512">&lt;use href="#fas-link">&lt;/use>&lt;/svg>&amp;nbsp;
 &lt;/a>
&lt;/h2>
&lt;p>In the AWS world, some questions come up again and again.&lt;br>
Not because they are poorly phrased, but because they point to a &lt;strong>real friction between security, networking, and application architecture&lt;/strong>.&lt;/p></description></item><item><title>AWS multi-accounts: architectural solution or disguised organizational debt?</title><link>https://blog.dev.simpleenough.net/blog/multiaccounts_aws/</link><pubDate>Wed, 18 Feb 2026 17:30:00 +0100</pubDate><guid>https://blog.dev.simpleenough.net/blog/multiaccounts_aws/</guid><description>&lt;h2 id="i-introduction" class="heading">I. Introduction&lt;a href="#i-introduction" aria-labelledby="i-introduction">
&lt;!-- &lt;i class="fas fa-link anchor">&lt;/i> -->
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512">&lt;use href="#fas-link">&lt;/use>&lt;/svg>&amp;nbsp;
 &lt;/a>
&lt;/h2>
&lt;p>Creating multiple AWS accounts is now widely presented as a &lt;strong>near-universal best practice&lt;/strong>.&lt;br>
It is often introduced through simple, console-oriented tutorials that give the impression that the problem boils down to a few clicks.&lt;/p>
&lt;p>This view is misleading.&lt;/p>
&lt;p>&lt;strong>Multi-account&lt;/strong> is not an implementation detail, but a &lt;strong>fundamental architectural choice&lt;/strong>.&lt;br>
It directly impacts:&lt;/p>
&lt;ul>
&lt;li>how teams work,&lt;/li>
&lt;li>how security is enforced,&lt;/li>
&lt;li>cost visibility,&lt;/li>
&lt;li>the ability to automate,&lt;/li>
&lt;li>and organizational resilience to human error.&lt;/li>
&lt;/ul>
&lt;p>When misunderstood, it creates &lt;strong>organizational debt&lt;/strong> just as costly as traditional technical debt.&lt;/p></description></item><item><title>Why AWS Spot Instances Become Impossible to Get in December</title><link>https://blog.dev.simpleenough.net/blog/spotdecember/</link><pubDate>Mon, 01 Dec 2025 17:08:49 +0200</pubDate><guid>https://blog.dev.simpleenough.net/blog/spotdecember/</guid><description>&lt;h1 id="i-why-aws-spot-instances-become-impossible-to-get-in-december" class="heading">I. Why AWS Spot Instances Become Impossible to Get in December&lt;a href="#i-why-aws-spot-instances-become-impossible-to-get-in-december" aria-labelledby="i-why-aws-spot-instances-become-impossible-to-get-in-december">
&lt;!-- &lt;i class="fas fa-link anchor">&lt;/i> -->
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512">&lt;use href="#fas-link">&lt;/use>&lt;/svg>&amp;nbsp;
 &lt;/a>
&lt;/h1>
&lt;p>&lt;strong>EC2 Spot Instances&lt;/strong> are a fantastic way to save 50–70% on your AWS compute costs.&lt;br>
They use the unused capacity of AWS data centers… but in &lt;strong>December&lt;/strong>, this unused capacity almost completely disappears.&lt;/p>
&lt;p>Result:&lt;/p>
&lt;ul>
&lt;li>Auto Scaling Groups fail to launch new instances&lt;/li>
&lt;li>deployments get stuck&lt;/li>
&lt;li>“insufficient capacity” everywhere&lt;/li>
&lt;li>Spot interruptions become much more frequent&lt;/li>
&lt;/ul>
&lt;p>If you’ve experienced this, rest assured: it’s &lt;strong>not your fault&lt;/strong>, and not a configuration issue.&lt;br>
It’s a &lt;strong>seasonal phenomenon&lt;/strong>, and it happens every single year.&lt;/p></description></item><item><title>Karpenter: The Intelligent Autoscaler for EKS</title><link>https://blog.dev.simpleenough.net/blog/karpenter/</link><pubDate>Mon, 24 Nov 2025 11:18:06 +0200</pubDate><guid>https://blog.dev.simpleenough.net/blog/karpenter/</guid><description>&lt;h2 id="i-what-is-karpenter" class="heading">I. What is Karpenter?&lt;a href="#i-what-is-karpenter" aria-labelledby="i-what-is-karpenter">
&lt;!-- &lt;i class="fas fa-link anchor">&lt;/i> -->
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512">&lt;use href="#fas-link">&lt;/use>&lt;/svg>&amp;nbsp;
 &lt;/a>
&lt;/h2>
&lt;p>&lt;strong>Karpenter&lt;/strong> is an open-source autoscaler for Kubernetes, created by AWS.&lt;br>
Its purpose is to &lt;strong>automatically adjust the EC2 node capacity of an EKS cluster based on real workload demand.&lt;/strong>&lt;/p>
&lt;p>In short:&lt;/p>
&lt;ul>
&lt;li>When your cluster is short on resources, &lt;strong>Karpenter adds new nodes.&lt;/strong>&lt;/li>
&lt;li>When nodes become unnecessary, &lt;strong>it removes them.&lt;/strong>&lt;/li>
&lt;/ul>
&lt;p>But more importantly:&lt;/p>
&lt;p>It does this &lt;strong>faster&lt;/strong>, &lt;strong>more intelligently&lt;/strong>, and &lt;strong>more efficiently&lt;/strong> than Kubernetes’ traditional autoscaler (&lt;strong>Cluster Autoscaler&lt;/strong>).&lt;/p></description></item><item><title>GitHub Pages vs AWS S3: Which One to Choose for Hosting Your Static Website?</title><link>https://blog.dev.simpleenough.net/blog/githubvss3/</link><pubDate>Tue, 28 Oct 2025 11:00:00 +0200</pubDate><guid>https://blog.dev.simpleenough.net/blog/githubvss3/</guid><description>&lt;h2 id="i-introduction-context-and-challenges" class="heading">I. Introduction: Context and Challenges&lt;a href="#i-introduction-context-and-challenges" aria-labelledby="i-introduction-context-and-challenges">
&lt;!-- &lt;i class="fas fa-link anchor">&lt;/i> -->
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512">&lt;use href="#fas-link">&lt;/use>&lt;/svg>&amp;nbsp;
 &lt;/a>
&lt;/h2>
&lt;p>In today’s web landscape, &lt;strong>static websites&lt;/strong> (HTML/CSS/JS with no backend) are highly valued for their simplicity, speed, and minimal cost. Two main solutions lead the discussion for free or low-cost hosting: &lt;strong>GitHub Pages&lt;/strong> and &lt;strong>AWS S3&lt;/strong>.&lt;br>
This article compares the two approaches in terms of technology, cost, performance, and scalability to help you choose the one that best fits your needs.&lt;/p></description></item><item><title>How to Host a Static Website for Free with AWS S3</title><link>https://blog.dev.simpleenough.net/blog/hosts3/</link><pubDate>Tue, 30 Sep 2025 14:00:00 +0200</pubDate><guid>https://blog.dev.simpleenough.net/blog/hosts3/</guid><description>&lt;h2 id="i-why-choose-aws-s3-to-host-a-static-website-for-free" class="heading">I. Why Choose &lt;strong>AWS S3&lt;/strong> to Host a &lt;strong>Static Website for Free&lt;/strong>?&lt;a href="#i-why-choose-aws-s3-to-host-a-static-website-for-free" aria-labelledby="i-why-choose-aws-s3-to-host-a-static-website-for-free">
&lt;!-- &lt;i class="fas fa-link anchor">&lt;/i> -->
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512">&lt;use href="#fas-link">&lt;/use>&lt;/svg>&amp;nbsp;
 &lt;/a>
&lt;/h2>
&lt;ul>
&lt;li>&lt;strong>Amazon S3&lt;/strong> allows hosting of &lt;strong>fully static websites&lt;/strong> (HTML, CSS, JavaScript).&lt;/li>
&lt;li>With the &lt;strong>AWS Free Tier&lt;/strong>, a small site can stay &lt;strong>free for 12 months&lt;/strong> (up to 5 GB of storage, 20,000 GET requests &amp;amp; 2,000 PUT requests per month).&lt;/li>
&lt;li>Highly resilient, scalable, and &lt;strong>serverless&lt;/strong>, S3 provides &lt;strong>99.999999999% durability&lt;/strong> and handles traffic spikes effortlessly.&lt;/li>
&lt;li>For HTTPS and custom domains, Amazon recommends using &lt;strong>Amazon CloudFront + Route 53&lt;/strong>.&lt;/li>
&lt;/ul>
&lt;hr>




&lt;h2 id="ii-prerequisites-and-initial-setup" class="heading">II. Prerequisites and Initial Setup&lt;a href="#ii-prerequisites-and-initial-setup" aria-labelledby="ii-prerequisites-and-initial-setup">
&lt;!-- &lt;i class="fas fa-link anchor">&lt;/i> -->
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512">&lt;use href="#fas-link">&lt;/use>&lt;/svg>&amp;nbsp;
 &lt;/a>
&lt;/h2>
&lt;ul>
&lt;li>Create a bucket&lt;/li>
&lt;li>Disable public access restrictions&lt;/li>
&lt;li>Add a public access policy&lt;/li>
&lt;/ul>
&lt;p>Before deploying a static site with S3, basic configuration is required. Here&amp;rsquo;s the step-by-step setup:&lt;/p></description></item><item><title>Amazon Macie: A Comprehensive Solution for Data Security and Privacy</title><link>https://blog.dev.simpleenough.net/blog/macie/</link><pubDate>Wed, 10 Sep 2025 08:00:00 +0200</pubDate><guid>https://blog.dev.simpleenough.net/blog/macie/</guid><description>&lt;h2 id="i-introduction-to-amazon-macie" class="heading">I. Introduction to Amazon Macie&lt;a href="#i-introduction-to-amazon-macie" aria-labelledby="i-introduction-to-amazon-macie">
&lt;!-- &lt;i class="fas fa-link anchor">&lt;/i> -->
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512">&lt;use href="#fas-link">&lt;/use>&lt;/svg>&amp;nbsp;
 &lt;/a>
&lt;/h2>
&lt;p>Amazon Macie is a fully managed &lt;strong>data security&lt;/strong> service provided by AWS. It uses &lt;strong>machine learning&lt;/strong> and &lt;strong>pattern matching&lt;/strong> to automatically discover, classify, and protect sensitive data stored in Amazon S3. It provides &lt;strong>risk visibility&lt;/strong>, generates &lt;strong>findings&lt;/strong> when security or privacy issues are detected, and automates protective actions. A 30-day free trial is included for automated S3 bucket evaluation and data scanning.&lt;/p></description></item><item><title>Introduction to Amazon Inspector</title><link>https://blog.dev.simpleenough.net/blog/inspector/</link><pubDate>Wed, 03 Sep 2025 11:18:06 +0200</pubDate><guid>https://blog.dev.simpleenough.net/blog/inspector/</guid><description>&lt;h2 id="i-overview-of-amazon-inspector" class="heading">I. Overview of Amazon Inspector&lt;a href="#i-overview-of-amazon-inspector" aria-labelledby="i-overview-of-amazon-inspector">
&lt;!-- &lt;i class="fas fa-link anchor">&lt;/i> -->
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512">&lt;use href="#fas-link">&lt;/use>&lt;/svg>&amp;nbsp;
 &lt;/a>
&lt;/h2>
&lt;p>Amazon Inspector is an &lt;strong>automated vulnerability management&lt;/strong> service on AWS that automatically discovers workloads such as EC2 instances, container images in ECR, and Lambda functions, and continuously scans them for software vulnerabilities and unexpected network exposures.&lt;br>
It generates &lt;em>findings&lt;/em> used to prioritize patches based on a &lt;strong>contextualized risk score&lt;/strong>, which adapts the CVSS score according to the environment (e.g., absence of open ports).&lt;/p></description></item><item><title>AWS Containers</title><link>https://blog.dev.simpleenough.net/blog/container/</link><pubDate>Fri, 29 Aug 2025 09:09:45 +0200</pubDate><guid>https://blog.dev.simpleenough.net/blog/container/</guid><description>&lt;h2 id="i-introduction" class="heading">I. Introduction&lt;a href="#i-introduction" aria-labelledby="i-introduction">
&lt;!-- &lt;i class="fas fa-link anchor">&lt;/i> -->
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512">&lt;use href="#fas-link">&lt;/use>&lt;/svg>&amp;nbsp;
 &lt;/a>
&lt;/h2>
&lt;p>&lt;strong>Containers&lt;/strong> encapsulate an application and all its dependencies in an isolated and reproducible environment. Unlike virtual machines, containers share the host system&amp;rsquo;s kernel, making them &lt;strong>lighter&lt;/strong>, &lt;strong>faster to start&lt;/strong>, and &lt;strong>easier to deploy&lt;/strong>.&lt;/p>
&lt;p>This approach has revolutionized the software lifecycle by improving the &lt;strong>portability&lt;/strong> of applications between environments (development, testing, production).&lt;/p>
&lt;p>&lt;strong>AWS&lt;/strong> offers several services to build, manage, orchestrate, and run containers. Each service fits a specific &lt;strong>level of control&lt;/strong>, &lt;strong>user expertise&lt;/strong>, or &lt;strong>application type&lt;/strong>.&lt;/p></description></item><item><title>Report: Amazon GuardDuty Malware Protection for S3</title><link>https://blog.dev.simpleenough.net/blog/guardduty/</link><pubDate>Wed, 20 Aug 2025 10:09:45 +0200</pubDate><guid>https://blog.dev.simpleenough.net/blog/guardduty/</guid><description>&lt;h2 id="i-what-is-amazon-guardduty" class="heading">I. What is Amazon GuardDuty?&lt;a href="#i-what-is-amazon-guardduty" aria-labelledby="i-what-is-amazon-guardduty">
&lt;!-- &lt;i class="fas fa-link anchor">&lt;/i> -->
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512">&lt;use href="#fas-link">&lt;/use>&lt;/svg>&amp;nbsp;
 &lt;/a>
&lt;/h2>
&lt;p>&lt;strong>Amazon GuardDuty&lt;/strong> is an AI-based security service that continuously monitors AWS accounts and workloads.&lt;br>
It uses machine learning algorithms to detect suspicious activities, abnormal behaviors, and potential threats in your cloud environment.&lt;br>
GuardDuty integrates seamlessly with other AWS services like S3, EC2, and IAM to provide a comprehensive view of your infrastructure&amp;rsquo;s security posture.&lt;br>
It also works alongside AWS CloudTrail and AWS Config to gather additional context and trigger automatic responses to threats.&lt;/p></description></item><item><title>Global Availability of EC2 Instance Types</title><link>https://blog.dev.simpleenough.net/blog/dispoec2/</link><pubDate>Wed, 13 Aug 2025 07:57:39 +0200</pubDate><guid>https://blog.dev.simpleenough.net/blog/dispoec2/</guid><description>&lt;h2 id="i-introduction" class="heading">I. Introduction&lt;a href="#i-introduction" aria-labelledby="i-introduction">
&lt;!-- &lt;i class="fas fa-link anchor">&lt;/i> -->
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512">&lt;use href="#fas-link">&lt;/use>&lt;/svg>&amp;nbsp;
 &lt;/a>
&lt;/h2>
&lt;p>When designing infrastructure on &lt;strong>AWS&lt;/strong>, one of the first technical decisions involves the &lt;strong>EC2 instance types&lt;/strong> used. However, this decision cannot be made in isolation: the &lt;strong>regional availability&lt;/strong> of instance types varies by geographic location, impacting your architecture’s resilience, scalability, and cost.&lt;/p>
&lt;p>This article explains in detail how to understand and anticipate this global availability, with a clear approach directly applicable by developers, DevOps engineers, and data scientists.&lt;/p></description></item><item><title>Interview EC2</title><link>https://blog.dev.simpleenough.net/blog/ec2/</link><pubDate>Mon, 09 Jun 2025 15:55:01 +0200</pubDate><guid>https://blog.dev.simpleenough.net/blog/ec2/</guid><description>&lt;h2 id="i-what-is-amazon-ec2-and-what-is-it-used-for" class="heading">I. What is Amazon EC2 and what is it used for?&lt;a href="#i-what-is-amazon-ec2-and-what-is-it-used-for" aria-labelledby="i-what-is-amazon-ec2-and-what-is-it-used-for">
&lt;!-- &lt;i class="fas fa-link anchor">&lt;/i> -->
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512">&lt;use href="#fas-link">&lt;/use>&lt;/svg>&amp;nbsp;
 &lt;/a>
&lt;/h2>





 &lt;blockquote class="blockquote">
 &lt;p>&lt;strong>AWS Expert&lt;/strong>: Amazon EC2 (Elastic Compute Cloud) is an &lt;strong>on-demand infrastructure service&lt;/strong> that allows you to launch virtual servers — called &lt;em>instances&lt;/em> — in the cloud. It is used to host web applications, run data processing, serve as development environments, or simulate production loads.&lt;/p>
 &lt;/blockquote>
&lt;p>What makes EC2 powerful is its &lt;strong>scalability&lt;/strong> and &lt;strong>flexibility&lt;/strong>. You can start with a small instance for testing, then scale up to high-capacity clusters without switching platforms. Developers also love the &lt;strong>full control&lt;/strong> they get over configuration, open ports, attached disks, and more.&lt;/p></description></item><item><title>This is who IAM</title><link>https://blog.dev.simpleenough.net/blog/iam/</link><pubDate>Tue, 27 May 2025 15:33:47 +0200</pubDate><guid>https://blog.dev.simpleenough.net/blog/iam/</guid><description>&lt;h2 id="i-iam-core-components-and-concepts" class="heading">I. IAM: Core Components and Concepts&lt;a href="#i-iam-core-components-and-concepts" aria-labelledby="i-iam-core-components-and-concepts">
&lt;!-- &lt;i class="fas fa-link anchor">&lt;/i> -->
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512">&lt;use href="#fas-link">&lt;/use>&lt;/svg>&amp;nbsp;
 &lt;/a>
&lt;/h2>
&lt;p>IAM is based on &lt;strong>entities&lt;/strong> and &lt;strong>policies&lt;/strong>.&lt;/p>




&lt;h3 id="iam-entities" class="heading">IAM Entities&lt;a href="#iam-entities" aria-labelledby="iam-entities">
&lt;!-- &lt;i class="fas fa-link anchor">&lt;/i> -->
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512">&lt;use href="#fas-link">&lt;/use>&lt;/svg>&amp;nbsp;
 &lt;/a>
&lt;/h3>
&lt;ul>
&lt;li>&lt;strong>Users&lt;/strong>: Represent people or applications. Example: a developer named &amp;ldquo;alice&amp;rdquo;.&lt;/li>
&lt;li>&lt;strong>Groups&lt;/strong>: Collections of users sharing the same permissions.&lt;/li>
&lt;li>&lt;strong>Roles&lt;/strong>: IAM entities that can be temporarily assumed by others. Ideal for &lt;strong>federation&lt;/strong> or services like EC2 or Lambda.&lt;/li>
&lt;li>&lt;strong>Policies&lt;/strong>: JSON documents that define permissions attached to an entity.&lt;/li>
&lt;/ul>




&lt;h3 id="sample-json-policy" class="heading">Sample JSON Policy&lt;a href="#sample-json-policy" aria-labelledby="sample-json-policy">
&lt;!-- &lt;i class="fas fa-link anchor">&lt;/i> -->
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512">&lt;use href="#fas-link">&lt;/use>&lt;/svg>&amp;nbsp;
 &lt;/a>
&lt;/h3>
&lt;div class="mb-3 syntax-highlight">&lt;div class="highlight">&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-json" data-lang="json">&lt;span style="display:flex;">&lt;span>{
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">&amp;#34;Version&amp;#34;&lt;/span>: &lt;span style="color:#e6db74">&amp;#34;2012-10-17&amp;#34;&lt;/span>,
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">&amp;#34;Statement&amp;#34;&lt;/span>: [
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> {
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">&amp;#34;Effect&amp;#34;&lt;/span>: &lt;span style="color:#e6db74">&amp;#34;Allow&amp;#34;&lt;/span>,
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">&amp;#34;Action&amp;#34;&lt;/span>: &lt;span style="color:#e6db74">&amp;#34;s3:ListBucket&amp;#34;&lt;/span>,
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> &lt;span style="color:#f92672">&amp;#34;Resource&amp;#34;&lt;/span>: &lt;span style="color:#e6db74">&amp;#34;arn:aws:s3:::example_bucket&amp;#34;&lt;/span>
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> }
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span> ]
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>}&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;/div>&lt;p>This IAM policy allows an AWS entity (user, role, or group) to list the objects in a specific S3 bucket named &lt;code>example_bucket&lt;/code>. It uses the standard IAM version format (&lt;code>2012-10-17&lt;/code>) and allows the &lt;code>s3:ListBucket&lt;/code> action on the resource identified by its ARN. It lets the entity see the list of objects (names, sizes, metadata), but not read or modify them—unless additional permissions are granted. This minimal policy is often used for inventory or bucket navigation via the AWS Console or API.&lt;/p></description></item><item><title>3 Simple Ways to Save Up to 90% on EC2 Costs: Spot Instances</title><link>https://blog.dev.simpleenough.net/blog/spot/</link><pubDate>Fri, 02 May 2025 17:08:49 +0200</pubDate><guid>https://blog.dev.simpleenough.net/blog/spot/</guid><description>&lt;h2 id="i-introduction-to-spot-instances" class="heading">I. Introduction to Spot Instances&lt;a href="#i-introduction-to-spot-instances" aria-labelledby="i-introduction-to-spot-instances">
&lt;!-- &lt;i class="fas fa-link anchor">&lt;/i> -->
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512">&lt;use href="#fas-link">&lt;/use>&lt;/svg>&amp;nbsp;
 &lt;/a>
&lt;/h2>
&lt;p>&lt;strong>Amazon EC2 Spot Instances&lt;/strong> offer a powerful way to drastically reduce cloud computing costs. Designed to utilize unused Amazon EC2 capacity, these instances are available at a &lt;strong>price up to 90% lower&lt;/strong> than On-Demand instances.&lt;/p>
&lt;p>While these savings are appealing, Spot Instances are not suitable for all workloads. They are ideal for &lt;strong>flexible, interruption-tolerant&lt;/strong>, or distributed jobs such as data processing, machine learning training, or performance testing.&lt;/p></description></item><item><title>A problem. Don’t panic, prepare a support ticket</title><link>https://blog.dev.simpleenough.net/blog/assistance/</link><pubDate>Fri, 25 Apr 2025 13:10:00 +0100</pubDate><guid>https://blog.dev.simpleenough.net/blog/assistance/</guid><description>&lt;h2 id="i-identify-and-reproduce-the-problem-precisely" class="heading">I. Identify and Reproduce the Problem Precisely&lt;a href="#i-identify-and-reproduce-the-problem-precisely" aria-labelledby="i-identify-and-reproduce-the-problem-precisely">
&lt;!-- &lt;i class="fas fa-link anchor">&lt;/i> -->
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512">&lt;use href="#fas-link">&lt;/use>&lt;/svg>&amp;nbsp;
 &lt;/a>
&lt;/h2>
&lt;p>Before contacting AWS Support, it&amp;rsquo;s crucial to clearly document the observed behavior. The goal is to enable the &lt;strong>support team&lt;/strong> to quickly analyze the context. Start by identifying the service involved: EC2, S3, Lambda, or another component of your cloud infrastructure. Documenting an incident clearly is key to avoiding unnecessary back-and-forth.&lt;/p></description></item><item><title>Introduction to AWS ELB</title><link>https://blog.dev.simpleenough.net/blog/elb/</link><pubDate>Sat, 15 Mar 2025 21:11:49 +0000</pubDate><guid>https://blog.dev.simpleenough.net/blog/elb/</guid><description>&lt;h2 id="i-introduction-to-load-balancers-in-aws" class="heading">I. Introduction to Load Balancers in AWS&lt;a href="#i-introduction-to-load-balancers-in-aws" aria-labelledby="i-introduction-to-load-balancers-in-aws">
&lt;!-- &lt;i class="fas fa-link anchor">&lt;/i> -->
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512">&lt;use href="#fas-link">&lt;/use>&lt;/svg>&amp;nbsp;
 &lt;/a>
&lt;/h2>
&lt;p>An Elastic Load Balancer (ELB) acts as a traffic distributor, automatically spreading incoming traffic across multiple target resources such as &lt;strong>EC2 instances&lt;/strong>, &lt;strong>containers&lt;/strong>, or &lt;strong>IP addresses&lt;/strong>.&lt;/p>
&lt;p>This functionality is a cornerstone of fault-tolerant and highly available cloud application design. AWS offers three types of ELB tailored to different use cases, each with specific features.&lt;/p></description></item><item><title>Amazon EventBridge vs Amazon SNS: Which Solution to Choose?</title><link>https://blog.dev.simpleenough.net/blog/eventdriven/</link><pubDate>Tue, 11 Mar 2025 10:05:00 +0100</pubDate><guid>https://blog.dev.simpleenough.net/blog/eventdriven/</guid><description>&lt;h2 id="introduction" class="heading">Introduction&lt;a href="#introduction" aria-labelledby="introduction">
&lt;!-- &lt;i class="fas fa-link anchor">&lt;/i> -->
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512">&lt;use href="#fas-link">&lt;/use>&lt;/svg>&amp;nbsp;
 &lt;/a>
&lt;/h2>
&lt;p>In this article, we will compare these two services, explore their use cases, and see how to integrate them effectively into an AWS architecture.&lt;/p>
&lt;hr>




&lt;h2 id="i-comparison-of-amazon-eventbridge-vs-amazon-sns" class="heading">I. Comparison of Amazon EventBridge vs Amazon SNS&lt;a href="#i-comparison-of-amazon-eventbridge-vs-amazon-sns" aria-labelledby="i-comparison-of-amazon-eventbridge-vs-amazon-sns">
&lt;!-- &lt;i class="fas fa-link anchor">&lt;/i> -->
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512">&lt;use href="#fas-link">&lt;/use>&lt;/svg>&amp;nbsp;
 &lt;/a>
&lt;/h2>






 






&lt;table class="table">
 &lt;thead>
 
 
 &lt;tr>
 &lt;th >&lt;strong>Feature&lt;/strong>&lt;/th>
 &lt;th >&lt;strong>Amazon EventBridge&lt;/strong>&lt;/th>
 &lt;th >&lt;strong>Amazon SNS&lt;/strong>&lt;/th>
 &lt;/tr>
 
 &lt;/thead>
 &lt;tbody>
 
 
 &lt;tr>
 &lt;td >&lt;strong>Communication Type&lt;/strong>&lt;/td>
 &lt;td >Event-Driven&lt;/td>
 &lt;td >Publish-Subscribe (Pub/Sub)&lt;/td>
 &lt;/tr>
 
 
 
 &lt;tr>
 &lt;td >&lt;strong>Use Cases&lt;/strong>&lt;/td>
 &lt;td >Event routing between AWS services and SaaS applications&lt;/td>
 &lt;td >Sending notifications to subscribers (emails, SMS, Lambda, SQS, etc.)&lt;/td>
 &lt;/tr>
 
 
 
 &lt;tr>
 &lt;td >&lt;strong>Message Sources&lt;/strong>&lt;/td>
 &lt;td >AWS Services, SaaS applications, custom applications&lt;/td>
 &lt;td >Applications, users, AWS services&lt;/td>
 &lt;/tr>
 
 
 
 &lt;tr>
 &lt;td >&lt;strong>Targeting Consumers&lt;/strong>&lt;/td>
 &lt;td >Advanced filtering rules to send an event to one or multiple targets&lt;/td>
 &lt;td >Sends the same message to all topic subscribers&lt;/td>
 &lt;/tr>
 
 
 
 &lt;tr>
 &lt;td >&lt;strong>Supported Protocols&lt;/strong>&lt;/td>
 &lt;td >AWS Lambda, SQS, API Gateway, Kinesis, Step Functions, etc.&lt;/td>
 &lt;td >Emails, SMS, Lambda, SQS, HTTP(S) endpoints, mobile applications (FCM, APN)&lt;/td>
 &lt;/tr>
 
 
 
 &lt;tr>
 &lt;td >&lt;strong>Message Filtering&lt;/strong>&lt;/td>
 &lt;td >Advanced filtering based on JSON rules&lt;/td>
 &lt;td >Limited filtering based on message attributes&lt;/td>
 &lt;/tr>
 
 
 
 &lt;tr>
 &lt;td >&lt;strong>Architecture&lt;/strong>&lt;/td>
 &lt;td >Event-driven and integrates with other AWS services&lt;/td>
 &lt;td >Notification-based messaging between producers and consumers&lt;/td>
 &lt;/tr>
 
 
 
 &lt;tr>
 &lt;td >&lt;strong>Durability &amp;amp; Message Retention&lt;/strong>&lt;/td>
 &lt;td >No native storage (events are routed immediately)&lt;/td>
 &lt;td >Messages stored for 4 days (up to 14 days with Extended Retention)&lt;/td>
 &lt;/tr>
 
 
 
 &lt;tr>
 &lt;td >&lt;strong>Message Ordering&lt;/strong>&lt;/td>
 &lt;td >Not guaranteed (messages may arrive out of order)&lt;/td>
 &lt;td >FIFO ordering available with SNS FIFO&lt;/td>
 &lt;/tr>
 
 &lt;/tbody>
&lt;/table>



&lt;h2 id="ii-detailed-use-cases" class="heading">II. Detailed Use Cases&lt;a href="#ii-detailed-use-cases" aria-labelledby="ii-detailed-use-cases">
&lt;!-- &lt;i class="fas fa-link anchor">&lt;/i> -->
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512">&lt;use href="#fas-link">&lt;/use>&lt;/svg>&amp;nbsp;
 &lt;/a>
&lt;/h2>




&lt;h3 id="a-amazon-eventbridge-use-case-orchestrating-events-between-services" class="heading">A. &lt;strong>Amazon EventBridge Use Case&lt;/strong>: Orchestrating Events Between Services&lt;a href="#a-amazon-eventbridge-use-case-orchestrating-events-between-services" aria-labelledby="a-amazon-eventbridge-use-case-orchestrating-events-between-services">
&lt;!-- &lt;i class="fas fa-link anchor">&lt;/i> -->
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512">&lt;use href="#fas-link">&lt;/use>&lt;/svg>&amp;nbsp;
 &lt;/a>
&lt;/h3>
&lt;p>EventBridge is ideal for &lt;strong>connecting different AWS services and SaaS applications&lt;/strong>.&lt;/p></description></item><item><title>The 5 Must-Read Whitepapers</title><link>https://blog.dev.simpleenough.net/blog/whitepaper/</link><pubDate>Sat, 01 Mar 2025 10:56:41 +0100</pubDate><guid>https://blog.dev.simpleenough.net/blog/whitepaper/</guid><description>&lt;h1 id="prepare-for-your-first-aws-certification-with-these-essential-whitepapers" class="heading">Prepare for Your First AWS Certification with These Essential Whitepapers&lt;a href="#prepare-for-your-first-aws-certification-with-these-essential-whitepapers" aria-labelledby="prepare-for-your-first-aws-certification-with-these-essential-whitepapers">
&lt;!-- &lt;i class="fas fa-link anchor">&lt;/i> -->
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512">&lt;use href="#fas-link">&lt;/use>&lt;/svg>&amp;nbsp;
 &lt;/a>
&lt;/h1>
&lt;p>AWS whitepapers help you gain an in-depth understanding of best practices and cloud architectures. These free resources are invaluable for anyone looking to pass their certification exam successfully.&lt;/p>
&lt;p>In this article, we introduce the key whitepapers for your preparation and explain how to use them effectively.&lt;/p>




&lt;h2 id="i-why-read-aws-whitepapers" class="heading">I. Why Read AWS Whitepapers?&lt;a href="#i-why-read-aws-whitepapers" aria-labelledby="i-why-read-aws-whitepapers">
&lt;!-- &lt;i class="fas fa-link anchor">&lt;/i> -->
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512">&lt;use href="#fas-link">&lt;/use>&lt;/svg>&amp;nbsp;
 &lt;/a>
&lt;/h2>
&lt;p>AWS whitepapers are written by cloud experts and provide practical guidance on designing, managing, and securing AWS infrastructures. They cover topics ranging from general architecture principles to performance and security best practices. Reading these documents allows you to deepen your knowledge beyond simple tutorials and better understand the requirements of AWS fundamental or associate-level exams.&lt;/p></description></item><item><title>Reverse</title><link>https://blog.dev.simpleenough.net/projects/reverse-project/</link><pubDate>Tue, 25 Feb 2025 00:00:00 +0000</pubDate><guid>https://blog.dev.simpleenough.net/projects/reverse-project/</guid><description>&lt;p>Visualization tool.
Triggering a scan to generate IaC for AWS.
Infrastructure History.&lt;/p></description></item><item><title>How to Filter S3 Events by Object Size?</title><link>https://blog.dev.simpleenough.net/blog/sortsizes3/</link><pubDate>Tue, 18 Feb 2025 17:16:31 +0100</pubDate><guid>https://blog.dev.simpleenough.net/blog/sortsizes3/</guid><description>&lt;h2 id="i-when-do-you-need-to-filter-s3-events-by-object-size" class="heading">I. When Do You Need to Filter S3 Events by Object Size?&lt;a href="#i-when-do-you-need-to-filter-s3-events-by-object-size" aria-labelledby="i-when-do-you-need-to-filter-s3-events-by-object-size">
&lt;!-- &lt;i class="fas fa-link anchor">&lt;/i> -->
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512">&lt;use href="#fas-link">&lt;/use>&lt;/svg>&amp;nbsp;
 &lt;/a>
&lt;/h2>
&lt;p>Filtering S3 events by object size is useful in various scenarios, especially when triggered actions depend on file volume. Here are some concrete use cases where this filtering is relevant:&lt;/p>




&lt;h3 id="1-cost-optimization-and-storage-management" class="heading">1. Cost Optimization and Storage Management&lt;a href="#1-cost-optimization-and-storage-management" aria-labelledby="1-cost-optimization-and-storage-management">
&lt;!-- &lt;i class="fas fa-link anchor">&lt;/i> -->
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512">&lt;use href="#fas-link">&lt;/use>&lt;/svg>&amp;nbsp;
 &lt;/a>
&lt;/h3>
&lt;ul>
&lt;li>&lt;strong>Automatically deleting oversized files&lt;/strong>: Prevents the accumulation of unnecessary files that take up space and generate extra costs.&lt;/li>
&lt;li>&lt;strong>Automatically moving files to lower-cost storage&lt;/strong> (e.g., Glacier) when they exceed a certain size.&lt;/li>
&lt;/ul>




&lt;h3 id="2-process-automation" class="heading">2. Process Automation&lt;a href="#2-process-automation" aria-labelledby="2-process-automation">
&lt;!-- &lt;i class="fas fa-link anchor">&lt;/i> -->
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512">&lt;use href="#fas-link">&lt;/use>&lt;/svg>&amp;nbsp;
 &lt;/a>
&lt;/h3>
&lt;ul>
&lt;li>&lt;strong>Executing a specific process on large files&lt;/strong> (e.g., video/audio conversion, compression, splitting large files into smaller chunks).&lt;/li>
&lt;li>&lt;strong>Triggering a Lambda function to index only relevant files&lt;/strong> based on their size.&lt;/li>
&lt;/ul>




&lt;h3 id="3-security-and-compliance" class="heading">3. Security and Compliance&lt;a href="#3-security-and-compliance" aria-labelledby="3-security-and-compliance">
&lt;!-- &lt;i class="fas fa-link anchor">&lt;/i> -->
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512">&lt;use href="#fas-link">&lt;/use>&lt;/svg>&amp;nbsp;
 &lt;/a>
&lt;/h3>
&lt;ul>
&lt;li>&lt;strong>Avoiding the storage of excessively large files in public buckets&lt;/strong>, which could lead to abuse (e.g., uploading large archives by malicious users).&lt;/li>
&lt;li>&lt;strong>Triggering an alert or blocking uploads&lt;/strong> if a user exceeds a defined size limit.&lt;/li>
&lt;/ul>




&lt;h3 id="4-data-flow-optimization" class="heading">4. Data Flow Optimization&lt;a href="#4-data-flow-optimization" aria-labelledby="4-data-flow-optimization">
&lt;!-- &lt;i class="fas fa-link anchor">&lt;/i> -->
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512">&lt;use href="#fas-link">&lt;/use>&lt;/svg>&amp;nbsp;
 &lt;/a>
&lt;/h3>
&lt;ul>
&lt;li>&lt;strong>Directing small files to real-time processing&lt;/strong> (Lambda, Kinesis) and larger files to batch processing to optimize system efficiency.&lt;/li>
&lt;li>&lt;strong>Redirecting files based on their size to different buckets&lt;/strong> (e.g., files &amp;lt; 1MB to a high-speed access bucket, files &amp;gt; 100MB to cold storage).&lt;/li>
&lt;/ul>




&lt;h3 id="5-monitoring-and-reporting" class="heading">5. Monitoring and Reporting&lt;a href="#5-monitoring-and-reporting" aria-labelledby="5-monitoring-and-reporting">
&lt;!-- &lt;i class="fas fa-link anchor">&lt;/i> -->
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512">&lt;use href="#fas-link">&lt;/use>&lt;/svg>&amp;nbsp;
 &lt;/a>
&lt;/h3>
&lt;ul>
&lt;li>&lt;strong>Generating reports on storage usage&lt;/strong> by filtering objects exceeding a critical size.&lt;/li>
&lt;li>&lt;strong>Detecting anomalies&lt;/strong>, such as sudden uploads of very large files, which could indicate an issue (e.g., massive log errors, data leaks, etc.).&lt;/li>
&lt;/ul>
&lt;hr>




&lt;h2 id="ii-how-to-filter-s3-events-by-object-size-c3-methods" class="heading">II. How to Filter S3 Events by Object Size? c3 Methods&lt;a href="#ii-how-to-filter-s3-events-by-object-size-c3-methods" aria-labelledby="ii-how-to-filter-s3-events-by-object-size-c3-methods">
&lt;!-- &lt;i class="fas fa-link anchor">&lt;/i> -->
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512">&lt;use href="#fas-link">&lt;/use>&lt;/svg>&amp;nbsp;
 &lt;/a>
&lt;/h2>




&lt;h3 id="1-filtering-via-aws-eventbridge-and-aws-lambda" class="heading">1. Filtering via AWS EventBridge and AWS Lambda&lt;a href="#1-filtering-via-aws-eventbridge-and-aws-lambda" aria-labelledby="1-filtering-via-aws-eventbridge-and-aws-lambda">
&lt;!-- &lt;i class="fas fa-link anchor">&lt;/i> -->
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512">&lt;use href="#fas-link">&lt;/use>&lt;/svg>&amp;nbsp;
 &lt;/a>
&lt;/h3>
&lt;p>AWS S3 sends events to EventBridge or an AWS Lambda function. Unfortunately, EventBridge rules do not directly allow filtering by object size. However, you can configure an &lt;strong>AWS Lambda&lt;/strong> function to process events and apply filtering based on size.&lt;/p></description></item><item><title>Demystifying AWS KMS</title><link>https://blog.dev.simpleenough.net/blog/demystifying-aws-kms/</link><pubDate>Sun, 19 Jan 2025 09:56:41 +0100</pubDate><guid>https://blog.dev.simpleenough.net/blog/demystifying-aws-kms/</guid><description>&lt;h2 id="i-introduction-to-aws-kms" class="heading">I. Introduction to AWS KMS&lt;a href="#i-introduction-to-aws-kms" aria-labelledby="i-introduction-to-aws-kms">
&lt;!-- &lt;i class="fas fa-link anchor">&lt;/i> -->
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512">&lt;use href="#fas-link">&lt;/use>&lt;/svg>&amp;nbsp;
 &lt;/a>
&lt;/h2>




&lt;h3 id="a-what-is-aws-kms" class="heading">&lt;strong>A. What is AWS KMS?&lt;/strong>&lt;a href="#a-what-is-aws-kms" aria-labelledby="a-what-is-aws-kms">
&lt;!-- &lt;i class="fas fa-link anchor">&lt;/i> -->
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512">&lt;use href="#fas-link">&lt;/use>&lt;/svg>&amp;nbsp;
 &lt;/a>
&lt;/h3>
&lt;p>AWS KMS, short for &lt;strong>Key Management Service&lt;/strong>, is a fully managed service designed to simplify the creation, management, and control of encryption keys. Everytime encryption is mentioned in AWS services like EBS, S3, RDS, or SSM, AWS KMS is probably involved. This service integrates seamlessly with IAM and, of course, it also ensures robust access control and auditing through CloudTrail.&lt;/p></description></item><item><title>A Brief History of AWS Architectures</title><link>https://blog.dev.simpleenough.net/blog/history/</link><pubDate>Fri, 20 Dec 2024 09:56:41 +0100</pubDate><guid>https://blog.dev.simpleenough.net/blog/history/</guid><description>&lt;h1 id="i-the-early-days-of-aws-and-cloud-computing-2002---2006" class="heading">I. The Early Days of AWS and Cloud Computing (2002 - 2006)&lt;a href="#i-the-early-days-of-aws-and-cloud-computing-2002---2006" aria-labelledby="i-the-early-days-of-aws-and-cloud-computing-2002---2006">
&lt;!-- &lt;i class="fas fa-link anchor">&lt;/i> -->
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512">&lt;use href="#fas-link">&lt;/use>&lt;/svg>&amp;nbsp;
 &lt;/a>
&lt;/h1>




&lt;h3 id="context-the-origin-of-the-aws-project" class="heading">Context: The Origin of the AWS Project&lt;a href="#context-the-origin-of-the-aws-project" aria-labelledby="context-the-origin-of-the-aws-project">
&lt;!-- &lt;i class="fas fa-link anchor">&lt;/i> -->
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512">&lt;use href="#fas-link">&lt;/use>&lt;/svg>&amp;nbsp;
 &lt;/a>
&lt;/h3>
&lt;p>Before AWS became a cloud giant, Amazon.com (the e-commerce site) had to manage a massive IT infrastructure to support its rapid growth. The company invested in expensive data centers and had to anticipate server capacity for peak traffic periods (such as Black Friday). However, much of this capacity remained unused outside of high-demand periods.&lt;/p></description></item><item><title>Learn AWS by Yourself? 10 Services to Know</title><link>https://blog.dev.simpleenough.net/blog/learnaws/</link><pubDate>Wed, 20 Nov 2024 09:56:41 +0100</pubDate><guid>https://blog.dev.simpleenough.net/blog/learnaws/</guid><description>&lt;h5 id="here-are-the-10-essential-services-to-master-to-fully-leverage-aws" class="heading">Here are the 10 essential services to master to fully leverage AWS.&lt;a href="#here-are-the-10-essential-services-to-master-to-fully-leverage-aws" aria-labelledby="here-are-the-10-essential-services-to-master-to-fully-leverage-aws">
&lt;!-- &lt;i class="fas fa-link anchor">&lt;/i> -->
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512">&lt;use href="#fas-link">&lt;/use>&lt;/svg>&amp;nbsp;
 &lt;/a>
&lt;/h5>




&lt;h1 id="1-iam-identity-and-access-management" class="heading">1. IAM (Identity and Access Management)&lt;a href="#1-iam-identity-and-access-management" aria-labelledby="1-iam-identity-and-access-management">
&lt;!-- &lt;i class="fas fa-link anchor">&lt;/i> -->
 &lt;svg class="svg-inline--fa fas fa-link anchor" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 640 512">&lt;use href="#fas-link">&lt;/use>&lt;/svg>&amp;nbsp;
 &lt;/a>
&lt;/h1>
&lt;p>IAM is the AWS service that allows you to manage access to your account&amp;rsquo;s resources. It plays a crucial role in security by controlling who can do what on your cloud infrastructure. With IAM, you can create individual users or group multiple users into groups. You can also define roles that allow other AWS services to interact with each other.&lt;/p></description></item></channel></rss>