Okay, so I finally played with the ACloudGuru Playground and it's... awesome.

Lou (🚀 Open Up The Cloud ☁️) - Jan 25 '21 - - Dev Community

Anyone yet had a chance to play around with the ACloudGuru cloud playground? If you don't know what it is, there's more information on the ACloudGuru website.

Disclaimer: I'm not affiliated with ACloudGuru in any way (but if they want to get in touch, they can 😉 as I really like the product).

Anyway, I finally got around to having a play this last weekend and I must say, it's awesome. I'm surprised more people aren't talking about it.

Also note: I think they might have taken the functionality from Linux Academy during their acquisition, I'd be curious to know if this is the case.

 Why am I raving about it?

  • No chance of a horrifying bill
  • No worries about cleaning up resources
  • No chance of credentials leaking and security hacks
  • No need to get out a credit card to sign up
  • Works on all major cloud providers
  • Easily record/screenshot your screen without fear

I was finding myself just going crazy creating resources, tinkering with things, etc, completely uninhibited experimentation is so great for learning.

The playground pretty much does exactly what you need as a learner... I'll definitely be recommending it to other people who are new to cloud or learning.

AWS can be really scary to beginners, especially without guardrails. I once got a $3000 AWS bill when my credentials were leaked, oops.

Anyway, I'd love to know what you think, because I thought it's pretty awesome.


If you’re interested in Cloud I write a monthly newsletter for Cloud Software Engineers. I spend the month digging around the internet for the best cloud engineering content and provide a monthly summary. I read every article I share, and I focus on fundamentals as much as possible.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .