Forem: Abdullateef OGUNDIPE

My Experience at AWS Summit Paris 2026

Abdullateef OGUNDIPE — Sat, 04 Apr 2026 18:18:50 +0000

I recently attended the AWS Summit Paris 2026, which took place on April 1st at the Palais des Congrès de Paris. This was my second consecutive year attending, and honestly, it felt even more impactful this time around.

I came in with a clear intention: to stay updated on the latest developments in AWS, especially around AI, while also taking the opportunity to network and better understand how I can grow my skills within the ecosystem. Like last year, the atmosphere was vibrant, familiar faces, new connections, and a strong sense of community. AWS did a great job with coordination, and the venue was filled with multiple floors dedicated to different tracks and industries, making it easy to explore based on your interests.

I arrived quite early because I didn’t want to miss attending the keynote at the main hall this time like I did last year. I managed to get a seat within the first rows of the main auditorium, which made the experience even more immersive.

The keynote opened with Amélie Clugnet, Director of AWS France, who welcomed everyone with a lot of energy. She highlighted that this year’s summit was special, as AWS is celebrating 20 years. She also shared some key figures about AWS’s presence in France, including major investments, a growing workforce, and a strong partner ecosystem.

One concept that stood out early on was the idea of structuring AWS strategy like an aerospace system, "Arienspace", something she described in terms of navigation, structure, and propulsion. For navigation, she pointed to services like Amazon Bedrock, while the structure was tied to foundational systems like AWS Nitro. It was a simple but powerful way to frame how AWS is thinking about the future of cloud and AI.

Next, Stéphane Israël took the stage to talk about the AWS European Sovereign Cloud. He emphasized the importance of sovereignty in cloud infrastructure, mentioning significant investment and the idea of a fully independent cloud structure designed specifically for Europe.

One of the most memorable moments for me came when Stephan Hadinger, CTO of AWS France, stepped on stage. He framed his talk around two simple but powerful questions: “Why?” and “Why not?” That really stuck with me. It shifted the perspective from just building solutions to rethinking what’s actually possible.

He spoke about having the right tools to build modern applications, and this is where agentic AI came into focus. Tools like Kiro were introduced as a way to go from prototype to production using AI agents. There was also mention of solutions that help move from insights to actions much faster, reinforcing how AWS is pushing toward more autonomous and intelligent systems.

The keynote also featured real-world use cases from companies. Stéphane Baumier shared how Canal+ has been scaling its platform to handle massive live audiences, reaching millions of viewers while maintaining operational excellence. It was interesting to see how these architectures are applied in high-demand environments.

Later, Marc Roussel talked about deploying AI at scale within organizations, especially the challenges of moving from experimentation to production. And Gautier Cloix brought a slightly different perspective, focusing on how AI, especially agent-based systems, can be used not just for efficiency, but to create real-world impact.

Another key takeaway came from Julien Lépine, who emphasized that AWS positions itself as the best place to build by combining infrastructure, data, and inference. That idea tied together a lot of what was discussed throughout the keynote everything from compute with EC2 and serverless with Lambda to data and AI integration.

One quote from the keynote really stayed with me:

“Don’t accept the limitations of today as the boundaries of tomorrow. We are just getting started.”

After the keynote, I spent most of my time exploring the expo floors, especially the areas focused on AI innovation, training, and builder communities. This was probably the most valuable part of the event for me personally.

I had a really useful conversation with the AWS Training team, where I discussed my current certification path and got advice on how to move forward, particularly toward AI-focused certifications. I also spoke with teams working on robotics navigation, something very close to my current research—which made the experience even more relevant.

I got introduced to Strands Robotics and learned more about how to get started in that space, which was exciting. Beyond that, I visited several other stands across different floors, including AWS partners working on security and observability in production systems. Each conversation added a new layer of perspective.

Unfortunately, I had to leave a bit early to catch my trip back, but even with that, the experience was incredibly valuable. Walking away from the event, I have a much clearer focus. I want to go deeper into AWS AI services, explore agent-based systems like those discussed during the keynote, continue my work in robotics, and strengthen my certification path—especially in the AI track.

AWS Summit Paris wasn’t just another tech event for me. It was a moment to reflect, learn, and reset my direction.

S2: Setting Up the Foundations — My Robotics Environment Journey

Abdullateef OGUNDIPE — Sat, 04 Apr 2026 11:28:02 +0000

Session 2 felt like the real beginning, even though we still hadn’t built a robot yet. This time, it was about something less exciting on the surface, but absolutely critical, setting up the environment.

The tools we would be working with were introduced gradually. At the core of everything was ROS 2, supported by tools like Gazebo and RViz for simulation and visualization. Then came the programming side with Python and C++, with Rust mentioned as a bonus track for those who want to go further. We also touched on development tools like Git, GitHub, and VS Code, with a glimpse into things like Docker and OpenCV that we may explore later.

But the real conversation wasn’t just about tools. It was about something deeper, the environment problem.

In robotics, your environment is not just where you work; it determines whether things work at all. A small mismatch in versions, configurations, or dependencies can break everything. It became clear that learning how to set up and manage your own environment is not optional. It is a core skill for any robotics engineer.

Rather than handing us a ready-made setup, the facilitators guided us through doing it ourselves. That decision alone changed how I approached the session. It wasn’t just installation, it was training in independence.

Then came one of the more memorable statements from Bakel Bakel:

“Throw your Windows out of the windows.”

It got a laugh, but the message behind it was serious. Linux, especially Ubuntu, is the standard in robotics. Most tools, particularly ROS 2, are built with Linux in mind. If you want fewer problems and better compatibility, you align yourself with that ecosystem.

That said, the approach wasn’t rigid. We were given multiple pathways depending on our systems and preferences. You could switch fully to Ubuntu, install it alongside Windows, or use WSL to run Ubuntu within Windows. For Mac users, the response was more playful, “see me in my office”...but it still hinted at the extra considerations involved.

What followed over the next sessions was a step-by-step journey through these options. Starting with WSL, then moving into dual boot setups, and even special considerations for different systems.

For me, I decided to take a slightly unconventional approach.

I set up two environments.

One is Ubuntu 24.04 running through WSL on a Windows 11 system, using ROS Jazzy. The other is a dual-boot setup with Ubuntu 22.04 on a Windows 10 machine, running ROS Humble. This decision was not random. From my past research and implementation experience, I have learned that small differences that seem insignificant at first can become major obstacles later.

Having two environments allows me to balance flexibility and performance. The WSL setup gives me convenience and access within my main system, while the dual-boot setup aligns more closely with the recommendation for the robotics workshop.

It might seem like extra work, but for me, it is a way of reducing future frustration and ensuring that I can follow along properly while also experimenting beyond the basics.

By the end of the session, which took several days, I had successfully installed the necessary tools and prepared both environments. It felt less like a technical achievement and more like laying the foundation for everything that will come next.

There is still a lot I don’t know. In fact, it feels like I am stepping deeper into what I would describe as the space between the known unknown and the unknown known.

But this time, I am approaching it with more structure, more awareness, and a bit more patience.

Now, everything is set.

Let’s see how things unfold from here.

À bientôt.

S1: My Aurora Robotics 2.0 Experience

Abdullateef OGUNDIPE — Sat, 04 Apr 2026 10:58:09 +0000

Over the past few years, I have found myself constantly asking one question: where do all my interests truly meet?

My journey has taken me through electrical and electronic engineering, with a focus on control systems, into artificial intelligence, and then into cloud computing. For a while, these felt like separate paths I was exploring one after the other. But with time, a pattern started to emerge. There was one field that quietly sat at the center of all of them—robotics.

It made sense the more I thought about it. Robotics brings together control systems, especially the nonlinear aspects I have always been interested in. It creates space for artificial intelligence to play a real role in perception and decision-making. And with the direction technology is heading, cloud computing becomes an added advantage for scaling and coordination. It wasn’t just another field; it felt like a natural convergence point.

After spending some time working in the automation and telecommunications industries, I returned to research about few years ago. My current doctoral work focuses on designing control systems for coordinating multi-agent systems, particularly mobile robots operating within a shared environment using model predictive control. That experience, combined with several robotics courses I took along the way, opened my eyes to both the beauty and the difficulty of the field.

I began to appreciate the depth of mathematics behind control systems, but also the gap that often exists between theory and real-world implementation. I could follow tutorials, understand parts of the code, and even replicate certain results using ROS-based mobile robot platforms. With the help of available resources and even AI tools, I managed to get some experimental setups running. But deep down, I knew something was missing.

There were moments I struggled, not because I wasn’t trying, but because I didn’t fully understand some of the fundamentals. I often felt like I was building on top of incomplete knowledge, and that made me question whether there were better, more structured ways to approach what I was doing.

At the same time, the field itself is evolving quickly. Tools like ROS2 are becoming essential, and strong programming skills in languages like Python and C++ are no longer optional. It became clear to me that if I wanted to grow properly in robotics, I needed to go back and strengthen my foundation, this time with more structure and intention.

That was when I came across Aurora Robotics 2.0. It happened almost by chance, just a day or two before the training was about to begin. I didn’t overthink it. I signed up immediately. And alongside that decision, I made another one, to document the journey as it unfolds.

The first day turned out to be quite different from what I expected. There were no robots involved. No lines of code written. Yet, it was one of the most important sessions I have had in a while.

The orientation introduced us to the structure of the program and the people behind it, including Bakel Bakel and the rest of the team. Listening to them and reflecting on their journeys was surprisingly grounding. It reminded me that learning is not always about how far you have gone, but about how well you understand what you are doing.

At some point during the session, I found myself reflecting on a simple idea that stayed with me:

Knowledge is not about age or level of education. It’s about whether you know it or you don’t.

It felt obvious, almost too simple, but also very honest. A reminder to focus less on appearances and more on actual understanding.

We were also introduced to the way the training is structured, moving from concepts and mathematics into code and simulation, and eventually into real-world application. That progression immediately resonated with me because it directly addresses the gap I have been experiencing in my own learning.

Beyond the technical direction, there was also a strong emphasis on mindset. Curiosity was encouraged over perfection. We were reminded that failure is part of the process, not something to avoid. The idea of failing fast and learning faster stood out, as well as the importance of consistency over short bursts of intense effort. There was also a clear message about collaboration, that robotics is not something you do alone.

By the end of the session, I realized that what we had gained was not technical knowledge, but something just as important—a reset in how to approach the journey ahead.

We also briefly touched on the tools we will be using, which will be explored more deeply in the next session. That will likely be the point where things start becoming more hands-on.

For now, this feels like the right starting point. Not with code or hardware, but with clarity.

This is Day 1 of my robotics journey with Aurora Robotics.

Why Cloud Skills Matter in 2025 and Beyond

Abdullateef OGUNDIPE — Wed, 31 Dec 2025 15:37:40 +0000

Is Cloud Computing… in the Sky?

“Cloud computing is like… stuff happening in the clouds, right? Rain, thunder, lightning?”

“Haha, no! It’s not weather. It’s actually powerful computers and data centers you can use over the internet.”

“So it’s not magic floating in the sky?!”

“Exactly. And once you understand it, you’ll see why this ‘invisible cloud’ is shaping the future.”

This simple conversation captures a misunderstanding that still exists today. Cloud computing sounds abstract, almost mystical, but in reality it is one of the most practical, impactful technologies of our time. As we move deeper into 2025 and beyond, cloud skills are no longer optional. They are foundational.

What Cloud Computing Really Is?

Cloud computing is the on-demand delivery of computing resources such as servers, databases, storage, networking, applications, and AI services over the internet. Instead of buying and maintaining physical hardware, you rent what you need, when you need it, and pay only for what you use
.

Think of it like electricity. You don’t own a power station at home. You just plug in your devices and pay for the energy you consume. Cloud computing works the same way, but for technology infrastructure.

This model has transformed how software is built, deployed, and scaled across the world.

Why Amazon Web Services Dominates the Cloud

Amazon Web Services, commonly known as AWS, is the world’s leading cloud computing platform. It serves millions of customers, including startups, large enterprises, universities, and governments.

AWS offers over 200 services covering areas such as compute, storage, databases, machine learning, security, networking, analytics, and Internet of Things. This massive ecosystem allows organizations to build almost anything, from simple websites to global-scale AI systems.

One of the biggest reasons AWS is so widely adopted is cost efficiency. There is no upfront hardware cost, no data center maintenance, and no long-term commitment required to get started. Teams can experiment, fail fast, and innovate without massive financial risk.

The Real Benefits of Cloud Computing

Cloud computing is not just a technical upgrade. It fundamentally changes how organizations operate.
Flexibility and scalability are at the core. You can scale resources up during peak usage and scale them down when demand drops. This is something traditional infrastructure struggles to achieve.
Reliability and security are also major advantages. Cloud providers invest heavily in global infrastructure, redundancy, compliance, and security tooling that most individual companies could never afford on their own.
Collaboration becomes easier too. Teams can work from different locations, access shared resources instantly, and deploy updates without waiting for physical hardware changes. Most importantly, cloud enables fast innovation and deployment. New ideas can move from prototype to production in days instead of months.

Why Cloud Skills Matter More Than Ever in 2025

Cloud skills in 2025 and beyond are not just a technical advantage. They are a strategic necessity.

Modern technologies such as artificial intelligence, machine learning, big data analytics, serverless computing, and cybersecurity all run on cloud platforms. If you want to work with these technologies, cloud knowledge is unavoidable.

Whether you are a software engineer, data scientist, security analyst, DevOps engineer, or IT manager, understanding cloud computing gives you the ability to design scalable systems, optimize costs, and build solutions that actually work in the real world.

Cloud skills also unlock career mobility. They allow professionals to move across industries, roles, and even countries, because cloud platforms are globally standardized.

As one quote puts it:

cloud skills are not just about keeping up with technology. They are about building the future of technology.

Getting Started with Cloud and AI

The good news is that there is a clear learning path for beginners.

A great starting point is the AWS Certified Cloud Practitioner or AWS AI Practitioner certification. These certifications focus on foundational knowledge, cloud concepts, pricing models, security basics, and core services.

Once you are comfortable with the basics, the next step is to move into associate-level certifications such as Solutions Architect Associate or Developer Associate. These go deeper into system design, application deployment, and best practices.

For advanced learners, AWS Specialty Certifications allow you to focus on areas like machine learning, security, data analytics, or networking.

Learning Resources That Actually Help

There are many high-quality resources available to build cloud skills effectively.

AWS Skill Builder provides official learning paths, labs, and exam preparation materials directly from AWS.
Platforms like A Cloud Guru and Coursera offer structured courses with hands-on labs and real-world scenarios.
Hands-on projects are critical. Building small applications, deploying them to the cloud, breaking things, and fixing them is where real learning happens.

The Power of Community and Continuous Learning

Cloud computing evolves rapidly. New services, features, and best practices are introduced constantly. Staying relevant requires continuous learning.

Joining cloud communities can make a huge difference. Local groups, university cloud clubs, and online communities provide mentorship, shared learning, and motivation. Communities like AWS user groups or campus cloud clubs help turn learning into a collaborative experience rather than a solo struggle.

Following industry blogs, attending webinars, and experimenting with new services keeps your skills fresh and relevant.

Complementary Skills That Multiply Your Impact

Cloud skills become even more powerful when combined with other competencies.

Basic programming skills help you automate infrastructure and build scalable applications.

Security knowledge ensures that what you build is safe and compliant.

Data analytics skills allow you to extract insights from cloud-hosted data.

Together, these skills turn you from someone who uses the cloud into someone who builds meaningful solutions on it.

Final Thoughts

Cloud computing is not magic in the sky. It is real infrastructure powering real products used by billions of people every day.

In 2025 and beyond, cloud skills represent opportunity, innovation, and career growth. They give you the tools to build, scale, and secure the technology that defines our modern world.

Whether you are just starting out or looking to level up, investing in cloud skills today is one of the smartest decisions you can make for your future.

The cloud is invisible, but its impact is everywhere.

AI Agent with Amazon Bedrock: A Brief Guide

Abdullateef OGUNDIPE — Wed, 31 Dec 2025 15:27:04 +0000

A Guide on AI Agent with Amazon Bedrock

From confused chatbots to intelligent AI agents — a step-by-step journey using Amazon Bedrock.

Introduction: When Chatbots Get It Wrong

Imagine asking a customer support chatbot a simple question — "I want to return my order" — and receiving a completely irrelevant response. Frustrating, right?

Despite the explosion of AI tools, many teams still struggle to build useful, context-aware AI assistants. The problem isn’t the lack of models — it’s the complexity of integration.

This learning post shows a brief guide on how to build powerful AI agent using

Amazon Bedrock, focusing on concepts, architecture, and a practical implementation path.

What You’ll Learn

By the end of this post, you will:

Understand what Amazon Bedrock is and why it’s different
Learn what makes an AI agent (beyond just text generation)
Design a real-world AI agent architecture
Build a simple AI assistant using AWS services
Discover practical use cases and next steps

What Is Amazon Bedrock?

Amazon Bedrock is a fully managed, serverless service that allows you to build generative AI applications using foundation models (FMs) from leading providers such as:

Anthropic (Claude)
Meta (Llama)
AI21 Labs
Amazon Titan

Why Bedrock Matters

🚫 No infrastructure management
🚫 No model training required
✅ Enterprise-grade security
✅ Easy integration with AWS services

You focus on logic and experience — AWS handles the heavy lifting.

Why AI Agents Matter Today

AI agents are more than chatbots. They:

Understand natural language
Maintain context
Take actions (via APIs or functions)
Reduce manual workflows

Real-World Agent Applications

Customer support assistants
HR onboarding bots
Internal knowledge search
Healthcare triage systems
Legal document summarization

Generative AI vs AI Agents

Generative AI	AI Agent
Generates text	Understands intent
Stateless	Context-aware
No actions	Calls APIs / functions
Output-only	Decision + execution

An AI agent combines reasoning, memory, and action.

Manual vs AI Agent: A Return Process Example

🧍 Manual Return (Physical Store)

Walk to the store
Explain the issue
Clerk checks receipt
Forms are filled
Long waiting time

🤖 AI Agent Return (Digital Assistant)

"I want to return order 12345 because it’s broken"

AI understands intent instantly
Extracts order ID and reason
Calls backend return API
Confirms return — instantly

This is the power of AI agents.

Core Concepts Behind AI Agents

To build an AI agent, you need more than a model:

Natural Language Processing (NLP)
Prompt Engineering
Context & Memory Management
Knowledge Bases & Embeddings
Retrieval-Augmented Generation (RAG)

Amazon Bedrock supports these building blocks seamlessly.

What We’ll Build

We’ll create a simple AI agent that:

Uses Anthropic Claude via Amazon Bedrock
Accepts user input from a web UI
Processes requests with AWS Lambda
Exposes an API using API Gateway
Returns intelligent, contextual responses

Architecture Overview

Frontend

HTML / CSS / JavaScript (or chat widget)

⬇️

API Gateway

Secure REST endpoint

⬇️

AWS Lambda

Handles logic
Calls Amazon Bedrock

⬇️

Amazon Bedrock

Foundation model inference

Step-by-Step Build Summary

1️⃣ Choose a Foundation Model

Select Claude or Titan from Amazon Bedrock

2️⃣ Add a Knowledge Base (Optional)

Store documents in Amazon S3
Enable semantic search via embeddings

3️⃣ Create a Lambda Function

Use boto3 to invoke Bedrock
Handle prompt and response formatting

4️⃣ Build the Frontend

Simple chat interface
Send user input to API Gateway

Video link for step by step implementation Step by Step implemetation

Presentation: 10:00 - 42:00
Implementation : 43:00 -

Tools & Services Used

Amazon Bedrock – foundation models
AWS Lambda – backend logic
Amazon API Gateway – REST API
AWS IAM – secure permissions
HTML/CSS/JavaScript – frontend UI

Real-World Applications

🏛️ Citizen service chatbots
🏥 Healthcare assistants
⚖️ Legal research tools
🧑‍💼 HR knowledge bots

AI agents are becoming core digital employees.

Key Learning Resources

Amazon Bedrock Documentation
AWS IAM Best Practices
Lambda + API Gateway Integration

https://docs.aws.amazon.com/bedrock/latest/userguide/what-is-bedrock.htm
https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html
https://docs.aws.amazon.com/lambda/latest/dg/services-apigateway.html
https://www.youtube.com/watch?v=JBXSwvdJJ6Q

Start simple. Experiment fast. Let users feel the magic.

Amazon Bedrock YouTube Demos

Final Thoughts

AI agents are no longer "future tech" — they’re today’s advantage.

Amazon Bedrock removes the hardest barriers to entry, allowing developers to focus on use cases, logic, and user experience.

Start simple. Experiment fast. Let users feel the magic.

👋 Thanks for reading!

If you found this helpful, consider:

Leaving a reaction
Sharing with your team
Following for more AWS & AI learning posts

Happy building 🚀

Day 7: Challenges, Mitigations, and Cost Analysis for the Migration

Abdullateef OGUNDIPE — Sun, 08 Dec 2024 09:00:59 +0000

Recap of Day 6

Yesterday, we delved into the world of monitoring and troubleshooting with AWS CloudWatch, ensuring that the LimitlessAO Power Solutions website remains accessible, secure, and high-performing. By tracking key metrics and setting up alerts, we equipped ourselves with tools to handle potential issues proactively. Today, we will wrap up this series by reflecting on the challenges faced during the migration, exploring strategies to mitigate these issues, and analyzing the cost of running this architecture on AWS.

Challenges Encountered During Migration

Website migration to AWS, while highly rewarding, is not without its hurdles. Here are some challenges you might encounter:

DNS Propagation Delays

DNS changes, such as updating name servers or creating alias records, can take several hours to propagate worldwide. This delay may temporarily affect website accessibility.
Mitigation: Plan the migration during non-peak hours to minimize the impact on users. Inform users of potential downtime beforehand.

SSL/TLS Configuration Issues

Configuring HTTPS using AWS Certificate Manager can sometimes lead to errors, especially if the domain validation process is incomplete or the certificate is not correctly associated with CloudFront.
Mitigation: Ensure all domain validation steps are completed promptly. Verify that the certificate is correctly attached to your CloudFront distribution.

Access and Permissions Management

Misconfigured IAM permissions can hinder setup processes, such as creating S3 buckets or enabling CloudFront metrics in CloudWatch.
Mitigation: Follow the principle of least privilege and ensure that your IAM policies are explicitly tailored to the tasks at hand.

Cost Overruns

Without proper monitoring, AWS resources can incur unexpected costs, such as high data transfer rates or unnecessary service usage.
Mitigation: Use AWS Billing and Cost Management tools to monitor and control costs. Set up billing alarms to avoid surprises.

Content Delivery Issues

If objects in S3 are not publicly accessible or Cache-Control headers are improperly configured, CloudFront may fail to serve content efficiently.
Mitigation: Check bucket permissions and ensure proper cache settings for optimal delivery performance.

Cost Analysis

The total cost of running the LimitlessAO Power Solutions website on AWS depends on several factors, including traffic volume, storage needs, and service configurations. Here’s a breakdown of expected costs:

S3 (Storage and Requests)

Storage: $0.023 per GB for the first 50 TB per month (Standard Tier).
GET and PUT Requests: $0.0004 per 1,000 requests.

CloudFront (Data Transfer and Requests)

Data Transfer Out: $0.085 per GB (up to 10 TB).
HTTP/HTTPS Requests: $0.0075 per 10,000 requests.

Route 53 (DNS Management)

Hosted Zone: $0.50 per month per hosted zone.
DNS Queries: $0.40 per million queries (first billion queries per month).

CloudWatch (Monitoring and Logs)

Basic Metrics: Free.
Detailed Metrics: $0.30 per metric per month.
Logs: $0.50 per GB ingested.

AWS Certificate Manager (SSL/TLS)

Free for public certificates used with integrated AWS services.

Estimated Monthly Cost
For a small to medium-sized static website with moderate traffic, costs typically range from $5 to $20 per month. For higher traffic volumes, expect a proportionate increase.

Closing Thoughts on Hosting a Static Website

The migration of the LimitlessAO Power Solutions website to AWS has demonstrated how the cloud empowers businesses with scalability, security, and global reach. While challenges are inevitable, AWS offers robust tools and best practices to overcome them. The result is a reliable and high-performing architecture capable of serving users across the globe.

What’s Next?

While we’ve successfully migrated a static website, the dynamic nature of modern web applications demands more complexity. In our next series, we’ll explore how to host a dynamic website on AWS. We’ll cover integrating databases, enabling server-side processing with services like AWS Lambda or EC2, and implementing advanced monitoring and scaling strategies.

"The cloud isn’t just about technology; it’s about unlocking potential for innovation and growth."

Stay tuned—LimitlessAO is just getting started!

Day 6: Monitoring and Troubleshooting Your Website with AWS CloudWatch

Abdullateef OGUNDIPE — Sat, 07 Dec 2024 20:14:24 +0000

Recap of Day 5

Yesterday, we successfully configured Route 53 to map the custom domain, www.limitlessao.com, to the CloudFront distribution. This made the LimitlessAO Power Solutions website accessible via a user-friendly and secure domain name. Today, we’ll focus on monitoring the website’s performance and diagnosing potential issues using AWS CloudWatch. CloudWatch provides insightful metrics, logs, and alarms to help ensure the website is always up and running.

Why Use AWS CloudWatch?

AWS CloudWatch is a monitoring and observability service that provides real-time insights into your infrastructure and application performance. For the LimitlessAO website, CloudWatch will allow us to:

Monitor key metrics like latency, error rates, and data transfer.
Set up alarms for unusual traffic or performance issues.
Review logs to diagnose and resolve issues proactively.

Step-by-Step Implementation

Step 1: Enable CloudFront Metrics in CloudWatch
CloudFront integrates seamlessly with CloudWatch to provide detailed metrics. To enable these metrics:

Navigate to the CloudFront Console.
Select your CloudFront distribution from the list.
Click on the Telemetry tab, then scroll down to the Monitoring section.
Click Manage additional metrics to enable more detailed or real-time metrics.
Select the metrics you wish to enable (e.g., request count, error rates, cache statistics).
Save your changes to apply the settings.
For additional guidance, refer to the AWS documentation on CloudFront Monitoring.

Step 2: View Metrics in CloudWatch

Navigate to the CloudWatch Console.
Go to Metrics and select CloudFront under the available namespaces.
Review important metrics such as:
Requests: Total number of HTTP/HTTPS requests.
4xx/5xx Errors: Client and server error rates.
Cache Hit Ratio: Percentage of requests served from CloudFront cache.
Latency: Time taken to serve requests.

Step 3: Set Up Alarms for Key Metrics

To be notified of potential issues, set up CloudWatch Alarms:
In the CloudWatch Console, go to Alarms and click Create Alarm.
Select a metric (e.g., 5xxErrorRate) and set a threshold.
Example: Trigger an alarm if the 5xx error rate exceeds 5% for 5 minutes.
Configure an action:
Send a notification via SNS (Simple Notification Service) to your email.
Review and create the alarm. For further guidance: Creating CloudWatch Alarms.

Step 4: Analyze Logs for Troubleshooting

CloudFront logs can provide detailed information about requests and errors
In the CloudFront Console, go to your distribution and enable Access Logs.
Specify an S3 bucket to store the logs.
Use CloudWatch Logs Insights for deeper analysis:
Navigate to CloudWatch Logs and query the logs to identify anomalies. For more information: Analyzing CloudFront Logs.

Step 5: Monitor S3 Metrics

Go to the S3 Console.
Under the Metrics tab for your bucket, monitor:
Number of Requests: Traffic to the bucket.
Data Transfer Out: Bandwidth usage.
First Byte Latency: Speed of responses.
You can also set alarms for these metrics in CloudWatch.

"Monitoring is not just about detecting issues; it’s about ensuring uninterrupted excellence."

What’s Next?

With CloudWatch configured, you now have a robust monitoring system to track your website’s performance and resolve potential issues. Tomorrow, in our final post, we’ll discuss potential problems that might arise during migration, their mitigation strategies, and analyze the cost of running this architecture on AWS.

Stay tuned!
LimitlessAO

Day 5: Configuring Route 53 to Map Your Domain to the CloudFront Distribution

Abdullateef OGUNDIPE — Fri, 06 Dec 2024 08:27:03 +0000

Recap of Day 4

Yesterday, we set up CloudFront to serve as the content delivery network for the LimitlessAO Power Solutions website, ensuring fast global access. Additionally, we secured the website with an SSL certificate from AWS Certificate Manager, enabling HTTPS for secure communication. Today, we’ll finalize the website’s accessibility by using Route 53 to map the website's custom domain (www.limitlessao.com) to the CloudFront distribution.

Why Use Route 53?

Route 53 is Amazon's DNS web service, designed for high availability and scalability. It allows you to route internet traffic to AWS resources or other destinations effectively. By configuring Route 53, visitors can access your website using a user-friendly domain name rather than a long CloudFront URL.

Step-by-Step Implementation

Step 1: Register a Domain or Use an Existing One

If you don’t have a domain, you can register one via Route 53
To register a domain with Route 53, navigate to the Route 53 Console, click Register Domain, and follow the steps.
If you already own a domain, confirm that it is correctly set up for DNS management. For more information: Registering a Domain with Route 53.

Step 2: Create a Hosted Zone in Route 53

In the Route 53 Console, navigate to Hosted Zones.
Click Create Hosted Zone and provide the following:
Domain Name: Enter your domain name (e.g., limitlessao.com).
Type: Select Public Hosted Zone.
Note the Name Server (NS) Records provided by Route 53. These will need to be updated with your domain registrar if you’re using a third-party domain.

Step 3: Create Alias Records to Route Traffic

In your Route 53 Hosted Zone, create two records:
A Record for the Root Domain:
Record Name: Leave blank or use @.
Alias: Yes
Alias Target: Select your CloudFront distribution.
CNAME Record for the Subdomain (www):
Record Name: www.
Alias: Yes
Alias Target: Select your CloudFront distribution.
Save the records.
For more details: Routing Traffic to a CloudFront Distribution.

Step 4: Test the Domain

After the DNS changes propagate, open your browser and enter your domain name (www.limitlessao.com).
The website should now load via CloudFront with HTTPS enabled.
If there are issues, check the status of your DNS records in Route 53 and the CloudFront distribution.

"A user-friendly domain is the doorway to your digital presence—make it seamless and secure."

What’s Next?
With the domain now mapped to the CloudFront distribution, the website migration process is almost complete. Tomorrow, we’ll focus on monitoring and troubleshooting the website using AWS CloudWatch to ensure optimal performance and reliability.

Stay tuned!
LimitlessAO

Day 4: Configuring CloudFront and Securing Your Website with HTTPS

Abdullateef OGUNDIPE — Thu, 05 Dec 2024 08:00:57 +0000

Recap of Day 3

Yesterday, we laid the groundwork by creating a secure AWS environment and setting up an S3 bucket to host the static files for the LimitlessAO Power Solutions website. We also enabled static website hosting, providing a temporary endpoint URL for accessing the site. Today, we’ll take it a step further by integrating CloudFront, a Content Delivery Network (CDN), to ensure fast and reliable delivery of website content worldwide. Additionally, we’ll configure an SSL certificate using AWS Certificate Manager (ACM) to secure the website with HTTPS.

Why CloudFront and HTTPS?

CloudFront enhances the performance and reliability of your website by caching content across a global network of edge locations. This minimizes latency for users regardless of their location. Adding HTTPS with an SSL certificate ensures encrypted communication between your website and its visitors, boosting both security and trust.

Step-by-Step Implementation

Step 1: Configure CloudFront

Go to the CloudFront Management Console.
Click Create Distribution and select Web Distribution.
Set the following configuration:
Origin Domain Name: Select your S3 bucket from the dropdown list.
Origin Access Control (OAC): Create an OAC to restrict direct access to your S3 bucket.

Viewer Protocol Policy: Select Redirect HTTP to HTTPS to enforce secure connections.

Cache Behavior: Leave the defaults or customize based on your caching needs.
Save the configuration and wait for the distribution to deploy (this might take a few minutes).

Step 2: Restrict Public Access to the S3 Bucket

Once CloudFront is set up, we need to ensure that the S3 bucket cannot be accessed directly:
Go to the Permissions tab of your S3 bucket.
Edit the Bucket Policy to allow only access from CloudFront using the OAC created earlier.
Save the changes.

Step 3: Configure HTTPS with ACM

Navigate to the AWS Certificate Manager.
Request a public certificate:
Enter your domain name (e.g., www.limitlessao-website.com).
Choose DNS Validation for a straightforward process.
After requesting the certificate, ACM will provide a CNAME record to add to your DNS configuration.
Use Route 53 (or your DNS provider) to create a CNAME record for validation.
Once validated, the certificate status will change to Issued.

Step 4: Associate the SSL Certificate with CloudFront

Go back to your CloudFront distribution settings.
Edit the SSL Certificate section under the Distribution Settings:
Select Custom SSL Certificate and choose the certificate issued by ACM.
Save the configuration and allow the distribution to update.

"Security is not just a feature—it’s the foundation for trust in the digital world."

What’s Next?
With CloudFront and HTTPS in place, the website is optimized for performance and secured for its users. Tomorrow, we’ll integrate Route 53 to map your custom domain to the CloudFront distribution, completing the migration process.

Stay tuned!
LimitlessAO

Day 3: Setting Up Your AWS Environment and Creating an S3 Bucket for Static Website Hosting

Abdullateef OGUNDIPE — Wed, 04 Dec 2024 09:18:22 +0000

Recap of Day 2

Yesterday, we designed the architecture for migrating the LimitlessAO Power Solutions website to AWS. Using a combination of AWS services like S3, CloudFront, Route 53, and ACM, we outlined a robust solution for hosting a static website that’s secure, reliable, and scalable. Today, we’ll bring that design closer to reality by setting up the AWS environment. This includes creating an AWS account (if you don’t already have one), configuring IAM for secure access, and preparing S3 to host the website files.

Overview of the Services We’ll Use

Amazon S3 (Simple Storage Service): A storage service where we’ll host the static files of our website.
IAM (Identity and Access Management): Provides secure access control for users and services interacting with AWS resources.
CloudFront (Content Delivery Network): Although not implemented today, S3 setup ensures readiness for integration with CloudFront later. As we go through these steps, remember that AWS’s scalability means this environment can adapt to future dynamic needs.

Why Are We Creating an IAM User?

AWS security best practices recommend avoiding the use of the root account for day-to-day operations. The root account has unrestricted access to your AWS resources, and its misuse or compromise could have catastrophic consequences. By creating an IAM user, we limit permissions to only what’s necessary for specific tasks, thereby enhancing security. Once the IAM user is created, we’ll log in using this account to perform all subsequent operations.

Step-by-Step Implementation

Step 1: Create an AWS Account
If you don’t have an AWS account, follow these steps:

Visit the AWS Sign-Up Page.
Provide your details, including payment information (AWS offers a Free Tier for many services, but ensure you monitor usage to avoid charges).
Complete the verification and login process.
For more details, refer to the official AWS documentation: Creating an AWS Account.

Step 2: Configure IAM for Security (Not Compulsory)
Security is paramount when working with cloud services. We’ll create an IAM user with restricted permissions:

Navigate to the IAM Dashboard.
Create a new user:
Click on "Users" > "Add Users."
Assign a username (e.g., WebsiteAdmin).
Select AWS Management Console Access for GUI.
Attach policies:
Use the AmazonS3FullAccess policy for this user (we’ll restrict this later).
Download access credentials (store them securely). For further reading: Getting Started with IAM.

Once the IAM user is created, log out of the root account and log back in using the IAM user credentials via the AWS Management Console: AWS Console Login. This step ensures that we follow best security practices while creating and managing resources.

Step 3: Create an S3 Bucket for Static Website Hosting

Go to the S3 Management Console.

Click Create Bucket and follow these settings: Bucket Name: Use a unique name, e.g., limitlessao-website

Block Public Access: Keep this enabled for now; we’ll adjust it later for CloudFront

Upload static website files: Use the Upload button to add HTML, CSS, JavaScript, and other assets.

To learn more about S3: Hosting a Static Website on Amazon S3.

Step 4: Enable Static Website Hosting

Open your newly created bucket.
Go to Properties and enable Static Website Hosting:
Index Document: index.html
Save the configuration and note down the Endpoint URL. This URL is your website's address until we integrate CloudFront.

"The foundation of any great system starts with careful setup, because a strong start paves the way for success."

What’s Next?

Tomorrow, we’ll integrate CloudFront into this setup to optimize content delivery globally, ensuring low latency and high performance. Additionally, we’ll configure an SSL certificate with ACM to enable secure HTTPS connections. Stay tuned!

LimitlessAO

Day 2: Designing the AWS Architecture for Migration

Abdullateef OGUNDIPE — Tue, 03 Dec 2024 08:54:15 +0000

Recap of Day 1

In our first post, we introduced the migration plan for the LimitlessAO Power Solutions Website to AWS. We explored why AWS is the ideal platform for this project, emphasizing scalability, cost optimization, and security. Today, we will design the architecture that will guide the entire migration process, using AWS services like S3, CloudFront, Route 53, and ACM. Additionally, we’ll provide step-by-step instructions to create the architecture diagram using draw.io or Lucidchart, making this process easy to follow and replicate.

AWS Architecture Design Overview

Migrating the LimitlessAO Power Solutions Website requires a carefully designed architecture that ensures scalability, reliability, and security. The diagram above illustrates the architecture we will implement, which consists of several AWS services working together to host and deliver the website.

"In the cloud, simplicity today paves the way for scalability tomorrow."

Here's a breakdown of the components and their roles:

S3 Bucket (Simple Storage Service)
The website's static files (HTML, CSS, JavaScript, images) will be stored in a private S3 bucket. This ensures cost-effective and secure storage. Access to these files will be managed using an Origin Access Control (OAC), restricting public access and allowing only the CloudFront distribution to fetch content.

CloudFront (Content Delivery Network)
CloudFront is used to deliver website content globally with low latency. It works by caching the website files in AWS edge locations around the world. CloudFront is configured to use an SSL/TLS certificate for secure HTTPS communication, which will be issued through AWS Certificate Manager (ACM).

AWS Certificate Manager (ACM)
ACM provides the SSL/TLS certificate used by CloudFront to encrypt data between the client and the server. This ensures that all communication is secure and adheres to HTTPS protocols.

Route 53 (DNS Service)
Route 53 will handle DNS management, directing users' requests to the CloudFront distribution. This service ensures high availability and reliable routing of traffic to the website.

CloudFront Function
A CloudFront Function is configured to redirect all HTTP traffic to HTTPS and ensure users accessing "www" are redirected to the root domain (e.g., redirecting www.example.com to example.com). This helps maintain a consistent user experience.

Step-by-Step Guide to Creating the Architecture Diagram

Step 1: Choose Your Tool (draw.io or Lucidchart)
Visit diagrams.net for a free, browser-based diagramming tool. Alternatively, use Lucidchart for a more collaborative, professional experience (free trial available).

Step 2: Set Up the Canvas
Open your chosen tool and create a new blank diagram.
Set the diagram type to AWS Architecture (both tools offer AWS icons).

Step 3: Add Key Components
Drag and drop the following icons from the AWS library:

S3 bucket: Representing static website storage.
CloudFront: As the CDN layer.
Route 53: For DNS routing.
ACM (SSL/TLS Certificate): For HTTPS encryption.
Client/User: Representing the end-user accessing the website.
CloudFront Function: For domain and protocol redirection.

Step 4: Connect Components
Use arrows to define relationships:

Connect Client to Route 53, showing DNS lookup.
Link Route 53 to CloudFront, representing domain resolution and content delivery.
Attach CloudFront to S3, highlighting the origin for website content.
Add a connection between CloudFront and ACM, illustrating HTTPS encryption.
Include a feedback loop from CloudFront to CloudFront Function, showing viewer requests for redirection.

Step 5: Label the Connections
Add annotations for each arrow to explain the interactions, such as “DNS Lookup,” “Viewer Request,” or “Content Fetch.”

Step 6: Add Final Touches
Use text labels to identify each service clearly.
Adjust alignment and spacing to ensure the diagram is neat and professional.

How This Architecture Works

Once implemented, this architecture enables secure, reliable, and efficient website hosting

Users access the website via a custom domain managed in Route 53.
Route 53 directs traffic to CloudFront, which delivers cached content globally.
CloudFront retrieves website files securely from S3 via OAC.
ACM ensures all connections are encrypted with HTTPS.
The CloudFront Function handles domain redirection (e.g., from “www” to the root domain) and enforces HTTPS.

"A well-designed solution solves today's needs while staying ready for tomorrow's possibilities."

What’s Next?

For Day 3, we’ll set up the AWS environment, including creating an account, configuring IAM roles for security, and preparing S3 for hosting the website files. Make sure to stay tuned as we move closer to making this architecture a reality!

Stay tuned!
LimitlessAO

Day 2: Designing the AWS Architecture for Migration

Abdullateef OGUNDIPE — Tue, 03 Dec 2024 08:54:15 +0000

Recap of Day 1

AWS Architecture Design Overview

"In the cloud, simplicity today paves the way for scalability tomorrow."

Here's a breakdown of the components and their roles:

Step-by-Step Guide to Creating the Architecture Diagram

Step 2: Set Up the Canvas
Open your chosen tool and create a new blank diagram.
Set the diagram type to AWS Architecture (both tools offer AWS icons).

Step 3: Add Key Components
Drag and drop the following icons from the AWS library:

S3 bucket: Representing static website storage.
CloudFront: As the CDN layer.
Route 53: For DNS routing.
ACM (SSL/TLS Certificate): For HTTPS encryption.
Client/User: Representing the end-user accessing the website.
CloudFront Function: For domain and protocol redirection.

Step 4: Connect Components
Use arrows to define relationships:

Connect Client to Route 53, showing DNS lookup.
Link Route 53 to CloudFront, representing domain resolution and content delivery.
Attach CloudFront to S3, highlighting the origin for website content.
Add a connection between CloudFront and ACM, illustrating HTTPS encryption.
Include a feedback loop from CloudFront to CloudFront Function, showing viewer requests for redirection.

Step 5: Label the Connections
Add annotations for each arrow to explain the interactions, such as “DNS Lookup,” “Viewer Request,” or “Content Fetch.”

Step 6: Add Final Touches
Use text labels to identify each service clearly.
Adjust alignment and spacing to ensure the diagram is neat and professional.

How This Architecture Works

Once implemented, this architecture enables secure, reliable, and efficient website hosting

Users access the website via a custom domain managed in Route 53.
Route 53 directs traffic to CloudFront, which delivers cached content globally.
CloudFront retrieves website files securely from S3 via OAC.
ACM ensures all connections are encrypted with HTTPS.
The CloudFront Function handles domain redirection (e.g., from “www” to the root domain) and enforces HTTPS.

"A well-designed solution solves today's needs while staying ready for tomorrow's possibilities."

What’s Next?

Stay tuned!
LimitlessAO