There's a peculiar problem with cloud certification prep that nobody talks about honestly: the only way to learn the console is to use it, and the only way to use it is to risk a bill.
You can read all the documentation you want. You can watch every video. But when you sit down for the exam and the question is "a developer reports their Lambda can't reach the RDS instance — which of the following is the most likely cause?", what you're really being asked is whether you've ever seen a security group misconfiguration in your life. People who've debugged that in a real account answer in five seconds. People who've only read about it lose ten minutes and still get it wrong.
We built console simulators to close that gap.
What "console simulator" actually means
A simulator is not a video walkthrough. It's not a flashcard deck of screenshots. It's a real, in-browser application that:
- Renders the actual console UI you'd see at AWS, Azure, or GCP — the same buttons, the same forms, the same multi-tab dialogs.
- Runs real CLI commands against simulated state.
aws ec2 describe-instancesreturns JSON shaped exactly like the real API. - Holds an in-memory resource store that obeys the same invariants the real provider does: you can't attach an internet gateway twice; cross-region operations don't see resources in other regions; security groups actually filter traffic in the simulated network plane.
- Scores against the real DOM and real resource state. Each lab has a graded checklist. Step 5 isn't "did you click a button" — it's "is there now an IAM role with this trust policy and these attached managed policies." If you accomplished the goal a different way than the lab outline expected, that's still correct.
That last point matters more than it sounds. Lab platforms that score against a recorded macro of clicks fail when you take a slightly different route. Ours doesn't, because it inspects state.
Where we are today
As of this post:
- Over 970 hands-on labs are live and verified under the strict-pass standard described above. Every step drives the actual DOM. Every checkpoint queries the actual simulated resource store. Every lab passes the audit gate before it ships.
- 45 cloud certifications covered — every AWS, Azure, and GCP cert AccelaStudy® AI tracks has hands-on lab coverage of the topics that show up most heavily on the real exam.
- 70+ services simulated. Compute, networking, storage, security, identity, observability, serverless, databases, container orchestration. The big surfaces.
The strict-pass corpus is fully audited — every lab in it has been mechanically verified to use real data-testid selectors and real resourceTypes, not stubs. We'd rather ship 970 labs we know work than 2,000 with sloppy parts.
CompTIA, Kubernetes, GitHub, and a handful of others are the next batch. Same standard, no shortcuts.
What this means in practice
A few things change when your prep includes hands-on labs that aren't a hassle:
You stop being scared of the console. The first time you create a custom IAM policy is in a lab where there's no dollar amount attached to it, no production blast radius, and no permission denied error from your employer's account that you can't actually edit.
You build muscle memory for the right paths. The exam doesn't ask "describe how to attach an IAM role to an EC2 instance." It asks situational questions where the answer depends on whether you remember that you do that from the EC2 dashboard, not the IAM dashboard. People who've done it remember.
You see the same screens you'll see at work tomorrow. Console layouts evolve, but the underlying nouns — security groups, route tables, IAM users vs. roles, S3 bucket policies vs. ACLs — don't. Practicing in the simulator builds intuition that transfers to whatever account you log into next.
You don't get bills. No more setting an alarm to delete the test cluster you spun up. No more forgetting about a NAT gateway that's been costing you $0.045/hour for three weeks. Real-world cost, zero in our simulators.
What it doesn't do
It doesn't talk to the real cloud. By design.
You can't bring your real AWS account into the simulator and operate on it. You can't deploy a real production system from a lab. The simulator's job is to teach you the console behavior so that when you're back at work, the cloud feels familiar — not to be the cloud.
For learners who already have an employer-provided sandbox, that's fine. The simulator is a complement, not a replacement. For learners who don't, it's the entire point: certification-grade hands-on practice without a credit card.
How to use them
The labs are wired into the course pages. When you're studying for AWS Solutions Architect Associate, the labs that touch the topics on that exam blueprint show up under the course outline, sorted by difficulty.
You can run them ad hoc to practice a specific service, or you can let Autopilot schedule them. Autopilot tends to drop a lab into your day when your proficiency on a topic looks paper-thin — when you can answer questions about VPC peering correctly but slowly, or get the conceptual questions but stumble on the operational ones. That gap between "I know it" and "I can do it" is exactly where labs do the most.
Start with the cert you're studying for, pick the topic where you're least confident, and try one lab. If it's the first time you've built a thing rather than read about it, you'll feel the difference inside fifteen minutes.