Janhavi Jagtap

Associate DevOps Engineer | AWS | Linux | Docker | Kubernetes | Terraform | CI/CD | Learning in Public 🚀

[Janhavi Jagtap @JanhaviTechAWS]

🚀 Starting my 30-Day DevOps Journey!
For the next 30 days, I'll be learning and sharing:
☁️ AWS
🐧 Linux
🐳 Docker
☸️ Kubernetes
⚙️ Jenkins
🏗️ Terraform
Goal:
✅ Learn consistently
✅ Build projects
✅ Prepare for DevOps & SRE interviews
Let's grow together! 🚀
#DevOps #AWS #SRE

[Janhavi Jagtap @JanhaviTechAWS]

@OdysseyBunty fewer large instances - simplicity and high compute needs
more small instances - better scalability, availability, and fault tolerance
Actually it's depends on workload

[Janhavi Jagtap @JanhaviTechAWS]

@cloudandtechie Needs to be scalable, fault-tolerant

[Janhavi Jagtap @JanhaviTechAWS]

@clovisdsdo S3 is the storage service, while an s3 bucket is a container inside S3 where you actually store your objects

[Janhavi Jagtap @JanhaviTechAWS]

@_vmlops 😅😅

[Janhavi Jagtap @JanhaviTechAWS]

@Taniyatweets_ Linux - I’d choose control and flexibility over convenience

[Janhavi Jagtap @JanhaviTechAWS]

@Taniyatweets_ Coding

[Janhavi Jagtap @JanhaviTechAWS]

@chanduuu_cs accuracy is the most important factor, after that we prioritize speed.

[Janhavi Jagtap @JanhaviTechAWS]

@neerajjj6785 Nooo..,.

[Janhavi Jagtap @JanhaviTechAWS]

@clovisdsdo You can’t directly move an ec2 instance to another subnet. I’d create an AMI of the existing instance, launch a new instance from that AMI in the correct subnet, test it, and then terminate the old instance.

[Janhavi Jagtap @JanhaviTechAWS]

🚨Day 28/30 - AWS Disaster Recovery

Production systems need a plan for failures.

Backup ≠ DR

Backup → Recover data
DR → Recover the entire service

RPO + RTO + Failover + Testing = Reliable DR

#DevOps #AWS #SRE #Cloud #DisasterRecovery

[Janhavi Jagtap @JanhaviTechAWS]

@uday_devops Cloud trail

[Janhavi Jagtap @JanhaviTechAWS]

High Availability ≠ simply adding more servers.

A production system needs redundancy + health checks + monitoring + automated recovery + tested failover.

Secret tip- If failover has never been tested, you don't really know whether your HA design works.

[Janhavi Jagtap @JanhaviTechAWS]

🚀Day 27/30 - High Availability & Scalability

Production architecture-
Route 53→ALB →EC2/EKS →DB
✅Multi-AZ
✅Auto Scaling
✅Health Checks
✅No Single Point of Failure

Goal:Reliable systems that stay available even when components fail.
#DevOps #AWS #SRE #Cloud #SystemDesign

[Janhavi Jagtap @JanhaviTechAWS]

@prayag_sonar OpenCode said "bring it on" to the whole industry😅

[Janhavi Jagtap @JanhaviTechAWS]

@BytePilotLabs True, I'd also add checking is step 1, but actually testing failure (chaos engineering/ manual failure injection) confirms if redundancy really works or just looks good on paper

[Janhavi Jagtap @JanhaviTechAWS]

@Rabay_Hasan AWS

[Janhavi Jagtap @JanhaviTechAWS]

@PratikSinhatwt No, Practical experience matters, especially understanding how the system actually works

[Janhavi Jagtap @JanhaviTechAWS]

@willie_sre Never assume a deployment is safe just because the pipeline is green. Production has a way of finding the edge cases your tests missed😂

[Janhavi Jagtap @JanhaviTechAWS]

@the_codewala it’s a data-interchange format used to store and transfer structured data...

[Janhavi Jagtap @JanhaviTechAWS]

@kritikakodes Maybe the vibe ends where kubectl apply begins..😂

[Janhavi Jagtap @JanhaviTechAWS]

@ydamitcodes Security