Enter the OSI Model — your go-to mental map for understanding how data moves from your laptop to a remote server (and back), across networks, protocols, layers, and devices.

🚀 What Is the OSI Model?

The OSI (Open Systems Interconnection) Model breaks network communication into 7 layers, each with a clear role. Together, they make sure data gets from Point A to Point B — securely, reliably, and efficiently.

Imagine sending a parcel:

• You write the message 📝 (Application Layer)

• Translate & seal it 📦 (Presentation)

• Start the delivery session 🚚 (Session)

• Split it into boxes 📦📦 (Transport)

• Add addresses 🏷️ (Network)

• Use the local courier 🏢 (Data Link)

• Deliver it physically 📮 (Physical)

That’s how your data travels online.

🧩 OSI Model – 7 Layers Explained

Layer 7 – Application

This is where users interact with network-based apps like browsers, email, or WhatsApp.

👉 Example protocols: HTTP, HTTPS, FTP, SMTP, DNS

Layer 6 – Presentation

This layer prepares data for the application by formatting, encrypting, or compressing it.

👉 Example: SSL/TLS (for encryption), JPEG, ASCII

Layer 5 – Session

Manages conversations (sessions) between devices — starting, maintaining, and ending them.

👉 Example: NetBIOS, PPTP

Layer 4 – Transport

Breaks data into packets, ensures it reaches the right app, handles retries and flow control.

👉 Example: TCP (reliable), UDP (fast but no guarantee)

Layer 3 – Network

Decides the best route to send data from source to destination across networks.

👉 Example: IP, ICMP, ARP, OSPF

Layer 2 – Data Link

Transfers data between devices in the same network and adds MAC addresses.

👉 Example: Ethernet, MAC address, PPP

Layer 1 – Physical

Moves raw bits (0s and 1s) through cables, Wi-Fi signals, or fiber optics.

👉 Example: Cables, Wi-Fi, Bluetooth, Hubs

👩‍💻 Why This Matters for

Every Role in Tech

✅ Developers

Understand how your front-end talks to back-end APIs and what can go wrong in that journey.

✅ QA Engineers

Diagnose test failures caused by session timeouts, protocol mismatches, or network delays.

✅ DevOps / SREs

Pinpoint issues in distributed systems: Is it DNS? Firewall? App port? OSI helps break it down fast.

✅ Security Engineers

Design protections across layers: encryption (Layer 6), firewalls (Layer 4), access controls (Layer 2), and more.

✅ Product Managers / Leads

Communicate more effectively with your tech teams by understanding how systems actually connect.

📷 A One-Page Visual to Simplify It All

To make learning easier, I’ve created a color-coded, beginner-friendly diagram that shows all 7 layers, their role, and real-world protocol examples.

✋ Final Takeaway

Understanding the OSI Model isn’t just theory — it’s a practical skill that helps you debug smarter, design better systems, build secure networks, and communicate clearly across teams in today’s connected tech world.

Whether you’re shipping code, testing features, maintaining uptime, or explaining bugs to stakeholders — this 7-layer model gives you clarity and confidence in how data truly flows.

👉 Like this kind of breakdown?

Subscribe now

Subscribe for beginner-friendly guides on Cloud, DevOps, Networking, and Tech Fundamentals — explained clearly, without jargon.

Let’s make tech simple, together. 🚀

🚀 Introduction

Goodbye DynamoDB, Hello Native S3 Locking!

Starting with Terraform 1.10, the S3 backend now supports native locking using S3 object versioning and lockfiles.

✅ No need to configure and maintain a DynamoDB table for state locking.

✅ Simpler, cleaner, and cost-effective Terraform backend setup!

In this post, you’ll learn:

• What’s changed

• Why it matters

• Step-by-step how to migrate

• Updated IAM permissions needed

• Common FAQs

🔥 What’s New?

Before Terraform 1.10:

• S3 stored the state file.

• DynamoDB managed the lock to prevent simultaneous updates.

Now:

• S3 does both state storage and locking natively!

• DynamoDB is no longer needed.

From Terraform 1.11:

• The dynamodb_table argument is deprecated.

• You’ll get warnings if you keep using it.

• Future versions may completely remove support.

🎯 Why It Matters

• 🚀 Simpler Setup: Only S3 is needed.

• 🚀 Lower AWS Costs: No DynamoDB throughput billing.

• 🚀 Fewer IAM policies: Only S3 permissions needed.

• 🚀 Fewer Failure Points: Reduced complexity.

🛠 How to Migrate — Step-by-Step

1. Upgrade Terraform to 1.10+

Check your current version:

terraform -version

Install Terraform 1.10 or newer if needed.

2. Enable S3 Bucket Versioning

S3 versioning must be enabled for lockfile support.

You can enable versioning for your bucket using the AWS S3 console or the command below. Replace <your-tf-state-bucket-name> with your bucket name.

aws s3api put-bucket-versioning \
  --bucket <your-tf-state-bucket-name> \
  --versioning-configuration Status=Enabled

3. Update Terraform Backend Configuration

Remove dynamodb_table From your current S3 backend config and add use_lockfile = true.

👉 Old (DynamoDB-based):

terraform {
  backend "s3" {
    bucket         = "your-tf-state-bucket-name"
    key            = "path/to/terraform.tfstate"
    region         = "us-east-1"
    dynamodb_table = "terraform-locks"
  }
}

👉 New (Native S3 Locking):

terraform {
  backend "s3" {
    bucket         = "your-tf-state-bucket-name"
    key            = "path/to/terraform.tfstate"
    region         = "us-east-1"
    use_lockfile   = true  # NEW: enables native locking using S3
  }
}

✅ The new important setting:

use_lockfile = true

(Default is true from Terraform 1.10+, but it’s better to explicitly set it for clarity.)

4. Update IAM Permissions

You no longer need DynamoDB permissions.

Update your IAM role or policy to allow only necessary S3 operations.

Minimal required permissions:

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": [
        "s3:GetObject",
        "s3:PutObject",
        "s3:DeleteObject",
        "s3:ListBucket"
      ],
      "Resource": [
        "arn:aws:s3:::your-tf-state-bucket-name",
        "arn:aws:s3:::your-tf-state-bucket-name/*"
      ]
    }
  ]
}

You can also add optional recommendations:

• s3:GetObjectVersion

• s3:DeleteObjectVersion

👉 These are helpful if your organization uses strict security controls around S3 object versioning and deletions.

5. Reinitialize Terraform Backend

After updating your configuration, you must reinitialize the backend.

terraform init -reconfigure

✅ This will update the backend settings without touching your state files.

6. (Optional) Clean up the Old DynamoDB Table

If no other systems are using it, you can safely delete the DynamoDB table.

aws dynamodb delete-table --table-name terraform-locks

⚡ Pro tip: Backup the table first if you’re unsure.

🚨 Important Notes

• use_lockfile = true is now the preferred and future-compatible setting.

• Starting Terraform 1.11, dynamodb_table will be deprecated — you’ll get warnings.

• In future versions (1.12+), dynamodb_table might be removed entirely, causing errors if not migrated.

• S3 versioning is mandatory for lockfiles to work correctly.

🔍 Common Questions

Q: Can I continue using DynamoDB?

👉 Yes, for now. But expect deprecation warnings after 1.11.

Q: Is native S3 locking production-ready?

👉 Yes, HashiCorp has officially documented and recommended it.

Q: What happens if I don’t enable versioning?

👉 Terraform will fail with an error because locking depends on S3 object versions.

Q: Do I need S3 Object Lock (WORM)?

👉 No. S3 Versioning is sufficient. Object Lock is not required.

🎯 Conclusion

Native S3 locking is the future for Terraform on AWS.

✅ Simpler backend.

✅ Lower infrastructure cost.

✅ Easier IAM management.

✅ Future-proof your projects before the old dynamodb_table breaks!

If you haven’t migrated yet — now is the perfect time! 🚀

These are the 4 Terraform state file mistakes I see most often in real-world DevOps projects.

❌ Manual edits

❌ Storing the state locally

❌ No locking

❌ Forgetting versioning

I made a short video breaking it down in < 60 seconds:

🎥 Watch here →

If you’ve seen any of these happen in your projects, hit reply — I’d love to hear your take.

— Dnyaneshwar

AWS re:Invent 2024 continues to unveil transformative updates that are set to redefine cloud computing. Here’s a concise overview of the key announcements from Day 2:

1. VPC Lattice Enhancements

AWS has expanded VPC Lattice to support TCP traffic across VPC resources. This enhancement simplifies the management of network traffic, providing a unified approach to handle both HTTP and TCP protocols within your Virtual Private Cloud.

2. Amazon EC2 P

5en Instances Now Generally Available

The new Amazon EC2 P5en instances are optimized for generative AI and high-performance computing workloads. They offer enhanced networking capabilities, delivering higher bandwidth and lower latency, which is crucial for training large AI models and executing complex simulations.

3. Amazon Aurora Introduces Distributed SQL (dSQL) – Preview

Amazon Aurora has announced a preview of its Distributed SQL feature. This allows for horizontal scaling of transactional workloads across multiple nodes, providing improved performance and availability for applications with demanding database requirements.

4. Amazon S3 Tables with Apache Iceberg for Analytics Workloads

AWS has introduced Amazon S3 Tables integrated with Apache Iceberg, enabling efficient management of large-scale analytics datasets. This integration facilitates faster query performance and simplifies data lake operations.

5. Amazon EC2 Trn2 Instances Now Available

The Amazon EC2 Trn2 instances are now generally available, powered by AWS Trainium2 chips. They are designed to accelerate deep learning and generative AI training and inference, offering significant performance improvements for machine learning workloads.

6. Amazon DynamoDB Global Tables Previews Multi-Region Strong Consistency

Amazon DynamoDB has introduced a preview of multi-Region strong consistency for global tables. This feature ensures that applications can read the latest data across multiple Regions, enhancing data accuracy and reliability for globally distributed applications.

7. Amazon S3 Metadata – Preview

The new Amazon S3 Metadata feature provides an automated and easily queryable metadata management system. It enables instant discovery and understanding of S3 data, streamlining data curation and utilization for analytics and real-time applications.

These announcements highlight AWS’s commitment to delivering innovative solutions that enhance performance, scalability, and manageability for cloud professionals.

Stay Informed

To keep up with the latest developments from AWS re:Invent 2024, subscribe to our Substack for daily summaries and in-depth analyses.

Subscribe now

Don’t miss out on these critical updates. Subscribe now to stay ahead in the ever-evolving cloud landscape.

For more detailed information, refer to the official AWS announcements:

• VPC Lattice Enhancements

• Amazon EC2 P5en Instances Now Generally Available

• Amazon Aurora Distributed SQL (dSQL) – Preview

• Amazon S3 Tables with Apache Iceberg

• Amazon EC2 Trn2 Instances Now Available

• Amazon DynamoDB Global Tables Multi-Region Strong Consistency

• Amazon S3 Metadata – Preview

Share

Leave a comment

AWS re:Invent 2024 kicked off with a bang, introducing innovations that cloud professionals can’t ignore. Here’s a quick summary of the top announcements to keep you ahead of the curve:

1. AWS Verified Access Enhancements

AWS Verified Access now supports secure access to resources over non-HTTP(S) protocols. This extension broadens its applicability, enabling robust security standards across diverse applications.

2. AWS DMS Schema Conversion with Generative AI

AWS Database Migration Service integrates Generative AI to automate schema conversion. This enhancement simplifies database migrations, accelerates processes, and reduces manual effort.

3. Amazon Bedrock: Knowledge Bases and Connectors

Amazon Bedrock introduces knowledge bases and connectors, enabling seamless data ingestion for AI-driven applications.

4. Amazon S3 Storage Classes in Dedicated Local Zones

Amazon S3 Storage Classes are now available in Dedicated Local Zones. This enhancement offers low-latency access for applications requiring localized data retrieval.

5. PartyRock App Discovery

PartyRock App Discovery delivers daily app recommendations, simplifying the discovery process and enhancing user engagement.

6. AWS Transfer Family for Web Apps

AWS Transfer Family now supports web applications, streamlining secure file transfers across diverse platforms.

7. AWS Invoice Configuration

Enhanced AWS Invoice Configuration provides greater flexibility and clarity in billing, helping businesses manage finances efficiently.

8. Third-Party Block Storage Arrays on AWS Outposts

AWS Outposts now supports third-party block storage arrays, enabling seamless integration of existing storage solutions with AWS infrastructure.

9. Amazon Bedrock ReRank API

The new ReRank API in Amazon Bedrock boosts accuracy in retrieval-augmented generation (RAG) applications, improving AI-generated responses.

10. Amazon EKS Hybrid Nodes

Amazon Elastic Kubernetes Service (EKS) now supports hybrid nodes, offering unified management for on-premises and cloud-based workloads.

11. AWS Control Tower Managed Controls

AWS Control Tower introduces managed controls with declarative policies, simplifying governance across multi-account environments.

12. Amazon CloudWatch Database Insights

Amazon CloudWatch now includes Database Insights, offering advanced performance metrics for database optimization.

13. Amazon EKS Auto Mode

Amazon EKS Auto Mode automates cluster management, reducing operational overhead for developers.

14. Amazon EC2 Allowed AMIs

Amazon EC2 now features Allowed AMIs for enhanced governance, ensuring only approved images are deployed.

15. Amazon S3 Default Data Integrity Protections

Amazon S3 introduces default data integrity protections, adding assurance for data accuracy and reliability.

16. Storage Browser for Amazon S3

Amazon S3 Storage Browser simplifies data management with an intuitive user interface.

17. Amazon MemoryDB Multi-Region Availability

Amazon MemoryDB expands multi-region availability for low-latency in-memory data solutions.

18. Amazon EC2 I7ie Instances

Amazon EC2 unveils I7ie instances, delivering high-performance storage for demanding workloads.

19. Amazon CloudWatch OpenSearch Integration

Amazon CloudWatch integrates with OpenSearch Service, enabling advanced analytics and monitoring.

20. Amazon OpenSearch Service Zero-ETL Integration

Amazon OpenSearch Service introduces zero-ETL integration with Amazon Security Lake, simplifying data ingestion.

21. AWS Declarative Policies

AWS Declarative Policies simplify policy enforcement across AWS Organizations with a declarative approach.

22. Amazon EC2 I8g Instances

Amazon EC2 I8g Instances powered by Graviton4 deliver improved performance for storage-heavy applications.

Stay Tuned for More Updates!

These announcements showcase AWS’s commitment to innovation, providing tools to optimize performance, enhance security, and simplify management for cloud professionals.

Don’t miss out on the upcoming news from re:Invent 2024. Subscribe to our updates for daily summaries and insights.

Share

Leave a comment

At AWS re:Invent 2024, Amazon Web Services introduced Amazon EKS Auto Mode, a feature designed to simplify Kubernetes cluster management by automating infrastructure provisioning, scaling, and maintenance. This advancement offers significant benefits to Amazon EKS users, enhancing operational efficiency and reducing the complexities associated with managing Kubernetes clusters.

Key Features of Amazon EKS Auto Mode:

• Automated Infrastructure Provisioning: EKS Auto Mode streamlines the setup of Kubernetes clusters by automatically selecting optimal compute instances and configuring the necessary networking components. This automation accelerates deployment times and minimizes manual intervention.

• Dynamic Scaling: The feature enables clusters to scale dynamically in response to workload demands, ensuring that applications maintain performance during traffic spikes and conserve resources during low-demand periods.

• Integrated Add-Ons Management: EKS Auto Mode manages essential Kubernetes add-ons, such as the AWS Load Balancer Controller, facilitating seamless integration and reducing the operational burden on users.

Benefits for Amazon EKS Users:

1. Simplified Cluster Management: By automating routine tasks, EKS Auto Mode allows users to focus more on application development and less on infrastructure maintenance, leading to increased productivity.

2. Cost Efficiency: Dynamic scaling ensures that resources are allocated based on actual demand, optimizing costs by preventing over-provisioning and underutilization of resources.

3. Enhanced Reliability: Automated management of add-ons and infrastructure components reduces the risk of misconfigurations, leading to more stable and reliable application deployments.

Considerations for Existing Users:

• Transitioning from Existing Autoscalers: Users currently employing tools like Cluster Autoscaler or Karpenter should evaluate how EKS Auto Mode’s automation aligns with their existing configurations. While EKS Auto Mode offers comprehensive automation, certain complex or highly customized scaling scenarios might still benefit from the granular control provided by these tools.

• Integration with Application-Level Scaling: EKS Auto Mode focuses on infrastructure-level scaling. Users utilizing the Horizontal Pod Autoscaler (HPA) for application-level scaling should assess how these mechanisms can work in tandem to achieve optimal performance and resource utilization.

In summary, the introduction of Amazon EKS Auto Mode at AWS re:Invent 2024 marks a significant advancement in Kubernetes cluster management. By automating critical aspects of infrastructure provisioning and scaling, it empowers EKS users to deploy and manage applications more efficiently and cost-effectively. Existing users should carefully consider how this new feature integrates with their current tools and workflows to fully leverage its capabilities.

Hey everyone, I’m Dnyaneshwar Sonawane. For those of you meeting me for the first time, I’m currently the Vice President of Cloud at HotelKey, and I’ve been in the cloud and DevOps space for over 14 years. But before I got here, my journey was a bit of a rollercoaster, and I wanted to share it with you—not just the wins but the risks, challenges, and lessons I’ve learned along the way.

When I started my career back in 2011 as a System Admin, I had no idea that one day I’d be leading cloud architecture for a company. To be honest, my life looked very different then.

🌱 The Early Days

I was born in a small village in Jalgaon, and life wasn’t exactly easy. I lost my father when I was just 4 months old. By the time I was 16, I’d lost my mother as well. It was a tough time. To support my mother and help with my educational expenses, I worked at a chemist shop during school. It wasn’t a glamorous job, but it taught me the importance of grit and responsibility early on.

Even after losing my mother, I knew I had to keep pushing forward. I worked while studying and eventually completed both my Bachelor’s and Master’s degrees while holding down a full-time job as a System Admin at SmartData. That was where my career began.

🚀 Turning Points

My career has been shaped by a few key turning points:

• In 2008, I met my wife in college. That experience really made me rethink how I approached my life and career. Falling in love gave me the push I needed to focus on securing a better future. I realized that if I wanted to build something great for myself and my family, I needed to take my career seriously and aim higher.

• In 2011, I got my first real job as a System Admin. That was the first step toward building my career in tech, and it was a proud moment for me. It felt like all my hard work was finally paying off.

• In 2013, I joined GlobalLogic. This is where I first learned DevOps, and it was a game changer. I moved from being a Linux Admin to a Senior Engineer, and eventually, I became a DevOps Lead. This transition is where I truly fell in love with cloud technologies and DevOps practices.

• But the biggest turning point came in 2016. I decided to leave GlobalLogic, which was a big MNC, to join HotelKey—a startup that was in its early days. Now, I’ll be honest with you: it was a risky move. I had just welcomed a newborn into my family, and leaving the security of an MNC for a startup felt like jumping into the unknown. But I saw an opportunity to dive deeper into AWS and DevOps, and I took it. That decision changed my career completely. In just a few years, I went from DevOps Lead to Vice President of Cloud, gaining a wealth of expertise in AWS and DevOps.

💡 Lessons Along the Way

Here are a few lessons I’ve picked up along the way that I think could help you too:

• Invest in your learning: Early on, I made a decision that I would never be cheap when it came to learning. I’ve spent a lot on my education, and it’s been one of the best decisions I’ve made. Whether it’s earning certifications like AWS and Terraform, or just picking up a new skill, always keep learning.

• Take calculated risks: Joining HotelKey was a huge risk, but it opened doors I couldn’t have imagined. If there’s an opportunity that feels right, even if it scares you a bit, it’s worth considering.

• Resilience pays off: The challenges I faced early in life—losing my parents, working to support myself—taught me resilience. This resilience has been a key factor in my career success.

• Surround yourself with the right people: My family, friends, mentors, and managers have played a huge role in my journey. I couldn’t have done it without them. Build a support system of people who believe in you.

🌟 Where I Am Now

Today, I’m in a position where I can give back and help others build their own Cloud and DevOps careers. I’m passionate about helping beginners and freshers, just like I was at the start of my journey. I know how overwhelming it can feel when you’re just starting out, and my goal is to make that process a little easier for you.

Whatever your current situation is, I want you to know that it’s possible to grow and build a successful career in Cloud and DevOps. You just need the right mindset, guidance, and a commitment to keep pushing forward—no matter the challenges.

🎯 What’s Next?

In the coming posts, I’ll be sharing the key foundational skills you need to succeed in Cloud and DevOps, plus actionable steps to get you closer to your career goals.

But for now, I want to hear from you. What’s been your biggest challenge so far in your Cloud and DevOps journey? Drop a comment and let’s talk about it!