Building D-Prompt Pal: A Live AI-Powered Club Member Portal with RAG, pgvector, Supabase, and Amazon Bedrock
D-Prompt Pal is a live AI-powered Club Member Portal built with FastAPI, Supabase, pgvector, and Amazon Bedrock. It provides grounded, source-cited answers from official club documents, supports automatic document re-indexing and live knowledge synchronization, and demonstrates a production-style RAG architecture for real-time student community updates.
Club Member Portal: A RAG-Powered Chatbot for Student Builder Groups
Built for the AWS Student Builder Groups Campus Hackathon
What We Built
The Club Member Portal is a full-stack web application that lets AWS Student Builder Group members sign up, log in, and chat with an AI assistant that answers questions using only our club's official documents — onboarding FAQs, AWS account setup guides, Builder Center publishing steps, Bedrock basics, workshop history, and more.
Every answer the assistant gives is grounded in our starter document pack and cites the exact source file and section it came from. If a member asks something outside the scope of our documents, the assistant doesn't guess — it says so and points them to our campus AWS Student Builder Group Leader for a direct answer. No hallucinated AWS pricing, no invented policies, no guesswork.
On hackathon day, we extended the portal to handle a live, fast-moving scenario: club admins can publish new or updated documents (like an event-day briefing with room changes and revised judging times), and the chatbot picks up that new knowledge within about 60 seconds — no restart, no redeploy, no page refresh for the member. The member dashboard reflects the updated document list in the same window.
Who This Helps
A new Student Builder who just joined our chapter. They log in, and instead of digging through scattered chat threads or old emails, they can simply ask: "When is the next workshop?" or "How do I publish on Builder Center?" — and get a sourced, trustworthy answer in seconds. On a hackathon day itself, the same system keeps every member current when logistics change on the fly, cutting down on flooded chat groups and repeated "did the room change?" questions.
Core Features
Phase 1 — Member Portal Foundation
- Email/password sign up and login
- Forgot password flow with reset link/code delivered by email
- Members-only chat page (no guest access)
- Retrieval-augmented chatbot loaded with an 8-file starter document pack at startup
- Every answer cites its source file and section
- Safe-fallback behavior: when the answer isn't in the documents, the bot says so and directs the member to our campus AWS Student Builder contact
Phase 2 — Live Knowledge Sync (Event Day)
- Admin page to add or update club documents (paste or upload)
- Automatic re-indexing on publish, searchable within ~60 seconds
- Chat responses reflect the latest index without the member refreshing their browser
- Member dashboard updates its document list in the same ~60-second window
- Ingested a live event-day briefing document and passed a 3-question smoke test against it
- Exposed a standardized
POST /askHTTP endpoint (JSON in, JSON out —answer+sources) so judges could evaluate our retrieval quality directly, independent of our UI
How It Works
- Auth — Members sign up and log in with email and password; a forgot-password flow sends a reset link/code by email.
- Ingestion — Club documents (Markdown files) are chunked and embedded into a searchable vector index at startup, and re-embedded on demand when an admin publishes a change.
- Retrieval-augmented answering — A member's question is embedded, the most relevant document chunks are retrieved, and the assistant is prompted to answer only from those chunks — with the source file and section attached to the response.
- Fallback safety — If retrieval confidence is weak or nothing relevant is found, the assistant returns a fixed, honest fallback message with our club leader's contact details rather than inventing an answer.
- Live sync — When an admin publishes a new or edited document, the index is rebuilt in the background; the chat layer and member dashboard both reflect the change within about a minute, with no manual refresh needed.
Deploying This on AWS
We built and demoed the portal locally, but it's designed to map cleanly onto managed AWS services for a production deployment:
- Authentication — Amazon Cognito would replace our local email/password auth, handling sign-up, login, and secure password resets out of the box.
- Password reset email delivery — Amazon SES would send reset links/codes instead of a local mail utility.
- Document storage — Club documents (the starter pack and any admin-published updates) would live in Amazon S3, acting as the source of truth for re-indexing.
- Re-indexing pipeline — An S3 event could trigger an AWS Lambda function to re-chunk and re-embed a newly published document, keeping the "publish → searchable in ~60 seconds" behavior serverless and event-driven.
- Vector search / retrieval — Amazon OpenSearch (or a managed vector store) would hold document embeddings for retrieval at query time.
- AI answers — Amazon Bedrock would generate grounded responses from retrieved chunks, keeping the "answer only from club documents" constraint enforceable at the model layer.
- Chat API — The
POST /askcontract we built for judge evaluation would sit behind API Gateway + Lambda (or a small containerized service), making it easy to scale and secure independent of the frontend.
This architecture keeps every part of the system managed and serverless-first, so re-indexing latency and chat availability scale without us operating any infrastructure directly.
Smoke Test Results
We validated the event-day sync behavior against three targeted questions covering the newly published briefing document, confirming the assistant correctly cited
event-day-briefing.md in each case after the ~60-second re-index window.Tech Stack
- Backend: [add your framework, e.g. FastAPI / Flask]
- Retrieval: [add your vector store, e.g. FAISS / ChromaDB]
- LLM: [add your model provider]
- Frontend: [add your framework]
- Auth: Email/password with local reset-email delivery (Cognito + SES planned for AWS deployment)
Screenshots of the webpage



Team & Acknowledgments
Built by [your team names] for the AWS Student Builder Groups Campus Hackathon. Thanks to our campus AWS Student Builder Group Leader, Shanmukha Sasi Sadineni, for guidance throughout.
Tags
#aws-student-builders-groups #buildonaws #amazon-bedrock #rag Enjoyed reading this content? Let the author know!
Your likes, comments, shares, and saves help creators reach more builders.
Loading recommendations
Loading article