Weekend Creative Challenge: AWS Service Detective
A Detective type game to identify AWS Services with given clues
Series: Weekend Challenge - August 2026 (3 articles)
- 1Weekend Creative Challenge: AWS Service Detective This article
Vision & What the App Does
Learning AWS involves becoming familiar with a large number of services, each designed to solve a different problem. While traditional quizzes are useful for testing knowledge, I wanted to experiment with a more engaging way to recognize and remember AWS services.
For this weekend's creative challenge, I built AWS Service Detective—a small interactive game that turns AWS service learning into a detective investigation.
The concept is simple: read the clues, identify the AWS service, and crack the case.
The game presents three difficulty levels:
- 🟢 Easy — foundational AWS services
- 🟡 Medium — services commonly encountered when building and deploying workloads
- 🔴 Hard — specialized services for more experienced AWS learners
Each level contains 10 cases. Every case provides up to three clues about an AWS service. The earlier the player identifies the service, the more points they earn.
The scoring system adds a small strategic element to the game:
Clue 1 = 30 points | Clue 2 = 20 points | Clue 3 = 10 points
So the challenge isn't simply about knowing the answer. It is also about deciding when to make the guess.
For example, the Easy level includes services such as Amazon S3, Amazon EC2, AWS Lambda, Amazon RDS, Amazon VPC, AWS IAM, Amazon CloudFront, Amazon Route 53, Amazon DynamoDB, and Amazon SNS.
The creative output is therefore more than a static quiz. It is a small gamified AWS learning experience designed to encourage recognition, recall, and curiosity.
How I Built It
I deliberately kept the first version simple.
Rather than starting with a complex backend, database, authentication system, or AI integration, I focused on getting the core game experience working first.
Version 1 was built as a single HTML file using HTML, CSS, and JavaScript. The application contains the visual design, game data, game logic, scoring, and interactions in one place.
One of the first creative decisions was the visual theme. Instead of making it look like a conventional technology quiz, I designed it around a detective case-file concept. The interface uses a dark investigation-board background, folder-style cards, case numbers, pins, stamps, and typewriter-style typography.
The game logic was also designed around progressive clues.
When a player starts a case, only the first clue is displayed. If the player chooses an incorrect answer, the next clue is revealed. A correct answer awards points based on the number of clues currently visible. If all three clues are used without finding the service, the case is closed and the correct answer is revealed.
I also added randomized answer choices so that the correct answer does not always appear in the same position. The services themselves are shuffled for each playthrough, making repeated games less predictable.
Another small design decision was to make the game feel like an investigation rather than an exam. Correct answers produce a "MATCH FOUND" result, while exhausting all clues results in "CASE CLOSED." The final score is also translated into detective ranks such as Rookie Detective, Field Agent, Senior Investigator, and Master Detective.
A deliberate decision: start small
The biggest challenge was resisting the temptation to build too much.
It would have been easy to immediately introduce a database, user accounts, leaderboards, APIs, and generative AI. Instead, I decided to prove the game concept first.
That approach allowed me to focus on the most important question:
Is the game actually fun and useful for learning AWS services?
Once that foundation works, additional AWS capabilities can be introduced in future versions.
AWS Services Used / Architecture Overview
Version 1
The current application is a self-contained HTML/CSS/JavaScript implementation, with the AWS service definitions and clues stored directly in the application. The source contains 10 services for each of the three difficulty levels, for a total of 30 cases. this HTML file is uploaded to S3 bucket and is now a static website.
The current architecture is therefore intentionally simple:

A future version could look like:

Potential future AWS services include Amazon S3, AWS Lambda, Amazon API Gateway, Amazon DynamoDB, Amazon Cognito, and Amazon Bedrock.
This would allow the game to evolve from a static learning exercise into a cloud-based AWS learning platform with persistent scores, user accounts, dynamically managed questions, leaderboards, and AI-generated clues.
What I Learned
This challenge reinforced something important for me: a project doesn't have to be complex to be meaningful.
I learned how a simple learning objective can be transformed into an interactive experience by adding game mechanics such as progressive clues, scoring, randomized questions, feedback, and rankings.
From a development perspective, I also practiced structuring client-side game state, including the selected difficulty, current case, revealed clues, score, and round progression.
More importantly, the challenge encouraged me to think beyond simply learning AWS services and instead ask:
How can I create something that helps someone else learn them too?
That shift—from consuming learning content to creating a learning experience—is probably the most valuable part of this weekend challenge.
I also learned the value of starting with an MVP. The first version doesn't need every possible AWS service or every possible feature. It needs a clear idea, a working experience, and a foundation that can be extended.
What's Next?
AWS Service Detective is currently Version 1.
The next iterations could introduce:
- A DynamoDB-backed question bank
- User authentication with Amazon Cognito
- Persistent scores and player history
- A leaderboard
- More AWS services and scenario-based clues
- An administration interface for adding cases
- Amazon Bedrock for generating additional clues
- AWS deployment and monitoring
The long-term vision is to turn this small weekend experiment into a gamified AWS learning platform.
For now, though, the mission is simple:
Read the clues. Name the service. Crack the case.
Link to the App / Repository
Version 1:
Project Link: AWS Service Detective
Version: 1.0
Cases: 30
Difficulty levels: 3
Maximum score per level: 300 points
Series: Weekend Challenge - August 2026 (3 articles)
- 1Weekend Creative Challenge: AWS Service Detective This article
Enjoyed reading this content? Let the author know!
Your likes, comments, shares, and saves help creators reach more builders.
Loading recommendations
Loading article