Learning AWS EC2 Basics: Regions, AZs & Auto Scaling

🚨 Too many resources in your EC2 console? Not all of them are actually yours to manage. If you’ve worked with services like EKS, ECS, Lambda, or WorkSpaces, you’ve probably seen EC2 instances, volumes, or ENIs that you didn’t directly create — yet they still showed up in your console. AWS has now fixed this confusion. Amazon EC2 introduces Managed Resource Visibility Settings. With this update, you can control whether AWS-managed resources appear in your EC2 console and API responses. Here’s what changed: 🔹 Resources managed by AWS services are now hidden by default 🔹 Only self-managed EC2 resources are visible by default 🔹 You can customize visibility via console or CLI 🔹 Applies to resources like EBS volumes, snapshots, and network interfaces 🔎 Why this matters In real-world environments, especially with microservices and managed services, your EC2 console can get cluttered with resources you don’t directly control. This update: • Reduces noise in your console • Improves operational clarity • Aligns better with the shared responsibility model • Helps teams focus only on what they actually manage A simple change — but a big win for clarity, control, and better cloud operations. 🚀 #AWS #EC2 #CloudComputing #CloudArchitecture #AWSCloud #DevOps #AWSCommunity #CloudEngineering #AWSBuilders #CloudOperations

AWS Lambda vs EC2 vs ECS When working in Amazon Web Services, choosing between AWS Lambda, Amazon EC2, and Amazon ECS depends on the needs of the business. Each service has a different purpose. 🔹 AWS Lambda – Good for small tasks that run only when needed. It helps save time and cost because there are no servers to manage. 🔹 Amazon EC2 – Good for applications that need full control of the server and steady performance. Often used for larger or older systems. 🔹 Amazon ECS – Good for running applications in containers and making updates easier as systems grow. My Approach: ✔ Review business and system needs ✔ Choose the best service based on cost, speed, and reliability ✔ Improve security and system uptime ✔ Help move older systems to modern cloud services ✔ Automate setup using Terraform and AWS CloudFormation ✔ Support smooth and safe deployments Bottom Line: Success in the cloud comes from choosing the right tool for the right job. Lambda works well for simple tasks, EC2 gives more control, and ECS helps manage growing applications. #AWS #CloudComputing #AWSLambda #EC2 #ECS #DevOps #CloudEngineer #Technology #CloudServices

Day10/100 days of kodekloud Challenge AWS ✔️ Successfully created and attached an Elastic IP to an EC2 instance (nautilus-ec2) in the us-east-1 region. Along the way, reinforced key concepts like resource tagging, allocation vs association, and troubleshooting real-world cloud issues. Small steps, consistent learning. #AWS #CloudComputing #DevOps #EC2 #LearningJourney #HandsOn #CloudSkills

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

Creating a server in the cloud takes just a few clicks… but understanding what happens behind it is where real learning begins. I explored how to launch an EC2 instance in AWS and realized how concepts like AMI, security groups, and key pairs come together to create a working server. Sharing a simple step-by-step breakdown 👇 #AWS #EC2 #CloudComputing #SoftwareEngineering #DevOps #LearnAWS

✅ What Are Terraform Providers? Providers act as a bridge between Terraform and cloud/service APIs to: Create infrastructure Update resources Delete and manage existing assets 🌐 Common Terraform Providers & APIs 🔹 AWS Provider (hashicorp/aws) Uses AWS APIs to manage resources like EC2, S3, IAM, RDS, Lambda. Authentication via Access Keys / IAM Roles. 🔹 Azure Provider (hashicorp/azurerm) Uses Azure REST APIs to manage VMs, Storage, Networks, etc. Authentication via Service Principal or Managed Identity. 🔹 Google Cloud Provider (hashicorp/google) Uses Google Cloud APIs for Compute Engine, Cloud Storage, GKE. Authentication via Service Account key (JSON). 🔹 Kubernetes Provider (hashicorp/kubernetes) Uses the Kubernetes API Server to manage Pods, Deployments, Services. Authentication via kubeconfig. ⚙️ What Happens When You Run terraform init? terraform init prepares your working directory by: ✅ Downloading providers from Terraform Registry ✅ Configuring the backend for state storage ✅ Downloading required modules ✅ Preparing Terraform for plan and apply 📁 .terraform Directory Created after running terraform init. Contains: Provider binaries Downloaded modules Backend‑related files 🔒 terraform.lock.hcl An auto‑generated lock file that: Ensures consistent provider versions Prevents accidental upgrades Improves reliability across teams and pipelines #Terraform #InfrastructureAsCode #CloudComputing #AWS #Azure #Kubernetes #CICD #Automation

I recently started the AWS Cloud Practitioner Essentials course on AWS Skill Builder, and it has been an amazing learning experience. Here are some key concepts I now understand better: • Benefits of AWS • Shared Responsibility Model • EC2 (instance types, families, and multi-tenancy) • AWS pricing models and cost optimization • Scalability and elasticity (including Elastic Load Balancing) • Messaging services: SQS & SNS • Serverless computing with Lambda • Containers and deployment strategies • Container services: ECS, EKS, ECR • AWS Fargate One thing I’m intentional about in this journey is building real understanding — not just following “click this, click that” tutorials. Still learning, still growing, the journey continues. #AWS #CloudComputing #LearningJourney

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

As part of my AWS learning journey, I explored Amazon S3 (Simple Storage Service), one of the most widely used storage services in the cloud. What is S3? Amazon S3 is an object storage service that allows us to store files (like images, videos, and documents) in the cloud. These files are stored as “objects” inside something called a “bucket.” Why is S3 powerful? 1) Highly scalable – store unlimited data 2) Extremely durable – designed for 99.999999999% durability 3) Accessible from anywhere via URL 4) Cost-efficient with multiple storage classes Real-world use cases 1) Storing images and videos for websites 2) Hosting static websites 3) Backup and archiving data 4) Supporting mobile and web applications Key takeaway Instead of storing files on a server (like EC2), we can offload static content to S3, making applications faster, scalable, and more efficient. This hands-on approach is helping me connect concepts better and understand how real-world cloud architectures are built. Looking forward to exploring more AWS services and sharing my journey #AWS #CloudComputing #AmazonS3 #DevOps #LearningJourney #TechBeginner #CloudStorage