<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Charity C. Francis on Medium]]></title>
        <description><![CDATA[Stories by Charity C. Francis on Medium]]></description>
        <link>https://medium.com/@charityfrancis5?source=rss-480169113db4------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*C5ywFibm2mdrTfQk.jpg</url>
            <title>Stories by Charity C. Francis on Medium</title>
            <link>https://medium.com/@charityfrancis5?source=rss-480169113db4------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 18:06:24 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@charityfrancis5/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[From Credentials to Federation: Setting Up SSO for AWS Using Microsoft Entra ID]]></title>
            <link>https://medium.com/@charityfrancis5/from-credentials-to-federation-setting-up-sso-for-aws-using-microsoft-entra-id-94614806527b?source=rss-480169113db4------2</link>
            <guid isPermaLink="false">https://medium.com/p/94614806527b</guid>
            <dc:creator><![CDATA[Charity C. Francis]]></dc:creator>
            <pubDate>Fri, 05 Dec 2025 13:25:35 GMT</pubDate>
            <atom:updated>2025-12-05T15:45:32.443Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oX4j3alZYP6HSlu-Ho_bUQ.png" /><figcaption>Setting Up SSO for AWS Using Microsoft Entra ID</figcaption></figure><p>Managing AWS access with standalone IAM users can quickly become messy. Multiple passwords, inconsistent permissions, and manual onboarding/offboarding. It all adds to an operational burden and a security risk waiting to happen.</p><p>So we decided to simplify everything.</p><p>Our goal was straightforward: <strong>let every team member sign in to AWS using their existing Microsoft Entra ID (M365) corporate account</strong>. No separate AWS passwords. No duplicated user management. Just secure, centralized identity. Think of when you want to log in to an application and use “sign in with Google” to gain access without entering a password; that’s SSO at work.</p><p>To achieve this, we integrated <strong>Microsoft Entra ID</strong> with <strong>AWS IAM Identity Center (IIC)</strong>, using SAML for authentication and SCIM for automatic user provisioning.</p><p>Below is the full breakdown of the implementation, the same steps I followed during the setup and testing process.</p><h3>Why Move to SSO?</h3><p>This integration solves two major problems:</p><h4>1. Centralized Authentication</h4><p>Users log in once using their M365 credentials and immediately gain access to the AWS accounts and roles assigned to them.</p><h4>2. Automated Provisioning</h4><p>With SCIM enabled, user and group changes in Entra ID sync automatically to AWS, including updates and offboarding. No manual work.</p><p>This removes the need for IAM users and replaces them with a clean, modern identity workflow.</p><h3>How We Implemented It</h3><p>The integration relies on two protocols:</p><ul><li><strong>SAML 2.0</strong> → handles authentication</li><li><strong>SCIM 2.0</strong> → handles automatic provisioning of users and groups</li></ul><p>We completed the setup across four phases, working together as the AWS and M365 admins.</p><h3>Before You Start— What You Need</h3><p>Think of this stage as packing your tools before starting the job.</p><h4>AWS Requirements</h4><ul><li>AWS Organizations is enabled in the account</li><li>Access to the AWS account (Admin or at least IAM Identity Center Admin)</li><li>AWS Identity Center is <strong>enabled</strong> in the Region you’ll use<br> (Identity Center is global, but configs apply to a home Region)</li></ul><h4>Microsoft Entra Requirements</h4><ul><li>Global Admin or at least Application Admin</li><li>Ability to create Enterprise Apps</li><li>Access to manage user assignments and groups<br> (you’ll use security groups for role mapping)</li></ul><h3>Configure AWS &amp; Collect Metadata</h3><p>Everything starts in the AWS Management Account.</p><h3>Setting Up Identity Federation: The Full Workflow</h3><p>We’ll integrate the two systems in this order:</p><ol><li><strong>Enable AWS Identity Center</strong></li><li><strong>Switch Identity Source — External Provider (Microsoft Entra)</strong></li><li><strong>Create an Enterprise App in Entra</strong></li><li><strong>Configure SAML settings</strong></li><li><strong>Map Entra groups → AWS roles</strong></li><li><strong>Test the login flow</strong></li></ol><p>Let’s break down each step.</p><h3>Step-by-Step Implementation Guide</h3><h3>Step 1: Enable AWS Identity Center</h3><p>When you open AWS IAM Identity Center for the first time:</p><ul><li>Click <strong>Enable</strong></li><li>Choose a <strong>Home Region</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DMg-h3skSRijYEn51y23Ag.png" /><figcaption>Enable IAM Identity Centre in the Right Region</figcaption></figure><p>Once enabled, the dashboard becomes your central control panel.</p><h3>Step 2: Change Identity Source to Microsoft Entra ID</h3><p>In Identity Center:</p><ol><li>Go to <strong>Settings</strong></li><li>Click <strong>Identity Source</strong></li><li>Select <strong>External Identity Provider</strong></li><li>Click <strong>Next</strong></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9lddWU0CdFjnJ_aEUrbqYA.png" /><figcaption>Change Identity Source</figcaption></figure><p>You’ll see three key values that AWS needs to provide to Entra:</p><ul><li><strong>AWS Identity Centre ACS URL</strong></li><li><strong>AWS Identity Centre Issuer URL</strong></li><li><strong>AWS Identity Centre Access Portal Sign-in URL</strong></li></ul><p>Download/save these — you’ll use them in Entra.</p><h3>Step 3: Create the Enterprise App in Microsoft Entra ID</h3><h3>Inside the Entra admin portal:</h3><ol><li>Go to <strong>Microsoft Entra ID</strong></li><li>Select <strong>Enterprise Applications</strong></li><li>Click <strong>+ New Application</strong></li><li>Choose <strong>Create your own application</strong></li><li>Name it something like: <strong>AWS Identity Center — SSO</strong></li><li>Choose I<strong>ntegrate any other application (Non-gallery)</strong></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2dh5x9hF9h8cO34jXw8k3A.png" /><figcaption>Create New Entreprise Application for SSO</figcaption></figure><p>Your app shell is now created.</p><h3>Step 4: Configure SAML SSO in Entra</h3><p>Inside your newly created Enterprise App:</p><h4>4.1 Enable SAML</h4><ol><li>Go to <strong>Single Sign-On</strong></li><li>Select <strong>SAML</strong></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6qc-piJAg3DFlnhAxuWMzg.png" /><figcaption>Configure SSO</figcaption></figure><h4>4.2 Configure Basic SAML</h4><p>Select edit and paste the values from AWS Identity Center:</p><ul><li><strong>Identifier (Entity ID)</strong> → AWS Issuer URL</li><li><strong>Reply URL (ACS URL)</strong> → AWS Access Portal Sign-in URL</li><li><strong>Logout URL</strong> → Optional, but you can use the same Issuer URL</li></ul><h4>4.3 Upload AWS Metadata</h4><p>Upload the AWS metadata file you downloaded earlier.<br> This ensures your certificate and endpoints match AWS.</p><h4>4.4 Download Entra ID Metadata</h4><p>From the “SAML Signing Certificate” box, <strong>Download</strong> the <strong>“Federation Metadata XML”</strong> file and securely send it to the AWS Admin. The AWS Admin will use this to complete the change to an external identity provider step.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/931/1*cY4JqkUOeUuFBwt2wdZ2yw.png" /><figcaption>Download Application Metadata File</figcaption></figure><h3>Step 5: Configure Attributes &amp; Claims</h3><p>AWS requires a specific set of SAML claims:</p><ul><li>Subject → user.userprincipalname</li><li>email → user.mail</li><li>firstName → user.givenname</li><li>lastName → user.surname</li></ul><h3>Step 6: Assign Users &amp; Groups to the App</h3><p>This is where you decide who gets access to AWS.</p><ul><li>Create groups like:</li><li>AWS-Administrators</li><li>AWS-Developers</li><li>AWS-ReadOnly</li></ul><p>Assign users to these groups.</p><p>Then in Entra:</p><ol><li>Go to <strong>Users and Groups</strong> in the Enterprise App</li><li>Assign your groups</li></ol><p>This becomes the mapping bridge to AWS roles later.</p><h3>Step 7: Connect Entra to AWS (Back to AWS Console)</h3><p>Return to AWS Identity Center:</p><ol><li>Go to <strong>Settings → Identity Source</strong></li><li>Upload the <strong>Entra SAML Metadata</strong> into AWS</li><li>Confirm the change</li></ol><p>AWS will now recognize Entra as the IDP.</p><h3>Step 8: <strong>Configure SCIM (Provisioning):</strong></h3><h4>8.1 In the AWS Console</h4><ul><li>Navigate to the <strong>Settings &gt; Provisioning</strong> tab and click <strong>Enable</strong>.</li><li>A pop-up will provide the <strong>SCIM endpoint (Tenant URL)</strong> and an <strong>Access token (Secret Token)</strong>.</li><li>Securely copy both values. They will be used to enable SCIM Provisioning on the Entra ID application.</li><li>Set the “Provisioning Mode” to <strong>Automatic</strong>.</li></ul><h4>8.2 In the Microsoft Entra ID Application</h4><ul><li>In the application’s menu, select <strong>Provisioning</strong>.</li><li>Set the “Provisioning Mode” to <strong>Automatic</strong>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MdsTVy6f2g1t1HyQc590FQ.png" /><figcaption>Change provisioning to automatic</figcaption></figure><ul><li>Expand “Admin Credentials” and enter the values from Phase 4.2:</li><li>Tenant URL: Paste the SCIM endpoint.</li><li>Secret Token: Paste the Access token.</li><li>Click <strong>Test Connection</strong> to validate. A success message must be received.</li><li><strong>Save</strong> the credential configuration.</li><li>Set the <strong>“Provisioning Status”</strong> to <strong>On</strong> and <strong>Save</strong> again to start the sync.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5MZ_RH24fpdRl03YI5UoYw.png" /><figcaption>Turn provisioning on</figcaption></figure><p>Provisioning ensures that the authentication between AWS IAM Identity Centre and Microsoft Entra ID remains in sync.</p><h3>9. Map Entra Groups or Users to AWS Permissions</h3><p>In AWS Identity Center:</p><ol><li>Go to <strong>AWS Accounts</strong></li><li>Select <strong>Permission sets</strong></li><li>Create Permission Sets e.g, predefined permissions like <strong>AdministratorAccess, PowerUserAccess, ReadOnlyAccess or custom permission sets.</strong></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5QYs1Ew9wPl2DKRecIMGog.png" /><figcaption>Define Permission Sets</figcaption></figure><p>Next:</p><ol><li>Select an account where the users can sign in via SSO</li><li>Click <strong>Assign Users or Groups</strong></li><li>Choose your Entra groups or users</li><li>Map them to the permission sets you created, e.g.:</li></ol><ul><li>AWS-Administrators → <strong>AdministratorAccess</strong></li><li>AWS-Developers → <strong>PowerUserAccess</strong></li><li>AWS-ReadOnly → <strong>ReadOnlyAccess</strong></li></ul><p>AWS will automatically create IAM roles for these permission sets.</p><h3>Step 9: Test Everything</h3><p>Ask a user or test with your own account:</p><ol><li>Go to the AWS SSO URL provided (your new portal)</li><li>Sign in with Microsoft Entra credentials</li><li>Confirm:</li></ol><ul><li>MFA works (as enforced in Entra)</li><li>Group → Role mapping is correct</li><li>Accounts and permission sets appear as expected</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7btYRaQ9ziQKw3Q3j18gOw.png" /><figcaption>Successful Login!</figcaption></figure><p>If login works: <strong>Identity federation is fully configured!</strong></p><p>Every AWS access decision now flows from <strong>Microsoft Entra ID group membership</strong>. This is what a modern cloud identity strategy looks like: centralized, automated, and secure.</p><p>Please tell me what you thought of this blog post. And please like and subscribe, it means the world to me!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=94614806527b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Set Up an AWS Client VPN (Step-by-Step with Screenshots)]]></title>
            <link>https://medium.com/@charityfrancis5/how-to-set-up-an-aws-client-vpn-step-by-step-with-screenshots-9f75cefa6ae4?source=rss-480169113db4------2</link>
            <guid isPermaLink="false">https://medium.com/p/9f75cefa6ae4</guid>
            <dc:creator><![CDATA[Charity C. Francis]]></dc:creator>
            <pubDate>Fri, 26 Sep 2025 07:33:08 GMT</pubDate>
            <atom:updated>2025-09-26T07:33:08.512Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/641/1*zoyegRdX63QG4jR3sM30eg.png" /><figcaption>How to Set Up an AWS Client VPN</figcaption></figure><p>When working with AWS, many of your resources live in <strong>private subnets</strong> for security. That’s great, until you actually need to connect from your laptop for testing, troubleshooting, or remote access.</p><p>Enter <strong>AWS Client VPN</strong>. Think of it as a secure tunnel between your computer and your VPC. Once connected, you can access private servers and services inside your cloud environment, just as if you were sitting within the network.</p><p>In this guide, I’ll walk you through setting up a Client VPN in AWS step by step, complete with screenshots to make the process easier.</p><h3>What is AWS Client VPN?</h3><p>AWS Client VPN is a managed, OpenVPN-based service that allows <strong>individual devices</strong> (laptops, desktops, phones) to connect securely to AWS or on-premises networks.</p><p>Key features:</p><ul><li>Based on <strong>OpenVPN</strong> (cross-platform: Windows, macOS, Linux).</li><li>Supports <strong>split tunneling</strong> (choose which traffic goes through the VPN).</li><li>Scales easily, with pay-as-you-go pricing.</li><li>Integrates with IAM, Active Directory, or certificates for authentication.</li></ul><h3>Client VPN vs Site-to-Site VPN</h3><p>It’s easy to confuse these two, so here’s a quick distinction:</p><p><a href="https://docs.aws.amazon.com/vpn/latest/s2svpn/VPC_VPN.html"><strong>Site-to-Site VPN</strong></a></p><ul><li>Connects entire <strong>networks</strong> (like your corporate office LAN to an AWS VPC).</li><li>Always on.</li><li>Ideal for hybrid cloud setups.</li></ul><p><strong>Client VPN</strong></p><ul><li>Connects <strong>devices</strong> (like your laptop) directly to an AWS VPC.</li><li>On-demand.</li><li>Perfect for developers, testers, and admins who need temporary access.</li></ul><p>In short: Site-to-Site connects <em>offices</em>; Client VPN connects <em>people</em>.</p><h3>Step-by-Step Setup Guide</h3><h3>Step 1: Create Server and Client Certificates</h3><p>AWS Client VPN relies on certificates to establish trust. You’ll need:</p><ul><li>A <strong>server certificate</strong> (imported into ACM).</li><li>A <strong>client certificate</strong> and key (installed locally and referenced in your VPN config).</li></ul><p>Using <strong>Easy-RSA</strong>:</p><pre># Clone Easy-RSA<br>git clone https://github.com/OpenVPN/easy-rsa.git<br>cd easy-rsa/easyrsa3</pre><pre># Initialize PKI<br>./easyrsa init-pki</pre><pre># Build CA<br>./easyrsa build-ca nopass</pre><pre># Generate server certificate<br>./easyrsa build-server-full server nopass</pre><pre># Generate client certificate<br>./easyrsa build-client-full client1.example.com nopass</pre><p>Copy the certs and keys into a dedicated folder, then import the <strong>server cert</strong> into <strong>AWS Certificate Manager (ACM)</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GO0-6feTtNDtzp0QQ_FxLQ.png" /></figure><h3>Step 2: Create a Client VPN Endpoint</h3><p>In the AWS Console, go to <strong>VPC → Create Client VPN Endpoint</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OaPcwyMazZDRBrtJvdE74Q.png" /><figcaption>Select Create Client VPN to start</figcaption></figure><p>Provide a name, description, and <strong>Client CIDR range</strong> (must not overlap with VPC CIDR).</p><p>Select the <strong>server certificate</strong> and client certificate from ACM (If using mutual authentication).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2ais-Sc5NU1UJ_kZYra33w.png" /><figcaption>Choose authentication type and add both imported certificates</figcaption></figure><p>Set up <strong>authentication</strong> (mutual certs or AD).</p><p>Enable <strong>split tunnel</strong> if you don’t want all traffic routed through VPN.</p><h3>Step 3: Associate the VPN with a Target Network</h3><p>Associate the endpoint with a <strong>subnet</strong> inside your VPC. This subnet determines where your traffic enters the VPC.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B1b0tAqjZmTfxGbw1u3_vw.png" /><figcaption>Click Associate Target Network and connect to your VPC subnet</figcaption></figure><h3>Step 4: Add Authorization Rules</h3><p>By default, nothing is accessible. You must explicitly allow access.</p><ul><li>Navigate to <strong>Authorization Rules</strong>.</li><li>Add a rule that permits traffic to your <strong>VPC CIDR range</strong> (e.g., 10.0.0.0/16).</li></ul><h3>Step 5: Check Security Groups</h3><p>Make sure your resources’ <strong>security groups</strong> allow inbound traffic from the <strong>Client VPN CIDR block</strong>.</p><p>For example:</p><ul><li>Allow <strong>RDP (3389)</strong> for Windows instances.</li><li>Allow <strong>SSH (22)</strong> for Linux instances.</li><li>Allow <strong>ICMP</strong> if you want to test with ping.</li></ul><h3>Step 6: Download the Client VPN Configuration</h3><ul><li>Go back to the Client VPN endpoint in AWS.</li><li>Click <strong>Download Client Configuration</strong>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yLpBQz3-7-tSJwm9aB1uhw.png" /><figcaption>Download Client Configuration</figcaption></figure><ul><li>Edit the configuration file to insert your <strong>client certificate</strong> and <strong>private key</strong> under &lt;cert&gt; &lt;/cert&gt;and &lt;key&gt; &lt;/key&gt;sections. Save the file.</li></ul><h3>Step 7: Install the AWS VPN Client</h3><p>Download and install the <a href="https://aws.amazon.com/vpn/client-vpn-download/"><strong>AWS VPN Client</strong></a> compatible with your local system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-vAQUhlQGZxvQkvxPD0SXg.png" /><figcaption>Choose the client compatible with your laptop</figcaption></figure><ul><li>Open the client.</li><li>Add a new profile by importing the config file.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gNjLq2pr6eHMxb5tsuc8uA.png" /></figure><ul><li>Click <strong>Connect</strong>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/527/1*Gb-AWNzkNIh53Sy3uqKLRA.png" /></figure><h3>Step 8: Test the Connection</h3><p>Finally, let’s confirm it works:</p><ul><li>Launch an EC2 instance inside your VPC (Windows or Linux).</li><li>Copy its <strong>private IP address</strong>.</li><li>From your local machine, try to <strong>RDP</strong> or <strong>SSH</strong> into the instance.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*dd4rfiRzPsiFFIXgqXdtEQ.png" /></figure><ul><li>Or simply test with a ping.</li></ul><p>If it works, congrats! Your Client VPN setup is successful!</p><h3>Final Thoughts</h3><p>AWS Client VPN may look complex, but the flow is straightforward once you break it down:</p><ol><li>Certificates (trust).</li><li>Endpoint (entry point).</li><li>Target network (landing subnet).</li><li>Authorization rules (permissions).</li><li>Security groups (access rules).</li></ol><p>With these pieces in place, you can securely connect to private resources in AWS from anywhere in the world.</p><p><strong>Pro tip</strong>: If you ever change settings like enabling split-tunnel or adding new routes, make sure to <strong>re-download the client config file</strong> and reconnect; otherwise, your local profile won’t reflect the new routing.</p><p>I hope you found this article helpful. I would love to read your comments and feedback for future improvements. Thank you!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9f75cefa6ae4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building a Serverless Document Processing Workflow with AWS Step Functions and CloudFormation]]></title>
            <link>https://medium.com/@charityfrancis5/building-a-serverless-document-processing-workflow-with-aws-step-functions-and-cloudformation-5b1148fd9437?source=rss-480169113db4------2</link>
            <guid isPermaLink="false">https://medium.com/p/5b1148fd9437</guid>
            <dc:creator><![CDATA[Charity C. Francis]]></dc:creator>
            <pubDate>Tue, 13 May 2025 17:30:06 GMT</pubDate>
            <atom:updated>2025-05-13T17:30:06.390Z</atom:updated>
            <content:encoded><![CDATA[<h3>Introduction</h3><p>In this blog post, I’ll walk you through how I built and deployed a fully automated document processing pipeline using <strong>AWS Step Functions</strong>, triggered by <strong>S3 events</strong>, and fully defined using <strong>CloudFormation</strong>.</p><p>The goal of the project was simple: process documents as soon as they’re uploaded to an S3 bucket. The pipeline:</p><ul><li>Extracts metadata from the document</li><li>Uses Amazon Textract to extract text</li><li>Analyzes the extracted text using Amazon Comprehend</li><li>Stores the final results back in S3</li></ul><p>This is a fully serverless and event-driven architecture — scalable, automated, and low-maintenance.</p><h3>What is AWS Step Functions?</h3><p>AWS Step Functions is a service that lets you coordinate multiple AWS services into serverless workflows using a state machine model. It’s ideal for orchestrating distributed systems and breaking complex processes into discrete, manageable steps.</p><p><strong>The beauty of Step Functions?</strong></p><ul><li>Visual workflow designer for better debugging</li><li>Built-in error handling and retries</li><li>Parallel and sequential execution support</li><li>Easy integration with Lambda, DynamoDB, ECS, SNS, SQS, and more</li></ul><h3>Architecture Overview</h3><p><strong>The services used for this little project include:</strong></p><ul><li>Amazon S3 (to receive uploaded documents)</li><li>S3 Event Notification (Alerts the lambda functions when a document is uploaded)</li><li><a href="https://aws.amazon.com/lambda/">AWS Lambda</a> (to process logic at each stage)</li><li><a href="https://aws.amazon.com/step-functions/">AWS Step Functions</a> (to orchestrate the workflow)</li><li><a href="https://aws.amazon.com/textract/">Amazon Textract</a> (extracts texts using machine learning)</li><li><a href="https://aws.amazon.com/comprehend/">Amazon Comprehend</a> (intelligently analyze text to derive insights)</li><li><a href="https://aws.amazon.com/iam/">IAM</a> (to define fine-grained access policies)</li><li><a href="https://aws.amazon.com/cloudformation/">CloudFormation</a> (for infrastructure as code)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lteGL5TmXzDS2fK0" /><figcaption>Step Functions Document Processor Workflow</figcaption></figure><h3>Workflow Breakdown</h3><p>Here’s how the pipeline works:</p><ol><li>A document is uploaded to a designated S3 bucket.</li><li>The upload triggers a Lambda function to start a Step Functions workflow.</li><li>Step Functions invokes:</li></ol><ul><li>A Lambda to extract metadata</li><li>A Lambda that runs Amazon Textract and extracts text from the document</li><li>Another Lambda that analyzes the text with Amazon Comprehend</li><li>A final Lambda that stores the results back in S3</li></ul><h3>Why CloudFormation?</h3><p>I used AWS CloudFormation to define and deploy all the infrastructure resources. Benefits include:</p><ul><li><strong>Consistency</strong>: Reproducible deployments across environments</li><li><strong>Automation</strong>: One template, one deployment command</li><li><strong>Versioning</strong>: Track changes in infrastructure as part of version control</li></ul><blockquote><em>Note: I configured the S3 event notification to trigger the initial Lambda manually through the AWS Console.</em></blockquote><p>In case you were wondering, here is how I did it:</p><ol><li>Go to the <strong>S3 console</strong> and open your bucket (document-processor-dp2).</li><li>Navigate to the <strong>Properties</strong> tab.</li><li>Scroll down to <strong>Event notifications</strong> and click <strong>Create event notification</strong>.</li><li>Name your event (e.g., StepFunctionTrigger).</li><li>Under <strong>Event types</strong>, select <strong>All Object Create Event.</strong></li><li>Under <strong>Destination</strong>, choose <strong>Lambda function</strong>.</li><li>Select your Lambda function (StartDocumentPipeline).</li><li>Save the notification.</li></ol><p>Make sure the Lambda has the proper invoke permissions from S3. This was handled in the CloudFormation template with a Lambda::Permission resource.</p><h3>CloudFormation Template Highlights</h3><p>Here are a few key parts of the template:</p><h3>IAM Role</h3><pre>LambdaExecutionRole:<br>  Type: AWS::IAM::Role<br>  Properties:<br>    RoleName: DocumentLambdaExecutionRole<br>    ...</pre><h3>Lambda to Start Step Function Execution</h3><pre>StartStepFunctionLambda:<br>  Type: AWS::Lambda::Function<br>  Properties:<br>    FunctionName: StartDocumentPipeline<br>    ...</pre><h3>Step Functions State Machine Definition</h3><pre>DocumentProcessingStateMachine:<br>  Type: AWS::StepFunctions::StateMachine<br>  Properties:<br>    StateMachineName: DocumentProcessingPipeline<br>    DefinitionString:<br>      !Sub |<br>        {<br>          &quot;StartAt&quot;: &quot;ExtractMetadata&quot;,<br>          &quot;States&quot;: {<br>            &quot;ExtractMetadata&quot;: { &quot;Type&quot;: &quot;Task&quot;, &quot;Resource&quot;: &quot;${ExtractMetadataFunction.Arn}&quot;, &quot;Next&quot;: &quot;ExtractText&quot; },<br>            &quot;ExtractText&quot;: { &quot;Type&quot;: &quot;Task&quot;, &quot;Resource&quot;: &quot;${ExtractTextFunction.Arn}&quot;, &quot;Next&quot;: &quot;AnalyzeText&quot; },<br>            &quot;AnalyzeText&quot;: { &quot;Type&quot;: &quot;Task&quot;, &quot;Resource&quot;: &quot;${AnalyzeTextFunction.Arn}&quot;, &quot;Next&quot;: &quot;StoreResults&quot; },<br>            &quot;StoreResults&quot;: { &quot;Type&quot;: &quot;Task&quot;, &quot;Resource&quot;: &quot;${StoreResultsFunction.Arn}&quot;, &quot;End&quot;: true }<br>          }<br>        }</pre><h3>Lessons Learned</h3><ul><li><strong>IAM roles are critical</strong>: Each service needs just the right permissions to interact with each other. In this case, Lambda can’t access the s3 bucket if the right permissions aren’t given.</li><li><strong>Step Functions made debugging easier</strong>: While testing the functionality of the workflow, I experienced an error that I had to debug. The Step functions visual workflow was very critical in debugging it, as it showed the exact state machine that failed and the error message.</li><li><strong>CloudFormation dependencies matter</strong>: Ensure roles and permissions are created before they’re referenced.</li><li><strong>Manual S3 notifications</strong>: My first move was to create everything using Cloudformation, including the event notification. This did not go well, as the event notification stayed in a loop, causing the template to fail after a long time. So I learned that not all configurations need to be in code — in this case, manual setup for event triggers was faster.</li></ul><h3>Conclusion</h3><p>This project was a practical example of how powerful serverless cloud workflows can be. By combining Step Functions with other AWS services and deploying through CloudFormation, I built an automated system that processes and understands documents without manual intervention.</p><p>Use cases? Think invoice processing, resume parsing, compliance scanning — the possibilities are endless.</p><h3>Want More?</h3><p>Want the full CloudFormation template or code samples? Drop a comment or reach out. I’m happy to share!</p><p>#AWS #StepFunctions #Textract #Comprehend #Serverless #CloudFormation #DevOps #Automation #CloudTalks</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5b1148fd9437" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Setting Up an NGINX Server on AWS: My Experience]]></title>
            <link>https://medium.com/@charityfrancis5/setting-up-an-nginx-server-on-aws-my-experience-4a5e757f39c2?source=rss-480169113db4------2</link>
            <guid isPermaLink="false">https://medium.com/p/4a5e757f39c2</guid>
            <dc:creator><![CDATA[Charity C. Francis]]></dc:creator>
            <pubDate>Thu, 30 Jan 2025 09:27:17 GMT</pubDate>
            <atom:updated>2025-01-30T17:51:04.412Z</atom:updated>
            <content:encoded><![CDATA[<p>DevOps! A very familiar concept that has fascinated me from the moment I decided to get into tech. I had placed it as one of my future learning goals, so here I am, all signed up for the intensive two-week HNG internship and ready to tackle it head-on.</p><p>For our first task, we had to configure an NGINX web server on an Ubuntu server. I applied cloud engineering principles (which I am already familiar with) like automation and infrastructure-as-code methodologies to the task. I faced some challenges as normal when working on any project/task, so here’s a breakdown of the experience and lessons learned.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6P_EyItELl-qAtrUucHLTQ.png" /></figure><h3>Approach to Completing the Task</h3><p>To accomplish this task, I followed these steps:</p><ol><li><strong>Provisioning the AWS Instance<br></strong> I used AWS CloudFormation to automate the deployment of an EC2 instance. My template included parameters for the AMI ID, instance type, VPC, and subnet. This is because I wanted my template to be highly reusable.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iXjS_h7rKkRHC8H9Gq3Wwg.png" /></figure><ol><li><strong>Configuring Security Groups<br></strong> I created a security group to allow HTTP (port 80) traffic, ensuring that my web server would be accessible from the internet.</li><li><strong>Automating NGINX Installation<br></strong> Using a user data script, I automated the installation and configuration of NGINX. The script included:</li></ol><ul><li>Updating the package list (apt update -y)</li><li>Installing NGINX (apt install -y nginx)</li><li>Writing a custom HTML page (echo “Welcome to DevOps Stage 0 — Charity Francis/Chereetee” &gt; /var/www/html/index.html)</li><li>Enabling and starting the NGINX service</li></ul><p><strong>4. Testing the Server<br></strong> After deployment, I verified that NGINX was running by accessing the public IP of my EC2 instance in a browser. Yay, it works!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/636/1*uwwvwE5x_toAHOErgR5E3w.png" /></figure><h3>Challenges and How I Overcame Them</h3><p>One of the many things I have learned since my time working with cloudformation templates is that there would most likely be errors that requiretroubleshooting. In this case, these are some of the errors I encountered when trying to create my stack:</p><ul><li><strong>Incorrect Subnet Configuration<br></strong>Initially, I defined PublicSubnetId as a list instead of a string in my CloudFormation template. This caused deployment failures. Fixing the data type resolved the issue.</li><li><strong>Security Group Egress Rule<br></strong>My instance would have lacked internet access necessary for package installations due to incorrect configuration of my outbound rules. Adding an egress rule (-1 protocol) resolved it.</li></ul><p>These are just a few of the challenges I faced trying to create the cloudformation stack. So many changes had to be made and research done to get to the final result.</p><h3>How This Task Contributes to My Learning and Professional Goals</h3><p>This task reinforced my understanding of:</p><ul><li><strong>Infrastructure as Code (IaC)</strong>: Writing reusable CloudFormation templates for automated deployments.</li><li><strong>Linux System Administration</strong>: Installing and managing web services on Ubuntu.</li><li><strong>Cloud Engineering &amp; DevOps Best Practices</strong>: Handling security, automation, and scalability in AWS.</li></ul><p>Mastering these skills is crucial for roles like<a href="https://hng.tech/hire/devops-engineers"> DevOps Engineers</a>, my role as a<a href="https://hng.tech/hire/cloud-engineers"> Cloud Engineer</a>, and<a href="https://hng.tech/hire/infrastructure-engineers"> Infrastructure Engineers</a>. Additionally, this internship will take us through understanding containerized solutions which will be beneficial for becoming a<a href="https://hng.tech/hire/kubernetes-specialists"> Kubernetes Specialist</a> or<a href="https://hng.tech/hire/docker-specialists"> Docker Specialist</a>.</p><h3>Conclusion</h3><p>Successfully deploying and configuring an NGINX server on AWS was a valuable learning experience. It gave me confidence in cloud automation and web server management, skills that are essential for aspiring<a href="https://hng.tech/hire/aws-solutions-architects"> AWS Solutions Architects</a> and<a href="https://hng.tech/hire/site-reliability-engineers"> Site Reliability Engineers</a>. I look forward to tackling more complex infrastructure challenges in the future!</p><p>For more on DevOps and cloud roles, check out these references:</p><ul><li><a href="https://hng.tech/hire/automation-engineers">Automation Engineers</a></li><li><a href="https://hng.tech/hire/ci-cd-pipeline-engineers">CI/CD Pipeline Engineers</a></li><li><a href="https://hng.tech/hire/monitoring-observability-engineers">Monitoring/Observability Engineers</a></li><li><a href="https://hng.tech/hire/google-cloud-engineers">Google Cloud Engineers</a></li><li><a href="https://hng.tech/hire/azure-devops-engineers">Azure DevOps Engineers</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4a5e757f39c2" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>