How I Became an AWS Community Builder¶
A few years ago it was regular DevOps: deploys, scripts, "why did it crash again." Then I went deeper into Kubernetes and cloud-native — and the way I think changed.
What Changed¶
Before: one server, one app, one deploy. If something crashed — checked logs and restarted.
Then I started thinking in clusters. Not "where is it running" but "how does the system recover on its own." Not "deploy" but "design a platform so deploys are part of the process."
This wasn't a "let's dive into cloud-native" decision. Daily work just gradually shifted the focus. More containers, more EKS, more questions like "how do we scale this without pain."
AWS and Containers¶
The AWS ecosystem for containers isn't just ECS or EKS. It's ECR, Fargate, Load Balancers, IAM for pods, and a bunch of details you have to wire together.
Example: I needed to store ML models, Helm charts, and Docker images in one place. Turned out ECR supports OCI — you can push everything to a single repo. Wrote an article about it — and that was already a step toward the community.
What Community Builders Gives You¶
Honestly: it's not a magic life change. It's access to early previews, connection with other Builders and with AWS. A chance to ask questions to people who've walked similar paths.
There are limits too: the program doesn't guarantee a career boost, you have to invest time in content and engagement yourself. But if you're already writing, speaking, or helping others — it's a natural next step.
Who Helped Along the Way¶
Thanks to Max Ivashchenko, Anna Jabłońska-Oszust, Viktor Vedmich, Cherevatenko Vsevolod, Vadym Kazulkin, Anton Babenko — for advice, examples, and motivation. And to AWS for the opportunity to be part of the program in the Containers category.
What's Next¶
Planning to go deeper into Kubernetes and cloud-native patterns, share practical production cases, and write about what actually works. If that interests you — you can follow on LinkedIn or AWS Community.