

Nikhil sinha
1K posts

@sinhaniik
SDE-1 @claimzippy → DevOps | Learning DevOps in Public | Docker • AWS • Linux • CI/CD | Real journey + mistakes | Open to DevOps roles (Remote/BLR)



Most people think AWS starts with EC2, S3, or Kubernetes. It actually starts with IAM. Because before anyone can launch a server, access a database, or upload a file, AWS needs to answer two questions: 1. Who are you? 2. What are you allowed to do? That's exactly what IAM solves. • Users → identities for humans • Policies → permissions written in JSON • Groups → permission management at scale Imagine a company with 100 developers. Without IAM: Everyone gets root access. One mistake can delete production databases, S3 buckets, or critical infrastructure. With IAM: You create individual Users for each employee. Then attach Policies that define exactly what actions they can perform. Example: Allow: * Read S3 buckets * Launch EC2 instances Deny: * Delete production databases But managing permissions user-by-user doesn't scale. That's where Groups come in. Create a "Developers" group. Attach S3 and EC2 policies once. Now every developer added to that group automatically inherits those permissions. Need to give all developers EC2 access tomorrow? Update the group once. 100 users get the new permissions instantly. No manual updates. No permission drift. No chaos. The mental model: User = Who you are Policy = What you can do Group = How permissions scale IAM isn't just another AWS service. It's the security foundation that sits underneath every AWS service you will ever use. If you're learning AWS, understanding IAM early will save you from countless security mistakes later. What's the most confusing IAM concept for you right now: Users, Policies, Groups, or Roles? #AWS #IAM







🚨 SpaceX just pulled off the greatest financial engineering feat of the century. In about a week. Here's everything that happened, in order: – Folded xAI into a rocket company, turning "space logistics" into an "AI infrastructure" story overnight – Priced the IPO at a flat $135. No book-building, no range. Take it or leave it – Floated just 4% of the company. 556 million shares against 13 billion – Raised $75 billion at a $1.77 trillion valuation, near 100x revenue – Lobbied to get into major indices in ~15 trading days. Amazon took years. Forced buying, by law – Handed an unusually large slice of the float to retail. Tiny supply, an army of buyers – Watched the stock rocket past $200, up nearly 20% in a single session – Saw ~46% of the entire float trade hands in one day – Then announced a $60 billion all-stock buyout of Cursor, the AI coding tool – Structured it so the higher the stock trades, the fewer shares it has to print to pay A company losing $4 billion a quarter is now buying AI startups with paper it manufactured out of a 4% float. The scarcity that pumped the stock now makes its shopping spree cheaper. This isn't aerospace. It isn't even AI. It's the finest financial engineering of the century, and it's only week one.












JUST IN: Cursor unveils “Origin,” a new code storage & git hosting platform built to take on GitHub.


started my day with a good read





Top 5 Fun Linux Terminal Commands You Must Try