Welcome — what this AWS blog is for
I run small AWS proofs of concept in a home lab. This is where I write them up — honestly, with the commands, so you (and future me) can reproduce them.
Why a POC blog?
Most cloud tutorials show the happy path. Real experiments are messier: something doesn't have the permissions you expected, a service behaves differently in one region, or a "five-minute" setup eats an afternoon. Those rough edges are exactly the useful bits, so I'll write them down rather than quietly fixing them and moving on.
What to expect
Short, focused posts built around a single question — "can I do X on AWS, and what does it actually take?" Each one aims to include the goal, the setup, what happened, and a couple of reusable takeaways. Where it helps, there'll be copy-pasteable commands like aws sts get-caller-identity so you can follow along.
Terminal
# the first thing I run in any new POC — confirm which account/role I'm in
aws sts get-caller-identityHome-lab rule #1: tear it down. Everything here is built to be deleted afterwards, and I'll flag anything that can quietly run up a bill.
Topics I'll likely cover
Serverless odds and ends (Lambda, EventBridge, Step Functions), a bit of networking (VPCs, subnets — handy alongside the site's CIDR calculator), IAM experiments, infrastructure-as-code with CloudFormation and Terraform, and the occasional "is this new service any good?" test drive.
Follow along
New posts land at the top of the blog index. If you work across clouds, the AWS ↔ Azure ↔ GCP service map pairs nicely with these write-ups.
A personal home-lab experiment blog, shared as-is and not affiliated with Amazon Web Services. Always check current AWS pricing and docs, and tear down test resources to avoid charges.