Kavya Ganesan’s Post

Most people think you need servers to run code… but what if your code runs without managing any server at all? 🤯 That’s exactly what AWS Lambda does. It’s a serverless compute service where you just upload your code, and AWS handles everything else — scaling, infrastructure, and execution. Example: -Imagine you upload a photo to a website. -Instead of running a server 24/7 to process that image: -AWS Lambda automatically triggers -Resizes the image -Stores it in another folder And the best part? You only pay for the time your code runs ⏱️ ⚡ Why it’s powerful: • No server management • Auto scaling (even for millions of requests) • Cost-efficient (pay per execution) • Easy integration with other AWS services 📌 In short: Focus on writing code, not managing servers. #AWS #Lambda #Serverless #CloudComputing #DevOps #LearningInPublic

I’ve been learning AWS core services and wanted to put together a simple breakdown with real-time examples. In this video, I covered the key areas that are actually used in most projects: Compute (EC2, Lambda), Storage (S3, EBS), Database (RDS, DynamoDB), Networking (VPC, CloudFront), and Security (IAM). Instead of just theory, I tried to explain how these are used in real-world scenarios like websites, applications, and company infrastructure. This helped me understand how everything connects in cloud environments, especially from a job perspective in Cloud and DevOps roles. If you’re starting with AWS or trying to get job-ready, this might be useful. Here’s the video: https://lnkd.in/gpBuBvEk Open to feedback and suggestions. #AWS #CloudComputing #DevOps #AWSCertification #CloudCareers #Learning

Excited to share my latest project: Migrating Legacy AWS Infrastructure to Infrastructure as Code using AWS CDK (TypeScript). I took a manually built “ClickOps” environment and redesigned it into a secure, reproducible AWS architecture with a VPC, public/private subnet segmentation, EC2, RDS, Security Groups, and AWS Secrets Manager, all deployed through code. Beyond implementation, I focused on the why behind the architecture decisions, applying system design principles around security, scalability, reliability, and cost optimization. 📖 Medium article —link in the first comment #AWS #AWSCDK #InfrastructureAsCode #DevOps #CloudArchitecture #SystemDesign

Say goodbye to DynamoDB... 👋 Terraform just became even simpler! 🚀 Amazon S3 now supports native state locking. No more needing to pair Amazon DynamoDB alongside S3. 💡 How to implement it? Simple. Just add one line to your backend: use_lockfile = true ✅ Why is state locking essential? 🧐 Without it, multiple people or pipelines can run Terraform simultaneously, which can lead to: • Overwriting each other’s changes 💥 • Corrupting the state file 🛠️ • Failed or inconsistent deployments ❌ Why is this a game changer? • No more unnecessary DynamoDB table 📉 • Simpler bootstrap setup ✨ • Lower costs 💰 • Cleaner CI/CD pipelines 🧼 #Terraform #AWS #DevOps #CloudComputing #InfrastructureAsCode

☁️ AWS Cheat Sheet 2026: The Services You Actually Need to Know ☁️ With 200+ services, AWS can feel like a labyrinth. But for 90% of use cases, you only need to master the "Core 20." Here is a breakdown of the essentials for every Cloud & DevOps Engineer. 👇 🏗️ 1. Compute (The Brains) EC2: Virtual servers. You manage the OS. Lambda: Serverless functions. Run code without provisioning servers. Fargate: Serverless containers. Run Docker without managing EC2 instances. 📦 2. Storage (The Memory) S3: Object storage. Infinite scaling for images, logs, and static sites. EBS: Block storage. Hard drives for your EC2 instances. EFS: Shared file system. One "drive" connected to multiple servers. 🌐 3. Networking (The Roads) VPC: Your private, isolated section of the AWS cloud. Route 53: Scalable DNS and domain registration. CloudFront: Content Delivery Network (CDN) to speed up your app globally. ALB/NLB: Load balancers to distribute traffic across your targets. 🗄️ 4. Databases (The Filing Cabinet) RDS: Managed Relational DBs (MySQL, Postgres, SQL Server). DynamoDB: Ultra-fast, serverless NoSQL database. ElastiCache: In-memory caching (Redis/Memcached) for speed. 🛡️ 5. Security (The Guard) IAM: Identity & Access Management. Who can do what? (Always follow Least Privilege). Secrets Manager: Securely store and rotate API keys and passwords. KMS: Key Management Service. Encrypt your data at rest. 🚀 6. DevOps & Automation (The Factory) CodePipeline: Orchestrates your CI/CD workflow. CloudFormation / CDK: Infrastructure as Code (IaC). Define your cloud in JSON, YAML, or TypeScript/Python. EKS: Managed Kubernetes (The industry standard for container orchestration). CloudWatch: Monitoring, logs, and alarms to see if things are breaking. 💡 Pro-Tip: If you are just starting, focus on IAM, VPC, EC2, and S3. They are the four pillars that almost every other service is built upon. What AWS service was the hardest for you to wrap your head around? For me, it was definitely VPC networking! Let's discuss in the comments. 💬 #AWS #CloudComputing #DevOps #SolutionsArchitect #TechCareer #AmazonWebServices #CloudNative #LearningPath

How many DynamoDB lock tables are sitting in your AWS account right now? OpenTofu silently kept stacking features I dreamed of in the old days, part 3 of v1.10.0. 👇 Every IaC project on AWS was a chore: 1. Create the S3 bucket for state 2. Create a DynamoDB table… for a single boolean lock 3. Write an IAM policy that grants access to both I still can't believe we needed an entire second AWS service just to hold one lock row. One line. That's the whole migration. Stay tuned for more OpenTofu content. 📦🔥 #OpenTofu #Terraform #InfrastructureAsCode #IaC #AWS #DevOps #PlatformEngineering #S3 #CloudNative #SRE

A lot of engineers still don’t know this about Amazon Web Services Amazon S3. Bucket naming is evolving. Previously, S3 bucket names had to be globally unique across all AWS accounts and regions. That meant names often looked like this: my-app-prod-us-east-1-938274 Now, new bucket naming behavior is moving toward account and region scoped uniqueness for newer bucket types and features. This is important for anyone working with: → Infrastructure as Code → Terraform → automation scripts → deployment pipelines A few key things to remember: ↳ Existing buckets remain unchanged ↳ Review your naming conventions ↳ Update reusable IaC modules ↳ Avoid assumptions in automation logic Small cloud changes like this can have a big impact on deployment workflows. Always review service updates before rolling changes into production. Have you updated your bucket naming standards yet? #AWS #CloudComputing #DevOps #Terraform #S3 #CloudEngineer

𝗔𝗪𝗦 𝗟𝗮𝗺𝗯𝗱𝗮 𝘁𝘂𝗿𝗻𝗲𝗱 𝘀𝗲𝗿𝘃𝗲𝗿𝘀 𝗶𝗻𝘁𝗼 𝗳𝘂𝗻𝗰𝘁𝗶𝗼𝗻𝘀 At Amazon Web Services (AWS), infrastructure doesn’t always mean servers. Sometimes, it’s just code that runs when needed. That changes how applications are built. Without serverless: • teams manage idle infrastructure • scaling requires planning • costs grow with unused resources With AWS Lambda, teams run 𝗲𝘃𝗲𝗻𝘁-𝗱𝗿𝗶𝘃𝗲𝗻 𝗰𝗼𝗱𝗲 𝘁𝗵𝗮𝘁 𝘀𝗰𝗮𝗹𝗲𝘀 𝗮𝘂𝘁𝗼𝗺𝗮𝘁𝗶𝗰𝗮𝗹𝗹𝘆. The DevOps lesson: 𝗗𝗼𝗻’𝘁 𝗺𝗮𝗻𝗮𝗴𝗲 𝘀𝗲𝗿𝘃𝗲𝗿𝘀. 𝗠𝗮𝗻𝗮𝗴𝗲 𝗲𝘃𝗲𝗻𝘁𝘀. When compute becomes on-demand, you only pay for what you use. At ServerScribe, we help teams design architectures that scale automatically — without operational overhead. Are you still managing servers — or building serverless systems? 👇 #DevOps #ServerScribe #AWSLambda #Serverless #CloudComputing #SRE #Scalability

My 30-Day AWS Terraform Challenge. Day 3/30. Inspired by Piyush sachdeva Today I worked on creating an S3 bucket using Terraform and focused on understanding how authentication and resource provisioning come together in AWS. Instead of just writing code, I spent time understanding how Terraform communicates with AWS and how credentials play a foundational role in every deployment. Key Learnings: • Terraform uses AWS credentials to interact with AWS APIs • Authentication can be configured using AWS CLI, environment variables, or profiles • Amazon S3 is an object storage service used for storing files like backups, logs, and application data • S3 bucket names must be globally unique and follow strict naming conventions • Terraform workflow is simple and powerful: init → plan → apply → destroy • Tagging resources helps with organization and cost tracking What I built: • A simple S3 bucket using Terraform • Configured AWS provider with region • Applied infrastructure changes and verified in AWS This day reinforced a key idea: Cloud infrastructure is not just about creating resources, it’s about understanding how systems securely connect and operate together. Building step by step. Full blog here: https://lnkd.in/gYgNXrzr GitHub repo: https://lnkd.in/gmsCBxZi #30DaysOfAwsTerraform #Terraform #DevOps #AWS #CloudEngineering

🚀 Just built and deployed my first fully serverless notification system on AWS! This project uses: ✅ AWS Lambda ✅ API Gateway ✅ DynamoDB ✅ SNS ✅ AWS SAM (Infrastructure as Code) 🔧 What it does: A user sends a POST request → API Gateway → Lambda processes it → stores data in DynamoDB → publishes notification via SNS. 💡 What I learned: - How to design event-driven architectures - How to deploy serverless apps using AWS SAM - How to connect multiple AWS services into a real system 📸 I’ve added screenshots + architecture diagram in the repo. 🔗 GitHub Repo: https://lnkd.in/dDCZw-gb This is part of my journey into Cloud Engineering ☁️ More projects coming soon 🚀 #AWS #CloudComputing #Serverless #DevOps #100DaysOfCode