In this article, I will explain how Instagram is designed under the hood. My goal is to make it simple enough for anyone to understand, yet deep enough for someone interested in backend systems or cloud engineering.

The Heart of Instagram

At its core, Instagram is a read heavy system. For every photo uploaded, millions of people may view it. This means the architecture must make reading content extremely fast.

Most of Instagram’s speed comes from separating the work into layers. One layer handles user actions, another handles data, and another handles delivery. This separation helps the system scale as more people join.

The Feed System

The feed is Instagram’s most important feature. When you open the app, content shows up immediately. To make this possible, Instagram precomputes much of what you see before you even open the app.

Instead of calculating the feed at the moment you refresh it, the system prepares it in the background. This idea is called fan out on write. Whenever someone uploads a post, Instagram starts preparing feed entries for that person’s followers.

This way, the app has almost no waiting time when you open it. The content is already ready to load.

Using Caches For Speed

To serve millions of requests every second, Instagram keeps frequently accessed data in memory. Reading from memory is far faster than reading from a database. This is why Instagram uses caching heavily for feed content, user profiles, reels, stories, and even comments.

By serving most requests from cache, Instagram reduces the load on its main database systems and keeps response times low.

Storing Data At Scale

Instagram started with a simple relational database. But as the user base grew, the team migrated much of the system to distributed databases.

Images and videos are stored in object storage. Metadata such as captions, comments, likes, followers, and notifications are stored in distributed databases designed for high availability and fast reads.

The key idea is that different types of data need different types of storage. A photo is large and rarely changes. A like count is tiny and can change every second. Each of these needs a different storage strategy.

The Role of Microservices

As Instagram expanded, the engineering team moved from a monolithic system to a microservices architecture. Each major feature like feed, stories, search, messaging, notifications, or ads works as a separate service.

This allows teams to build, deploy, and scale each service independently. If the reels service needs more capacity during peak hours, they can scale only that service. The rest of the application continues running smoothly.

Microservices also reduce the risk of system wide failures. If one service has issues, others remain stable.

Content Delivery Across The World

One of Instagram’s biggest challenges is delivering photos and videos quickly anywhere in the world. The solution is a global content delivery network.

A user in India should not wait for a video stored on a server in the United States. Instead, the video is cached on servers closer to the user. When they open the app, the content loads from the nearest location.

This design keeps Instagram responsive even for users far away from main data centers.

Messaging and Realtime Interactions

Sending a message must feel instant. Seeing a like or comment notification must feel immediate. Instagram relies on real time communication protocols to make this happen.

When a user sends a message, the system routes it through a high performance chat service that maintains connections with millions of devices simultaneously. This service is optimized for low latency and can deliver updates within milliseconds.

Realtime notifications follow a similar pattern. The system maintains lightweight connections and pushes updates the moment something happens.

Machine Learning Everywhere

Machine learning influences almost every part of Instagram. It decides what appears in your feed. It powers recommendations on Explore. It filters spam. It detects harmful content. It ranks reels. It helps the platform personalize what each user sees.

These models run on large clusters of GPUs and specialized infrastructure. They process enormous amounts of data every day and continuously retrain to improve accuracy. ML is one of the hidden engines that keeps Instagram engaging for billions of people.

Building Systems That Grow

The most impressive part of Instagram’s engineering is not a single feature. It is the mindset of building systems that can grow continuously.

Every component is designed to scale horizontally. When more users join, more servers can be added. When new features launch, new microservices handle them. When data grows, storage is expanded across regions.

Instagram’s architecture is not static. It is a living system that evolves with user behavior and technological change.

My website : https://cloudkinshuk.in

My LinkedIn : https://www.linkedin.com/in/kinshukjainn/

My twitter : https://x.com/realkinshuk004

But as I started working with more powerful tools like Docker, Kubernetes, and the broader AWS ecosystem, I kept hearing the same advice from seniors and online communities: "You should use Linux." For a long time, I resisted. Why switch when everything works?

My perspective changed when I discovered WSL2 (Windows Subsystem for Linux). It was my first real taste of the Linux world, and it opened my eyes. Without ever leaving Windows, I began to understand why Linux is considered the gold standard for developers. This isn't a Windows vs. Linux debate, but my personal observation on the real, practical advantages Linux offers, especially for students like us.

The Command Line Isn't Scary, It's Powerful

On Windows, we often rely on graphical interfaces to get things done. The command line can feel like an afterthought. In Linux, the command line, or shell is the heart of the operating system. When I started using it through WSL2 , I realized it wasn't just for running an occasional command; it was for controlling everything.

Simple commands for finding files, managing processes, and connecting to servers are incredibly fast and efficient. Most importantly, the servers where our applications will eventually run (like an AWS EC2 instance) don't have a fancy user interface. They are managed entirely through the command line. Getting comfortable with it early on is a massive advantage for any future developer.

Software Installation is a Breeze

Remember the process of installing a new tool on Windows? You search for it online, find the right download page, download a .exe file, and click "Next" through a series of installation windows.

In the Linux world, this is handled by a package manager. For Ubuntu (which is what I use in WSL2), the package manager is called apt. Instead of hunting for software, I can just open my terminal and type a single command:

sudo apt install nodejs

That's it. The package manager finds the right version, installs it, and sets it up for me. It's like having an app store for all your development tools. It saves an incredible amount of time and helps avoid the classic "path" configuration headaches that often frustrate beginners on Windows.

Develop in the Same Environment Your Code Will Run In

This is perhaps the biggest "aha!" moment I had. Most of the internet from the servers that host websites to the containers managed by Docker and Kubernetes runs on Linux.

When you develop on a non-Linux system, your code runs in an environment that is slightly different from where it will be deployed. This can lead to the dreaded "but it works on my machine!" problem, where code that runs perfectly for you breaks when it's deployed to a server.

By using Linux/ WSL2), you create a development environment that is nearly identical to the production environment. This consistency means fewer surprises and easier debugging. My work with Docker became so much smoother once I was building and running containers in a native Linux environment right on my Windows machine.

You Are in Complete Control

Linux is open source, which gives you an incredible amount of freedom and control. You can customize almost every aspect of the operating system to fit your workflow perfectly. While this can seem daunting, it means you can build a lightweight, distraction free environment tailored specifically for coding.

⚠️ Personal Advice

For students, this also has a very practical benefit: Linux can run on almost anything. Have an old laptop that struggles to run Windows 10 or 11? A lightweight Linux distribution can bring it back to life and turn it into a perfectly capable development machine.

⭐ My Final Thoughts

I'm still a Windows user and love the windows operating system no os can come close to it and love its ecosystem and interface for day-to-day tasks. But incorporating Linux into my workflow through WSL2 has been a game-changer. It has made me a more efficient developer and better prepared me for the environments where my code will ultimately live.

If you're a student developer who, like me, has only ever used Windows, I highly recommend giving WSL2 a try. You don't have to abandon your familiar OS. You can get the best of both worlds and gain a crucial skill that will serve you throughout your career in software.

🚀 From Hype to Reality: Can AI Really Build Scalable SaaS Applications?

Over the past few years, Artificial Intelligence has evolved at an incredible pace. It's not just helping people with daily tasks—it’s revolutionizing how we approach problem-solving, especially in the tech world. Developers are no longer just building basic CRUD apps with AI. They're now using tools like ChatGPT, Cursor, Windsor, and others to attempt real-world solutions.

At first, this shift felt natural. AI was like a helpful tutor—a coding assistant that could unblock you, suggest optimizations, and support small-scale projects. But something changed in 2025.

💡 The New Buzz: “AI Can Build Complete SaaS Applications”

Social media, blogs, and developer communities started pushing a new narrative. Suddenly, AI wasn't just a helper—it was being seen as a full-fledged co-developer. Phrases like “vibe coding with AI” and “AI built my entire SaaS” exploded in popularity. This wave of content created a lot of excitement—and just as much tension—within the developer community.

The upside? It gave non-technical people the confidence to explore AI coding tools. They could now spin up apps, test ideas, and feel empowered in ways they couldn’t before.

But here's where the story gets more complicated.

AI Is Powerful—But It’s Not a Magic Wand

Let’s be honest: these models are state-of-the-art. They’ve proven useful across both technical and non-technical domains. But that doesn’t mean they can replace a skilled developer, especially when it comes to building something scalable, secure, and production-ready.

Here's the core issue: many users jump in with very vague prompts, without giving the AI proper context about what they want. They expect the model to somehow figure out the app’s architecture, purpose, tech stack, and scalability needs—all from a general request like:

“Build me a SaaS app that does X.”

This is where things start to break down.

The Reality of Building SaaS Apps with AI

Building a SaaS application requires:

• Clear understanding of the problem domain

• Knowledge of tech stacks, architectures, and scalability patterns

• Proper data modeling, security best practices, and user management

• Deep context about the user journey and core features

AI doesn’t automatically know this unless you tell it. Even then, it doesn’t always pick the best combination of tools or scalable practices. Most of the time, the code it generates:

• Works at first glance

• Lacks deeper structure

• Doesn’t scale well under real-world load

• Misses edge cases and security layers

In some rare cases, it might get close. But in most, developers will need to refactor heavily, rewrite parts, and sometimes even start from scratch.

Why This Happens: It’s All About the Data

These AI models are trained on vast amounts of publicly available code—including low-quality code. That means when you ask for a feature, the model might stitch together pieces of code that look right but are actually outdated, insecure, or inefficient.

Unless you're experienced, you might accept that code at face value—only to realize later that:

• It doesn’t meet performance benchmarks

• It’s vulnerable to attacks

• It becomes unmanageable as the app grows

And that’s where many non-technical users hit a wall. They get stuck, frustrated, and often give up—because they expected the model to handle the entire process without their involvement.

✅ My Honest Take (as a Student Developer)

As a BTech student from an Electrical Engineering background at a Tier 3 college, I find these tools incredibly exciting. They’ve helped me learn, build, and experiment faster than ever before.

But I also understand their limits. AI isn’t a shortcut to skip learning how web apps actually work. It’s a power tool, but you still need to understand the blueprint. Without context, even the smartest AI will struggle to build something meaningful. The future? I believe AI will become an even better coding companion. Maybe one day it will build scalable SaaS apps with minimal input. But in 2025, we’re not fully there yet.

🧭 Final Thoughts

AI is changing how we build. It’s opening doors for more people to create. But let’s not get swept up in the hype. Instead of expecting AI to replace us, we should learn how to work with it better—as thoughtful developers, clear communicators, and responsible builders. Because at the end of the day, it’s not just about writing code. It’s about solving real problems—with real understanding.

Follow / connect for more :

Twitter / X : @realkinshuk004

Instagram : kinshukjain._

linkedin : kinshukjainn

_________________________________________________________________________________________

To know more about me :

https://cloudkinshuk.in/blog

https://cloudkinshuk.in/

_________________________________________________________________________________________

For more Blogs :

https://blog.cloudkinshuk.in

That’s how PassGentoo was born: an open-source, customizable password generator built using React, TypeScript, Tailwind CSS, and the Web Crypto API—and yes, co-built with AI tools like ChatGPT to speed up development, design secure logic, and write clear documentation.

ZeroLeaks is now live on a custom domain via AWS Amplify and Route 53, offering full HTTPS security and DNS-level control.

Note : This is the initial stage launch soon there will be login , auth , passoword storing functionality too

🛠️ Tech Stack Overview

Here’s what powers PassGentoo:

• React + TypeScript: For building robust, component-based UIs with type safety.

• Tailwind CSS: Utility-first styling for rapid, responsive design.

• Vite: A blazing-fast bundler for development and optimized production builds.

• Web Crypto API: For cryptographically strong random values generated securely.

• AWS Amplify + Route 53: For hosting, DNS, and HTTPS deployment.

🤖 Why I Chose to Build This With AI

I used AI tools like ChatGPT throughout the development process—not as a shortcut, but as a collaborator. From brainstorming UI decisions to understanding cryptographic APIs and writing real-time entropy logic, AI helped me:

• Understand best practices in secure random number generation

• Structure my frontend for maximum performance and readability

• Break down complex concepts like entropy and crack-time estimation

• Write this technical blog and improve my documentation quality

Instead of guessing, I could ask AI-specific technical questions and use that knowledge to implement and refine code on my own terms. This approach helped me learn faster and build more confidently.

🔐 True Randomness with window.crypto.getRandomValues()

Most people don’t realize how critical true randomness is in password generation. Weak randomness = guessable passwords = broken security.

That’s why PassGentoo uses window.crypto.getRandomValues()—a browser-native method that pulls random bytes from your device's OS entropy pool, offering cryptographically secure randomness. This is much stronger than Math.random(), which is deterministic and not secure for sensitive applications.

const entropy = new Uint8Array(1024);
window.crypto.getRandomValues(entropy);

This creates an entropy pool of 1024 bytes—plenty to securely generate multiple passwords in a single session.

🧠 Why Entropy Matters

Each byte has 256 possible values (0–255), giving us a high level of entropy. High entropy ensures that each password:

• Is unpredictable to attackers

• Cannot be guessed or brute-forced easily

• Respects OWASP-recommended security practices

This client-side implementation means nothing is ever sent to a server, and all logic runs locally in the browser for maximum privacy.

🎛️ Key Features

• Adjustable password length (12–64+)

• Toggleable character sets (uppercase, lowercase, numbers, symbols)

• Exclude visually confusing characters like l, I, 0, O

• Option to generate pronounceable passwords for better usability

📊 Real-Time Strength Feedback

ZeroLeaks also includes a real-time password strength analyzer:

• Shannon entropy calculation (in bits)

• Estimated crack time based on real-world attack models

• Color-coded strength meter (weak → strong) with live updates

This helps users understand the real-world implications of their password choices instantly.

🌐 Hosting & Deployment

I deployed PassGentoo at zeroleaks.cloudkinshuk.in using:

1. vite build for production-ready output

2. AWS Amplify for fast static hosting

3. A custom domain purchased via Hostinger

4. DNS setup via AWS Route 53:

   • A records → Amplify endpoint

   • NS + CNAME → custom subdomains

5. SSL/TLS enabled via AWS for HTTPS security

📚 What I Learned

• How to integrate the Web Crypto API securely

• How to create a balance between usability and security

• How to structure modern frontend apps with Vite, React, and Tailwind

• How to set up a full DNS + HTTPS pipeline on AWS

• How to document projects cleanly with the help of AI-generated explanations

💡 Why This Matters ?

Whether you’re a developer or an everyday user, generating secure passwords shouldn’t be hard—or feel like magic. With AI as my assistant and mentor, I built a tool that’s both functional and educational.

🔗 Live Demo | GitHub Repo || Portfolio || CheckSEOHere

I invite you to fork, customize, or extend PassGentoo in your own way. Use it, learn from it, or just explore how security can be practical and transparent.

✅ Built by Me — With Guidance from AI

This project reflects my evolving journey in tech, supported by AI tools that helped fill knowledge gaps, explain security principles, and write production-ready code.

I didn’t use AI to avoid learning—I used it to learn faster, build better, and ship smarter.

Let’s build more ethical, open, and secure tools for the web. PassGentoo is my small step in that direction.

🔍 What is SEO?

SEO stands for Search Engine Optimization. It’s the process of improving a website to rank higher in search engines like Google, Bing, or Yahoo.

Imagine search engines as librarians. When someone asks, "What’s the best book on dinosaurs?", the librarian picks the most relevant one. Search engines do the same for websites.

If you search "how to make chocolate cake", you’ll get millions of results—but most users only click on the first 5–10 links. If your website doesn’t rank in that top section, it’s unlikely people will even see it.

That’s why SEO is crucial: Higher rank = More visibility = More traffic = More impact.

🌟 My SEO Results

I achieved a 100% SEO score on Google Lighthouse for my personal portfolio. Here’s a snapshot from my website and you can check google page insights:

🛠️ Tech Stack Used

Vite : Fast bundling & dev server

TypeScript : Type-safe development

React : Component-based architecture

Framer Motion :Animations & micro-interactions

Tailwind CSS : Responsive utility-first CSS framework

React Icons : Lightweight vector icons

AWS Amplify : Hosting with CI/CD and free SSL

AWS Route 53 : DNS and custom domain setup

Hostinger : Domain name purchase

✅ My Complete SEO Optimization Strategy

1. 📌 Page Titles & Meta Tags

• Unique <title> and <meta description> for each page.

• Focused keywords used naturally (no keyword stuffing).

• <meta name="robots" content="index, follow"> added for crawlability.

Tools Used:

• vite-plugin-html for static pages

• react-helmet for dynamic pages and routing

2. 🌐 Custom Domain + HTTPS

• Domain purchased via Hostinger.

• Connected to AWS Route 53 and hosted on AWS Amplify.

• Free SSL (HTTPS) enabled by Amplify.

✅ Boosts trust, SEO ranking, and fulfills Google’s secure site requirements.

3. 📱 Mobile-Friendly Design

• Built a responsive layout using Tailwind CSS.

• Tested on:

Utility classes like sm:, md:, lg: made responsiveness easy.

4. ⚡ Performance + Core Web Vitals

• Vite helped reduce bundle size and improve loading speed.

• Optimizations included:

Verified with Google Lighthouse:

• ✅ LCP (Largest Contentful Paint)

• ✅ FID (First Input Delay)

• ✅ CLS (Cumulative Layout Shift)

5. 📄 Sitemap & robots.txt

Created and hosted manually:

How:

• Added in the /dist directory for Amplify builds

• Verified via Google Search Console

6. 🔍 Open Graph & Twitter Tags

Boosts how your site looks when shared on social media.

<meta property="og:title" content="Kinshuk Jain | Cloud & DevOps Enthusiast" />
<meta property="og:description" content="Explore my projects, skills, and blogs." />
<meta property="og:image" content="https://myportfolio.com/preview.png" />
<meta property="og:url" content="https://myportfolio.com" />
<meta name="twitter:card" content="summary_large_image" />

7. 🔗 Canonical Tags & URL Structure

• Used <link rel="canonical" href="https://myportfolio.com/about" />

• Clean, hyphenated, lowercase URLs (no query strings for static pages)

8. 🏷️ Semantic HTML & Accessibility

• Used semantic tags: <header>, <main>, <footer>, etc.

• One <h1> per page, followed by logical heading structure.

• Added alt tags to all images.

• Used aria-labels and ensured full keyboard navigation.

9. 🕸️ Internal Linking

• Linked pages like:

Helps Google bots and users easily navigate the site.

10. 🌍 External Backlinks & Social Signals

Shared the portfolio on:

• LinkedIn bio

• GitHub profile

• Dev.to / Hashnode blogs

✅ Helps Google discover and crawl your website faster.

11. 📈 Google Analytics :

• Connected Google Analytics to monitor:

🧱 AWS Amplify Build Setup (Sample)

"scripts": {
  "build": "vite build"
}

In Amplify Console:

• Source directory: /

• Build command: npm run build

• Output directory: dist/

✅ Ensure robots.txt and sitemap.xml are inside /dist before build.

🎨 Animations with Framer Motion (SEO Friendly)

• Used animations like initial, whileInView, animate

• Avoided hiding important content during animations

• Made sure text and layout appeared early (for good LCP score)

🧠 Final Thoughts

As a student, this project taught me not just how to build a website—but how to make it visible and optimized for real-world users. Whether you're creating a personal blog, project site, or portfolio, following these SEO techniques will definitely help improve your site’s visibility, performance, and user trust.

In an era where engineering boundaries are increasingly overlapping, the key to standing out as an Electrical or Electronics Engineering (EEE) student lies in strategic upskilling. Whether you aim for core sector jobs, automation, embedded systems, or even a tech-centric path like cloud and IoT, the right certifications can fast-track your journey.

This comprehensive guide dives deep into career-defining certifications that bridge the gap between academic knowledge and industry-ready skills.

🎯 Why Certifications Matter

EEE curriculums often lean heavily on theory. While foundational concepts are crucial, the private sector thrives on practical application and problem-solving.

Certifications help you:

• Validate real-world skills beyond college transcripts

• Show recruiters you're serious about continuous learning

• Build confidence for interviews and industrial projects

• Explore interdisciplinary roles that blend electronics, software, and systems

🔌 1. PLC / SCADA Automation

Overview:
PLC (Programmable Logic Controllers) and SCADA (Supervisory Control and Data Acquisition) systems are the backbone of modern automation in manufacturing, power plants, and infrastructure.

What You’ll Learn:

• Ladder Logic Programming

• Timers, Counters, and Memory functions

• SCADA HMI design and control

• Communication protocols like Modbus, Profibus

• Tools like Siemens TIA Portal, Allen Bradley, Delta DVP

Why It’s Valuable:
Every automated plant—from steel to cement, from textiles to energy—uses these systems. Being skilled in them makes you immediately employable.

Recommended Institutes:

• Prolific Systems

• Sofcon India

• Technologics Global

• CETPA Infotech

Career Roles:

• Automation Engineer

• Control Systems Engineer

• Electrical Maintenance Engineer

• Instrumentation Engineer

Bonus:
Add an AutoCAD Electrical course to visualize circuits and create professional drawings.

Duration: 1–3 months

🛠️ 2. Embedded Systems with C/C++ or Python

Overview:
Whether it's smart TVs, robots, medical devices, or drones—embedded systems are at the heart of innovation.

What You’ll Learn:

• Microcontroller programming (Arduino, STM32, PIC)

• C/C++ or Python for embedded logic

• Sensor interfacing (IR, Ultrasonic, PIR, etc.)

• Real-time operating systems (RTOS)

• Communication protocols (UART, SPI, I2C)

Why It’s Valuable:
It opens doors to IoT, robotics, automotive systems, consumer electronics, and more.

Recommended Platforms:

• Coursera: Embedded Systems by University of Colorado

• Udemy: Mastering Microcontrollers & Embedded Systems

• Pantech Solutions for hands-on kits

Career Roles:

• Embedded Firmware Developer

• IoT Engineer

• Robotics Engineer

• Electronics Product Designer

Project Ideas:

• Smart irrigation system

• Line-following robot

• Home automation using NodeMCU

Duration: 1–3 months (project-based learning recommended)

☁️ 3. AWS Cloud Certifications

Overview:
Amazon Web Services (AWS) offers certifications that help you understand cloud computing—essential for IoT, energy analytics, and modern system design.

Certifications to Consider:

• AWS Certified Cloud Practitioner (Beginner)

• AWS Certified Solutions Architect – Associate (Intermediate)

What You’ll Learn:

• Cloud computing fundamentals (compute, storage, networking)

• Serverless technologies (Lambda, API Gateway)

• AWS IoT Core, DynamoDB, S3, IAM

• Basic architecture and deployment of apps

Why It’s Valuable:
Cloud-enabled energy systems, IoT data processing, and digital twin systems require engineers with cloud understanding.

Recommended Platforms:

• AWS Skill Builder (Free)

• Stephane Maarek’s AWS courses on Udemy

• Tutorials Dojo Practice Exams

Career Roles:

• Cloud Support Engineer

• IoT Integration Engineer

• Cloud Developer (Entry-Level)

• Site Reliability Engineer (with further learning)

Cost: ₹7,000–₹10,000

🌿 4. Certified Energy Manager (CEM)

Overview:
Offered by the Bureau of Energy Efficiency (BEE), India, this is one of the most recognized certifications in the energy efficiency domain.

What You’ll Learn:

• Energy auditing and instrumentation

• HVAC system analysis

• Lighting, thermal systems, and process integration

• Power factor, harmonics, and load management

Why It’s Valuable:
As energy costs rise, organizations want to reduce consumption without sacrificing performance. CEMs are specialists in identifying inefficiencies and proposing cost-saving measures.

Eligibility:
Usually taken by graduates or final-year students with project experience

Official Site: BEE India - CEM

Career Roles:

• Energy Analyst

• Power Consultant

• Energy Efficiency Auditor

• Renewable Energy Planner

Duration: 2–6 months (Exam cycle based)

📊 5. MATLAB & Simulink Associate Certification

Overview:
MATLAB and Simulink are industry-standard tools used in R&D, control design, simulations, and signal processing.

What You’ll Learn:

• Modeling dynamic systems

• Control theory simulations

• Signal processing filters and analysis

• Power electronics simulation

Why It’s Valuable:
This skill is valued in EV development, aerospace, research labs, and industries requiring simulation-heavy work.

Recommended Learning Platforms:

• MathWorks official courses

• Udemy’s Simulink/MATLAB tutorials

• MATLAB Onramp (Free)

Career Roles:

• Simulation Engineer

• Control Design Engineer

• R&D Engineer (EV/Defense/Aerospace)

Cost: ₹7,000–₹9,000 (certification optional, skills more important)

📱 6. PCB Design and Circuit Simulation

Overview:
Understanding how to design and test Printed Circuit Boards (PCBs) makes you job-ready for electronics manufacturing and R&D.

What You’ll Learn:

• Schematic design

• Component placement

• PCB layout and routing

• Circuit simulation and testing

Tools:

• KiCAD (Open-source)

• Proteus / Multisim

• Altium Designer

• Autodesk Eagle

Why It’s Valuable:
Designing your own circuits and turning them into products is a powerful skill. Hardware startups and electronics OEMs need this.

Career Roles:

• Hardware Design Engineer

• PCB Layout Engineer

• Testing and Validation Engineer

Project Ideas:

• Arduino clone board

• Sensor interfacing PCB for IoT

Duration: 1–2 months with hands-on practice

🔋 7. EV Technology & Battery Management Systems (BMS)

Overview:
Electric Vehicles are the future—and they run on smart battery and powertrain systems. This field offers cutting-edge opportunities for EEE students.

What You’ll Learn:

• Battery chemistry and cell balancing

• EV charging systems

• Motor controllers (BLDC, PMSM)

• CAN bus communication

Recommended Platforms:

• Skill-Lync EV Specialization

• DIYguru EV Tech Courses

• Udemy’s Electric Vehicle Design Series

Career Roles:

• EV Powertrain Engineer

• Battery System Developer

• BMS Algorithm Developer

• Power Electronics Engineer

Bonus:
Link this with MATLAB/Simulink skills for simulation-heavy design roles.

Duration: 2–4 months

🧠 Career Mapping: Choose Based on Your Goals

💡 Final Thoughts: Skills > College Tag

The engineering world rewards those who take initiative. Certifications are your fast track to skills that matter—ones that open doors, spark ideas, and create job opportunities.

✅ Pick one certification that excites you
✅ Complete at least one project alongside it
✅ Document it on GitHub or a portfolio site
✅ Add it to your LinkedIn with a write-up
✅ Apply confidently—skills speak louder than college names

"Certifications are not just a stamp—they’re a shortcut to skills, and skills are currency in the engineering world."

Now go ahead—explore, upskill, and engineer your dream career path.

In today’s tech-driven world, having a standout portfolio website isn't just a bonus—it’s essential. With the rise of AI tools and competition in every field, I realized it was time for me to build something that would reflect my skills, personality, and projects. So I started my journey, and now, I have my very own portfolio website—hosted with a custom domain and powered by modern web technologies.

In this blog, I’ll guide you step-by-step on:

• What tools and technologies I used

• How I deployed it on AWS

• Folder structure & configuration

• How YOU can clone or replicate it with zero prior experience

🌐 My Portfolio:

I purchased the domain from Hostinger and deployed the project using AWS services. Here's everything I used and how I used it.

Link : https://cloudkinshuk.in

An Overview :

If you're not very familiar with programming and don't want to create a separate project from scratch using React and TypeScript, you can directly jump to the “Cloning the Project” section using the navigation menu. This will simplify the setup process and allow you to easily customize the UI, code, and data to fit your needs.

🧠 Tech Stack & Tools

⚙️ Development Environment

• IDE: VS Code

• Package Manager: npm (primary), bun/yarn/pnpm (optional)

📦 Core Technologies

🎨 Fonts

• Poppins from Google Fonts

☁️ Deployment & Cloud Setup

🧭 Cloud & Hosting

• Frontend Hosting: AWS Amplify (Serverless, scalable, easy CI/CD)

• DNS & SSL: AWS Route 53

• Domain Provider: Hostinger (.in domain for ₹1000 / 2 years)

• Version Control: Git & GitHub

🔗 GitHub Repo: kinshukjainn/kinshukkportfolio

Flow Diagram of Architecture :

Beginner-Friendly Alternatives for Deployment

If you’re new to cloud deployments, these platforms are perfect starting points:

• Vercel

• Netlify

• Railway

• Heroku

For Intermediate/Advanced Users:

• Google Cloud Platform (GCP) — great if you like Google’s ecosystem

• Microsoft Azure — ideal for Microsoft fans

Building Process (From Scratch)

💡 Tip: Only use one package manager — npm or bun or yarn or pnpm. Using more than one can cause conflicts during deployment.

Step 1: Create Your React App

Using npm (Recommended for beginners):

npm create vite@latest my-project-name

Using bun:

run this command in your terminal before running bun create vite in your project directory in vscode :

bun install

bun create vite

Using yarn: ( if you know yarn installation well then only use it )

yarn create vite my-project-name

✅ Step 2: Install Project Dependencies

Navigate to your project directory:

cd kinshukkportfolio # your project directory can be different

Then install packages:

npm install

If using yarn or bun:

yarn install
# OR
bun install

📁 Folder Structure

Here’s what my folder structure looks like:

REACTPORTFOLIO/
├── kinshukportfolio/
├── node_modules/
├── public/
├── src/
│   ├── assets/
│   ├── components/
│   ├── socialmedia/
│   ├── App.tsx
│   ├── index.css
│   ├── main.tsx
│   └── vite-env.d.ts
├── .gitignore
├── package.json
├── tailwind.config.js
├── vite.config.ts
├── tsconfig.json
└── README.md

🎨 Tailwind CSS Setup

Install Tailwind CSS:

npm install tailwindcss @tailwindcss/vite

Configure vite.config.ts:

import { defineConfig } from 'vite'
import react from '@vitejs/plugin-react'
import tailwindcss from '@tailwindcss/vite'

export default defineConfig({
  plugins: [react(), tailwindcss()],
})

Add Tailwind Imports in index.css:

@import "tailwindcss";

🔌 Other Dependencies Setup

React Icons

npm install react-icons

Framer Motion

npm install framer-motion

Lucide React (Icon Library)

npm install lucide-react

▶️ Running the App Locally

After everything is set up, run:

npm run dev

You should see your site running at localhost:5173 (or similar).

📜 My package.json (For Reference)

{
  "name": "portweb",
  "private": true,
  "version": "0.0.0",
  "type": "module",
  "scripts": {
    "dev": "vite",
    "build": "tsc -b && vite build",
    "lint": "eslint .",
    "preview": "vite preview"
  },
  "dependencies": {
    "@headlessui/react": "^2.2.0",
    "@mui/icons-material": "^6.4.7",
    "@mui/material": "^6.4.7",
    "@tailwindcss/vite": "^4.0.14",
    "framer-motion": "^12.5.0",
    "lucide-react": "^0.482.0",
    "react": "^19.0.0",
    "react-dom": "^19.0.0",
    "react-icons": "^5.5.0",
    "react-router-dom": "^7.3.0",
    "react-syntax-highlighter": "^15.6.1",
    "tailwindcss": "^4.0.14",
    "uuid": "^11.1.0"
  },
  "devDependencies": {
    "@eslint/js": "^9.21.0",
    "@types/react": "^19.0.12",
    "@types/react-dom": "^19.0.4",
    "@vitejs/plugin-react": "^4.3.4",
    "eslint": "^9.21.0",
    "eslint-plugin-react-hooks": "^5.1.0",
    "eslint-plugin-react-refresh": "^0.4.19",
    "globals": "^15.15.0",
    "typescript": "~5.7.2",
    "typescript-eslint": "^8.24.1",
    "vite": "^6.2.0"
  }
}

🧪 Cloning the Project (For Beginners)

Want to replicate this exact setup? Here’s how:

1. Create a GitHub account (if you don’t already have one)

2. Visit my repo: github.com/kinshukjainn/kinshukkportfolio

3. Click "Fork"

4. Clone your forked version:

    git clone https://github.com/yourusername/reponame.git
    cd kinshukkportfolio
    npm install
    npm run dev
   

Here is a video of how to clone a forked repo :

Customize the content, styles, and animations to make it your own!

If you have proceed till here you are very near to deploy your own portfolio website on the cloud and also would be able to host it :

Alright Kinshuk! Here's a step-by-step beginner-friendly guide to help you:

Buy a Domain on Hostinger & Connect It to AWS (Amplify + Route 53)

Part 1: Buying a Domain from Hostinger

1. Go to Hostinger

   • Create an account if you don’t have one.

   • Login to your dashboard.

2. Buy a Domain

   • Click on "Domains" in the top navbar.

   • Search for your desired domain (e.g., cloudkinshuk.dev).

   • Click Buy Now and proceed with the payment.

3. Access Domain Settings

   • After purchase, go to “Domains” → “Manage”.

   • You’ll see options like DNS, Nameservers, WHOIS, etc.

Part 2: Set Up an AWS Account

1. Go to AWS Console

   • Click "Create an AWS account".

   • Fill in your name, email, and password.

   • Add billing info (₹2 might be deducted for card verification).

2. Sign In to AWS Console

   • Go to the AWS Console, sign in as a root user (with your email).

Part 3: Create Route 53 Hosted Zone

1. Search for “Route 53” in the AWS Console.

2. On the left panel, go to "Hosted Zones" → Create Hosted Zone

   • Domain Name: your domain (e.g., cloudkinshuk.dev)

   • Type: Public Hosted Zone

   • Click Create

3. Note Down the NS Records (Nameservers)

   • AWS will generate 4 NS records (like ns-123.awsdns-xyz.com).

Part 4: Update Nameservers in Hostinger

1. Go back to Hostinger > Domains > Manage

2. Scroll to "Nameservers"

3. Choose "Use custom nameservers"

Paste the 4 NS records you got from Route 53

ns-1962.awsdns-53.co.uk  
ns-897.awsdns-47.net  
ns-1136.awsdns-14.org  
ns-200.awsdns-25.com

Note: These are just examples and won’t work for your domain. You must use the exact NS records that AWS gives you after creating a hosted zone in Route 53. Always copy-paste from your actual AWS dashboard.

1. Save the changes
   ⏳ It might take 5 minutes to a few hours to reflect.

Part 5: Deploy Your Project with AWS Amplify

1. Go to AWS Console → Search for “Amplify”

2. Click on “Get Started” under Host a web app

3. Connect your GitHub Repository

   • Authorize GitHub → Select your repo (e.g., portfolio or blog)

4. Choose branch (e.g., main)

5. Click Next, then Deploy

🔄 Amplify will now:

• Build

• Deploy

• Host your site at a temporary domain like: main.abcd123.amplifyapp.com

Part 6: Connect Custom Domain (from Hostinger)

1. In Amplify → Click on your deployed app → Go to “Domain Management”

2. Click “Add Domain”

   • Enter your domain name (e.g., cloudkinshuk.dev)

3. Choose subdomains:

   • www.cloudkinshuk.dev

   • cloudkinshuk.dev

4. Click Save
   Amplify will show you CNAME and A records to be added in Route 53.

Part 7: Add Domain Records in Route 53 →

1. Go back to Route 53 → Hosted Zones → Select your domain

2. Click “Create Record”

   • Choose type A – IPv4 address

   • Select Alias = Yes → Choose Alias Target = Amplify target (will be shown)

   • Click Create

3. For www:

   • Create a CNAME record

   • Name = www

   • Value = Amplify's www.cloudkinshuk.dev target

Part 8: Enable Redirection from www → non-www

1. In Amplify > Domain Management

2. Click on "Edit" for domain settings

3. Check the box for Redirect www to root domain (www.cloudkinshuk.dev → cloudkinshuk.dev)

Done!

Now visiting your domain like https://cloudkinshuk.dev will open your Amplify-hosted project.

Pro Tips →

• DNS changes may take 5–60 minutes to propagate globally.

• Make sure your project has a proper build script in package.json (like next build or vite build).

• You can also enable HTTPS (SSL) from Amplify automatically.

Final Thoughts →

Creating this portfolio site helped me improve my React and cloud skills while giving me a central place to showcase my projects and resume. Whether you're a beginner or an experienced dev, building your own portfolio is the best investment in your career.

If you liked this guide or found it helpful, give the repo a ⭐ on GitHub and feel free to connect!

Connect With Me :

My social Links : →

• Portfolio: cloudkinshuk

• GitHub: kinshukjainn

• LinkedIn: kinshukjainn

• Instagram: kinshukjain._

• twitter(X) : kinshukjainn

While you're in charge of the school's overall operations, it's not realistic to place all the responsibility for growth and management solely on yourself or the staff. Instead, responsibilities are shared. As a principal, you delegate certain duties to both staff and students, ensuring that each group does its part. This distribution of responsibilities is key to the smooth functioning and success of the school.

Similarly, in the AWS Shared Responsibility Model, both AWS and the customer have their own roles. AWS takes care of the security of the cloud (like infrastructure, networking, and hardware), while the customer is responsible for security in the cloud (like data, access management, and configurations).

Just like a school cannot function properly without shared responsibility, cloud environments remain secure and efficient only when both AWS and the customer understand and fulfill their respective roles.

This analogy helps us clearly understand how the AWS Shared Responsibility Model works.

Some important principle of AWS customer responsibility model :

List of important principles of the AWS Customer Responsibility Model explained in simple English with a slight sarcastic touch, while still sounding like you know your stuff and respect AWS:

AWS Customer Responsibility Model – The "You Handle This" Edition

1. Your Data, Your Drama

AWS isn’t your babysitter. You put your data on the cloud? You better make sure it’s encrypted, backed up, and not publicly exposed unless you want a front-row seat to a data leak scandal.

2. You Control Access, So Don’t Give the Keys to Everyone

IAM (Identity and Access Management) is your responsibility. If your intern has admin access to your production server—congrats, you played yourself.

3. Patching Your OS Isn’t AWS’s Job

If you’re using EC2 or managing your own environment, patch it regularly. AWS won’t come knocking on your door with a “Hey, update available!” reminder.

4. Security Groups Are Not Suggestions

Leaving all ports open "just to test something" is like leaving your house unlocked because you’re “only going out for five minutes.” Guess what? Hackers don’t need five minutes.

5. You Pick the Services, So Don’t Blame AWS When You Mess Up

Chose the wrong storage class or made an S3 bucket public by accident? That’s on you. AWS gives you powerful tools, but with great power comes great... yeah, you know the drill.

6. Logs Exist for a Reason – Read Them Before the Fire Starts

Cloud trail , CloudWatch, and other logs are your eyes in the cloud. Ignoring them is like driving blindfolded and acting shocked when you crash.

7. Shared Responsibility Doesn’t Mean Shared Blame

Just because AWS handles the infrastructure doesn’t mean you get a free pass. If you mis configure something, it’s your circus, your monkeys.

Explore how each component of AWS architecture contributes to building scalable, secure, and reliable applications, whether for startups or large enterprises.

1. Amazon EC2 with Auto Scaling Group (ASG)

Amazon EC2 (Elastic Compute Cloud) provides virtual servers for your applications, while Auto Scaling Groups dynamically adjust the number of servers based on demand.

Scalability Benefits:
During high-traffic events, such as sales or viral campaigns, additional servers are automatically provisioned. Conversely, when demand decreases, surplus servers are decommissioned, optimizing costs and maintaining seamless performance.

2. AWS Elastic Load Balancer (ELB)

The Elastic Load Balancer efficiently distributes incoming traffic across multiple EC2 instances.

Scalability Benefits:
By balancing the load, ELB prevents any single server from becoming overwhelmed. It also ensures traffic is directed to healthy instances during deployments or outages, enhancing reliability.

3. Amazon S3 with Versioning

Amazon S3 offers robust storage solutions for files, backups, static websites, and media, with versioning to maintain multiple file versions.

Scalability Benefits:
With the capability to store unlimited data and support millions of users, S3 ensures data integrity and recovery from accidental deletions or overwrites through versioning.

4. AWS WAF, GuardDuty, and KMS

• WAF (Web Application Firewall): Shields your application from common threats like SQL injection and XSS.

• GuardDuty: Monitors for suspicious activities, such as unauthorized access attempts.

• KMS (Key Management Service): Provides encryption for data at rest and in transit.

Security and Scalability Benefits:
AWS integrates security at every level, automatically scaling protection as your user base expands, eliminating the need for manual management.

5. CloudFront and CloudFormation

CloudFront, a Content Delivery Network (CDN), caches content closer to users globally, while CloudFormation automates infrastructure deployment using templates (Infrastructure as Code).

Scalability Benefits:
CloudFront reduces server load and accelerates content delivery by serving it from nearby locations. CloudFormation enables rapid environment scaling and recovery, ideal for disaster recovery and global expansion.

6. Amazon RDS (Relational Database Service)

Amazon RDS offers managed database services supporting MySQL, PostgreSQL, and more.

Scalability Benefits:
RDS allows for increased storage and performance as your application grows, with features like read replicas, backups, and automatic failover to efficiently handle millions of queries.

7. ECS and ECR (Optional: Kubernetes)

• ECS (Elastic Container Service): Manages application containers.

• ECR (Elastic Container Registry): Stores container images.

• Optional Kubernetes (EKS): Provides advanced container orchestration.

Scalability Benefits:
Containers enhance application portability and efficiency. ECS and EKS automate scaling, container restarts, and cluster management, ideal for microservices and modern distributed applications.

Final Thoughts

This AWS architecture is designed for scalability, reliability, and security, making it suitable for everything from small websites to global enterprise applications. It offers:

• Automatic scaling during peak loads,

• High availability across regions,

• Built-in robust security,

• Simplified automation and recovery with CloudFormation.

Whether you're developing a social network, e-commerce platform, or internal tool, this setup is engineered to grow alongside your business.

kinshuk Jain : Management of blogs

See blogging is a great way of expressing your thoughts in public not only thoughts also the ideas . Your social media cannot make you ideas or thoughts to express everything .See you have some limitation on social media platforms and due to that you cannot express everything , until and unless you have a greate crediblity and impressive presence on social media platforms like instagram or twitter ( now X)

Reason 2 :

Through blogging your ideas get into public which is visible to mostly everyone until and unless you make it private or limit it to certain access . This can increase your chances of getting some opportunities towards you . This is making you a potential candidate for someone to hire you or who wants to collab / work with you .

Reason 3:

The blogging can make your skills represent in a different way for example: there are many skill set which cannot be shown on social media directly . There is a way but its not feasable enough make it possible or even if you do it it might not gain that much attention on social media platforms. So you can do that by blogging , its flexible, free and with single link you can represent all your ideas. These ideas and thoughts would be visible to everyone without any restriction

Like how you 
are reading my blog right now and 
enjoying !!! 😆

Reason 4 :

This also represents that you are not only serious about the work or skills, you are leveraging right now. As you are sharing thoughts in blogs that means , you are confident to share your thoughts / opinion on that particular skills and thats something which can make you stand out. That also shows the collaboration and open mindset for learning and growth. I think thats something which is absolutely game changer in your career and proffesional profile building .

Embarking on your cloud computing journey can be daunting, especially with the vast array of services offered by Amazon Web Services (AWS). However, AWS is quite approachable once you break it down into manageable parts. In this article, I will introduce you to five AWS services that are crucial for beginners, complete with real-world examples explained in straightforward terms.

1. Amazon S3 (Simple Storage Service)

Overview:
Amazon S3 functions like Google Drive for developers, allowing you to store files such as images, videos, and documents in the cloud, accessible from anywhere.

Use Case:
If you're developing a personal portfolio website and need a place to host your images and project screenshots, you can upload them to S3 and link them directly. Additionally, you can host an entire static website (HTML/CSS/JS) on S3 at little to no cost.

Benefits:

• Cost-effective cloud storage

• Simplified file sharing and backups

• Capability to host static websites

2. Amazon EC2 (Elastic Compute Cloud)

Overview:
EC2 is akin to renting a virtual computer on the internet, where you can install software, run websites, or even train machine learning models.

Use Case:
If you're learning Linux or developing a web application like a resume builder, you can launch an EC2 instance (a virtual machine), install Linux/Ubuntu, set up Apache or Nginx, and deploy your application.

Benefits:

• Complete control over your virtual server

• Ideal for hosting applications or learning Linux

• Easily scalable as your project grows

3. AWS Lambda

Overview:
AWS Lambda allows you to run your code without managing servers. Simply write your function, and AWS handles the rest.

Use Case:
Suppose you want to automatically send a thank-you email whenever someone submits a form on your site. With Lambda, you can write a small Python or Node.js script to accomplish this, running only when the form is submitted—eliminating the need for a server to run continuously.

Benefits:

• No server management required

• Pay only when your code executes

• Excellent for automation and backend logic

4. Amazon RDS (Relational Database Service)

Overview:
RDS simplifies the setup and management of databases like MySQL, PostgreSQL, or SQL Server in the cloud.

Use Case:
If you're creating a to-do list app and need a database to store user tasks, you can launch an RDS instance, connect it to your app, and let AWS manage updates, backups, and scaling.

Benefits:

• Simplified database setup

• Reliable and secure

• Automatic handling of backups and maintenance

5. AWS IAM (Identity and Access Management)

Overview:
IAM enables you to manage who can access your AWS resources and what actions they can perform, similar to setting up roles and permissions for your team or applications.

Use Case:
In a group project, if you want a colleague to assist in deploying a site, you can create an IAM user with limited access—perhaps only to EC2—ensuring they cannot accidentally delete your S3 files or database.

Benefits:

• Robust security control

• Best practice for team or multi-service environments

• Prevents accidental or unauthorized access

Conclusion

Starting with AWS doesn't have to be overwhelming. These five services—S3, EC2, Lambda, RDS, and IAM—are foundational to many cloud applications today. Mastering these will give you a significant advantage!

Pro Tip: Begin with AWS's free-tier eligible services and try building a small project using a few of these services—such as a blog site hosted on S3 with form submissions powered by Lambda.

Feel free to reach out if you'd like this content transformed into a Canva post or a carousel for LinkedIn/Instagram!