<?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 Francia Rasolomampionona on Medium]]></title>
        <description><![CDATA[Stories by Francia Rasolomampionona on Medium]]></description>
        <link>https://medium.com/@francia.rasolomampionona?source=rss-da53ab4aa01c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*NBLV2O8_mA3i4uG0qkPn2A.jpeg</url>
            <title>Stories by Francia Rasolomampionona on Medium</title>
            <link>https://medium.com/@francia.rasolomampionona?source=rss-da53ab4aa01c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 12:50:51 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@francia.rasolomampionona/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[LAMP Stack on AWS]]></title>
            <link>https://aws.plainenglish.io/lamp-stack-on-aws-255db69ebc41?source=rss-da53ab4aa01c------2</link>
            <guid isPermaLink="false">https://medium.com/p/255db69ebc41</guid>
            <category><![CDATA[lamp]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[lamp-stack-development]]></category>
            <category><![CDATA[aws-ec2]]></category>
            <dc:creator><![CDATA[Francia Rasolomampionona]]></dc:creator>
            <pubDate>Wed, 22 Jul 2026 18:23:49 GMT</pubDate>
            <atom:updated>2026-07-22T18:23:49.966Z</atom:updated>
            <content:encoded><![CDATA[<p>Linux, Apache, MySQL/Mariadb, PHP/Python/Perl</p><p><strong>Step 1: Install Apache</strong></p><p>To install apache on amazon linux:</p><p>sudo yum update</p><p>sudo yum install httpd</p><p>sudo systemctl start httpd</p><p>sudo systemctl enable httpd</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ujt8N79D1RLnTwxuGsxtEw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*otlwkqyaKCH4XhQPKRhIOQ.png" /></figure><p><strong>Step 2: Install mysql</strong></p><p>sudo yum install mariadb-server -y</p><p>sudo systemctl start mariadb</p><p>sudo systemctl enable mariadb</p><p>sudo mysql (to set up root user before running the security installation script):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/947/1*nuiYSazjhekMIxNByQeDOQ.png" /></figure><p>sudo mysql_secure_installation</p><p><strong>Step 3: Install PHP</strong></p><p>sudo dnf install php php-mysqli php-json php-common -y</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2HzA1duu9yDeJRdmIOdfhQ.png" /></figure><p><strong>Step 4: Create a virtual host for the website</strong></p><p>sudo mkdir -p /var/www/html/projectlamp<br> sudo chown -R $USER:$USER /var/www/html/projectlamp/<br> sudo chmod -R 755 /var/www<br> sudo nano /etc/httpd/conf/httpd.conf (add this if missing IncludeOptional conf.d/*.conf)<br> sudo nano /etc/httpd/conf.d/projectlamp.conf</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/930/1*Bk8DQLv0CiHFUCM5sdbEDw.png" /></figure><p>sudo httpd -t (checking)<br>sudo systemctl restart httpd</p><p><strong>Step 5: Enable PHP</strong><br>sudo nano /etc/httpd/conf.d/projectlamp.conf (add DirectoryIndex index.php index.html)<br>sudo systemctl restart httpd<br>cd /var/www/html/projectlamp/<br>sudo nano index.php (add &lt;?php phpinfo(); ?&gt;)<br>sudo systemctl restart httpd</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5wM7jSdgL1btuROrkfiFlA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=255db69ebc41" width="1" height="1" alt=""><hr><p><a href="https://aws.plainenglish.io/lamp-stack-on-aws-255db69ebc41">LAMP Stack on AWS</a> was originally published in <a href="https://aws.plainenglish.io/">AWS in Plain English</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to establish secure communication between Public and Private VPCs via VPC Peering]]></title>
            <link>https://awstip.com/ht-03-how-to-establish-secure-communication-between-public-and-private-vpcs-via-vpc-peering-a305b7fcde96?source=rss-da53ab4aa01c------2</link>
            <guid isPermaLink="false">https://medium.com/p/a305b7fcde96</guid>
            <category><![CDATA[aws-ec2]]></category>
            <category><![CDATA[aws-vpc-peering]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[aws-security]]></category>
            <dc:creator><![CDATA[Francia Rasolomampionona]]></dc:creator>
            <pubDate>Tue, 19 May 2026 16:41:00 GMT</pubDate>
            <atom:updated>2026-07-04T06:03:36.780Z</atom:updated>
            <content:encoded><![CDATA[<h4>Simple architecture of the project</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/532/1*byEqIEY2V-x8mczeME6f1g.png" /><figcaption>AWS docs</figcaption></figure><p><strong>Step 1: Configure Peering Connection: VPC — Peering Connection</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Bu-A11t70gI1TR0dhgy4Ug.jpeg" /></figure><p>Requester is the public VPC, the accepter is the private one.</p><p><strong>Step 2: From the accepter VPC, Accept the request: Action — Accept request</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b1xWU5PbLN0rAAlpDCZvNA.jpeg" /></figure><p><strong>Step 3: Configure the route table:</strong></p><p>Go to each route table section and add the other side CIDR block as destination, and the peering connection as Target</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1WdI4GZAwPcd84KqkRjvog.jpeg" /></figure><p><strong>Step 4: Update the security group accordingly</strong></p><p>Go to each subnet group and add the appropriate rules</p><p>Private vpc:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k3oLBtWKwb7qvFvekeAozg.jpeg" /></figure><p>Public vpc:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*czgbTIM0M3m9Vm8YGsc1zA.jpeg" /></figure><p><strong>Step 5: Test the flow</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/697/1*xvoLrCslnEkTi2_qL3mRpg.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a305b7fcde96" width="1" height="1" alt=""><hr><p><a href="https://awstip.com/ht-03-how-to-establish-secure-communication-between-public-and-private-vpcs-via-vpc-peering-a305b7fcde96">How to establish secure communication between Public and Private VPCs via VPC Peering</a> was originally published in <a href="https://awstip.com/">AWS Tip</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How did I pass the AWS Solution Architect Associate certification?]]></title>
            <link>https://awstip.com/how-did-i-ace-aws-solution-architect-associate-certification-b7aa41181640?source=rss-da53ab4aa01c------2</link>
            <guid isPermaLink="false">https://medium.com/p/b7aa41181640</guid>
            <category><![CDATA[aws-saa-c03]]></category>
            <category><![CDATA[aws-exam-preparation]]></category>
            <dc:creator><![CDATA[Francia Rasolomampionona]]></dc:creator>
            <pubDate>Mon, 27 Apr 2026 11:21:35 GMT</pubDate>
            <atom:updated>2026-05-11T15:37:30.307Z</atom:updated>
            <content:encoded><![CDATA[<p>I will first discuss all the resources I have used, and then I will talk about the learning resources I would choose if I were to take it in 2026.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/574/1*hRNxo__C25UzUDhIs8sqHQ.png" /></figure><p><strong>1) Learning path and hands-on experience</strong><br>First, I have used the learning path on AWS skill builder.<br>You can research “Solution Architect Associate- learning path”.After spending 2 months on that, I have done some workshops to acquire more hands-on experience.</p><h4><strong>2) Practice test</strong></h4><p>I have done 2 series of practice test on AWS skill builder</p><p>Also, I have evaluated myself with practice test on udemy by Stephan Maarek.<br>I waited for a higher score (&gt;90%)</p><h4><strong>3) 2days before exam</strong></h4><p>I went through an one hour summary of the learning path on AWS skill builder</p><h4>4) Alternatively</h4><p>If I have to re-take tthat exam now, I would choose one of the following platform for preparation:</p><p>1- AWS Skill Builder for course, lab and workshop</p><p>2- Udemy with Stephan Maarek for course and practice test: <a href="https://www.udemy.com/course/aws-certified-solutions-architect-associate-saa-c03/">https://www.udemy.com/course/aws-certified-solutions-architect-associate-saa-c03/</a></p><p>3- Udemy or Digital Cloud Training with Neal Davis: <a href="https://www.udemy.com/course/aws-certified-solutions-architect-associate-hands-on">https://www.udemy.com/course/aws-certified-solutions-architect-associate-hands-on</a></p><p>4- Tutorial Dojo: <a href="https://portal.tutorialsdojo.com/courses/aws-certified-solutions-architect-associate-exam-video-course/">https://portal.tutorialsdojo.com/courses/aws-certified-solutions-architect-associate-exam-video-course/</a></p><p>5- Kodekloud: <a href="https://learn.kodekloud.com/user/courses/aws-solutions-architect-associate-certification">https://learn.kodekloud.com/user/courses/aws-solutions-architect-associate-certification</a></p><p>6- For free: AWS SAA preparation with Andrew Brown on youtube: <a href="https://www.youtube.com/watch?v=c3Cn4xYfxJY">https://www.youtube.com/watch?v=c3Cn4xYfxJY</a></p><p>About the exam: <a href="https://aws.amazon.com/fr/certification/certified-solutions-architect-associate/">https://aws.amazon.com/fr/certification/certified-solutions-architect-associate/</a></p><p>Happy Learning !</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b7aa41181640" width="1" height="1" alt=""><hr><p><a href="https://awstip.com/how-did-i-ace-aws-solution-architect-associate-certification-b7aa41181640">How did I pass the AWS Solution Architect Associate certification?</a> was originally published in <a href="https://awstip.com/">AWS Tip</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to configure Site to Site VPN on AWS]]></title>
            <link>https://awstip.com/how-to-configure-aws-site-to-site-vpn-on-aws-0ae03d5e8ec2?source=rss-da53ab4aa01c------2</link>
            <guid isPermaLink="false">https://medium.com/p/0ae03d5e8ec2</guid>
            <category><![CDATA[aws-vpc]]></category>
            <category><![CDATA[aws-network-firewall]]></category>
            <category><![CDATA[aws-site-to-site-vpn]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[aws-vpn]]></category>
            <dc:creator><![CDATA[Francia Rasolomampionona]]></dc:creator>
            <pubDate>Mon, 27 Apr 2026 10:54:30 GMT</pubDate>
            <atom:updated>2026-07-04T06:03:10.309Z</atom:updated>
            <content:encoded><![CDATA[<p>Site to Site VPN is needed for two main things: interconnection with on-premises environment, and remote access via private-encrypted traffic.</p><h4>Step 1: create a customer gateway</h4><p>Search for VPC then select Virtual Private Network(VPN), after that click on customer gateways.</p><p>Fill with the required information :</p><p>Name:<br>BGP ASN if it’s dynamic or use BGP:<br>IP Address of the customer firewall (on-prem):<br>Certificat ARN if applied:<br>Device name:<br>Tag:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l9cKr2VSQyI5T4ufBmuM0w.png" /></figure><p>Command line: aws ec2 create-customer-gateway — ipv6-address 2001:0db8:85a3:0000:0000:8a2e:0370:7334 — bgp-asn 65051 — type ipsec.1 — region us-west-1</p><h4>Step 2: Create a target gateway:</h4><p>This step is about creating Virtual Private Gateway (on AWS side) and attaching it to the VPC.<br>Add Name, Select ASN, and assign tag if needed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7QCoccOV3uUEcBHaRK-iCw.png" /></figure><p>After creation, select the VPG, Action, choose attach to VPC.</p><h4>Step 3: Configure routing</h4><p>You can enable route propagation for your route table to automatically propagate Site-to-Site VPN routes.</p><p>For static routing, the static IP prefixes that you specify for your VPN configuration are propagated to the route table when the status of the VPN connection is up.Similarly, for dynamic routing, the BGP-advertised routes from your customer gateway are propagated to the route table when the status of the VPN connection is up.</p><p>To enable route propagation: go to navigation pane, choose Route tables, select the route table that’s associate with the subnet, open the Route propagation tab, choose edit route propagation. Then select the vpg that you created, check enable, and save.</p><h4><strong>Step 4: Update your security group</strong></h4><p>To allow access to instances in your VPC from your network, you must update your security group rules to enable inbound SSH, RDP, and ICMP access.</p><p>Go to security Groups, select the relevant SG, edit inbound rules and add rules that allow the needed network flow.</p><h4><strong>Step 5: Create a VPN connection</strong></h4><p>Add all details: Name, VPG, Customer gateway, Routing options (Static or dynamic), PSK, CIDR, Tunnel options (For static, it has phase1 and phase2 configuration), Tags.<br>With AWS we have high availability features with 2 tunnels</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eA_5Pgl_2mo-cGdnfKy8wA.png" /></figure><p>Now you can configure the on-premise device to match all configurations.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0ae03d5e8ec2" width="1" height="1" alt=""><hr><p><a href="https://awstip.com/how-to-configure-aws-site-to-site-vpn-on-aws-0ae03d5e8ec2">How to configure Site to Site VPN on AWS</a> was originally published in <a href="https://awstip.com/">AWS Tip</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AWS S3 Files, new feature for AWS S3]]></title>
            <link>https://medium.com/@francia.rasolomampionona/aws-s3-files-new-feature-for-aws-s3-0fc431d32783?source=rss-da53ab4aa01c------2</link>
            <guid isPermaLink="false">https://medium.com/p/0fc431d32783</guid>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[aws-s3]]></category>
            <category><![CDATA[aws-s3-files]]></category>
            <dc:creator><![CDATA[Francia Rasolomampionona]]></dc:creator>
            <pubDate>Thu, 23 Apr 2026 17:46:35 GMT</pubDate>
            <atom:updated>2026-04-23T17:46:35.975Z</atom:updated>
            <content:encoded><![CDATA[<p>Big news from <a href="https://www.linkedin.com/company/amazon-web-services/">Amazon Web Services (AWS)</a>: Introducing Amazon S3 Files (Apr 7, 2026)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*CzfuToDR1F8z8g37" /></figure><p>For years, teams have had to choose between object storage and file systems, or build complex pipelines to bridge the gap. That’s changing.<br>With S3 Files, Amazon S3 becomes a fully-featured, high-performance file system, without moving your data.</p><p><strong>What this means:</strong><br>• Access S3 buckets like a shared file system<br>• Full file system semantics + low-latency performance<br>• No data duplication or staging needed<br>• Works with existing tools, no code changes required</p><p><strong>Why it matters:</strong><br>• Run file-based applications directly on S3<br>• Enable AI agents to persist memory and share state<br>• Simplify ML data prep, no more copying datasets<br>• Let teams collaborate using familiar file-based workflows</p><p>This is a major step toward unifying storage and compute,removing friction for developers, data engineers, and ML teams alike.</p><p>Announcement link: <a href="https://aws.amazon.com/fr/about-aws/whats-new/2026/04/amazon-s3-files/">https://aws.amazon.com/fr/about-aws/whats-new/2026/04/amazon-s3-files/</a></p><p>Documentation link: <a href="https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-files.html">https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-files.html</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0fc431d32783" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AWS DevOps Agent Overview]]></title>
            <link>https://medium.com/@francia.rasolomampionona/aws-devops-agent-overview-75709d2284b5?source=rss-da53ab4aa01c------2</link>
            <guid isPermaLink="false">https://medium.com/p/75709d2284b5</guid>
            <category><![CDATA[aws-devops-agent]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Francia Rasolomampionona]]></dc:creator>
            <pubDate>Thu, 23 Apr 2026 17:41:30 GMT</pubDate>
            <atom:updated>2026-04-23T17:41:30.844Z</atom:updated>
            <content:encoded><![CDATA[<p>AWS DevOps Agent just hit General availability on Mar 31, 2026! An always-on AI teammate for incident response, infrastructure management , and SRE tasks across AWS, multicloud, and on-prem as AWS stated.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ZflQhE545LWF8Kf_" /></figure><p>It works by learning your resources and their relationships, correlating telemetry, code, and deployment data, and then guiding or automating the response to operational issues.</p><h4>Main capabilities:</h4><ul><li>Automated incident investigation when alerts or tickets come in;</li><li>Natural-language chat for querying infrastructure and steering investigations;</li><li>Detailed mitigation plans with validation and rollback guidance;</li><li>Incident coordination through tools like Slack and ServiceNow;</li><li>AWS Support case creation with investigation context attached.</li></ul><h4><strong>Integration with third-party:</strong></h4><p>It can be integrated with:</p><ul><li>GitHub/Gitlab</li><li>Datadog/Dynatrace</li><li>Grafana/New Relic/ Splunk</li><li>Slack/PagerDuty/Service Now</li><li>Azure Cloud/Azure DevOps</li><li>MCP Server</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*56lIRdaXmpJL6sf-c3Sq6Q.png" /></figure><p>What I really about this is that it shows also the topology of all your AWS services.</p><p>Documentation link: <a href="https://docs.aws.amazon.com/devopsagent/">https://docs.aws.amazon.com/devopsagent/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=75709d2284b5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Secure Cold Backup Architecture on AWS]]></title>
            <link>https://medium.com/@francia.rasolomampionona/building-a-secure-cold-backup-architecture-on-aws-f5543957eb28?source=rss-da53ab4aa01c------2</link>
            <guid isPermaLink="false">https://medium.com/p/f5543957eb28</guid>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[aws-s3]]></category>
            <dc:creator><![CDATA[Francia Rasolomampionona]]></dc:creator>
            <pubDate>Mon, 30 Mar 2026 13:56:46 GMT</pubDate>
            <atom:updated>2026-07-04T06:02:47.860Z</atom:updated>
            <content:encoded><![CDATA[<p>Data is growing faster than ever, but not all data needs to stay “hot.” For long-term retention, compliance, and disaster recovery, a <strong>cold backup strategy</strong> is essential. In this article, we’ll break down a robust hybrid architecture that moves on-premises data into cost-effective archival storage on AWS, securely, efficiently, and with a clear restore path.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JrxKcj1fbHgM3xZzvAi8ww.png" /></figure><h3><strong>Architecture Overview</strong></h3><p>This solution connects an on-premises file storage system (NAS/SAN) to AWS using a managed transfer service, then transitions data through multiple storage tiers for cost optimization.</p><h4>Key building blocks:</h4><ul><li>On-premises <strong>file server + NAS/SAN</strong></li><li><strong>AWS DataSync</strong> (Agent + Service)</li><li><strong>Amazon S3</strong> (Standard, Glacier tiers)</li><li>Security &amp; monitoring: <strong>AWS IAM</strong>, <strong>AWS KMS</strong>, <strong>Amazon CloudWatch</strong>, <strong>AWS CloudTrail</strong></li></ul><h3>Step 1: Data Ingestion from On-Premises</h3><p>The journey starts inside your data center:</p><ul><li>Files live on a NAS/SAN and are exposed via <strong>NFS/SMB</strong></li><li>An <strong>AWS DataSync Agent (VM)</strong> is deployed locally</li><li>Data is transferred securely over:</li><li>Internet (TLS encryption)</li><li>VPN or Direct Connect</li></ul><h4>Why DataSync?</h4><ul><li>Incremental transfers (only changed data moves)</li><li>Built-in encryption and integrity checks</li><li>No need to build custom sync scripts</li></ul><h3>Step 2: Landing Zone in Amazon S3</h3><p>Incoming data lands in an <strong>Amazon S3 Standard bucket</strong> (staging zone).</p><p>This layer serves as:</p><ul><li>A buffer for ingestion</li><li>A validation checkpoint</li><li>A trigger point for lifecycle policies</li></ul><p>Think of this as your “transit hub” before archival.</p><h3>Step 3: Lifecycle-Based Archival</h3><p>Once data is safely in S3, lifecycle policies automatically move it to cheaper storage tiers:</p><h4>Storage tiers used:</h4><ul><li><strong>S3 Standard → S3 Glacier Flexible Retrieval</strong></li></ul><p>Transition after ~30 days</p><p>Retrieval time: minutes to hours</p><ul><li><strong>S3 Glacier Flexible Retrieval → S3 Glacier Deep Archive</strong></li></ul><p>For long-term retention</p><p>Retrieval time: up to 48 hours</p><p>Minimum storage duration: 180 days</p><p>This tiered approach balances:</p><ul><li>Cost optimization</li><li>Retrieval flexibility</li><li>Durability (11 9’s)</li></ul><h3>Step 4: Security &amp; Compliance</h3><p>Security is baked into every layer:</p><ul><li><strong>AWS IAM: </strong>Fine-grained access control</li><li><strong>AWS KMS: </strong>AES-256 encryption for data at rest</li><li><strong>Amazon CloudWatch: </strong>Metrics, alerts, and operational visibility</li><li><strong>AWS CloudTrail: </strong>Full audit trail of API activity</li><li>S3 Inventory + SNS notifications for reporting and automation</li></ul><p>Result: end-to-end encrypted, auditable, and compliant storage.</p><h3>Step 5: Restore Workflow</h3><p>Cold storage is only useful if you can restore data when needed.</p><h4>Restore process:</h4><ol><li>Data is retrieved from <strong>Glacier / Deep Archive</strong></li><li>Temporarily restored into <strong>S3 Standard</strong></li><li>Accessed via:</li></ol><ul><li><strong>Amazon VPC</strong> Endpoint (Gateway S3)</li><li>Secure internal network path</li></ul><h4>Restore timelines:</h4><ul><li>Glacier Flexible Retrieval: minutes to hours</li><li>Deep Archive (bulk): up to 48 hours</li></ul><p>This design ensures you don’t pay for hot storage unless you actually need the data.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f5543957eb28" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tier 3 Application Architecture]]></title>
            <link>https://medium.com/@francia.rasolomampionona/tier-3-application-architecture-2cc610fc9cb0?source=rss-da53ab4aa01c------2</link>
            <guid isPermaLink="false">https://medium.com/p/2cc610fc9cb0</guid>
            <category><![CDATA[tier3]]></category>
            <category><![CDATA[aws-certification]]></category>
            <category><![CDATA[aws-ec2]]></category>
            <category><![CDATA[aws-backup]]></category>
            <category><![CDATA[aws-cloudwatch]]></category>
            <dc:creator><![CDATA[Francia Rasolomampionona]]></dc:creator>
            <pubDate>Wed, 25 Mar 2026 06:14:15 GMT</pubDate>
            <atom:updated>2026-07-04T06:02:20.102Z</atom:updated>
            <content:encoded><![CDATA[<p>Building a Secure 3-Tier AWS Architecture (Web, App, Database)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*d6eq5dFrMZyagINwTFiS5g.png" /></figure><h3>1. Context</h3><p>In modern cloud environments, designing a <strong>secure, scalable, and maintainable architecture</strong> is essential. One of the most common and reliable patterns is the <strong>3-tier architecture</strong>, which separates an application into three layers:</p><ul><li><strong>Web Tier (Frontend)</strong></li><li><strong>Application Tier (Backend logic)</strong></li><li><strong>Database Tier (Data storage)</strong></li></ul><p>This separation improves:</p><ul><li>Security</li><li>Scalability</li><li>Maintainability</li></ul><p>In this setup, everything is deployed inside a <strong>Virtual Private Cloud (VPC)</strong> with CIDR 10.0.0.0/16, ensuring network isolation and control.</p><h3>Architecture Overview</h3><p>This architecture includes:</p><ul><li><strong>Internet Gateway</strong> for public access</li><li><strong>Public Subnet</strong> for Web &amp; App servers</li><li><strong>Private Subnet</strong> for Database</li><li><strong>EC2 instances</strong> for each tier (For this architecture, I chose EC2+windows server+SQLentreprise, but you can also directly use AWS RDS service)</li><li>Monitoring and backup services</li></ul><p>Traffic flow:<br>Internet → Web Server → App Server → Database</p><h3>2. Public vs Private Subnets + Security Groups</h3><h3>Public Subnet (Web + App Tier)</h3><p><strong>Subnet:</strong> 10.0.1.0/24<br>This subnet is connected to the <strong>Internet Gateway</strong>, meaning resources inside it can be accessed from the internet.</p><h3>Web EC2 (Web Tier)</h3><ul><li>Handles incoming user requests</li><li>Security Group:</li><li>Allow <strong>HTTPS (443)</strong> from internet</li><li>RDP (3389) restricted by IP (good practice)</li></ul><h3>App EC2 (Application Tier)</h3><ul><li>Processes business logic</li><li>Not directly exposed to the internet</li><li>Security Group:</li><li>Only allows traffic from <strong>Web Security Group</strong></li></ul><p><strong>Best practice:</strong> Even in a public subnet, restrict access using Security Groups.</p><h3>Private Subnet (Database Tier)</h3><p><strong>Subnet:</strong> 10.0.3.0/24</p><ul><li>No direct internet access</li><li>Fully isolated</li></ul><h3>DB EC2 (Database Tier)</h3><ul><li>Stores sensitive data</li></ul><p>Security Group:</p><ul><li>Only allows DB port (e.g., 3306) from App SG</li><li>No public access</li></ul><p>This is critical for <strong>data protection</strong> and prevents direct attacks.</p><h3>What are Security Groups (SG)?</h3><p>Security Groups act like <strong>virtual firewalls</strong>:</p><ul><li>Control <strong>who can access what</strong></li><li>Work at <strong>instance level</strong></li><li>Are <strong>stateful</strong> (responses are automatically allowed)</li></ul><h3>3. Additional Services (Monitoring &amp; Backup)</h3><p>To make the architecture production-ready, we add supporting AWS services.</p><h3>Cloud Monitoring (CloudWatch)</h3><p>Used for:</p><ul><li>Metrics (CPU, memory, etc.)</li><li>Logs (application/system logs)</li><li>Alarms (threshold alerts)</li></ul><h3>Example:</h3><ul><li>CPU &gt; 80% → Trigger alert</li><li>Instance down → Send notification</li></ul><h3>Notifications (SNS)</h3><ul><li>Sends <strong>email alerts</strong></li><li>Integrated with monitoring</li></ul><p>Example:</p><ul><li>CloudWatch alarm → SNS → Email notification</li></ul><h3>Backup Strategy (AWS Backup)</h3><ul><li>Automates backups of EC2 (EBS snapshots)</li><li>Retention: <strong>30–90 days</strong></li></ul><h3>Benefits:</h3><ul><li>Data recovery</li><li>Protection against failures</li><li>Compliance</li></ul><h3>Key Strengths of This Architecture</h3><p>Strong security (private DB, SG rules)<br>Clear separation of concerns (3-tier design)<br>Scalable and production-ready<br>Monitoring + alerting included<br>Backup strategy implemented</p><h3>Final Thoughts</h3><p>This architecture is a <strong>solid foundation for real-world applications</strong>. It demonstrates:</p><ul><li>Proper network design (VPC, subnets)</li><li>Secure communication between tiers</li><li>Use of essential AWS services</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2cc610fc9cb0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Website hosting automation on AWS using CICD pipeline]]></title>
            <link>https://awstip.com/automate-a-website-hosting-on-aws-using-cicd-pipeline-467b094cd3e5?source=rss-da53ab4aa01c------2</link>
            <guid isPermaLink="false">https://medium.com/p/467b094cd3e5</guid>
            <category><![CDATA[aws-cloudfront]]></category>
            <category><![CDATA[aws-devops]]></category>
            <category><![CDATA[aws-codepipeline]]></category>
            <category><![CDATA[aws-s3]]></category>
            <dc:creator><![CDATA[Francia Rasolomampionona]]></dc:creator>
            <pubDate>Tue, 10 Mar 2026 17:28:31 GMT</pubDate>
            <atom:updated>2026-07-22T16:28:18.275Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong>ARCHITECTURE OF THE PROJECT</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/667/1*7FjndkPNUjhU-7O3DamYYQ.png" /></figure><p><strong>Step 1: AWS S3 configuration</strong></p><p>You can create a bucket</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/864/1*TqdAas88uXmQvyzz_AZwfA.png" /></figure><p>Enable “static website hosting” on properties</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/865/1*9R0Zi98cXkFLihd46xt7bw.png" /></figure><p>Upload all your files</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/867/1*TSXzteXssRauiBIWOF4KtA.png" /></figure><p>Leave all settings as default ( block public access)</p><p><strong>Step2: Cloudfront Configuration</strong></p><p>Create a distribution</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/869/1*4vwq4yQrRfTrLlJntr2LZA.png" /></figure><p>Choose your origin</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/853/1*H93FczeaUOym7vLrtHSkEw.png" /></figure><p>Confiure DNS and SSL certificate</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/874/1*bugrmaKZJDt9qQO-6X9QYQ.png" /></figure><p>Test the website accessibility via cloudfront</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/871/1*TVHmMtKsChg9r1zot8W9fA.png" /></figure><p><strong>Step 3: Configure the domain name</strong></p><p>Use a DNS record type CNAME to forward this cloudfront URL to your preferred URL</p><p><strong>Step 4: Configure CodePipeline</strong></p><p>Create a pipeline and connect it to Github OAuth, repository and branch.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/876/1*0jJfFElNPOdMO7OC9APdYQ.png" /></figure><p>Once done, make a change to your file and commit the changes, the pipeline on CodePipeline will be triggered automatically:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/778/1*gmZ_1aCMDaI4Hj-YX2vUZw.png" /></figure><p><strong>Step 4: Invalidate the cache</strong></p><p>As we are using Cloudfront, we should invalidate it to have the recent changes:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/860/1*PrmjqvtezKgDketO7fuo9w.png" /></figure><p><strong>Step 5: Test the result</strong></p><p>Now, we can visualize the change from the website</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/603/1*Ql8u5CZ2vGYd72T3RiPUZQ.png" /></figure><p>Please delete all ressources to avoid being billed: S3, Cloudfront, ACM, CodePipeline, Route53</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=467b094cd3e5" width="1" height="1" alt=""><hr><p><a href="https://awstip.com/automate-a-website-hosting-on-aws-using-cicd-pipeline-467b094cd3e5">Website hosting automation on AWS using CICD pipeline</a> was originally published in <a href="https://awstip.com/">AWS Tip</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Web application deployment within EC2 instance]]></title>
            <link>https://medium.com/@francia.rasolomampionona/how-to-create-an-ec2-instance-and-configure-nginx-on-it-for-your-web-application-bbf93af3a144?source=rss-da53ab4aa01c------2</link>
            <guid isPermaLink="false">https://medium.com/p/bbf93af3a144</guid>
            <category><![CDATA[aws-key-pair]]></category>
            <category><![CDATA[aws-security-group]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[aws-certification]]></category>
            <category><![CDATA[aws-ec2]]></category>
            <dc:creator><![CDATA[Francia Rasolomampionona]]></dc:creator>
            <pubDate>Tue, 17 Sep 2024 16:16:27 GMT</pubDate>
            <atom:updated>2026-07-22T16:28:50.968Z</atom:updated>
            <content:encoded><![CDATA[<h4>How to create an EC2 instance and configure nginx on it for web application</h4><p><strong>Step 1: We will create an AWS Key Pair:</strong></p><p>In order to access our EC2 via SSH, we need to have a Key Pair, the EC2 instance will have the public key, and we will need the private one.</p><p><em>Go to EC2- Network &amp; Security-Key Pairs, click on Create key pair:</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KeyDfnAW0leMqaU7dL1IHA.png" /></figure><p>Then enter a key pair name, choose the type and format:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/815/1*KD_z_LKNfuIwBKv2dX_-pw.png" /></figure><p><strong>Step 2: Create a security group that allow SSH and HTTP access from any network:</strong></p><p><em>Go to EC2- Network &amp; Security- Security Groups, then click ‘create security group’.</em></p><p>Configure the relevant inbound rules for SSH and HTTP:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BT0emb9lVlXOnmscrlzIkw.png" /></figure><p><strong>Step 3: Launch EC2 instance:</strong></p><p><em>Go to EC2- Instances- Instances, then click ‘Launch Instances’.</em></p><p>Enter the name and choose the OS:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/791/1*NOZORYLG3yRN8JQQkrFIuQ.png" /></figure><p>Choose the architecture and the instance type. Now we can assign the key pair that we have created to the EC2 instance:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/766/1*ihG7yIKDopMJgZT5eap-vg.png" /></figure><p>Configure the network setting as needed, or keep the default parameters.</p><p>Choose our previous security group to allow SSH/HTTP:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/789/1*16I71xvhf8buCw1AIOv05w.png" /></figure><p>Now, click ‘Launch instance’.</p><p><strong>Step 4: Access the EC2 instance via SSH</strong></p><p>Using our Key pair:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/675/1*bi313VMaeAa9gZobCp7jug.png" /></figure><p><strong>Step 5: Install nginx</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/983/1*T2qfYWpq0oSNT1BcwYK-HQ.png" /></figure><p>Check that the service nginx is running:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/984/1*NA0ZKs3eR6my_9vfaj0mdQ.png" /></figure><p>Access the nginx web server via HTTP protocol:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9ioxK1pN7Q91sQzP0A-U-A.png" /></figure><p><strong>Bonus: Delete the EC2 instance after the lab:</strong></p><p>Click on terminate (delete) instance to delete EC2 instance permanently:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sy2m_BzucNFB4CObuVBAxg.png" /></figure><p><strong>Now, you can repeat the steps and customize!</strong></p><p><strong>Thank you !</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bbf93af3a144" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>