AWS Builder Center

I Got Sandbox Access on AWS Builder Center — Here's What I Broke in an Hour

AWS Builder Center just started handing out free, time-limited sandbox environments. I got one, gave myself an hour, and managed to break something before I even finished my coffee. Here's what happened and what it taught me.

AI Developer
AWS Builder Center recently started offering free, time-limited sandbox environments a pre-provisioned AWS account where you can deploy resources and experiment without touching anything real. I requested one on a Tuesday morning, told myself I would "just poke around for an hour," and had something broken before my coffee was finished.
This post is about that hour.
Cute cartoon character sitting among toppled blocks, smiling sheepishly after a mistake

Cute cartoon character stepping into an AWS sandbox environment


Why a Sandbox, Few Months In

I passed the AWS Certified Developer exam a few weeks ago, and the honest truth is that certifications are good at testing what you know and bad at testing what you have actually touched. A sandbox is the opposite: no exam, no flashcards, just an account that resets itself and doesn't care what you break.
So I went in with one goal spin up something I understood on paper but had never built from scratch, and see how much of that "on paper" understanding survived contact with a real console.

What I Broke

I picked a small serverless setup: an API Gateway endpoint in front of a Lambda function, reading from a DynamoDB table. Simple, well-documented, the kind of thing every tutorial builds in the first ten minutes.
I had it running in about fifteen minutes. It broke in the sixteenth.
The Lambda function couldn't read the DynamoDB table, and my first instinct the confident, certified-developer instinct was that I'd fat-fingered the table name. I hadn't. The table name was correct. The region was correct. The function code was correct. What was missing was painfully simple: I'd attached a permissions policy to the function's execution role, but I'd attached it to the wrong role, because the sandbox had auto-generated a default execution role that looked almost identical to the one I'd created myself.
Two roles, nearly identical names, one of them empty. I spent twenty minutes debugging code that was never the problem.

The Part That Actually Taught Me Something

Here's what I didn't expect: this wasn't a knowledge gap. I know how IAM roles and Lambda execution roles work. I could explain it in an interview. What the sandbox exposed wasn't a gap in what I know it was a gap in what I notice when I'm moving fast in a real console instead of following a tutorial's exact steps in order.
That's a different kind of mistake than the ones from Season 1. Those were "I didn't know this yet." This one was "I knew this and still walked right past it," which is a little more humbling and, I think, a lot more useful to sit with.

Why This Matters More Than It Sounds

A sandbox environment removes the one excuse that usually stops builders from experimenting: the fear of an unexpected bill or a resource left running somewhere. Because the environment is time-limited and disposable, I clicked around with a kind of carelessness I don't normally allow myself in a real account, and that carelessness is exactly what surfaced the mistake. If I'd been more careful, I probably would have caught the wrong-role issue before deploying but I also wouldn't have learned that I needed to be that careful in the first place.
That's the actual value of a sandbox. It's not a safer place to be right. It's a cheaper place to be wrong.

What I'd Tell Someone Trying This Next

Don't go in with a tutorial open in the next tab. Go in with something you think you already understand, and try to build it without a script. The gap between "I can follow these steps" and "I can build this from memory" is exactly where a sandbox earns its keep and for me, that gap turned out to be one nearly-identical IAM role wide.
If you've got Builder Center access, the sandbox is worth the hour. Just don't expect to spend it the way you planned.
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