AWS (US-EAST-1) Outage explained in plain English 1. Started with a DNS issue that stopped AWS services from talking to each other. 2. This caused DynamoDB to fail, which many AWS services depend on. 3. EC2 instances & Lambda functions began failing as the problem spread. 4.
Home / LinkedIn creators / Govardhana Miriyala Kannaiah

Govardhana Miriyala Kannaiah
I help businesses with Digital & Cloud Transformation Consulting | 49,000+ read my Practical DevOps & Cloud newsletter | Runs Job Surface helping job seekers find hidden DevOps & Cloud roles
We read 561 of their posts. Here is what they actually do.
Engagement over time
Average likes per post, by month.
That puts them in the 43th percentile of the 1,360 creators we track in the 100K to 1M follower band. Reach is not the same as resonance, and this is the ratio that separates them.
Their hooks, word for word
The opening line of their best-performing posts. This is what stops the scroll.
- AWS (US-EAST-1) Outage explained in plain English5.1K likes
- Not a joke, many DevOps engineers don’t fully understand the `pod.yaml` file structure or the role each part plays in defining a pod.4.8K likes
- For Cloud Engineers who are confused with private vs public IPs 👇3.9K likes
- Most Kubernetes errors aren’t Kubernetes errors. They’re Linux.3.4K likes
- Hiring in DevOps is broken.3.2K likes
- I once asked this in an AWS cloud engineer interview.3.1K likes
Content pillars
What they post about, with a line from a real post as evidence.
- Core Fundamentals over Tool Chasing
Multiple top posts urge mastering Linux and networking before touching Kubernetes.
- Plain-English Incident & Technical Deconstructions
Top post explains major AWS outage step-by-step for cloud and DevOps engineers.
- Industry Realities & Career Friction
Criticizes broken DevOps job specs and maps tool knowledge to business salary outcomes.
Signature moves and voice
The repeatable moves that show up across their best posts.
- Open with contrarian fundamentals ('Most Kubernetes errors are Linux')
- Break down complex networking numbers into bite-sized reference ranges
- Append a standard newsletter pitch with explicit repost call-to-action
What works for them
Patterns that separate their top posts from the rest.
- Real-world incident breakdowns using numbered cause-and-effect sequences drive peak viral reach.
- Contrarian takes exposing prerequisite knowledge gaps heavily outperform generic link listicles.
- Practical interview questions with common misconception traps generate strong comment engagement.
When they post
Every post, grouped by day of week.
Best day is Friday at 670 average likes. Tuesday is their weakest at 479.
What format works
Text, image, video or carousel, ranked by what actually lands for them.
| Format | Posts | Avg likes | |
|---|---|---|---|
| Image | 415 | 624 | |
| Text only | 144 | 372 | |
| Carousel | 1 | 290 | |
| Video | 1 | 24 |
Format fingerprint
How their posts are built, measured across every post we analysed.
Steal this
Moves you can apply to your own posts this week.
- Explain major industry outages simply in four numbered sequential steps.
- Challenge popular tool adoption by highlighting forgotten foundational prerequisites like Linux.
- Contrast theoretical technical calculations against realistic cloud provider reservation limits.
Best-performing posts
Ranked by likes, across everything we analysed.
Not a joke, many DevOps engineers don’t fully understand the `pod.yaml` file structure or the role each part plays in defining a pod. 👋 PS - I wrote an article including advanced options like probes, node and pod affinity with a detailed breakdown of this use case in my newsletter here:…
For Cloud Engineers who are confused with private vs public IPs 👇 10. 0. 0. 0 to 10. 255. 255. 255 - large corporate networks and cloud VPCs 172. 16. 0. 0 to 172. 31. 255. 255 - mid size networks, Docker uses this by default 192. 168. 0. 0 to 192. 168. 255.
Most Kubernetes errors aren’t Kubernetes errors. They’re Linux. Almost every pod, every container, every node... runs on Linux. Troubleshooting a pod stuck in CrashLoopBackOff? You’ll end up checking Linux logs. Struggling with persistent volumes? You’re debugging Linux file systems.
Hiring in DevOps is broken. Ever seen a job post asking for 11 years of Kubernetes experience when Kubernetes itself is just about that old? That is DevOps hiring today. Everyone wants "experts" but forgets that DevOps is a mindset, not just a toolset.
Similar creators
Comparable follower counts, analysed the same way.
Stop paying $3,000 for what 2pr does in 1 minute.
free trial, no limits on requests — start growing on LinkedIn today.
Built from public LinkedIn posts, last refreshed 2026-10-24. Follower counts and engagement change over time. Govardhana Miriyala Kannaiah is not affiliated with 2pr.io.