The free AWS tier still wants your credit card. The new sandbox doesn't.

The advice for learning AWS has been the same for a decade: sign up for the free tier, be careful, and set a billing alarm so you don't wake up to a four-figure invoice because you left a NAT gateway running. That advice is fine, but it quietly skips the part that stops a lot of people before they start, which is that AWS wants a valid credit or debit card on file before it lets you do anything at all.

That's still true, even after the free tier got reworked in 2025. New accounts now come with up to $200 in credits ($100 when you sign up, and up to $100 more for completing a handful of starter activities like launching an EC2 instance or setting a budget), and there's a Free account plan that won't charge you until you deliberately upgrade. Good changes, genuinely. But read AWS's own free tier FAQ and it's right there: "You are required to provide a valid payment method to sign up for an AWS account, whether you choose a free plan or a paid plan." The Free plan changes whether you get charged. It doesn't change whether you have to hand over a card.

So when AWS announced free sandbox environments in Builder Center on July 8, that's the line it actually crosses. No personal account, no card, no billing alarm to babysit. You get a real AWS account, pre-provisioned, for a few hours at a time.

What it actually is

The thing to understand up front is that this is not a simulator and it's not a screenshot walkthrough. When you start a sandbox you're handed a real, pre-provisioned AWS account that somebody else set up and pays for. The resources you deploy into it are real resources in real regions. The IAM roles are real. The Lambda cold starts are real. The only thing that's fake is the bill, because it isn't yours.

The numbers, straight from the announcement:

• 8 hours of access from the moment you activate a sandbox.
• One sandbox per week, with the counter resetting every Sunday.
• ~15 minutes for most environments to finish provisioning after you request one.
• Automatic cleanup when your time is up. Everything you built gets wiped.

You reach all of it through the Workshops section of AWS Builder Center. The sandbox isn't a standalone "here's a blank console" button, it's attached to the workshops themselves, so you request one from inside an eligible workshop and it drops you into an account that's already scoped for that lab.

The catch, because there's always a catch

None of the constraints are hidden, but they're worth saying plainly because they decide whether this fits how you actually want to learn.

You can't freelance. The sandbox is tied to eligible workshops. This isn't an empty AWS account you can wander around in and build whatever you feel like. It's a guided lab environment. If your learning style is "open the console and poke at things until something makes sense," this specific offering will frustrate you, because it's the opposite of that on purpose.

8 hours is a hard wall. When the clock runs out, the environment is gone, and so is everything in it. That's fine for a self-contained workshop you finish in one sitting. It is useless for anything you meant to build up over a week. If your project needs to persist across sessions, this is the wrong tool, full stop.

One per week is one per week. Reset is Sunday. Burn your sandbox on a Monday and misjudge how long the workshop takes, and you're waiting until the weekend for another shot. Plan the session like you mean it, block the time, pick the workshop first, and don't activate the sandbox until you're actually ready to work.

Not every workshop qualifies. Sandboxes are live for a selected set of workshops at launch, with more being switched on over time. So the flow is: browse the workshops, find one that's both interesting and sandbox-enabled, then request the environment.

The topics available cover the stuff you'd want to get your hands on anyway, serverless APIs, VPCs, containers, and the various AI/ML services, so there's real range even inside the "guided only" limitation.

Where this fits next to the free tier and Skill Builder

It's easy to lump all of AWS's free learning options together, but they solve different problems, and picking the wrong one is how people end up frustrated.

AWS Free Tier is for when you want your own account to keep. You get the credits, the always-free service limits, and the freedom to build whatever you want and leave it running. The cost of that freedom is the card on file and the responsibility to not run up a bill. This is the right choice the moment you're building something real that has to outlive an afternoon.

AWS Builder Labs on Skill Builder is the other card-free option, and it's worth knowing about. The free Introduction to AWS Cloud learning plan gives you 10 foundational hands-on labs (VPC, S3, EC2, IAM, KMS, DynamoDB, CloudFront, Lambda, API Gateway) that run in the browser, self-paced, retryable as many times as you want. These are more tightly scripted than a Builder Center workshop, closer to "follow these exact steps in a controlled lab," which is exactly what you want when a concept is brand new to you.

Builder Center sandboxes sit between those two. More open than a Skill Builder lab, more constrained than your own account. The distinguishing feature is that it's a real, throwaway AWS account with genuinely nothing at stake, no card, and no cleanup to remember, because AWS wipes it for you.

If I were starting from zero today, I'd run them in that order backwards: Skill Builder labs to get the vocabulary and the muscle memory, Builder Center sandboxes to do slightly meatier guided builds without any billing anxiety, and only then open my own free-tier account once I had something I actually wanted to keep and was confident I wouldn't leave an expensive resource running by accident.

The honest take

The "learn AWS for free" headline has technically been true for years, and it's also been quietly misleading, because "free" always came with "…as long as you're careful, and also give us a card." The billing-alarm anxiety is real, and it's kept plenty of curious people from ever launching a single instance.

What the Builder Center sandbox removes is that anxiety, completely, for the specific window where you're just trying to learn. You will hit the guardrails fast if you try to use it as your personal cloud, the 8-hour wipe and the one-per-week limit make sure of that. But for its actual job, working through a real workshop in a real AWS account with zero chance of a bill and zero cleanup afterward, it's the most honest "free" AWS has shipped.

Go pick a workshop at builder.aws.com/build/workshops, block out an afternoon, and don't activate the sandbox until you're ready to spend the whole eight hours. That's the entire strategy.