<?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 Adekunle Adesanmi on Medium]]></title>
        <description><![CDATA[Stories by Adekunle Adesanmi on Medium]]></description>
        <link>https://medium.com/@kunleadesanmi?source=rss-56aafda8615b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Eu37UoB28QTIGm9Afeks4A.jpeg</url>
            <title>Stories by Adekunle Adesanmi on Medium</title>
            <link>https://medium.com/@kunleadesanmi?source=rss-56aafda8615b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 07:04:01 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kunleadesanmi/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[Clawdbot: Innovation Meets Reality — A Security Perspective]]></title>
            <link>https://medium.com/@kunleadesanmi/clawdbot-innovation-meets-reality-a-security-perspective-8a77f3c14a64?source=rss-56aafda8615b------2</link>
            <guid isPermaLink="false">https://medium.com/p/8a77f3c14a64</guid>
            <dc:creator><![CDATA[Adekunle Adesanmi]]></dc:creator>
            <pubDate>Sun, 01 Feb 2026 15:47:21 GMT</pubDate>
            <atom:updated>2026-02-02T06:31:07.590Z</atom:updated>
            <content:encoded><![CDATA[<h3>Clawdbot: Innovation Meets Reality — A Security Perspective</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/633/1*Mk_fhI8evVijE6zrxMUatg.png" /></figure><h3>The Viral Phenomenon</h3><p>If you’ve been on X lately, you’ve probably seen OpenClaw (formerly Clawdbot) explode across your timeline. The pitch is compelling: a personal AI assistant that lives in your messaging apps, manages your email, writes code, creates content, and executes tasks autonomously. With thousands of GitHub stars in days, it’s captured the imagination of developers worldwide.</p><p>The promise is seductive: no browser tabs, no copy-pasting, no context switching. Just message your AI, and it acts on your behalf across all your services.</p><p>But beneath the viral hype lies a more complex reality that every technologist should understand before deploying this tech.</p><h3>What Makes OpenClaw Different (And Why That Matters)</h3><p>OpenClaw isn’t just another ChatGPT wrapper. It’s fundamentally different in three critical ways:</p><p><strong>1. Persistent Access</strong> Unlike ChatGPT which you visit in a browser, OpenClaw runs 24/7 on infrastructure you control, with continuous access to your systems, files, and credentials.</p><p><strong>2. Real Execution Authority</strong> It doesn’t just suggest commands — it executes them. It can read your emails, send messages, commit code, manage cloud infrastructure, and interact with any service you’ve connected.</p><p><strong>3. Autonomous Operation</strong> It can act proactively without explicit prompts, monitor systems continuously, and make decisions based on incoming data from emails, webhooks, and scheduled tasks.</p><p>This combination creates something powerful but architecturally different from traditional software. It’s a long-running autonomous agent with delegated authority over your digital identity.</p><h3>Security Issues</h3><p>In late January 2026, security researcher Jamieson O’Reilly ran a routine internet scan and discovered:</p><ul><li><strong>Hundreds of exposed instances </strong>sitting completely exposed on the public internet.</li><li><strong>Zero authentication</strong> on several systems, allowing anyone to access administrative panels</li><li><strong>Full access to: </strong>API keys (Anthropic, OpenAI, etc.), OAuth tokens (Gmail, Slack, GitHub), Complete conversation histories, System configuration data</li></ul><h3>Real-World Demonstrations</h3><p><strong>The 5-Minute Hack:</strong> Matvey Kukuy, CEO of Archestra AI, demonstrated extracting private keys from a compromised OpenClaw instance via email prompt injection in under 5 minutes:</p><ol><li>Send an email with prompt injection</li><li>Wait for OpenClaw to check e-mail</li><li>Receive the private key from the hacked machine</li></ol><p><strong>The Supply Chain Attack:</strong> A security researcher uploaded a proof-of-concept poisoned skill to ClawdHub (OpenClaw skill marketplace):</p><ul><li>Artificially inflated download count to 4,000+, making it the “most popular” skill</li><li>Within 8 hours, many developers across 7 countries installed and executed it</li><li>Demonstrated complete lack of supply chain verification</li></ul><p><strong>The Root Access Incident:</strong> One exposed instance belonged to an AI software agency and was running with root privileges. An unauthenticated user could execute arbitrary commands on production systems with full administrative access.</p><h3>What Was Fixed</h3><p>The OpenClaw team released patches addressing:</p><p>✅ The proxy authentication bypass vulnerability<br> ✅ Localhost connection auto-authentication<br> ✅ Added moltbot security audit tool to detect common misconfigurations<br> ✅ Improved documentation on secure deployment</p><p>This fixed the immediate “exposed to internet” problem for new installations.</p><h3>What Remains Unfixed</h3><p>However, fundamental architectural issues persist:</p><p><strong>1. Plaintext Credential Storage</strong> API keys, OAuth tokens, and secrets are still stored unencrypted in local Markdown and JSON files.</p><p><strong>2. Supply Chain Vulnerability</strong> ClawdHub (the skill marketplace) has no code signing, verification, or vetting process. The demonstrated attack remains viable today.</p><p><strong>3. Prompt Injection</strong> As an agent that processes emails, documents, and web content, OpenClaw is fundamentally susceptible to prompt injection attacks. This is an architectural limitation, not a patchable bug.</p><p><strong>4. Existing Exposed Instances</strong> The fix only applies to new installations. The hundreds of already-deployed vulnerable instances remain exposed unless users manually update and reconfigure.</p><p><strong>5. Expertise Gap</strong> As Eric Schwake from Salt Security noted: “A significant gap exists between the consumer enthusiasm for OpenClaw’s one-click appeal and the technical expertise needed to operate a secure agentic gateway.”</p><h3>The Fundamental Trade-Off: Capability vs. Security</h3><p>Here’s the uncomfortable truth: many of OpenClaw’s security challenges aren’t bugs — they’re features.</p><p>For an AI agent to be genuinely useful, it needs:</p><ul><li>Broad access to your systems and data</li><li>Ability to execute commands autonomously</li><li>Persistent credentials to act on your behalf</li><li>Trust to process untrusted input (emails, documents)</li></ul><p>These requirements directly conflict with traditional security principles:</p><ul><li>Least privilege access</li><li>Air-gapped sensitive systems</li><li>Human approval for critical actions</li><li>Zero trust for external input</li></ul><p>This isn’t unique to OpenClaw — it’s a challenge facing the entire emerging category of autonomous AI agents.</p><h3>Expert Perspectives</h3><p><strong>Hudson Rock (Cybersecurity Research):</strong></p><blockquote><em>“Clawdbot represents the future of personal AI, but its security posture relies on an outdated model of endpoint trust. Without encryption-at-rest or containerization, the ‘Local-First’ AI revolution risks becoming a goldmine for the global cybercrime economy.”</em></blockquote><p><strong>Palo Alto Networks:</strong></p><blockquote><em>“Moltbot represents a ‘lethal trifecta’ of vulnerabilities: access to private data, exposure to untrusted content, and the ability to communicate externally.”</em></blockquote><p><strong>Eric Schwake, Salt Security:</strong></p><blockquote><em>“Many users unintentionally create a large visibility void by failing to track which corporate and personal tokens they’ve shared with the system.”</em></blockquote><h3>The Nuanced Reality</h3><p>This isn’t a simple “OpenClaw bad” story. The technology is genuinely innovative and represents an important direction for AI tooling. But we need honest conversations about the risks.</p><h3>What OpenClaw Does Well</h3><p>✅ <strong>Demonstrates the potential</strong> of autonomous AI agents<br> ✅ <strong>Open source</strong> approach enables community scrutiny and improvement<br> ✅ <strong>Compelling user experience</strong> that shows what’s possible<br> ✅ <strong>Active community</strong> building skills and extensions</p><h3>Where Serious Concerns Remain</h3><p>⚠️ <strong>Security model</strong> relies on user expertise most users don’t have<br> ⚠️ <strong>Credential management</strong> stores secrets in plaintext<br> ⚠️ <strong>Supply chain</strong> lacks code signing or verification<br> ⚠️ <strong>Architectural limitations</strong> make some attacks unpatchable<br> ⚠️ <strong>User expectations</strong> don’t match security requirements</p><h3>Practical Guidance: Should You Use OpenClaw?</h3><p>The answer depends entirely on your risk tolerance and use case.</p><h3>❌ Do NOT Use For:</h3><ul><li>Production systems or work infrastructure</li><li>Managing corporate accounts or data</li><li>Anything involving compliance requirements (HIPAA, SOC 2, PCI-DSS)</li><li>Primary personal accounts (Gmail, GitHub, banking)</li><li>Any data you cannot afford to lose or have exposed</li><li>Enterprise deployments without dedicated security engineering</li></ul><h3>✅ Potentially Appropriate For:</h3><ul><li>Personal experimentation and learning</li><li>Dedicated secondary accounts created specifically for testing</li><li>Isolated development environments</li><li>Security research projects</li><li>Understanding emerging AI agent architectures</li><li>Proof-of-concept demonstrations</li></ul><h3>🔒 If You Choose to Deploy, Minimum Requirements:</h3><ol><li><strong>Isolated Infrastructure</strong></li></ol><ul><li>Dedicated VPS or cloud instance (never your primary machine)</li><li>Virtual machine with network isolation</li><li>Containerized deployment with hardening</li></ul><p><strong>2. Credential Isolation</strong></p><ul><li>Use credential broker (Composio, AWS Secrets Manager)</li><li>Never store plaintext API keys in files</li><li>Dedicated secondary accounts only (work-assistant@gmail.com, not your actual Gmail)</li></ul><p><strong>3. Network Hardening</strong></p><ul><li>Private networking (Tailscale, VPC with no public IPs)</li><li>Firewall rules denying all inbound traffic</li><li>VPN-only access</li></ul><p><strong>4. Supply Chain Verification</strong></p><ul><li>Manually review all skill code before installation</li><li>Never auto-install from ClawdHub without inspection</li><li>Maintain an allowlist of verified skills</li></ul><p><strong>5. Operational Security</strong></p><ul><li>Run these regularly</li></ul><pre>openclaw security audit<br>openclaw security audit --deep<br>openclaw security audit --fix</pre><ul><li>Monitor for unexpected behavior</li><li>Maintain audit logs</li><li>Have incident response procedures</li><li>Regular backups</li></ul><p><strong>6. Accept the Risk</strong></p><ul><li>Assume everything connected may be compromised</li><li>Plan for credential rotation</li><li>Limit blast radius</li><li>Never connect critical systems</li></ul><h3>The Bigger Picture: What This Means for AI Agents</h3><p>OpenClaw’s security challenges aren’t unique — they’re indicative of broader issues the industry must address as we move toward autonomous AI agents.</p><p><strong>Key Questions We Need to Answer:</strong></p><ol><li><strong>How do we grant AI agents sufficient capability without creating unacceptable risk?</strong></li><li><strong>What are the right authentication/authorization models for agents acting on our behalf?</strong></li><li><strong>How do we validate and trust third-party AI agent components (skills, plugins, tools)?</strong></li><li><strong>What’s the appropriate division of responsibility between developers, operators, and users?</strong></li><li><strong>How do we build agents that are both useful and auditable?</strong></li></ol><p>These are hard problems without clear answers yet.</p><h3>Recommendations for Different Stakeholders</h3><h3>For Individual Developers:</h3><ul><li>Treat OpenClaw as a learning tool, not production software</li><li>Use dedicated test accounts and isolated infrastructure</li><li>Study the security architecture to understand agent security challenges</li><li>Contribute to improving the ecosystem (code review, security audits)</li><li>Share knowledge about secure deployment patterns</li></ul><h3>For Engineering Teams:</h3><ul><li>Block production deployments until security posture improves</li><li>If experimental deployment is approved: isolated environment, secondary accounts only, comprehensive monitoring</li><li>Use this as a case study for AI agent security training</li><li>Develop internal guidelines for evaluating AI agent tools</li></ul><h3>For Security Professionals:</h3><ul><li>Add OpenClaw instances to vulnerability scanning (Shodan searches for exposed instances)</li><li>Develop threat models for AI agent architectures</li><li>Contribute security guidance to the open-source community</li><li>Research credential isolation patterns for agents</li></ul><h3>For the OpenClaw Community:</h3><ul><li>Prioritize security over feature velocity</li><li>Implement credential encryption at rest</li><li>Add code signing to ClawdHub</li><li>Create tiered security profiles (personal, professional, enterprise)</li><li>Build better defaults (secure by default, not secure by configuration)</li></ul><h3>Conclusion: Innovation with Eyes Open</h3><p>OpenClaw represents a fascinating glimpse into the future of AI-human collaboration. The technology is genuinely innovative, the team is responsive, and the potential is enormous.</p><p>But potential doesn’t equal readiness.</p><p>The current security posture — even after recent fixes — remains unsuitable for production use, enterprise deployment, or management of sensitive data. The fundamental architecture trades security for capability in ways that cannot be easily patched.</p><p>This isn’t a reason to dismiss the technology entirely. It’s a reason to engage with it honestly, deploy it responsibly, and push for improvements that make autonomous AI agents both powerful and safe.</p><p>The future of AI agents is coming whether we’re ready or not. Projects like OpenClaw are showing us what’s possible — and what we need to solve before that future arrives.</p><p><strong>The question isn’t whether to innovate with AI agents. It’s how to do so without creating the next generation of security disasters.</strong></p><p><em>What are your thoughts on autonomous AI agents? Have you experimented with OpenClaw</em> <em>or similar tools? What security measures do you think are essential for this technology to reach production readiness?</em></p><p><em>I’d love to hear from security professionals, AI researchers, and developers working in this space. Let’s have an honest conversation about building the future responsibly.</em></p><h3>Resources &amp; Further Reading</h3><p><strong>Official Documentation:</strong></p><ul><li>OpenClaw Docs: <a href="https://docs.openclaw.ai/">https://docs.openclaw.ai/</a></li><li>Security Guide: <a href="https://docs.openclaw.ai/gateway/security">https://docs.openclaw.ai/gateway/security</a></li></ul><p><strong>Security Research:</strong></p><ul><li>Jamieson O’Reilly’s disclosures: <a href="https://x.com/theonejvo/status/2015401219746128322">https://twitter.com/theonejvo</a></li><li>Composio Security Analysis: <a href="https://composio.dev/blog/secure-openclaw-moltbot-clawdbot-setup">https://composio.dev/blog/secure-moltbot-clawdbot-setup-composio</a></li><li>SOCRadar Analysis: <a href="https://socradar.io/blog/clawdbot-is-it-safe/">https://socradar.io/blog/clawdbot-is-it-safe/</a></li></ul><p><strong>Community:</strong></p><ul><li>GitHub: <a href="https://github.com/openclaw/openclaw">https://github.com/openclaw/openclaw</a></li><li>Discord: <a href="https://discord.com/invite/moltbot">https://discord.com/invite/moltbot</a></li></ul><p>#AI #Cybersecurity #AIAgents #Moltbot #Clawdbot #OpenClaw #TechSecurity #ResponsibleAI #DevSecOps #CloudSecurity</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8a77f3c14a64" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My Cloud Journey — From Aws Cloudformation to Terraform]]></title>
            <link>https://awstip.com/my-cloud-journey-terraform-42616761d0bb?source=rss-56aafda8615b------2</link>
            <guid isPermaLink="false">https://medium.com/p/42616761d0bb</guid>
            <category><![CDATA[iac]]></category>
            <category><![CDATA[terraform]]></category>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Adekunle Adesanmi]]></dc:creator>
            <pubDate>Fri, 16 Aug 2024 14:21:24 GMT</pubDate>
            <atom:updated>2024-08-22T15:11:42.874Z</atom:updated>
            <content:encoded><![CDATA[<h3>My Cloud Journey — From Aws CloudFormation to Terraform</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/748/1*E5algfmzpxZV3Nd9WVYU8Q.png" /></figure><p>Infrastructure as Code (IaC) is transforming cloud computing and DevOps. By enabling automated provisioning, configuration, and management of infrastructure through code, IaC empowers teams to <strong>streamline their workflows</strong> and <strong>reduce human error</strong>. Traditionally, setting up servers and networking involved manual processes that were often time-consuming and prone to inconsistencies. With IaC, teams can define their infrastructure using code, allowing for <strong>version control</strong>, <strong>reproducibility</strong>, and <strong>easier collaboration</strong> across development and operations.</p><p>As organizations embrace IaC, they are not only transforming how they manage resources but also fostering a mindset of <strong>innovation and agility</strong>. This evolution is crucial in today’s fast-paced technological landscape, where the ability to <strong>quickly adapt</strong> can be the difference between success and failure. In essence, Infrastructure as Code is more than just a trend; it is a foundational shift that is defining the future of cloud computing and DevOps practices.</p><p>I have been using AWS CloudFormation to deploy cloud infrastructures for some time, but I am now switching to Terraform because of its numerous advantages.</p><h3>Benefits of Terraform</h3><h4><strong>1. Flexibility</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/571/1*N09zS1rqiXH9gCZjEbyXYw.png" /></figure><p>Terraform offers a level of <strong>flexibility and control</strong> that I find particularly appealing. Unlike AWS CloudFormation, which is tightly coupled with the AWS ecosystem, Terraform provides a multi-cloud capability that will allow me to manage resources across various providers like Azure, Google Cloud, and even on-premises solutions. This flexibility is crucial in today’s diverse cloud landscape, where organizations often adopt a <strong>hybrid</strong> or <strong>multi-cloud</strong> strategy to avoid vendor lock-in and to leverage the best services from each provider.</p><h4><strong>2. State Management</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/505/1*mX-zv3QLeSmPb36bwLKgdw.png" /></figure><p>Another significant advantage of Terraform is its state management. With its state files, Terraform keeps track of the resources it manages, allowing for efficient updates and changes. This means I can confidently modify my infrastructure without worrying about disrupting existing services. This can also be managed remotely, enabling collaboration across teams and ensuring that everyone is working with the most up-to-date information. Remote state management helps mitigate issues that can arise from state file mismatches, particularly in larger or distributed teams. By utilizing backends like S3, Azure Blob Storage, or Terraform Cloud, I can securely store my state files and control access, which further enhances the reliability of my infrastructure.</p><h4><strong>3. Terraform Community</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/687/1*we8GVb6mq8L6mN-aGZiVhg.png" /></figure><p>The Terraform community is vibrant and continually growing, providing a wealth of modules and examples that can accelerate my development process. The <strong>Terraform Registry </strong>is a treasure trove of reusable code, enabling me to implement best practices and industry standards without starting from scratch. This not only saves time but also enhances the quality and reliability of my infrastructure deployments.</p><h4>4. Declarative Language</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/628/1*52ck2W6RMKD2ZsVgBmjiUg.png" /></figure><p>Another aspect that stands out is Terraform’s declarative language, HashiCorp Configuration Language (HCL). HCL is designed to be both human-readable and machine-friendly, making it easier for team members to <strong>collaborate</strong> on infrastructure code. The clear syntax reduces the learning curve, allowing new team members to onboard quickly and contribute effectively.</p><h4>5. Immutable Deployments</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/318/1*qWiGp-MmZP_EPDQY2U1oMw.png" /></figure><p>With Terraform, changes to the infrastructure are made by modifying the code rather than altering existing resources. When changes are required, the code is updated, and Terraform compares the<strong> desired state</strong> with the <strong>current state</strong> to determine what changes are needed. This results in creating new resources or updating existing ones, ensuring that the infrastructure is always recreated from scratch based on the latest code.</p><h4>6. Integration and Extensibility</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/326/1*u0sMHwtZ0CsQ1jwG2ImbkA.png" /></figure><p>Terraform <strong>integrates</strong> with popular DevOps and CI/CD tools, enabling seamless integration of infrastructure changes into development pipelines. Automatic triggering of Terraform workflows based on code changes enhances<strong> agility</strong> and minimizes manual intervention.</p><p>As I transition to Terraform, I am particularly excited about the potential for integrating it with CI/CD pipelines. <strong>Automation</strong> is at the heart of DevOps, and Terraform’s ability to work seamlessly with tools like Jenkins, GitLab CI, and GitHub Actions means I can implement infrastructure changes in a more streamlined and automated manner. This integration will enhance my workflow, allowing for quicker iterations and more reliable deployments.</p><h3>The Terraform Workflow</h3><p>The Terraform workflow consists of several key commands that guide you through the process of managing your infrastructure:</p><ul><li><em>terraform init</em>: Initializes a Terraform working directory, downloading necessary provider plugins.</li><li><em>terraform plan</em>: Creates an execution plan, showing what actions Terraform will take to reach the desired state.</li><li><em>terraform apply</em>: Executes the plan, making the necessary changes to your infrastructure.</li><li><em>terraform show</em>: Displays the current state of your infrastructure.</li><li><em>terraform destroy</em>: Tears down the infrastructure defined in your Terraform configuration.</li></ul><p>Let’s take a look at Terraform’s core concepts and best practices.</p><h3>Key Concepts in Terraform</h3><ul><li>Provider Configuration: Terraform uses providers as plugins to interact with various cloud platforms and services. These providers are responsible for understanding API interactions and exposing resources that Terraform can manage.</li><li>Resource Management: Resources are the building blocks of your infrastructure. Terraform allows you to define, provision, and manage these resources across multiple cloud providers and services.</li><li>State Management: Terraform maintains a state file that keeps track of the current state of your infrastructure. This state is crucial for Terraform to determine what changes need to be made to reach the desired configuration.</li></ul><h3>Best Practices for Terraform</h3><p>To maximize the benefits of Terraform and ensure smooth operations, consider these best practices:</p><h4>1. Use Modules for Reusability</h4><p>Modules in Terraform promote the DRY (Don’t Repeat Yourself) principle. By encapsulating groups of resources into reusable modules, you can significantly reduce code duplication and improve maintainability.</p><h4>2. Implement a Consistent Folder Structure</h4><p>Organize your Terraform projects with a clear and consistent folder structure. A common approach is to have a root folder containing modules, with each module having subdirectories for <a href="http://main.tf/">main.tf</a>, <a href="http://variables.tf/">variables.tf</a>, and <a href="http://outputs.tf/">outputs.tf</a> files.</p><h4>3. Separate Environments</h4><p>Keep your production and development environments separate. Each environment should have its own directory, typically at the same level as your modules directory, containing environment-specific configurations.</p><h4>4. Version Control Your Terraform Code</h4><p>Store your Terraform configurations in a version control system like Git. This practice enables collaboration, tracks changes over time, and facilitates rollbacks if needed.</p><h4>5. Use Remote State Storage</h4><p>Store your Terraform state files remotely (e.g., in an S3 bucket) rather than locally. This approach improves collaboration and security, especially in team environments.</p><p>In summary, while AWS CloudFormation has served me well, the switch to Terraform represents a strategic move towards greater flexibility, community support, and automation capabilities. I am eager to explore the full potential of Infrastructure as Code with Terraform and to see how it can further improve my cloud infrastructure management.</p><p>In the coming weeks, I plan to dive deep into Terraform’s features, experimenting with how to manage infrastructure more efficiently. I aim to document my discoveries and share insights that may help others in their transition or day-to-day use of Terraform.</p><p>Stay tuned as I explore the possibilities that Terraform holds and gain insights into scaling infrastructure seamlessly in the cloud.</p><p>You can connect with me on <a href="https://www.linkedin.com/in/adekunle-adesanmi/">LinkedIn</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=42616761d0bb" width="1" height="1" alt=""><hr><p><a href="https://awstip.com/my-cloud-journey-terraform-42616761d0bb">My Cloud Journey — From Aws Cloudformation to Terraform</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[My Cloud Journey — Week 6 Part 3 | Auto Scaling Group deployment with AWSCloudFormation]]></title>
            <link>https://medium.com/@kunleadesanmi/my-cloud-journey-week-6-part-3-auto-scaling-group-deployment-with-awscloudformation-c0b9aedb1f1c?source=rss-56aafda8615b------2</link>
            <guid isPermaLink="false">https://medium.com/p/c0b9aedb1f1c</guid>
            <category><![CDATA[cloud-engineering]]></category>
            <category><![CDATA[autoscaling]]></category>
            <category><![CDATA[auto-scaling-groups]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Adekunle Adesanmi]]></dc:creator>
            <pubDate>Fri, 07 Jun 2024 14:30:06 GMT</pubDate>
            <atom:updated>2024-08-18T14:20:42.159Z</atom:updated>
            <content:encoded><![CDATA[<h3>My Cloud Journey — Week 6 | Advanced AWS — Part 3 | Auto Scaling Group deployment with CloudFormation</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/431/1*p7UmYeOBxRFsKy6V0YRaPA.png" /></figure><p>In this task, the goal was to create a Virtual Private Cloud (VPC) with public and private subnets in two Availability Zones (AZs), an Internet Gateway, routing tables, and an Auto Scaling group for the web servers. The VPC structure is the same as the one in my <a href="https://medium.com/@kunleadesanmi/my-cloud-journey-week-6-advanced-aws-part-2-application-load-balancer-deployment-using-6a7e61902c73">previous post</a> on Application Load Balancer, so I was able to reuse some of the code from it.</p><p>Here’s the CloudFormation template that I created for the deployment:</p><pre>AWSTemplateFormatVersion: &#39;2010-09-09&#39;<br>Description: &#39;CloudFormation for AutoScalingGroup&#39;<br><br>Resources:<br>  # My VPC<br>  MyVPC:<br>    Type: &#39;AWS::EC2::VPC&#39;<br>    Properties:<br>      CidrBlock: &#39;172.16.0.0/16&#39;<br>      EnableDnsSupport: true<br>      EnableDnsHostnames: true<br>      Tags:<br>        - Key: Name<br>          Value: MyVPC<br><br>  # Public Subnet in AZ 1<br>  PublicSubnet1A:<br>    Type: &#39;AWS::EC2::Subnet&#39;<br>    Properties:<br>      VpcId: !Ref MyVPC<br>      CidrBlock: &#39;172.16.1.0/24&#39;<br>      AvailabilityZone: !Select [0, !GetAZs &#39;&#39;]<br>      MapPublicIpOnLaunch: true<br>      Tags:<br>        - Key: Name<br>          Value: PublicSubnet1A<br><br>  # App Private Subnet in AZ 1<br>  AppPrivateSubnet1A:<br>    Type: &#39;AWS::EC2::Subnet&#39;<br>    Properties:<br>      VpcId: !Ref MyVPC<br>      CidrBlock: &#39;172.16.2.0/24&#39;<br>      AvailabilityZone: !Select [0, !GetAZs &#39;&#39;]<br>      Tags:<br>        - Key: Name<br>          Value: AppPrivateSubnet1A<br><br>  # Data Private Subnet in AZ 1<br>  DataPrivateSubnet1A:<br>    Type: &#39;AWS::EC2::Subnet&#39;<br>    Properties:<br>      VpcId: !Ref MyVPC<br>      CidrBlock: &#39;172.16.3.0/24&#39;<br>      AvailabilityZone: !Select [0, !GetAZs &#39;&#39;]<br>      Tags:<br>        - Key: Name<br>          Value: DataPrivateSubnet1A<br><br>  # Public Subnet in AZ 2<br>  PublicSubnet2B:<br>    Type: &#39;AWS::EC2::Subnet&#39;<br>    Properties:<br>      VpcId: !Ref MyVPC<br>      CidrBlock: &#39;172.16.4.0/24&#39;<br>      AvailabilityZone: !Select [1, !GetAZs &#39;&#39;]<br>      MapPublicIpOnLaunch: true<br>      Tags:<br>        - Key: Name<br>          Value: PublicSubnet2B<br><br>  # App Private Subnet in AZ 2<br>  AppPrivateSubnet2B:<br>    Type: &#39;AWS::EC2::Subnet&#39;<br>    Properties:<br>      VpcId: !Ref MyVPC<br>      CidrBlock: &#39;172.16.5.0/24&#39;<br>      AvailabilityZone: !Select [1, !GetAZs &#39;&#39;]<br>      Tags:<br>        - Key: Name<br>          Value: AppPrivateSubnet2B<br><br>  # Data Private Subnet in AZ 2<br>  DataPrivateSubnet2B:<br>    Type: &#39;AWS::EC2::Subnet&#39;<br>    Properties:<br>      VpcId: !Ref MyVPC<br>      CidrBlock: &#39;172.16.6.0/24&#39;<br>      AvailabilityZone: !Select [1, !GetAZs &#39;&#39;]<br>      Tags:<br>        - Key: Name<br>          Value: DataPrivateSubnet2B<br><br># Internet Gateway IGW<br>  InternetGateway:<br>    Type: &#39;AWS::EC2::InternetGateway&#39;<br>    Properties:<br>      Tags:<br>        - Key: Name<br>          Value: MyVPC-IGW<br><br># Attach Gateway  <br>  AttachGateway:<br>    Type: &#39;AWS::EC2::VPCGatewayAttachment&#39;<br>    Properties:<br>      VpcId: !Ref MyVPC<br>      InternetGatewayId: !Ref InternetGateway<br><br># Route Table<br>  PublicRouteTable:<br>    Type: &#39;AWS::EC2::RouteTable&#39;<br>    Properties:<br>      VpcId: !Ref MyVPC<br>      Tags:<br>        - Key: Name<br>          Value: PublicRouteTable<br><br># Public Route<br>  PublicRoute:<br>    Type: &#39;AWS::EC2::Route&#39;<br>    DependsOn: AttachGateway<br>    Properties:<br>      RouteTableId: !Ref PublicRouteTable<br>      DestinationCidrBlock: &#39;0.0.0.0/0&#39;<br>      GatewayId: !Ref InternetGateway<br><br># Public Subnet Association<br>  PublicSubnet1ARouteTableAssociation:<br>    Type: &#39;AWS::EC2::SubnetRouteTableAssociation&#39;<br>    Properties:<br>      SubnetId: !Ref PublicSubnet1A<br>      RouteTableId: !Ref PublicRouteTable<br><br># Web Server Security Group<br>  WebServerSecurityGroup:<br>    Type: &#39;AWS::EC2::SecurityGroup&#39;<br>    Properties:<br>      GroupDescription: Enable HTTP access via port 80<br>      VpcId: !Ref MyVPC<br>      SecurityGroupIngress:<br>        - IpProtocol: tcp<br>          FromPort: &#39;80&#39;<br>          ToPort: &#39;80&#39;<br>          CidrIp: 0.0.0.0/0<br><br># Launch Configuration<br>  MyLaunchConfig:<br>    Type: &#39;AWS::AutoScaling::LaunchConfiguration&#39;<br>    Properties:<br>      ImageId: &#39;ami-0bb84b8ffd87024d8&#39;<br>      InstanceType: t2.micro<br>      SecurityGroups:<br>        - !Ref WebServerSecurityGroup<br>      UserData:<br>        Fn::Base64: !Sub |<br>          #!/bin/bash<br>          yum install -y httpd<br>          systemctl start httpd<br>          systemctl enable httpd<br>          echo &quot;Hello from Auto Scaling Instance!&quot; &gt; /var/www/html/index.html<br><br># Auto Scaling Group<br>  MyASG:<br>    Type: &#39;AWS::AutoScaling::AutoScalingGroup&#39;<br>    Properties:<br>      LaunchConfigurationName: !Ref MyLaunchConfig<br>      DesiredCapacity: 2<br>      MinSize: 1<br>      MaxSize: 3<br>      VPCZoneIdentifier:<br>        - !Ref PublicSubnet1A<br>        - !Ref PublicSubnet2B<br><br># Alarm<br>  CPUAlarm:<br>    Type: &#39;AWS::CloudWatch::Alarm&#39;<br>    Properties:<br>      AlarmDescription: &#39;Alarm when CPU exceeds 70%&#39;<br>      EvaluationPeriods: 1<br>      Period: 300<br>      MetricName: CPUUtilization<br>      ComparisonOperator: GreaterThanThreshold<br>      Threshold: 70<br>      Namespace: &#39;AWS/EC2&#39;<br>      Statistic: Average<br>      AlarmActions:<br>        - !Ref ScaleOutPolicy<br>      Dimensions:<br>        - Name: AutoScalingGroupName<br>          Value: !Ref MyASG<br><br># Scale Out Policy<br>  ScaleOutPolicy:<br>    Type: &#39;AWS::AutoScaling::ScalingPolicy&#39;<br>    Properties:<br>      AutoScalingGroupName: !Ref MyASG<br>      PolicyType: SimpleScaling<br>      ScalingAdjustment: 1<br>      AdjustmentType: ChangeInCapacity<br>      Cooldown: 300<br><br></pre><p>Here’s a breakdown of the key components:</p><ol><li><strong>VPC and Subnets</strong>: The template creates a VPC with a CIDR block of 172.16.0.0/16. It then defines six subnets: two public subnets (one in each AZ), two private app subnets, and two private data subnets.</li><li><strong>Internet Gateway and Routing</strong>: An Internet Gateway is created and attached to the VPC. A public route table is defined, and a route is added to send internet-bound traffic (0.0.0.0/0) through the Internet Gateway. The public subnets are associated with this route table, allowing instances in those subnets to access the internet.</li><li><strong>Security Group</strong>: A security group named “WebServerSecurityGroup” is created, allowing inbound HTTP traffic (port 80) from any IP address (0.0.0.0/0).</li><li><strong>Launch Configuration</strong>: A launch configuration named “MyLaunchConfig” is defined. It specifies an Amazon Linux 2 AMI (ami-0bb84b8ffd87024d8) and an instance type (t2.micro). The launch configuration also includes a user data script that installs and starts the Apache web server, and creates a simple “Hello from Auto Scaling Instance!” index.html file.</li><li><strong>Auto Scaling Group</strong>: An Auto Scaling group named “MyASG” is created, using the “MyLaunchConfig” launch configuration. The desired capacity is set to 2 instances, with a minimum of 1 and a maximum of 3. The Auto Scaling group is associated with the two public subnets (PublicSubnet1A and PublicSubnet2B).</li><li><strong>CloudWatch Alarm and Scaling Policy</strong>: A CloudWatch alarm named “CPUAlarm” is defined to monitor the CPU utilization of instances in the Auto Scaling group. If the average CPU utilization exceeds 70% for one evaluation period (5 minutes), the alarm triggers a scaling policy named “ScaleOutPolicy”. This policy increases the desired capacity of the Auto Scaling group by 1 instance, up to the maximum of 3 instances. A cooldown period of 5 minutes is set to prevent excessive scaling.</li></ol><p>Here are screenshots of the deployed stack.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lKRpkRhbM6gZTaaanUde0A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tdNaBR277C3TY5eHfcW03w.png" /></figure><p>Until next time, when I share more on my cloud journey, feel free to contact me to discuss Agile or cloud adoption.</p><p>You can connect with me on <a href="https://www.linkedin.com/in/adekunle-adesanmi/">LinkedIn</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c0b9aedb1f1c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My Cloud Journey — Week 6 | Advanced AWS Part 2 | Application Load Balancer deployment using…]]></title>
            <link>https://medium.com/@kunleadesanmi/my-cloud-journey-week-6-advanced-aws-part-2-application-load-balancer-deployment-using-6a7e61902c73?source=rss-56aafda8615b------2</link>
            <guid isPermaLink="false">https://medium.com/p/6a7e61902c73</guid>
            <category><![CDATA[cloudformation]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[cloud-architecture]]></category>
            <category><![CDATA[application-load-balancer]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Adekunle Adesanmi]]></dc:creator>
            <pubDate>Thu, 06 Jun 2024 17:15:33 GMT</pubDate>
            <atom:updated>2024-07-09T13:01:54.595Z</atom:updated>
            <content:encoded><![CDATA[<h3>My Cloud Journey — Week 6 | Advanced AWS Part 2 | Application Load Balancer deployment using CloudFormation</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/574/1*dW9iapsZ8-mw68REqj8Bgg.png" /></figure><p>In my <a href="https://medium.com/@kunleadesanmi/my-cloud-journey-week-6-advanced-aws-part-1-315b190b092d">previous post</a>, I covered some important concepts that I found interesting during my exploration of advanced AWS topics. In this post, I will go into a specific exercise I completed using AWSCloudFormation, with subsequent posts focusing on additional exercises.</p><p>The task in this exercise is to set up a web infrastructure with an Application Load Balancer (ALB) distributing traffic across two EC2 instances in separate Availability Zones (AZs).</p><p>Here is the CloudFormation template that I used, written in YAML format.</p><p>The template sets up a Virtual Private Cloud (VPC) with public and private subnets across two Availability Zones (AZs), an Internet Gateway, routing tables, and an Application Load Balancer (ALB) with two target EC2 instances.</p><pre>AWSTemplateFormatVersion: &#39;2010-09-09&#39;<br>Description: &#39;CloudFormation for ALB&#39;<br><br>Resources:<br>  # My VPC<br>  MyVPC:<br>    Type: &#39;AWS::EC2::VPC&#39;<br>    Properties:<br>      CidrBlock: &#39;172.16.0.0/16&#39;<br>      EnableDnsSupport: true<br>      EnableDnsHostnames: true<br>      Tags:<br>        - Key: Name<br>          Value: MyVPC<br><br>  # Public Subnet in AZ 1<br>  PublicSubnet1A:<br>    Type: &#39;AWS::EC2::Subnet&#39;<br>    Properties:<br>      VpcId: !Ref MyVPC<br>      CidrBlock: &#39;172.16.1.0/24&#39;<br>      AvailabilityZone: !Select [0, !GetAZs &#39;&#39;]<br>      MapPublicIpOnLaunch: true<br>      Tags:<br>        - Key: Name<br>          Value: PublicSubnet1A<br><br>  # App Private Subnet in AZ 1<br>  AppPrivateSubnet1A:<br>    Type: &#39;AWS::EC2::Subnet&#39;<br>    Properties:<br>      VpcId: !Ref MyVPC<br>      CidrBlock: &#39;172.16.2.0/24&#39;<br>      AvailabilityZone: !Select [0, !GetAZs &#39;&#39;]<br>      Tags:<br>        - Key: Name<br>          Value: AppPrivateSubnet1A<br><br>  # Data Private Subnet in AZ 1<br>  DataPrivateSubnet1A:<br>    Type: &#39;AWS::EC2::Subnet&#39;<br>    Properties:<br>      VpcId: !Ref MyVPC<br>      CidrBlock: &#39;172.16.3.0/24&#39;<br>      AvailabilityZone: !Select [0, !GetAZs &#39;&#39;]<br>      Tags:<br>        - Key: Name<br>          Value: DataPrivateSubnet1A<br><br>  # Public Subnet in AZ 2<br>  PublicSubnet2B:<br>    Type: &#39;AWS::EC2::Subnet&#39;<br>    Properties:<br>      VpcId: !Ref MyVPC<br>      CidrBlock: &#39;172.16.4.0/24&#39;<br>      AvailabilityZone: !Select [1, !GetAZs &#39;&#39;]<br>      MapPublicIpOnLaunch: true<br>      Tags:<br>        - Key: Name<br>          Value: PublicSubnet2B<br><br>  # App Private Subnet in AZ 2<br>  AppPrivateSubnet2B:<br>    Type: &#39;AWS::EC2::Subnet&#39;<br>    Properties:<br>      VpcId: !Ref MyVPC<br>      CidrBlock: &#39;172.16.5.0/24&#39;<br>      AvailabilityZone: !Select [1, !GetAZs &#39;&#39;]<br>      Tags:<br>        - Key: Name<br>          Value: AppPrivateSubnet2B<br><br>  # Data Private Subnet in AZ 2<br>  DataPrivateSubnet2B:<br>    Type: &#39;AWS::EC2::Subnet&#39;<br>    Properties:<br>      VpcId: !Ref MyVPC<br>      CidrBlock: &#39;172.16.6.0/24&#39;<br>      AvailabilityZone: !Select [1, !GetAZs &#39;&#39;]<br>      Tags:<br>        - Key: Name<br>          Value: DataPrivateSubnet2B<br><br># Internet Gateway IGW<br>  InternetGateway:<br>    Type: &#39;AWS::EC2::InternetGateway&#39;<br>    Properties:<br>      Tags:<br>        - Key: Name<br>          Value: MyVPC-IGW<br><br># Attach Gateway  <br>  AttachGateway:<br>    Type: &#39;AWS::EC2::VPCGatewayAttachment&#39;<br>    Properties:<br>      VpcId: !Ref MyVPC<br>      InternetGatewayId: !Ref InternetGateway<br><br># Route Table<br>  PublicRouteTable:<br>    Type: &#39;AWS::EC2::RouteTable&#39;<br>    Properties:<br>      VpcId: !Ref MyVPC<br>      Tags:<br>        - Key: Name<br>          Value: PublicRouteTable<br><br># Public Route<br>  PublicRoute:<br>    Type: &#39;AWS::EC2::Route&#39;<br>    DependsOn: AttachGateway<br>    Properties:<br>      RouteTableId: !Ref PublicRouteTable<br>      DestinationCidrBlock: &#39;0.0.0.0/0&#39;<br>      GatewayId: !Ref InternetGateway<br><br># Public Subnet Association<br>  PublicSubnet1ARouteTableAssociation:<br>    Type: &#39;AWS::EC2::SubnetRouteTableAssociation&#39;<br>    Properties:<br>      SubnetId: !Ref PublicSubnet1A<br>      RouteTableId: !Ref PublicRouteTable<br><br># Application Load Balancer<br>  MyLoadBalancer:<br>    Type: &#39;AWS::ElasticLoadBalancingV2::LoadBalancer&#39;<br>    Properties:<br>      Subnets:<br>        - !Ref PublicSubnet1A<br>        - !Ref PublicSubnet2B<br>      SecurityGroups:<br>        - !Ref WebServerSecurityGroup<br><br># Target Group for ALB<br>  MyTargetGroup:<br>    Type: &#39;AWS::ElasticLoadBalancingV2::TargetGroup&#39;<br>    Properties:<br>      Port: 80<br>      Protocol: HTTP<br>      VpcId: !Ref MyVPC<br>      Targets:<br>        - Id: !Ref WebServerInstance1A<br>          Port: 80<br>        - Id: !Ref WebServerInstance2B<br>          Port: 80<br><br># Listener for ALB<br>  MyListener:<br>    Type: &#39;AWS::ElasticLoadBalancingV2::Listener&#39;<br>    Properties:<br>      DefaultActions:<br>        - Type: forward<br>          TargetGroupArn: !Ref MyTargetGroup<br>      LoadBalancerArn: !Ref MyLoadBalancer<br>      Port: 80<br>      Protocol: HTTP<br><br># Web Server Security Group<br>  WebServerSecurityGroup:<br>    Type: &#39;AWS::EC2::SecurityGroup&#39;<br>    Properties:<br>      GroupDescription: Enable HTTP access via port 80<br>      VpcId: !Ref MyVPC<br>      SecurityGroupIngress:<br>        - IpProtocol: tcp<br>          FromPort: &#39;80&#39;<br>          ToPort: &#39;80&#39;<br>          CidrIp: 0.0.0.0/0<br><br># WebServerInstance1A:<br>  WebServerInstance1A:<br>    Type: &#39;AWS::EC2::Instance&#39;<br>    Properties:<br>      ImageId: &#39;ami-0bb84b8ffd87024d8&#39;<br>      InstanceType: &#39;t2.micro&#39;<br>      SubnetId: !Ref PublicSubnet1A<br>      SecurityGroupIds:<br>        - !Ref WebServerSecurityGroup<br>      Tags:<br>        - Key: Name<br>          Value: WebServerInstance1A<br>      UserData:<br>        Fn::Base64:  !Sub  |<br>          #!/bin/bash<br>          yum update -y<br>          yum install -y httpd<br>          systemctl start httpd<br>          systemctl enable httpd<br>          echo &quot;Hello World from WebServerInstance 1A&quot; &gt; /var/www/html/index.html<br><br># WebServerInstance2B:<br>  WebServerInstance2B:<br>    Type: &#39;AWS::EC2::Instance&#39;<br>    Properties:<br>      ImageId: &#39;ami-0bb84b8ffd87024d8&#39;<br>      InstanceType: &#39;t2.micro&#39;<br>      SubnetId: !Ref PublicSubnet2B<br>      SecurityGroupIds:<br>        - !Ref WebServerSecurityGroup<br>      Tags:<br>        - Key: Name<br>          Value: WebServerInstance2B<br>      UserData:<br>        Fn::Base64:  !Sub  |<br>          #!/bin/bash<br>          yum update -y<br>          yum install -y httpd<br>          systemctl start httpd<br>          systemctl enable httpd<br>          echo &quot;Hello World from WebServerInstance 2B&quot; &gt; /var/www/html/index.html</pre><p>Here’s a breakdown of the key components:</p><ol><li><strong>VPC and Subnets</strong>: The template creates a VPC with a CIDR block of 172.16.0.0/16. It then defines six subnets: two public subnets (one in each AZ), two private app subnets, and two private data subnets.</li><li><strong>Internet Gateway</strong>: An Internet Gateway is created and attached to the VPC, allowing resources in the public subnets to access the Internet.</li><li><strong>Route Tables</strong>: A public route table is created, and a route is added to send all internet-bound traffic (0.0.0.0/0) through the Internet Gateway. The public subnets are associated with this route table.</li><li><strong>Security Group</strong>: A security group is created to allow inbound HTTP traffic (port 80) from anywhere (0.0.0.0/0) to the web servers.</li><li><strong>Application Load Balancer (ALB)</strong>: An ALB is created and placed in the public subnets. It listens for incoming HTTP traffic on port 80.</li><li><strong>Target Group</strong>: A target group is created for the ALB, which will route traffic to the registered targets (EC2 instances).</li><li><strong>EC2 Instances</strong>: Two EC2 instances are launched, one in each public subnet. These instances will serve as the web servers behind the ALB. The instances are configured with a User Data script that installs Apache HTTP Server and creates a simple “Hello World” index.html file.</li></ol><p>Here’s a screenshot of the deployed stack.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3npJh9rGOI3c7AHeOFindA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2NAJeBYv_T8gYDrzlmN8Ew.png" /></figure><p>Join me next time as I share more CloudFormation deployments!</p><p>Feel free to contact me to discuss Agile, cloud adoption, or anything tech-related. 🚀<br>You can also connect with me on <a href="https://www.linkedin.com/in/adekunle-adesanmi/">LinkedIn</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6a7e61902c73" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My Cloud Journey — Week 6|  Advanced AWS Part 1]]></title>
            <link>https://medium.com/@kunleadesanmi/my-cloud-journey-week-6-advanced-aws-part-1-315b190b092d?source=rss-56aafda8615b------2</link>
            <guid isPermaLink="false">https://medium.com/p/315b190b092d</guid>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[iam-roles]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[s3]]></category>
            <category><![CDATA[cloud-engineering]]></category>
            <dc:creator><![CDATA[Adekunle Adesanmi]]></dc:creator>
            <pubDate>Wed, 05 Jun 2024 17:00:32 GMT</pubDate>
            <atom:updated>2024-07-09T15:18:39.020Z</atom:updated>
            <content:encoded><![CDATA[<h3>My Cloud Journey — Week 6 | Advanced AWS Part 1</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/702/1*Fx4kelFqs-dCG6mAivzVsA.png" /></figure><p>Week 6 at the academy lasted 8 weeks literally! This was partly due to the extensive AWS material, which exceeded a week’s workload. I also dedicated significant time to additional studies on DevOps, CloudFormation and Terraform.</p><p>We explored IAM, S3, RDS, EC2, Load Balancers, and Auto Scaling extensively, diving into a range of AWS services. I gained insights into resource management, security, and performance optimization. Not only did we create these resources via the AWS console, but we also created them using AWS CloudFormation. In this piece, I will discuss the essential aspects that influenced my grasp of cloud computing.</p><p>Caution! This article will be theoretical, but the following one will feature some of the exercises done for week 6.</p><h3>Identity and Access Management (IAM)</h3><h4>IAM Users, Groups, Policies and Roles</h4><p>AWS Identity and Access Management (IAM) forms the foundation of secure access control. Here are some essential concepts:</p><ol><li><strong>IAM Users</strong>: An IAM user represents either a person or a service that interacts with AWS resources. When you create an IAM user, you define their credentials and permissions within your AWS account.</li><li><strong>IAM Groups</strong>: An IAM group is a collection of users who share access control policies. These groups allow you to specify permissions for multiple users, making it easier to manage their permissions.</li><li><strong>IAM Roles</strong>: An IAM role is an identity with specific permissions. Unlike an IAM user, a role isn’t uniquely associated with one person; it’s intended to be assumable by anyone who needs it.</li><li><strong>IAM Policies</strong>: An IAM policy is a document attached to a resource (such as an AWS user, group, or role) that defines what actions a principal (user or service) can perform on that resource. When a request is made, AWS evaluates the attached policies to determine whether the request is allowed or denied. These policies are typically written in JSON format and grant specific permissions for actions like accessing Amazon DynamoDB, managing S3 buckets, launching EC2 instances, invoking Lambda functions, and more.</li></ol><h4>IAM best practices</h4><ol><li>Adopt a Zero Trust Approach: Assume no implicit trust. Always verify and authenticate users, even within your organization.</li><li>Identify and Protect High-Value Data: Understand which data is critical and ensure strict access controls for it.</li><li>Enforce Strong Password Policies: Require complex passwords and regular updates.</li><li>Use Multi-Factor Authentication (MFA): Add an extra layer of security by combining passwords with a second form of authentication.</li><li>Automate Workflows: Use IAM roles and policies to automate access management and reduce manual intervention.</li><li>Apply the Principle of Least Privilege: Grant only necessary permissions to users, minimizing potential risks.</li><li>Enforce Just-in-Time Access: Provide access only when needed, reducing exposure.</li><li>Leverage Role-Based and Attribute-Based Access Control: Combine these approaches for fine-grained</li></ol><h3>Elastic Compute Cloud (EC2) Storage</h3><h4>EC2 Storage Options</h4><ol><li><strong>Instance Store</strong>: For temporary storage (akin to RAM), I explored instance store volumes. These provide high-speed, ephemeral storage but don’t persist data beyond instance termination.</li><li><strong>Elastic Block Store (EBS)</strong>: EBS volumes offer permanent storage (similar to hard disks). Types include:</li></ol><ul><li>General Purpose SSD</li><li>Provisioned IOPS</li><li>Throughput Optimized</li><li>Cold HDD</li></ul><h3>Load Balancing and Auto Scaling</h3><h4>Elastic Load Balancing (ELB)</h4><ol><li><strong>Application Load Balancer (ALB)</strong>: Ideal for HTTP/HTTPS traffic, ALB handles containers, microservices, and complex content management systems.</li><li><strong>Network Load Balancer (NLB)</strong>: For TCP, UDP, and TLS traffic, NLB operates at layer 4, serving high-performance web servers and caching systems.</li><li><strong>Classic Load Balancer</strong>: Although older, it still serves specific use cases.</li></ol><h4>Auto Scaling Groups</h4><p>An Auto Scaling group is a logical collection of Amazon EC2 instances used for automatic scaling and management.</p><h4>Benefits of Auto Scaling Groups:</h4><p><strong>Fault Tolerance</strong>:</p><ul><li>Auto Scaling detects unhealthy instances and replaces them automatically.</li><li>Configuring multiple Availability Zones ensures resilience even if one zone becomes unavailable.</li></ul><p><strong>Availability</strong>:</p><ul><li>Auto Scaling maintains the right capacity to handle current traffic demand.</li><li>Scales up or down dynamically based on load, ensuring optimal performance.</li></ul><p><strong>Cost Management</strong>:</p><ul><li>Dynamically adjusts capacity, saving costs by launching instances only when needed.</li><li>Terminates instances when demand decreases, avoiding unnecessary expenses.</li></ul><h4>Components of an Auto Scaling Group:</h4><ol><li>Instances</li><li>Health Checks</li><li>Launch Configurations</li><li>Minimum and Maximum Instances</li><li>Scaling Policies</li></ol><h3>Amazon S3 (Simple Storage Service)</h3><p>Amazon S3 is a powerful object storage service offered by Amazon Web Services (AWS). Here are the key points:</p><ol><li><strong>Scalability</strong>: S3 can store virtually any amount of data, from small files to exabytes, with unmatched performance. It automatically grows and shrinks as you add or remove data, and you pay only for what you use.</li><li><strong>Durability and Availability</strong>: S3 provides industry-leading data durability (99.999999999% or 11 nines) and availability (99.99%) by default. It’s designed to be highly reliable, and backed by strong SLAs.</li><li><strong>Versioning</strong>: leveraged versioning for protection against accidental deletions and compliance requirements.</li><li><strong>Security and Data Protection</strong>:</li></ol><ul><li>Secure: S3 encrypts data by default and supports various access controls.</li><li>Auditing: Monitor access requests to your S3 resources.</li><li>Compliance: Meet regulatory requirements.</li></ul><p>4. <strong>Storage Classes</strong>: Standard, Intelligent Tiering, Infrequent Access, One Zone IA, Glacier and Glacier Deep Archive.</p><p>5. <strong>Use Cases</strong>: Static website hosting, big data analytics, backup and restore</p><h3>Relational Database Service (RDS)</h3><p><strong>Amazon Relational Database Service (RDS)</strong> is a fully managed cloud database service provided by <strong>Amazon Web Services (AWS)</strong>. Here’s what you need to know:</p><ol><li><strong>Purpose</strong>: RDS simplifies database management by automating tasks like provisioning, backups, and patching. It allows you to focus on your application rather than database administration.</li><li><strong>Choice of Engines</strong>: You can deploy and scale various relational database engines, including:</li></ol><ul><li><strong>Amazon Aurora</strong> (compatible with PostgreSQL and MySQL)</li><li>PostgreSQL</li><li>MySQL</li><li>MariaDB</li><li>SQL Server</li><li>Oracle</li><li>Db2</li></ul><p><strong>3. High Availability</strong>: RDS offers Multi-AZ deployments for high availability and failover.</p><p><strong>4. Use Cases</strong>:</p><ul><li><strong>Web and Mobile Applications</strong>: Support growing apps with scalability and flexible pay-per-use pricing.</li><li><strong>Managed Databases</strong>: Innovate without the complexity of self-managing databases.</li><li><strong>Migrate from Legacy Systems</strong>: Consider migrating to Amazon Aurora for cost savings and improved performance.</li></ul><p><strong>Benefits</strong>:</p><ul><li>Multi-AZ deployments for high availability</li><li>Read replicas for read scaling and disaster recovery</li><li>Automatic backups</li></ul><h3>Conclusion</h3><p>Week 6, or perhaps I ought to say weeks 6 to 13 of my exploration of the AWS cloud, has offered me a fascinating comprehension of AWS offerings. From understanding IAM principles to exploring load balancing and storage choices, I have acquired valuable knowledge. As I progress, I am eager to delve deeper into more cloud technologies and play a part in creating innovative solutions.</p><p>Feel free to contact me to discuss Agile, cloud adoption, or anything tech-related. 🚀<br>You can also connect with me on <a href="https://www.linkedin.com/in/adekunle-adesanmi/">LinkedIn</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=315b190b092d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Future-Proof Your Business With Application Modernization]]></title>
            <link>https://medium.com/@kunleadesanmi/future-proof-your-business-the-crucial-role-of-application-modernization-2ddd67d32a86?source=rss-56aafda8615b------2</link>
            <guid isPermaLink="false">https://medium.com/p/2ddd67d32a86</guid>
            <category><![CDATA[application-modernization]]></category>
            <category><![CDATA[app-monetization]]></category>
            <category><![CDATA[cloud-architecture]]></category>
            <category><![CDATA[cloud-engineering]]></category>
            <category><![CDATA[cloud-native]]></category>
            <dc:creator><![CDATA[Adekunle Adesanmi]]></dc:creator>
            <pubDate>Fri, 03 May 2024 11:13:03 GMT</pubDate>
            <atom:updated>2024-07-09T15:19:41.923Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/638/1*-O7Ky08g396A3cXJYgpaKg.png" /></figure><p>Last year I began a Software Engineering and DevOps course with IBM and came across the idea of application modernization. Three key areas were highlighted — Architecture, Infrastructure and Delivery. Architectures have transitioned from monoliths to service-oriented architectures to microservices. Infrastructure has evolved from physical servers to virtual machines to the cloud, and delivery has shifted from Waterfall to Agile to DevOps.</p><p>As an expert in agile delivery, this aligns perfectly with my ideology. I have frequently discussed the importance of microservices and DevOps practices with my teams and employers, but not specifically in the context of application modernization.</p><p>In this article, we will discuss the importance of application modernization and examine strategies for surviving and thriving in today’s digital environment.</p><p>Let’s dive right in!</p><p>In today’s fast-paced and ever-changing digital landscape, businesses face unprecedented challenges and opportunities. With technological advancements, evolving customer expectations, and increasing competition, organizations must continually adapt and innovate to stay relevant and competitive. At the heart of this transformation lies application modernization — a strategic imperative for organizations seeking to enhance agility, scalability, and customer experience in today’s digital economy.</p><h3>What is application modernization and why is it needed?</h3><p>As legacy systems age and business needs evolve, organizations often find themselves constrained by outdated technologies, inefficient processes, and inflexible architectures. Application modernization addresses these challenges by transforming legacy applications into modern, agile, and cloud-native solutions that can adapt to changing business requirements and deliver value at scale.</p><p>It involves leveraging the latest technologies, such as cloud computing, microservices, and DevOps practices, to enhance performance, security, and user experience. This is why I am improving my Cloud, DevOps and DevSecOps expertise through hands-on training with <a href="https://www.linkedin.com/feed/?linkOrigin=LI_BADGE&amp;shareActive=true&amp;shareUrl=https%3A%2F%2Flink.medium.com%2FO4YPNk0piJb#">Cloud Engineer Academy</a> along with other courses.</p><p>I also like the way Microsoft describes application modernization as <em>“the process of updating an organization’s existing apps to a cloud-first model — sometimes called legacy modernization”</em></p><h3>What are the benefits of application modernization?</h3><p><strong>Enhanced agility and faster time to market</strong></p><p>Application modernization helps organizations improve agility and speed-to-market by streamlining development processes, reducing time-to-market, and accelerating innovation cycles. By embracing DevOps practices and modern DevOps tools for example in continuous integration and continuous deployment (CI/CD), organizations can automate processes, enhance teamwork, and efficiently deliver top-notch software on a large scale. This agility allows organizations to iterate quickly, experiment with new ideas, and respond rapidly to changing customer needs and market dynamics.</p><p><strong>Improved security</strong></p><p>Legacy systems often lack robust security measures, making them vulnerable to cyber threats. Organisations adopting a cloud-first strategy can leverage integrated security features and updates to protect their workloads. Task automation for crucial functions including high availability, disaster recovery, backups, and performance monitoring are examples of additional built-in functionalities.</p><p><strong>Improved Scalability and Resilience</strong></p><p>Legacy applications frequently struggle to scale and adapt to fluctuating workloads, leading to performance issues, downtime, and poor user experiences. Application modernization addresses these challenges by designing applications for scalability and resilience, leveraging cloud-native technologies such as auto-scaling, load balancing, and fault tolerance. By building applications that can scale dynamically to handle peaks in demand and withstand failures gracefully, organizations can ensure reliability, availability, and performance under any circumstances.</p><p><strong>Seamless integration</strong></p><p>Not only will modernised apps function with the latest technology, but they will also continue to function as technology advances. Quick upgrades and modifications are easily achievable thanks to this seamless integration, catering to the current and future requirements of organizations.</p><p><strong>Rapid Innovation and Cost Optimization</strong></p><p>Application modernization reduces maintenance costs associated with outdated systems, eliminates the need for expensive hardware upgrades, and enables organizations to leverage the cost-effectiveness of cloud computing. When organizations spend less time and resources on app and infrastructure maintenance, they can focus more on innovation.</p><h3>Choosing the Right Modernization Approach</h3><p>Organizations should conduct a thorough analysis of their existing application portfolio to identify which systems or applications need modernization and prioritize them based on business value and impact. Depending on the specific requirements and constraints, businesses can opt for various modernization approaches, such as rehosting, rearchitecting, or rebuilding applications from scratch.</p><h4>Rehosting</h4><p>This modernization technique, sometimes known as “lift-and-shift,” places an emphasis on speed because it essentially eliminates the need for code modifications. Businesses transfer apps from their old environment to their new one in their original form.</p><h4>Rearchitecting</h4><p>If an organisation needs the scaling benefits of the cloud, rearchitecting can be the best option. Rearchitecting modifies and extends functionality and code to improve cloud scalability. Central to this is the adoption of cloud-native architectures, which leverage the scalability, flexibility, and cost-effectiveness of cloud computing platforms. Cloud-native architectures enable rapid development, deployment, and scaling of applications, allowing organizations to respond quickly to market demands and deliver exceptional customer experiences.</p><h4>Rebuilding</h4><p>When recreating applications using cloud solutions, rebuilding is sometimes the best option. It’s an enormous and often costly shift, but it could be necessary if existing apps have limited functionality or lifespan.</p><h3>Challenges and Risks</h3><p>While the benefits of application modernization are compelling, organizations may encounter challenges and risks on their modernization journey. These challenges may include <strong>legacy dependencies</strong>,<strong> technical debt</strong>, <strong>organizational resistanc</strong>e, and<strong> cultural barrier</strong>s. However, by taking a systematic approach, establishing clear goals and priorities, and leveraging the expertise of modernization partners, organizations can overcome these challenges and mitigate risks effectively.</p><p>In conclusion, application modernization is a critical enabler for organizations seeking to survive and thrive in today’s digital landscape. By adopting cloud-native architectures, enhancing agility and speed-to-market, improving scalability and resilience, and optimizing costs and resource utilization, organizations can unlock higher levels of innovation, efficiency, and competitiveness. However, successful modernization requires a strategic approach, a commitment to continuous improvement, and a willingness to embrace change. By investing in application modernization, organizations can future-proof their IT infrastructure, architecture, and delivery, drive digital transformation, and position themselves for long-term success in the digital economy.</p><p>Thank you for visiting. See you in my next article!</p><p>Feel free to contact me to discuss Agile, cloud adoption, or anything tech-related. 🚀<br>You can also connect with me on <a href="https://www.linkedin.com/in/adekunle-adesanmi/">LinkedIn</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2ddd67d32a86" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Creating and deploying a three-tier AWS Architecture using CloudFormation| My Cloud Journey — Week…]]></title>
            <link>https://towardsaws.com/creating-and-deploying-a-three-tier-aws-architecture-using-cloudformation-my-cloud-journey-week-2ba2d84b992f?source=rss-56aafda8615b------2</link>
            <guid isPermaLink="false">https://medium.com/p/2ba2d84b992f</guid>
            <category><![CDATA[cloud-engineering]]></category>
            <category><![CDATA[cloud-architecture]]></category>
            <category><![CDATA[cloudformation]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <dc:creator><![CDATA[Adekunle Adesanmi]]></dc:creator>
            <pubDate>Tue, 16 Apr 2024 12:35:35 GMT</pubDate>
            <atom:updated>2024-08-19T07:02:02.164Z</atom:updated>
            <content:encoded><![CDATA[<h3>Creating and deploying a Three-tier AWS Architecture using CloudFormation| My Cloud Journey — Week 5</h3><p>Hello everyone!</p><p>Today, I’ll be sharing my experience of writing and deploying a three-tier AWS architecture using Infrastructure as Code (CloudFormation). The design can be seen <a href="https://medium.com/@kunleadesanmi/my-cloud-journey-week-5-project-a5827ea715ce">here</a> and the manual implementation can also be seen <a href="https://medium.com/@kunleadesanmi/my-cloud-journey-module-5-project-vpc-implementation-using-the-aws-console-57bbac25166b">here</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/573/1*tKtDdClcow0h2BN2bfol2Q.png" /></figure><p>With AWS CloudFormation, we can create a template that describes our desired architecture, including all the necessary resources like virtual machines, load balancers, databases, and more. This template acts as our blueprint, guiding the deployment process.</p><h4>Challenges faced</h4><p>A major factor in the issues I encountered was trying to write all the code for all the resources before attempting to deploy them. This approach proved to be a mistake, as it made it difficult for me to identify the root causes of errors that occurred during the deployment of the CloudFormation template. It felt like a never-ending cycle of fixing one issue, only to be faced with another and another, without any confirmation that the fixes I made actually resolved the problems.</p><p>A more efficient approach (which I later adopted) is to deploy the resources incrementally, testing and validating each step along the way. This allows for easier identification of errors and provides confirmation that the fixes made are indeed resolving the issue. You can save time and effort by addressing issues as they arise, rather than dealing with a cascade of errors. It provides a clearer understanding of the progress made and allows for more accurate tracking of fixes.</p><p>So, next time you’re working on a CloudFormation template or any other IaC project, remember the importance of deploying resources incrementally to avoid the frustration of endless errors and uncertainty — I learnt this the hard way!</p><p>I encountered several other challenges. However, I want to highlight the three most significant ones:</p><ol><li><strong>Changing logical resource names</strong> — I changed some of my logical resource names while I was writing the whole stack and forgot to reflect the changes in the references I made to them within the stack.</li><li><strong>Routing issues</strong> — I created two NatGateways (one for each availability zone), one private subnet route table and two routes, both referencing the same route table. This came back with the error that the route is already being used. I spent a long time on this one, but eventually realised that I needed to create another route table, i.e one for each availability zone and the routes to point to different private route tables.</li><li><strong>Database servers</strong> — At this point the stack is in a good place with all the resources working. All that was left is the Instances and security groups. I created them and deployed the stack but got another error — ‘<strong><em>Resource handler returned message: “The parameter groupName cannot be used with the parameter subnet…’ </em></strong>at the database servers creation step. There was no ‘groupName’ parameter in the database servers code snippet, so I couldn’t understand the meaning or the reason for the error. After some hours of research. I read some comments online that suggested using ‘SecurityGroupIds’ parameter instead of ‘SecurityGroups’ if there’s a subnet attached to the instance. The suggestion fixed the last of my issues and I couldn’t be happier to see that ‘CREATE_COMPLETE’ message next to my stack.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3I3GvrLMPq0pb_KMLklNuw.png" /></figure><h4>CloudFormation Template</h4><p>Here is my CloudFormation template and a list of resources that it creates:</p><pre>AWSTemplateFormatVersion: &#39;2010-09-09&#39;<br>Description: &#39;VPC architecture for XYZ Limited web application&#39;<br><br>Resources:<br>  VPC:<br>    Type: &#39;AWS::EC2::VPC&#39;<br>    Properties:<br>      CidrBlock: &#39;10.0.0.0/16&#39;<br>      EnableDnsSupport: true<br>      EnableDnsHostnames: true<br>      Tags:<br>        - Key: Name<br>          Value: &#39;XYZ-VPC&#39;<br><br># Public subnet for the web tier in availability zone A<br>  PublicWebSubnetA:<br>    Type: &#39;AWS::EC2::Subnet&#39;<br>    Properties:<br>      VpcId: !Ref VPC<br>      CidrBlock: &quot;10.0.1.0/24&quot;<br>      AvailabilityZone: !Select [ 0, !GetAZs &#39;&#39;]<br>      MapPublicIpOnLaunch: true<br>      Tags:<br>        - Key: Name<br>          Value: Public-Web-Subnet-A<br><br># Private subnet for the app tier in availability zone A<br>  PrivateAppSubnetA:<br>    Type: &#39;AWS::EC2::Subnet&#39;<br>    Properties: <br>      VpcId: !Ref VPC<br>      CidrBlock: &quot;10.0.3.0/24&quot;<br>      AvailabilityZone: !Select [ 0, !GetAZs &#39;&#39;]<br>      Tags:<br>        - Key: Name<br>          Value: Private-App-Subnet-A  <br><br># Private subnet for the database tier in availability zone A<br>  PrivateDBSubnetA:<br>    Type: &#39;AWS::EC2::Subnet&#39;<br>    Properties:<br>      VpcId: !Ref VPC<br>      CidrBlock: &quot;10.0.5.0/24&quot;<br>      AvailabilityZone: !Select [ 0, !GetAZs &#39;&#39;]<br>      Tags:<br>        - Key: Name<br>          Value: Private-DB-Subnet-A       <br><br># Public subnet for the web tier in availability zone B<br>  PublicWebSubnetB:<br>    Type: &#39;AWS::EC2::Subnet&#39;<br>    Properties:<br>      VpcId: !Ref VPC<br>      CidrBlock: &quot;10.0.2.0/24&quot;<br>      AvailabilityZone: !Select [ 1, !GetAZs &#39;&#39;]<br>      MapPublicIpOnLaunch: true<br>      Tags:<br>        - Key: Name<br>          Value: Public-Web-Subnet-B<br><br># Private subnet for the app tier in availability zone B<br>  PrivateAppSubnetB:<br>    Type: &#39;AWS::EC2::Subnet&#39;<br>    Properties:<br>      VpcId: !Ref VPC<br>      CidrBlock: &quot;10.0.4.0/24&quot;<br>      AvailabilityZone: !Select [ 1, !GetAZs &#39;&#39;]<br>      Tags:<br>        - Key: Name<br>          Value: Private-App-Subnet-B<br><br># Private subnet for the database tier in availability zone B<br>  PrivateDBSubnetB:<br>    Type: &#39;AWS::EC2::Subnet&#39;<br>    Properties:<br>      VpcId: !Ref VPC<br>      CidrBlock: &quot;10.0.6.0/24&quot;<br>      AvailabilityZone: !Select [ 1, !GetAZs &#39;&#39;]<br>      Tags:<br>        - Key: Name<br>          Value: Private-DB-Subnet-B<br><br># Internet gateway for the VPC<br>  InternetGateway:<br>    Type: &#39;AWS::EC2::InternetGateway&#39;<br>    Properties:<br>      Tags:<br>        - Key: Name<br>          Value: &#39;XYZ-IGW&#39;<br>      <br># Attach the internet gateway to the VPC      <br>  InternetGatewayAttachment:<br>    Type: &#39;AWS::EC2::VPCGatewayAttachment&#39;<br>    Properties:<br>      VpcId: !Ref VPC<br>      InternetGatewayId: !Ref InternetGateway<br><br> # Route table for the public web subnets<br>  PublicRouteTable:<br>    Type: &#39;AWS::EC2::RouteTable&#39;<br>    Properties:<br>      VpcId: !Ref VPC<br>      Tags:<br>        - Key: Name<br>          Value: Public-RT<br><br># Route to the internet gateway<br>  PublicRoute:<br>    Type: &#39;AWS::EC2::Route&#39;<br>    DependsOn: InternetGatewayAttachment<br>    Properties:<br>      RouteTableId: !Ref PublicRouteTable<br>      DestinationCidrBlock: &quot;0.0.0.0/0&quot;<br>      GatewayId: !Ref InternetGateway<br><br># Elastic Ipaddress for NatgatewayA<br>  ElasticIPAddressA: <br>    Type: AWS::EC2::EIP<br>    Properties:<br>      Domain: VPC <br><br># Natgateway for puplic web subnet A<br>  NatGatewayA:<br>    Type: &#39;AWS::EC2::NatGateway&#39;<br>    Properties:<br>      AllocationId: !GetAtt ElasticIPAddressA.AllocationId<br>      SubnetId: !Ref PublicWebSubnetA<br>      Tags:<br>        - Key: Name<br>          Value: XYZ-NatA<br><br># Elastic Ipaddress for NatgatewayB<br>  ElasticIPAddressB: <br>    Type: &#39;AWS::EC2::EIP&#39;<br>    Properties:<br>      Domain: VPC <br><br># Natgateway for puplic web subnet B<br>  NatGatewayB:<br>    Type: &#39;AWS::EC2::NatGateway&#39;<br>    Properties:<br>      AllocationId: !GetAtt ElasticIPAddressB.AllocationId<br>      SubnetId: !Ref PublicWebSubnetB<br>      Tags:<br>        - Key: Name<br>          Value: XYZ-NatB<br><br># Route table for the private subnets in availability zone A<br>  PrivateRouteTableA:<br>    Type: &#39;AWS::EC2::RouteTable&#39;<br>    Properties:<br>      VpcId: !Ref VPC<br>      Tags:<br>        - Key: Name<br>          Value: Private-RTA<br><br># Route to natgatewayA<br>  PrivateRouteAppA:<br>    Type: &#39;AWS::EC2::Route&#39;<br>    DependsOn: NatGatewayA<br>    Properties:<br>      RouteTableId: !Ref PrivateRouteTableA<br>      DestinationCidrBlock: &quot;0.0.0.0/0&quot;<br>      NatGatewayId: !Ref NatGatewayA<br><br># Route table for the private subnets in availability zone B<br>  PrivateRouteTableB:<br>    Type: &#39;AWS::EC2::RouteTable&#39;<br>    Properties:<br>      VpcId: !Ref VPC<br>      Tags:<br>        - Key: Name<br>          Value: Private-RTB<br><br># Route to natgatewayB<br>  PrivateRouteAppB:<br>    Type: &#39;AWS::EC2::Route&#39;<br>    DependsOn: NatGatewayB<br>    Properties:<br>      RouteTableId: !Ref PrivateRouteTableB<br>      DestinationCidrBlock: &quot;0.0.0.0/0&quot;<br>      NatGatewayId: !Ref NatGatewayB<br><br># Attaching the public routetable to Public web subnet A<br>  PublicRouteTableAssociationA:<br>    Type: &#39;AWS::EC2::SubnetRouteTableAssociation&#39;<br>    Properties:<br>      SubnetId: !Ref PublicWebSubnetA<br>      RouteTableId: !Ref PublicRouteTable<br><br># Attaching the public routetable to Public web subnet B<br>  PublicRouteTableAssociationB:<br>    Type: &#39;AWS::EC2::SubnetRouteTableAssociation&#39;<br>    Properties:<br>      SubnetId: !Ref PublicWebSubnetB<br>      RouteTableId: !Ref PublicRouteTable<br><br># Attaching the private routetable to Private App subnet A<br>  PrivateRouteTableAssociationA:<br>    Type: &#39;AWS::EC2::SubnetRouteTableAssociation&#39;<br>    Properties:<br>      SubnetId: !Ref PrivateAppSubnetA <br>      RouteTableId: !Ref PrivateRouteTableA<br><br># Attaching the private routetable to Private App subnet B<br>  PrivateRouteTableAssociationB:<br>    Type: &#39;AWS::EC2::SubnetRouteTableAssociation&#39;<br>    Properties:<br>      SubnetId: !Ref PrivateAppSubnetB<br>      RouteTableId: !Ref PrivateRouteTableB          <br><br># Database Server in availability zone A<br>  DBServerA:<br>    Type: &#39;AWS::EC2::Instance&#39;<br>    Properties: <br>      InstanceType: t2.micro<br>      KeyName: yourkeypairname <br>      ImageId: ami-051f8a213df8bc089<br>      SubnetId: !Ref PrivateDBSubnetA<br>      SecurityGroupIds: <br>        - !Ref DbServerSG<br>  <br># Database Server in availability zone B<br>  DBServerB:<br>    Type: &#39;AWS::EC2::Instance&#39;<br>    Properties: <br>      InstanceType: t2.micro<br>      KeyName: yourkeypairname<br>      ImageId: ami-051f8a213df8bc089<br>      SubnetId: !Ref PrivateDBSubnetB<br>      SecurityGroupIds:  <br>        - !Ref DbServerSG<br><br># Web tier security group<br>  WebServerSG:<br>    Type: &#39;AWS::EC2::SecurityGroup&#39;<br>    Properties:<br>      GroupDescription: Security group for web servers<br>      VpcId: !Ref VPC<br>      SecuritygroupIngress:<br>        - IpProtocol: tcp<br>          FromPort: 80<br>          ToPort: 80<br>          CidrIp: &#39;0.0.0.0/0&#39;<br><br># App tier security group<br>  AppServerSG:<br>    Type: &#39;AWS::EC2::SecurityGroup&#39;<br>    Properties:<br>      GroupDescription: Security group for app servers<br>      VpcId: !Ref VPC<br>      SecuritygroupIngress:<br>        - IpProtocol: tcp<br>          FromPort: 80<br>          ToPort: 80<br>          SourceSecurityGroupId: !GetAtt WebServerSG.GroupId<br><br># Database tier security group<br>  DbServerSG:<br>    Type: &#39;AWS::EC2::SecurityGroup&#39;<br>    Properties:<br>      GroupDescription: <br>      VpcId: !Ref VPC<br>      SecuritygroupIngress:<br>        - IpProtocol: tcp<br>          FromPort: 1433<br>          ToPort: 1433<br>          SourceSecurityGroupId: !GetAtt AppServerSG.GroupId</pre><p>List of resources that the template creates:</p><ol><li>VPC (XYZ-VPC)</li></ol><p>2. Subnets:</p><p>- PublicWebSubnetA</p><p>- PrivateAppSubnetA</p><p>- PrivateDBSubnetA</p><p>- PublicWebSubnetB</p><p>- PrivateAppSubnetB</p><p>- PrivateDBSubnetB</p><p>3. Internet Gateway (XYZ-IGW)</p><p>4. Internet Gateway Attachment</p><p>5. Public Route Table (Public-RT)</p><p>6. Route to Internet Gateway</p><p>7. Elastic IP Address for NatGatewayA</p><p>8. NatGatewayA (XYZ-NatA)</p><p>9. Elastic IP Address for NatGatewayB</p><p>10. NatGatewayB (XYZ-NatB)</p><p>11. Private Route Table for Availability Zone A (Private-RTA)</p><p>12. Route to NatGatewayA for Private App Subnet A</p><p>13. Private Route Table for Availability Zone B (Private-RTB)</p><p>14. Route to NatGatewayB for Private App Subnet B</p><p>15. Subnet Route Table Association:</p><p>- PublicRouteTableAssociationA</p><p>- PublicRouteTableAssociationB</p><p>- PrivateRouteTableAssociationA</p><p>- PrivateRouteTableAssociationB</p><p>16. EC2 Instances:</p><p>- DBServerA</p><p>- DBServerB</p><p>17. Security Groups:</p><p>- WebServerSG</p><p>- AppServerSG</p><p>- DbServerSG</p><p>To deploy the stack from the terminal use this command — <strong><em>`aws cloudformation create-stack — stack-name yourstackname_stack — template-body file://yourfilename.yaml’</em></strong></p><p>Thanks for stopping by…see you next time!</p><p>Feel free to contact me to discuss Agile, cloud adoption, or anything tech-related. 🚀<br>You can also connect with me on <a href="https://www.linkedin.com/in/adekunle-adesanmi/">LinkedIn</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2ba2d84b992f" width="1" height="1" alt=""><hr><p><a href="https://towardsaws.com/creating-and-deploying-a-three-tier-aws-architecture-using-cloudformation-my-cloud-journey-week-2ba2d84b992f">Creating and deploying a three-tier AWS Architecture using CloudFormation| My Cloud Journey — Week…</a> was originally published in <a href="https://towardsaws.com/">Towards AWS</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My Cloud Journey | Module 5 Project | VPC Implementation using the AWS Console.]]></title>
            <link>https://medium.com/@kunleadesanmi/my-cloud-journey-module-5-project-vpc-implementation-using-the-aws-console-57bbac25166b?source=rss-56aafda8615b------2</link>
            <guid isPermaLink="false">https://medium.com/p/57bbac25166b</guid>
            <category><![CDATA[aws-vpc]]></category>
            <category><![CDATA[aws-console]]></category>
            <category><![CDATA[ar-cloud]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Adekunle Adesanmi]]></dc:creator>
            <pubDate>Mon, 08 Apr 2024 16:26:34 GMT</pubDate>
            <atom:updated>2024-07-09T15:21:06.334Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/683/1*1xwOamxPYag_UiZejS9yhw.png" /></figure><h3>Building a Three - tier Architecture using the AWS Management Console | My Cloud Journey — Week 5</h3><p>In this article, I will describe the process of building the VPC design discussed in my <a href="https://medium.com/@kunleadesanmi/my-cloud-journey-week-5-project-a5827ea715ce">previous article</a>. This article will primarily cover the manual steps using the AWS management console. In my upcoming article, I will showcase the implementation using Infrastructure as Code (AWS CloudFormation).</p><p>Initially, I intended to include both the manual and Infrastructure as Code implementations in one article. However, I have encountered some dependency issues with the CloudFormation template, and resolving these issues is taking longer than expected.</p><p>Let’s get started!</p><p>There are usually several ways to navigate AWS services. Here are the steps I took to build a simple, secure, and highly available VPC architecture.</p><h4>Creating the VPC using AWS Console</h4><p>Log in to your AWS account (preferably using your IAM credentials). After logging into your account, navigate to the VPC dashboard by clicking on “Services” in the top menu and then locate “VPC” under the “Networking &amp; Content Delivery” section and click on it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/791/1*Qw6263XJsYWswBAF0H5X3g.png" /></figure><h4>Setting Up a Virtual Private Cloud (VPC)</h4><ol><li>Click on the “Create VPC” button in your management console.</li><li>From the list of available VPC templates, select the <strong><em>“VPC with Public and Private Subnets”</em></strong> option. This option is ideal for scenarios where you need both public and private subnets.</li><li>Give your VPC a name that is meaningful to you, such as <strong><em>“XYZ-VPC”</em></strong>.</li><li>Define the CIDR block for your VPC. This is the IP address range that your VPC will use. For example, you can set it to <strong><em>“10.0.0.0/16”.</em></strong></li><li>Next, define the CIDR blocks for your public and private subnets. AWS would have preconfigured them for you but they can be overridden<em>.</em></li><li>Select whether or not you want a NAT Gateway to be created and in which Availabity Zone.</li><li>Once you have filled in all the necessary details, click on the “Create VPC” button to create your VPC along with the specified subnets.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/507/1*v1VpNiOxx2hDrY5Ir1-8Uw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/495/1*ezWGcTXLyO3eoCkPCbCM-g.png" /></figure><h4>Configuring Route Tables</h4><p>To configure route tables in your VPC, follow these steps:</p><ol><li>Navigate to the VPC dashboard and locate the <strong><em>“Route Tables”</em></strong> section.</li><li>You will find the route tables that have been automatically created: one for public subnets and one for each of the private subnets.</li><li>Confirm that there is a route with target ‘internet gateway’, and destination ‘0.0.0.0/0’. If not, click on the <strong><em>“Edit”</em></strong> option to add the route.</li><li>After configuring the route table for public subnets, proceed to edit the route table for private subnets.</li><li>Select the route table for private subnets that require internet access and choose the <strong><em>“Edit”</em></strong> option. In the editing interface, add a route to the NAT gateway (`0.0.0.0/0`).</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/535/1*xw3dmpRXGacXxL86jHv--g.png" /></figure><p><strong>Configure Security Groups and NACLs</strong></p><ol><li>In the VPC dashboard, select <strong><em>“Security Groups”</em></strong> from the left-hand menu.</li><li>Create security groups for your web, application, and database tiers, specifying inbound and outbound rules based on your security requirements.</li><li>In the VPC dashboard, select “Network ACLs” from the left-hand menu.</li><li>Create network ACLs for your public and private subnets, specifying inbound and outbound rules to control traffic flow.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/413/1*MtsHmCTg-lkiC0t187WQrA.png" /></figure><p><strong>Launch Instances and Test Connectivity </strong><br>In the EC2 dashboard, launch instances for your web, application, and database tiers, selecting the appropriate subnets and security groups.</p><ul><li>Access your web application from the internet to ensure it’s accessible.</li><li>Test connectivity between your application and database tiers to ensure proper communication within the VPC.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/609/1*WsCgHXG0BBp-zoZzlCxYbQ.png" /></figure><p>For efficiency, consistency and a whole bunch of other benefits, cloud engineers would be better off using Infrastructure as Code such as Terraform or in the case of AWS, CloudFormation in creating and maintaining cloud infrastructures.</p><p>In the next article I’ll be sharing how I implemented the architecture using CloudFormation.</p><p>Stay tuned!</p><p>Feel free to contact me to discuss Agile, cloud adoption, or anything tech-related. 🚀<br>You can also connect with me on <a href="https://www.linkedin.com/in/adekunle-adesanmi/">LinkedIn</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=57bbac25166b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My Cloud Journey | Module5 project | VPC Design]]></title>
            <link>https://medium.com/@kunleadesanmi/my-cloud-journey-week-5-project-a5827ea715ce?source=rss-56aafda8615b------2</link>
            <guid isPermaLink="false">https://medium.com/p/a5827ea715ce</guid>
            <category><![CDATA[vpc]]></category>
            <category><![CDATA[cloud-architecture]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[high-availability]]></category>
            <dc:creator><![CDATA[Adekunle Adesanmi]]></dc:creator>
            <pubDate>Mon, 25 Mar 2024 16:00:04 GMT</pubDate>
            <atom:updated>2024-07-09T15:21:35.012Z</atom:updated>
            <content:encoded><![CDATA[<h4>Designing a secure and highly available VPC on AWS</h4><p>This task aims to design a secure and highly available VPC architecture on AWS for XYZ Limited.</p><p>I will use my understanding of AWS’s Global Infrastructure, VPC, subnets, route tables, Network Access Control Lists (NACLs), NAT Gateways, to design a cloud environment that is both scalable and secure.</p><h4>Requirements</h4><p>Requirements were given to design a secure VPC architecture on AWS for XYZ Limited&#39;s new web application in a scalable and secure environment with high availability. The architecture must include a public-facing web component accessible from the internet and a backend database accessible only within the VPC.</p><h4>Design</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1021/1*5bGiE0egFvayeZKQuHdw0A.png" /></figure><h4>Summary of Design</h4><p>The VPC architecture consisted of a VPC with a CIDR block of 10.0.0.0/16 to fulfil the requirements given<strong>. </strong>There are six subnets — two for each tier of Web, Application and Database across two Availability Zones (AZs) to ensure fault tolerance and high availability.</p><p>Internet connectivity is established through an Internet Gateway attached to the VPC for public subnets. A NAT Gateway is implemented in one of the public subnets to enable internet access for instances in the private subnets without direct internet exposure.</p><p>Route tables are configured to direct traffic properly, with public route tables directing internet-bound traffic to the Internet Gateway and private route tables directing internet-bound traffic to the NAT Gateway.</p><p>Security measures include Network Access Control Lists (NACLs) and Security Groups to enforce access control policies, ensuring that only necessary traffic is allowed and restricting access to the database servers from the application servers.</p><p>Overall, the VPC architecture design focuses on meeting the requirements for secure internet access, high availability, and restricted access to the database, providing a scalable and robust environment for XYZ Limited&#39;s web application deployment on AWS.</p><p>In future articles, I will share the implementation of this design using the AWS console and IaC (AWS CloudFormation).</p><p>Stay tuned!</p><p>Feel free to contact me to discuss Agile, cloud adoption, or anything tech-related. 🚀<br>You can also connect with me on <a href="https://www.linkedin.com/in/adekunle-adesanmi/">LinkedIn</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a5827ea715ce" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My Cloud Journey — Week 4 | Linux and Bash]]></title>
            <link>https://medium.com/@kunleadesanmi/linux-and-bash-9b5e6917cee5?source=rss-56aafda8615b------2</link>
            <guid isPermaLink="false">https://medium.com/p/9b5e6917cee5</guid>
            <category><![CDATA[bash]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[linux]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[cloud-services]]></category>
            <dc:creator><![CDATA[Adekunle Adesanmi]]></dc:creator>
            <pubDate>Mon, 18 Mar 2024 17:25:38 GMT</pubDate>
            <atom:updated>2024-07-09T15:22:24.892Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/620/1*TqTCIw7Z3WOFQD1gG35OfA.jpeg" /></figure><h4>My Cloud Journey</h4><h4>Summary of lessons learned</h4><p>Welcome to Week 4 of my cloud journey where we looked into Linux and Bash! Shell scripting is important for cloud professionals, as it allows us to work efficiently with operating systems and command-line interfaces. We explored some common topics in shell scripting and I’ll just share a few so, let’s dive right in!</p><p>We started by using EC2 instances on AWS, which opened the doors to the world of Linux-based cloud computing. Through this hands-on experience, we were able to understand how to access and manage Linux-based virtual machines. This was just the first step in our journey, as it provided us with a solid foundation for exploring the Linux file system and using the command-line interface.</p><p><strong>File Operations</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/713/1*anpQEW1SkjHybyMCBzgGIQ.jpeg" /></figure><p>Next, we dived into the world of file operations. To understand the basic structure of the Linux file system, we started at the top-level directory or the root directory, represented by a forward slash (/). This is the starting point for all file paths in Linux. Think of it as the entrance to the library. From there, we’ll encounter important directories such as /home, /etc, and /var, which are like different sections of the maze.</p><p>As we navigate through this hierarchical structure, we will get familiar with some key concepts. Directories are like rooms in the maze, where we can store files and other directories. Files, on the other hand, are like the pieces of information we find in each room. Symbolic links are like shortcuts that help us move quickly between different rooms.</p><p>To help us on this journey, we have a set of basic commands at our disposal. For example, the<strong><em> `pwd`</em></strong> command allows us to see which directory we are currently in, like a map that shows our current location. The `cd` command helps us move from one directory to another, just like taking a turn in the maze. And the <strong><em>`ls`</em></strong> command lets us see what files and directories are inside the current directory, like a flashlight that helps us see what’s around us in the maze. We also learned how to create, delete, copy, and move files and folders using commands.</p><p>With these commands and my growing understanding of the Linux file system, I confidently explored further.</p><p>One of the fundamental commands we learned is <strong><em>`touch`</em></strong>, which is for creating new files. Creating files is just the beginning. Next comes editing of files. We learned about two popular text editors, namely `nano` and `vim`. They allow you to add, delete, and modify text within a file, giving you complete control over its content.</p><p>To put our skills to the test, we engaged in practical exercises that provided hands-on experience, where we could apply what we learned in a real-world setting. These exercises helped us solidify our understanding of file creation, editing, and navigation within the Linux file system.</p><h4>File Permissions</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kPHd4mJduizCUIGXG86sIw.jpeg" /></figure><p>In Linux, each file and directory has a set of permissions that determine who can read, write, or execute them. Think of it like a lock on a door — the permissions decide who can enter the room. The three main categories of permissions are owner, group, and others.</p><p>The owner is the person who created the file or directory. They have the highest level of control and can read, write, and execute the file. The group is a collection of users who have similar access rights. The others category includes everyone else who is not the owner or in the group.</p><p>To view the permissions of a file or directory, you can use the <strong><em>`ls -l`</em></strong> command. This will display a detailed list of files and directories along with their permissions. For example, if you see <strong><em>`-rw-r — r — `</em></strong>, it means that the owner has read and write permissions, while the group and others can only read the file.</p><p>To change the permissions of a file or directory, you can use the <strong><em>`chmod`</em></strong> command. For example, ‘<strong><em>chmod 755&#39;</em></strong> will give read write, and execute to the owner of the file and read and execute to the group and others.</p><p>Throughout the lessons, we encountered real-world examples and scenarios that helped us grasp the concepts better. For instance, imagine you have a shared folder on a cloud server where multiple users need to collaborate on a project. By understanding file permissions, you can ensure that only authorized users can access and modify the files, while others can only view them. It’s like having a secure vault where only trusted individuals have the key to unlock it.</p><p>By the end of Week 4, I had gained a solid foundation in cloud computing and system administration. I now have the skills and technical prowess to confidently tackle the challenges and opportunities that await me in the ever-evolving world of cloud technology.</p><p>Feel free to contact me to discuss Agile, cloud adoption, or anything tech-related. 🚀<br>You can also connect with me on <a href="https://www.linkedin.com/in/adekunle-adesanmi/">LinkedIn</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9b5e6917cee5" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>