AWS Builder Center
Weekend Creative Challenge: PlotTwist

Weekend Creative Challenge: PlotTwist

PlotTwist is a creative storytelling playground built with AWS that transforms simple ideas into unexpected stories and plot twists through interactive controls for genre, mood, and chaos.

##Vision & What the App Does What if a simple character and location could become the beginning of a completely unexpected story?
That was the idea behind PlotTwist, a small creative storytelling playground I built for the AWS Weekend Creative Challenge. PlotTwist lets users provide a character, setting, genre, mood, and chaos level, then turns those ingredients into an original short story with an unexpected plot twist.
The goal wasn't to build another complicated productivity application. I wanted to create something people could open, experiment with, and immediately have fun using.
Users can choose from genres such as Fantasy, Sci-Fi, Mystery, Comedy, Horror, and Adventure. They can also select moods including Funny, Wholesome, Dark, Chaotic, Emotional, and Mysterious. The Chaos Level gives users another way to influence the experience, ranging from relatively predictable stories to much more unpredictable scenarios.
PlotTwist also includes Surprise Me, which randomly creates a combination of character, setting, genre, mood, and chaos level. This makes it possible to generate ideas without knowing what you want to write beforehand. After generating a story, users can also remix the experience or increase the chaos and create another version.
The result is a lightweight creative tool designed around experimentation: enter an idea, generate a story, discover the twist, and try again.


##How I Built It I started the project with a simple goal: build something creative that could be completed and deployed within the challenge weekend without over-engineering it.
The frontend was built using React and Vite. I designed the interface around a dark, modern visual style with a focused story-creation card. Instead of making users navigate through multiple pages, the main screen contains everything required to create a story.
The first version used a temporary hardcoded story so I could focus on the interface and interaction design. Once the frontend was working, I moved the story generation logic to AWS Lambda.
I created a Lambda function called  plot-twist-generator . The function receives the user's inputs through an HTTP request and generates the story on the server side. I then exposed the Lambda function using a Lambda Function URL so the React application could communicate with it over HTTPS.
One of the biggest challenges during development was getting the AWS permissions and public Lambda endpoint configured correctly. My first attempt to use Amazon Bedrock with Amazon Nova resulted in an  Operation not allowed  error. Rather than allowing that issue to stop the project, I changed the architecture so the core creative experience would not depend on that service.
I built a lightweight PlotTwist Creative Story Engine inside Lambda instead. It uses combinations of openings, character traits, discoveries, conflicts, events, genre-specific twists, moods, and endings to produce different story variations. The chaos level controls how many unexpected events can enter the story and influences the type of twist selected.
Another challenge was exposing Lambda safely enough for the browser to call it. I configured a Lambda Function URL with public access and CORS support. I tested the endpoint independently using  curl  before connecting it to the frontend. This helped separate frontend issues from AWS backend issues and made debugging much easier.
Once the API returned successful responses, I connected it to the React application. Finally, I deployed the frontend using AWS Amplify, giving PlotTwist a publicly accessible URL.


##AWS Services Used / Architecture Overview The project uses two primary AWS services:

AWS Amplify

AWS Amplify hosts the React/Vite frontend and provides the public web application.

AWS Lambda

AWS Lambda runs the PlotTwist Creative Story Engine. It receives the user's creative inputs, processes them, generates the story and twist, and returns the result as JSON.

Lambda Function URL

The Lambda Function URL provides the HTTPS API endpoint used by the React frontend. The architecture is:
User
│
▼
┌─────────────────────┐
│ AWS Amplify │
│ React + Vite App │
└──────────┬──────────┘
│
│ HTTPS POST
▼
┌─────────────────────┐
│ Lambda Function URL │
└──────────┬──────────┘
│
▼
┌─────────────────────┐
│ AWS Lambda │
│ PlotTwist Engine │
└──────────┬──────────┘
│
▼
Story + Twist
│
▼
React UI
The architecture is intentionally simple. The frontend handles the user experience while Lambda handles the creative generation logic.


##What I Learned This challenge taught me that a useful AWS project doesn't necessarily need a large architecture.
My first instinct was to use multiple services and build a more complex AI pipeline. Instead, I learned to start with the smallest architecture that could deliver the intended experience.
I also learned more about AWS Lambda execution roles, resource-based policies, Function URLs, CORS configuration, and deploying a React application with AWS Amplify.
One particularly useful lesson was learning how to debug a distributed application systematically. When the browser initially failed to communicate with Lambda, I tested the Lambda function directly, then tested the public Function URL using  curl . This made it possible to identify whether the problem was in the Lambda code, IAM permissions, the Function URL, or the browser.
Most importantly, I learned to prioritize shipping a working product over continuously adding complexity. The challenge had a short timeline, so getting a functional application deployed early was more valuable than trying to build an unnecessarily large system.


##Try PlotTwist You can try the live application here:
Live App:  Try PlotTwist 
Source Code:  GitHub Repository 


##Final Thoughts PlotTwist started as a simple weekend idea: give people a few creative ingredients and see what unexpected stories come out.
The finished project demonstrates how a focused idea can become a working, publicly accessible application using AWS services without requiring a complicated architecture.
For me, the most rewarding part was seeing the complete journey—from a blank React project, through AWS configuration and debugging, to a live application that anyone can open and use.
Sometimes the best way to discover a story is to let the plot twist happen first.
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