Custom IAM Policy for EC2 Access via AWS CLI

Over the past few days, I designed and deployed a personal cloud environment on AWS using Terraform, allowing me to connect the dots between infrastructure as code, automation, and cloud architecture. What I implemented: - VPC with a /26 CIDR block for scalability - Public subnet with Internet Gateway - EC2 instance with IAM role-based access (no static credentials) - Security Group with restricted SSH access - Terraform installed on EC2 for infrastructure management To validate the setup, I successfully provisioned an S3 bucket directly from the instance using Terraform. This project is designed to evolve — next steps include adding private subnets, RDS, and serverless components like Lambda, SNS, and SQS. 💻 Check out the code here: https://lnkd.in/e_6EnV3T #AWS #Terraform #CloudComputing #DevOps #InfrastructureAsCode #CloudEngineering

🌐 Understanding AWS Route 53 Hosted Zones (Simplified) Ever wondered how your domain connects to your application? 👉 That’s where Hosted Zones in AWS Route 53 come in. A Hosted Zone is like a container for DNS records of your domain. It tells the internet where your application lives. 🔹 Public Hosted Zone – Routes traffic from the internet (used for websites, APIs, etc.) 🔹 Private Hosted Zone – Used inside a VPC (for internal services communication) 💡 Key benefits: ✔ Highly available and scalable ✔ Easy domain routing with DNS records (A, CNAME, MX, etc.) ✔ Supports routing policies (Latency, Weighted, Failover) 🚀 In simple terms: Hosted Zone = DNS control panel for your domain in AWS If you're working in DevOps or Cloud, mastering Route 53 is a must! #AWS #Route53 #DevOps #CloudComputing #DNS #Learning

One question every Cloud Engineer must answer: "What happens when a server fails?" I built the answer into my lab this week. I configured an AWS Application Load Balancer (ALB) in front of multiple EC2 instances — and here's what it gives me: ✅ Intelligent Traffic Distribution — requests spread evenly, no single point of overload ✅ Automated Health Checks — unhealthy instances are instantly removed from rotation ✅ Single DNS Entry Point — clean, scalable, no IP management headaches The result? A setup where one server going down means absolutely nothing to the end user. This is the foundation of High Availability architecture on AWS — and exactly the kind of thinking that separates a basic cloud setup from a production-grade one. Building further. 🛠️ #DevOps #CloudArchitect #AWS #CloudComputing #Networking #LoadBalancer

AWS as my first cloud platform—diving into EC2, S3, and VPC basics today. Excited to build scalable infrastructure, automate deployments, and master tools like Terraform and Kubernetes across clouds. From server setups to CI/CD pipelines, this is the tech adventure I've been waiting for! Who's on a similar path? Share your tips below. #DevOps #AWS #MultiCloud #CloudComputing #Day1

Built a Production-Grade Cloud Backup System on AWS I recently designed and implemented an automated cloud backup and alerting system using AWS services. Key Highlights: • Automated daily backups using Cron on EC2 • Secure storage in Amazon S3 with versioning & encryption • Event-driven architecture using S3 triggers and AWS Lambda • Real-time email notifications via SNS • Cost optimization using lifecycle policies #AWS #DevOps #CloudComputing #Automation #LearningByDoing

#updates Terraform on AWS just got simpler. With newer S3 backend configurations, you may no longer need a separate DynamoDB table for state locking. Just enable: "use_lockfile = true" Why it matters: • simpler setup • fewer AWS resources • less IAM complexity This is a useful improvement for DevOps teams managing Terraform at scale. Less infrastructure to maintain = cleaner workflows. Always verify compatibility before making changes in production. #Terraform #AWS #DevOps #Cloud

AWS feels overwhelming at first. 200+ services… where do you even start? Here’s what I learned: You don’t need all of them. You need the core 15 that actually run real systems. The mental model that helped me: 🔹 Compute → EC2, Lambda, ECS 🔹 Storage → S3, EBS 🔹 Networking → VPC 🔹 CI/CD → CodePipeline, CodeBuild 🔹 Security → IAM, KMS, CloudTrail 🔹 Observability → CloudWatch Big shift for me: Stopped memorizing services Started understanding how they work together as a system I wrote a simple guide breaking this down with real use-cases. If you're learning DevOps, this will make things clearer. What AWS service confused you the most at the start? 🤔 #DevOps #AWS #CloudComputing #BackendDevelopment #SoftwareEngineering #LearningInPublic #BuildInPublic #Cloud #TechJourney

🚀 **New Video is Live! | AWS VPC Peering Explained** I’ve just published a new YouTube video where I break down **VPC Peering in AWS** in a simple, beginner-friendly way. 🔗 Watch here: https://lnkd.in/d5t2VsrK In this video, you’ll learn: ✔️ What VPC Peering is ✔️ How to connect multiple VPCs securely ✔️ Key benefits and limitations ✔️ Real-world use cases If you're exploring cloud computing or preparing for AWS certifications, this will help you build a strong foundation in AWS networking. Let me know your thoughts in the comments and feel free to share it with others who might find it helpful! #AWS #CloudComputing #VPCEndpoints #Networking #DevOps #AWSTutorial #LearnAWS #CloudNetworking #TechContent

✅ Difference between AWS Autoscaling Vs Elastic load Balancer 🟧 AWS Autoscaling-> 1: It scales your infrastructure whenever needed 2: Automatically increases and decreases the size of auto scaling group (mainly ec2-instances) 3: Adds new instances when load reaches a certain level and spin down instances when no longer needed. 🟩 Elastic load Balancer-> 1: It automatically routes incoming application traffic across dynamically changing number of multiple ec2 instances. 2: It acts as single point of contact for all incoming traffic to the instances in your auto scaling group. 3: It is used to monitor the health of registered instances so that the load balancer sends requested traffic to healthy instance. 🗝️ AWS ELB distributes the traffic to the instances and auto scaling group spin in and spin out instances according to traffic. These both services can work together and then create complete ecosystem of AWS.