Yashvi Kothari

How Web Requests Work: DNS, TCP/IP, TLS, HTTP A protocol-level breakdown of DNS, TCP/IP, TLS, HTTP: mapped to the OSI model to understand what happens in every layer.

Read “How Web Requests Work: DNS, TCP/IP, TLS, HTTP“ by Yashvi Kothari on Medium:
medium.com/@yashvikotha...

I have completed a guide kinda kitchen analogy to walk you through these 5 services.

Spend a weekend with it, and you'll understand 80% of what powers the internet.

Read
builder.aws.com/content/2uwN...

#AWS #CloudComputing
@awscloud.bsky.social
@awscmblogposts.bsky.social
#AWScommunity

Lambda is code that runs on demand.

No servers to manage. It only works when triggered. It's the ultimate leverag,i.e automating small tasks that would otherwise consume your time and resources.

A house with no locks is not a home. IAM is the security guard for your AWS resources.

It answers one question: "Who can do what?"
The most common cloud failures are not tech failures; they are human failures of permission. Use IAM to grant least privilege.

Data needs a librarian. RDS is a managed database that organizes and protects your information.

It handles backups, patching, and scaling for you. You focus on building, not on database administration.

Every engine needs fuel and a place to park. S3 is your infinite storage pantry.

Store images, logs, backups, or even host a simple website. It’s cheap, durable, and universally accessible. It’s the hard drive of the internet.

It's just someone else's computer.

When you launch an EC2 instance, you're renting a computer. You pay only for the time you use it. It's the engine for your application.

AWS has over 200 services. You only need 5 to build most things.

EC2 → A computer.
S3 → A hard drive.
RDS → A database.
IAM → A security guard.
Lambda → An automation button

tl;dr:
Best practices are the floor.
Ground Hacks/hands on tricks and knowledge is the ceiling.
Go learn, ship, break, fix, and share—until your hard-won lessons become your unfair advantage.

One can’t outsource this.

No blog, no course, no certification replaces ftom personal projects /practical labs /ground experience which keeps compounding.

Yes so human experience that human touch is hard to replace: not because they know more, but because that kinda knowledge is uniquely theirs

Mentorship speeds this up.

Find someone who’s shipped at scale: ask them the “dumb” questions.

You’ll uncover the hidden “why” behind the “how.”

the stories, the failures, the unspoken rules.

to acquire this edge
Build in public,take ownership at workplace/projects.

Ship real systems, break them, fix them, and write about what you learned.

Most people never get past “hello world,” so your scars become your leverage.

Eg:-
Redis:
Best practice say, “Use streams for real-time data.”

But the expert /engineers tackle and understand how to benchmark stream sharding, recover gracefully from a network split, or tune for sudden traffic spikes.

This isn’t in the docs.
It’s in the scars.

A learning( intuition one) from shipping, breaking, fixing, and relearning over years.

It’s understood, context-sensitive, and yet invisible from outside still we can make a way forward.

Documentation gives you the first 70-80%.

But the last 20-30%
-> the real edgecomes from long-tail knowledge.

are the best(engineers/SMEs/experts) still paid a premium?

Because value isn’t in what you can read -> it’s in what you can never write down.

All the best practices in any field are easily Googled.
They’re documented, standardized, trained for ai,commercialized,etc

What Engineer breaks and understand that Best Practices Can’t Teach ?

Thanks 😭✨

You get the opportunity. You're full of excitement and curiosity. No one expects You to be an expert; you're a student of the game, absorbing everything you can and finding your place. (year 1)

Luck gets you started, but consistency keeps you going. You move from learning to sharing. Your contributions become a habit, proving your passion wasn't a one-time spark but a steady flame.(year 2)

This is the hat-trick. It's no longer luck or just consistency; it's part that sustained impact. Commitment (year3)

Luck is an event.
Consistency is a system.
Commitment is an identity.

AWS Community Builder 3rd year Renewal

AWS Community Builder 3rd year Badge

Happy to announce my 3rd renewal as an AWS Community Builder! A hat-trick. 😭🎉

Deeply grateful for this opportunity and the entire AWS community.

The goal remains the same: learn, build, share, and empower others.
#AWS #CommunityBuilder #AWSCommunityBuilder

Inspired by the "Build Games with Amazon Q CLI" New Blog Post

dev.to/aws-builders...

#AmazonQCLI #q #amazonq #awscommunity

Unpacking VMs and Containers Technology: Docker vs VirtualBox Understanding the trade-offs between full VMs and agile containers for development and deployment.

I have compare two #virtualization #containerization covering everything from their history to hands-on examples. Do Share your experiences in the comments! #Docker or #VirtualBox: Which do you prefer and why? 🤔 #devops #cloudops #devsecops #cloudsecurity #linux
medium.com/@yashvikotha...

Thankyou DEV team

😊 Part 2 Coming Soon
dev.to/aws-builders...

Troubleshooting will be shared in Part 2 within my restricted sandbox 😊.
Additionally, changes have been made to my IaC template sourced from the official website I had used.

Using Pulumi IaC to deploy NextJs static website with AWS S3 and EC2 This is a submission for the Pulumi Deploy and Document Challenge: Fast Static Website...

dev.to/aws-builders...

Troubleshooting will be shared in Part 2 within my restricted sandbox 😊.
Additionally, changes have been made to my IaC template sourced from the official website I had used.

@dev.to Submission #awscommunitybuilder
#devcommunity

😀