I had the fantastic opportunity to attend the AWS Student Community Day in Tirupati on November 1, 2025. The sessions were great and covered a wide spectrum of cloud subjects but one particular speaker particularly caught my attention.
The session was titled “The Future is Conversational: Analyze Cloud Networks with GenAI” and was led by Yeshwanth L M. Yeshwanth is a multi-talented individual in the tech community. He is a Solutions Engineer at Confluent, an active AWS Community Builder, a Microsoft Certified Trainer, an IEEE Volunteer, and the creator of the YouTube channel “Tech With Yeshwanth.”
His lecture handled a big pain point for cloud engineers and made it easier with Generative AI. This is what I took away from his highly entertaining talk.
The "Khatabook" Problem: Managing a Giant Network
Yeshwanth opened the discussion with a fantastic everyday analogy to explain cloud networking. Imagine your AWS network as a huge college hostel and you as the warden.
In this analogy, you have 10,000 pupils (your cloud servers), thousands of dormitories (your applications), and one main entrance (the Internet). As the warden your major job is to be aware of who is coming in and out of the main gate and to make sure the pupils are safe.
Let’s face it, keeping track of 10,000 students isn’t easy. At the main gate, your security guy logs everything into a big notebook. In the realm of AWS, this logbook is called a VPC Flow Log.
Now picture this logbook with 100 million entries a day! This leads to what Yeshwanth aptly termed the “Khatabook” (logbook) dilemma.
The Warden's Nightmare
This vast amount of data creates a terrible scenario. Suppose the college principal asks you a very precise inquiry. “Did anyone try to sneak into the girls' hostel (a secure server) at 2 AM last night?”
In old school environment your job? You have to go through 5,000 pages of the logbook with a pen and locate the answer. This is the “Old Way” that cloud infrastructure was. Technically this entails building complex, very precise SQL queries to sift through millions of logs.
Does this sound familiar? It’s sluggish. It’s unpleasant. And by the time you finally compose the appropriate query, get the answer, the intruder is already long gone.
The "What If" Moment
Here’s the thing… what if you didn’t have to create those complicated queries? What if you could just naturally ask a question?
Picture yourself pulling out your phone, texting an assistant: “Hey, show me all ‘REJECTED’ entries after 1 AM." Or, more college-campus relatable: “Which student (IP address) is ordering the most Swiggy or Zomato orders?”
This simple transition from writing hard-coded code to having a natural discussion is exactly where Generative AI comes in to revolutionize the game entirely.
Meet the "Super-Smart Warden": Amazon Bedrock
Yeshwanth’s answer to the “Super-Smart Warden” of the AWS ecosystem was Amazon Bedrock.
Amazon Bedrock is a fully managed solution that brings Generative AI into your cloud environment. Imagine giving your hostel a super brain It’s like having a Ramanujan, a mathematical genius, on your administrative staff. Instead of you scanning the book with a pen, this genius can read all 5,000 pages of your logbook in one second and just tell you the answer.
Traditional vs. Intelligent Architecture
To see what a major shift this is, we have to look at the warden's "Filing System".
The Traditional Architecture:
In a normal legacy arrangement, network traffic passes via your Virtual Private Cloud (VPC) and gets captured in VPC Flow Logs. The data is then dumped onto storage such as an Amazon S3 bucket or Amazon CloudWatch. You would normally use a technology like Amazon Athena to query the S3 data and then develop a visual Dashboard to interpret this. It works but it’s a lot of heavy lifting, ongoing maintenance and a lot of manual query building.
The Intelligent Architecture:
The current technique streamlines this pipeline entire. Your VPC logs continue to flow to S3 and CloudWatch. But the data is immediately streamed into Amazon Bedrock, not through Athena and constructing fancy dashboards. You just ask the AI “Is there any strange activity from someone I don’t know?” and it answers in a conversational manner.
The Magic Trick: How It Actually Works
You may wonder how it works behind the scenes? Is this a magic? Yeshwanth broke down the technical reality into a four-step approach.
Step 1: Getting the Logbook Pages
First of all, the system needs raw data. For example, a script calls a function get_flow_log_data. It is precisely the same as going up to the security officer and asking him for all the logbook entries from the last 24 hours. It extracts the raw text messages directly from Amazon CloudWatch Logs.
Step 2: Pre-Processing in Python
Even before you talk to the AI, the script gets clever. It executes a Python function called analyze_flow_logs_summary that uses the Pandas package. This is where you take the raw data and make a high level summary, automatically finding things like total records, top IPs, total bytes moved, etc.
Then it calls a method called format_flow_logs_for_bedrock to provide a nice, legible text "printout" of the first few log entries. Think of this phase as cleaning up your desk and summarizing your notes before your boss comes to see a report.
Step 3: Building the "Super-Prompt"
This is where things become fascinating. This is where the true magic happens. We don’t just ask a plain question to the AI. We feed one giant dossier of information into Amazon Bedrock, all at once. This “Super-Prompt” has three primary components:
The Role: We give the AI a persona by stating, "You are an AWS network expert."
The Summary: We provide the Pandas data we just created: "Here is a summary I already made: {Total Records: 5000, Top IP: 1.2.3.4...}"
The Raw Data: We feed it the actual log entries: "Here are the actual log entries: {1. 10.0.0.1 -> 10.0.0.2 [REJECT]...}"
Step 4: The "In-Context" Answer
Finally, we append the real question to the very end of this huge prompt. We add for example: "...Now, tell me this: 'Are there any suspicious activities?
Bedrock reads the pre-computed summary and the raw logs we just gave it. It uses that current context to locate the solution. Bottom line. The AI is not going out and searching a regular back-end database. It’s basically reading and understanding the huge chunk of material you just given it and giving you a human like answer.
Live Demo & Beyond Security
After discussing the principle, Yeshwanth walked into the AWS Console for a live demo to "catch some intruders" and how this architecture parses flow logs in real time. Seeing the AI immediately evaluate complex network traffic was super cool.
But the main point of the session’s message was much broader than merely AWS security. This log analysis architecture is just the beginning, the future is conversational. You can execute this very same four step “magic trick” on just about any data generating domain:
For a Cricket Analyst: You could feed ball-by-ball IPL data to an AI and ask, "What bowling pattern makes Virat Kohli get out most often?"
For a College Admin: You could upload raw campus Wi-Fi logs and ask, "Which classroom's Wi-Fi is the slowest?"
For Developers: You could take your user-click logs and ask, "Which part of my app is making users angry?"
Key Takeaways
If you only remember a few things from this session, here is what you need to know:
Goodbye to Complex Queries: You don’t have to write complex SQL anymore, nor search through millions of lines of text manually. With GenAI you can just ask natural questions to examine large datasets.
Context is Everything: The answer to making this work is not just asking a smart question. It’s creating a “Super-Prompt” that first sends Amazon Bedrock your summary data and raw logs so it gets the precise context it needs to offer a great answer.
Endless Possibilities: Yeshwanth used AWS network security for his example, but this conversational design works for anything. GenAI can be your analyst on call, whether it’s cricket statistics, college Wi-Fi, or app user behavior.
Conclusion
At the end of the day, going from writing rigid code syntax to having a simple discussion with your infrastructure is a big game shift. Generative AI is not just a pretty new toy to generate emails. It is a very practical, powerful technology that can be the ‘super-smart warden’ for your most complex operational data.
Attending this session at AWS Student Community Day was eye opening. It is getting easier fast to grasp complex systems. If you haven't yet played around with Amazon Bedrock or GenAI for your own data, I advise you to give it a try. Write a simple script, give it some logs and see what happens. The future is indeed conversational ! And all it takes to get started is understanding how to ask the correct questions !
About the Author
As an AWS Community Builder, I enjoy sharing the things I've learned through my own experiences and events, and I like to help others on their path. If you found this helpful or have any questions, don't hesitate to get in touch! 🚀
🔗 Connect with me on LinkedIn
References
Event: AWS Student Community Day Tirupati
Topic: The Future is Conversational: Analyzing Cloud Networks with GenAI
Date: November 01, 2025
Top comments (0)