Weekend Showcase Challenge: Campus Study Agent
Campus Study Agent is the next stage of my Summer Build Series journey, evolving a student productivity application into an automated AI study companion using serverless AWS services.
Campus Study Agent
From a Study Planner to an Always-On Agent
My Summer Build Series journey started with a simple student productivity problem: managing study tasks, focus sessions, and breaks often requires switching between different tools.
I first built Campus Study Planner, a lightweight web application that brought study tasks and a Pomodoro timer together in one interface. After deploying that project with AWS Amplify, I wanted to explore how the same student-focused idea could be taken further.
For the Summer Builds Showcase, I refined that direction into Campus Study Agent, an always-on AI study companion that automatically generates a daily creative study pulse.
The project represents the progression from a manually used productivity application to an automated workflow that can perform a task on a schedule without requiring the student to start it each time.
Vision and What It Does
The purpose of Campus Study Agent is to reduce the amount of manual effort required to receive useful study-focused content.
Instead of opening an application and requesting something every day, the agent uses a scheduled workflow to generate a fresh creative study pulse automatically.
From the user's perspective, the process is simple. The scheduled workflow runs in the background, generates new content, and stores the result so it can be accessed later.
The application follows this architecture:
Amazon EventBridge → AWS Lambda → Amazon Bedrock → Amazon S3
A Lambda Function URL is also available as a simple interface for testing and verifying the deployed application.
How I Built It
I started by taking the student-focused concept from Campus Study Planner and exploring how automation could make the experience more useful.
The first version of my summer project was a frontend application built with React, TypeScript, and Vite. I developed it in StackBlitz, pushed the source code to GitHub, and deployed it using AWS Amplify.
For the next stage, I moved toward an event-driven architecture. I created an AWS Lambda function to handle the application logic and integrated Amazon Bedrock to provide generative AI capabilities.
I then added Amazon S3 for persistent storage and configured Amazon EventBridge to trigger the Lambda function automatically. Finally, I enabled a Lambda Function URL so that I could verify the deployed workflow through a browser.
One of my key architectural decisions was to use serverless services. Each service has a focused responsibility, while the overall system can operate without maintaining a continuously running server.
Challenges and How I Overcame Them
One of the main challenges during development was getting the Amazon Bedrock operation working correctly. At one point, the Lambda function returned an
AccessDeniedException because the AWS account was still undergoing verification.Rather than changing the project design unnecessarily, I investigated the access issue and continued testing once the required service access became available.
After that, I tested the Lambda function again and received a successful
200 response. The deployed function also returned a confirmation that the creative pulse had been generated.This experience reinforced the importance of checking account status, permissions, service availability, and configuration when working with cloud services.
AWS Services Used and Architecture Overview
The project uses several AWS services:
- Amazon EventBridge for scheduled automation
- AWS Lambda for serverless execution
- Amazon Bedrock for generative AI
- Amazon S3 for persistent storage
- AWS IAM for access control and permissions
The workflow is:
Amazon EventBridge
↓
AWS Lambda
↓
Amazon Bedrock
↓
Amazon S3
EventBridge starts the scheduled process. Lambda receives the event and executes the application logic. It then communicates with Amazon Bedrock to generate the study-focused content and stores the resulting output in Amazon S3.
This event-driven design allows the agent to operate automatically rather than depending on a manual execution.
What I Learned Across the Summer
The biggest lesson from the Summer Build Series was learning how an idea can evolve through several stages.
I began with Campus Study Planner, where I learned about frontend development, GitHub integration, and deploying a React application using AWS Amplify.
Building Campus Study Agent introduced a different set of concepts. I gained practical experience with event-driven architecture, AWS Lambda, Amazon EventBridge, Amazon Bedrock, Amazon S3, and IAM.
I also learned more about troubleshooting real AWS deployment issues. The Bedrock access problem showed me that cloud development involves more than writing application code. Permissions, account configuration, service availability, testing, and deployment all have to work together.
Most importantly, the summer helped me understand the difference between an application that waits for a user and an agent that can perform work automatically.
Why I Chose This Build for the Showcase
I chose Campus Study Agent because it represents the strongest progression of my work during the Summer Build Series.
The project builds on the student productivity idea from Campus Study Planner and adds automation and generative AI. Rather than starting an unrelated project, I used what I had already learned and extended the concept into a more capable architecture.
This approach also gave me an opportunity to revisit the project, verify the deployed workflow, improve the documentation, and present the complete journey from the original application to the current agent.
Builder Who Inspired Me
The AWS Builder Center community played an important role throughout the Summer Build Series. Seeing other builders share their projects, architectures, experiments, and lessons encouraged me to keep improving my own work.
I would especially like to thank #AmitabhSoni for sharing their work and contributing to the learning experience throughout the series.
Project Links
GitHub Repository
Live Application
Conclusion
Campus Study Agent represents the evolution of my Summer Build Series work from a simple student productivity application into an automated AI-powered workflow.
The project combines Amazon EventBridge, AWS Lambda, Amazon Bedrock, Amazon S3, and IAM to create a serverless architecture that can generate study-focused content automatically.
The Showcase challenge gave me the opportunity to revisit the project, build on what I learned earlier in the summer, and present a more complete version of the idea.
The journey has strengthened my understanding of AWS services, serverless architecture, generative AI, event-driven automation, deployment, and troubleshooting. More importantly, it showed me that a small idea can become significantly more useful when it is continuously refined and connected to the right cloud services.
#application
Enjoyed reading this content? Let the author know!
Your likes, comments, shares, and saves help creators reach more builders.
Loading recommendations
Loading article