Why AWS Should Be Your First Cloud Provider to Learn as a DevOps Engineer
MOJAHID UL HAQUE
DevOps Engineer
Why AWS Should Be Your First Cloud Provider to Learn as a DevOps Engineer, SRE, or Platform Engineer.
Are you starting your journey into the world of cloud computing and wondering which cloud provider to dive into first? If you're a DevOps Engineer, SRE, or Platform Engineer, here's why AWS should be your starting point.
Originally posted on LinkedIn
View original postRelated Posts
Stop Leaving AWS Credits Unclaimed - That Outage Might've Owed You Money
Remember the AWS outage on October 20th? Six hours down. Over 100+ services affected. Millions of users impacted. Everyone's talked about the RCA, multi-region setups, and resilience planning. But here's what most teams completely miss: 👉 You might be owed money. The SLA Reality Check AWS makes uptime promises like: - Cognito — 99.9% - DynamoDB — 99.99% (and 99.999% for Global Tables) - EC2, Lambda, CloudFront… all have their own SLAs. Now, do the math: 6 hours of downtime in a 30-day month = 99.17% uptime. That's below every single SLA above. What That Means for You If your services were affected, you're entitled to service credits — typically 10–25% of your monthly bill. So if you spend $10K/month on Cognito or DynamoDB… that's real money sitting unclaimed. How to Claim It (Takes 10 Minutes) 1. Go to your AWS Support Center 2. Open a new case 3. List the affected services 4. Reference the SLA breach 5. Submit before the end of the second billing cycle AWS won't credit you automatically. You have to ask. The Takeaway Yes — improve your DR and multi-region strategy. But also — don't forget to claim what you're owed. It's quick, it's legit, and your FinOps team will thank you.
AWS Summit India Online 2025 - Key Points from Sessions
Excited to share that I attended the AWS Summit India Online 2025 on June 26! Key Points from the Sessions - Focus on Generative AI: Learned how AWS services like Amazon Bedrock and SageMaker are making it easier for organizations to implement and scale Generative AI solutions in real-world business environments. - AI from POC to Production: Sessions stressed moving beyond experimentation with Gen AI, highlighting frameworks and best practices for deploying production-ready AI and delivering genuine business value. - Cloud Security & Reliability: Gained insights into AWS's secure, scalable cloud infrastructure, which includes Indian regions for low-latency, resilient operations. - Data & Application Modernization: Explored strategies for modernizing applications, leveraging AI and analytics to enable smart, data-driven decisions. - Industry Use Cases: Discovered success stories in automating customer support, generating content, and industry applications across fields like finance, retail, healthcare, and media. - Responsible & Ethical AI: Learned about building trust in AI, governance, and using AWS guardrail tools for responsible adoption. - Networking & Community: Connected with a vibrant tech community and learned from AWS experts and business leaders through live Q&As and interactive workshops.
Redis OSS vs. ElastiCache for Valkey: A Comprehensive Comparison
Redis OSS vs. ElastiCache for Valkey: A Comprehensive Comparison Both Redis OSS and ElastiCache for Valkey have their merits. Your choice should align with your team's operational capabilities, budget constraints, and specific application requirements. Operational Overhead: - Redis OSS: Demands manual management, including server provisioning, configuration, failover handling, and backups. - ElastiCache for Valkey: Provides a fully managed service by AWS, automating tasks like provisioning, patching, scaling, and backups. Performance: - Redis OSS: Performance is contingent on effective configuration and tuning. - ElastiCache for Valkey: Optimized for AWS infrastructure, offering features like enhanced throughput and low-latency performance.