AWS Builder Center
Notice, made simple.

Notice, made simple.

Mobile-first web app that explains Bengali and Telugu civic/legal notices in plain language — and reads them aloud. Built for WeMakeDevs Bharat Builds Tour — First Commit hackathon, Sep 17–20 2026.

build<->break<->rebuild
How a weekend hackathon project turned into a lesson in AWS, stubborn cloud errors, and why deployment beats localhost every time:

The problem I actually cared about

A few weeks before the WeMakeDevs Bharat Builds Tour started, my uncle showed me a notice from the Kolkata Municipal Corporation. It was in Bangla, but the language was so formal and dense that even he — who reads Bangla fine — had to read it three times to understand what he was supposed to pay, and by when.
That same week, a friend in Hyderabad told me his parents do the same thing with Telugu notices: take a photo, send it to a relative who "knows Government English," wait for a translation, miss the deadline anyway.
This is not a rare problem. Millions of people in India get legal, civic, and landlord notices in languages they technically speak but in a register that feels designed to confuse them. I wanted to build something that takes that notice and gives back:
  • a plain-language summary,
  • clear action steps,
  • deadlines,
  • and an audio version they can listen to.
No lawyer. No relative on WhatsApp. Just the phone they already have.

What we built

Our project is called Notice, made simple. It is a mobile web app. You pick Bangla or Telugu, paste the notice text or upload a photo, and it gives you a simplified explanation plus a play button.
The full stack:
  • Frontend: React + Vite + Tailwind, hosted on AWS Amplify.
  • Backend: AWS Lambda (Python) behind API Gateway.
  • OCR: Amazon Textract for English/Hindi, bundled open-source Tesseract for Bangla/Telugu images.
  • Simplification: Amazon Bedrock (Claude 4.5 / Nova) with multi-region failover, plus a Groq fallback when AWS account verification was acting up.
  • Audio: Microsoft Edge TTS running inside Lambda for Bangla/Telugu audio, since Amazon Polly does not support those languages yet.
  • Storage: S3 for uploads and audio, DynamoDB for saved notices.
We are in the Ship It track, so everything is deployed and live. The app is at  main.d1ikau4tnjl5sq.amplifyapp.com  and the API is running on API Gateway in  ap-south-1 .

What fought back (a lot)

I thought the hard part would be the LLM prompt. I was wrong. The hard part was AWS account gates.
On day one, Bedrock returned  Operation not allowed  in every region. I tried IAM keys, short-lived bearer tokens from the console, multiple regions — same error. The root cause turned out to be account-level verification on the primary AWS account, not our code. For a few minutes,  ap-southeast-2  worked and returned real Nova output, which at least proved our request shape was correct.
Then Textract started returning  SubscriptionRequiredException . Then Claude 4.5 in another teammate's account returned  INVALID_PAYMENT_INSTRUMENT . Every service had a different billing or verification gate.
So I did what every hackathon teaches you eventually: build around the blockers.
  • Added multi-region Bedrock failover so the Lambda tries several regions before giving up.
  • Added Groq as a fallback provider for text simplification.
  • Bundled Tesseract inside the Lambda for Bangla/Telugu OCR so we were not blocked by Textract's language support.
  • Added Edge TTS inside the Lambda for audio, since Polly does not have Bangla/Telugu voices.
By Sunday, the app worked end-to-end even when the "official" AWS path was partly gated. That felt better than any clean architecture diagram.

What I learned

1. Deployment is a feature. A working localhost demo is not a demo. Until it is live, with a URL, on someone else's phone, it does not count. Hosting on Amplify and deploying Lambda through CloudFormation forced me to think about environment variables, CORS, S3 bucket permissions, and binary media types in API Gateway. Those are not "extras." They are the product.
2. Failovers are not over-engineering. I used to think multi-region code was for big companies. But when one AWS region says "Operation not allowed" and another works, a simple loop over regions saves your demo. The same with provider fallbacks. A Groq key in an env variable is a lot cheaper than a broken app at submission time.
3. Prompt engineering is engineering. Getting Claude/Nova to return strict JSON with the right fields, in Bangla/Telugu, with exact dates preserved, took more iterations than I expected. The final prompt includes a verbatim line: "deadlines must be an array of plain date strings only, formatted like ["2026-09-30"] — do not return objects." Without that, the model returns objects, arrays of objects, or wraps everything in another key. Frontend code breaks. Users notice.
4. Bundling binaries in Lambda is possible. I had never shipped a Tesseract binary inside a Lambda zip before. It turns out you can download a Lambda layer, extract the binary and traineddata files, and point  TESSDATA_PREFIX  at them. It is a bit manual, but it works. That single trick made Bangla/Telugu image upload usable.

Where AWS fits

AWS is not just the host here. The whole architecture is AWS-shaped:
  • Amplify gives us automatic deploys from GitHub and HTTPS hosting.
  • API Gateway + Lambda run the backend without me managing servers.
  • S3 stores uploaded notice images and generated MP3s.
  • DynamoDB saves each simplified notice so users can retrieve it later.
  • Bedrock / Textract / Polly are the intended production paths once account verification clears.
Even the fallback pieces are running inside AWS infrastructure. Groq and Edge TTS are stopgaps, but the app itself is deployed on AWS, which is exactly what the Ship It track asks for.

What's next

Right now the app is focused on property-tax and civic notices. The next step is to expand it to more notice types — eviction warnings, pension schemes, health camp notices — and add Hindi. We also want to make the audio player work offline so a user can save a notice and listen later without data.
The biggest lesson, though, is personal. I started the weekend thinking I would learn AWS services. I ended up learning that real problems do not wait for perfect cloud permissions. You ship with what works, then fix the rest.
If you are a student reading this and hesitating because your AWS account is new or your credits are scary: just start. The free tier is enough. The errors are normal. The deployed URL at the end is worth every  Operation not allowed .


Built for the WeMakeDevs Bharat Builds Tour — First Commit (Sep 2026). Live app:  https://main.d1ikau4tnjl5sq.amplifyapp.com  Source:  https://github.com/Yakshitha123-wq/vernacular-notice-simplifier 
Any opinions in this article are those of the individual author and may not reflect the opinions of AWS.
Enjoyed reading this content? Let the author know!

Your likes, comments, shares, and saves help creators reach more builders.

Loading recommendations

Loading article