5% of AWS bill wasted on unattached EBS volumes and snapshots

AWS networking costs are where budgets quietly get crushed. The good news? You can eliminate egress, NAT, and transit fees—and replace them with something far more predictable. This might be the holy grail of cost containment with 40-60% savings on your spend. Excited, curious? Let's talk, find out if this is for you. #CloudComputing #AWS #FinOps #CloudCost #CostOptimization #PrivateEquity #EBITDA #CloudNetworking #DigitalTransformation #TechStrategy Zia RehmanMinami CreamerPhil Ben-JosephJoseph Davey Chris Burney Bill Koschak

Reduced my client's AWS S3 bill from $100/month to just $13/month. The fix? Hetzner's Storage Box. Here's the comparison that made the decision easy: → AWS S3: ~$100/month → Hetzner Storage Box: $13/month → Savings: $87/month ($1,044/year) Migration was simpler than expected: → Exported everything from S3 using rclone → Mounted the Storage Box via SMB → Done. (I also did cost optimization for other aws services, reducing cost by over 10x, which I'll share later with the details) #AWS #Hetzner #FinOps #CloudComputing #CostOptimization #CloudStorage

Your AWS bill is too high.😳 And the reason is probably one of these 5 things. Cloud is supposed to save money. But without proper management, it quietly drains your budget every single month. Here’s what’s likely eating your money right now: 1 — Idle EC2 instances running 24/7 Instances that nobody is using but nobody turned off. → Use AWS Cost Explorer to find them → Set up auto-stop schedules for non-production environments 2 — Unattached EBS volumes When you delete an EC2 instance, the storage doesn’t always delete with it. → Go to EC2 → Volumes → filter by “available” → Delete anything not attached to a running instance 3 — Old snapshots nobody remembers Snapshots accumulate silently and cost real money over time. → Audit your snapshots monthly → Delete anything older than your retention policy 4 — Data transfer costs nobody planned for Moving data between regions or out to the internet costs more than most people expect. → Keep resources in the same region where possible → Use CloudFront to reduce outbound data transfer costs 5 — Wrong pricing model Paying On-Demand prices for workloads that run 24/7. → Switch predictable workloads to Reserved Instances or Savings Plans → Use Spot Instances for flexible, non-critical workloads FinOps isn’t just for big companies. Even a $200/month AWS bill has waste hiding in it. Check these five things today and let me know what you find. ♻️ Repost…someone on your timeline is overpaying right now. #FinOps #AWS #CloudCost #CloudEngineering #AWSCloud #CloudSecurity #Terraform

𝐇𝐨𝐰 𝐭𝐨 𝐜𝐮𝐭 𝐀𝐖𝐒 𝐜𝐨𝐬𝐭𝐬 𝐰𝐢𝐭𝐡𝐨𝐮𝐭 𝐬𝐚𝐜𝐫𝐢𝐟𝐢𝐜𝐢𝐧𝐠 𝐩𝐞𝐫𝐟𝐨𝐫𝐦𝐚𝐧𝐜𝐞 (12 𝐞𝐱𝐩𝐞𝐫𝐭-𝐛𝐚𝐜𝐤𝐞𝐝 𝐬𝐭𝐫𝐚𝐭𝐞𝐠𝐢𝐞𝐬) Looking to reduce AWS costs while maintaining high performance? Here’s how: - Right-Sizing Instances: Adjust instance sizes regularly. Use AWS Compute Optimizer to find the perfect fit for your resources. - Shut down when not in use: Use automations to shutdown dev/test environments on weekends - Use Reserved Instances & Savings Plans: Plan for long-term savings. - Leverage Spot Instances: Opt for cheaper Spot Instances. - Optimize Storage Costs: Choose the right S3 storage class. - Monitor Costs Proactively: Use AWS Cost Explorer and Budgets. - Utilize Auto Scaling: Adjust resources based on demand. - Optimize Data Transfer Costs: Use CloudFront and VPC endpoints. - Review Database Costs: Consider Aurora Serverless and RDS Reserved Instances. - Implement Tagging Strategy: Use tags to manage resources. - Review & Audit AWS Accounts: Regularly audit and consolidate billing. - Modernize your applications:  Implement serverless or containerization to stay ahead. 𝐃𝐌 me "roadmap" if you're serious about your cloud career and ready to fast-track your results. 👉Join our Growth Circle for more free resources - https://nfcgo.to/start Follow Riyaz Sayyad for more AWS Cloud content #aws #cloudcomputing #awscloud #awscommunity #amazonwebservices

🚀 Day 79 of 198: Mastering Amazon RDS! ☁️ Continuing my deep dive into the cloud, today was all about Amazon RDS - Connecting and Managing. Setting up a managed database is one thing, but establishing secure, efficient connections and maintaining it for long-term reliability is where the real work happens. Today's focus included: 🔹 Connection Strategies: Configuring VPC security groups and public accessibility settings to ensure secure access via CLI and GUI tools like MySQL Workbench. 🔹 Management Essentials: Leveraging CloudWatch for performance monitoring and understanding the failover mechanisms of Multi-AZ deployments. 🔹 Scalability: Exploring Read Replicas to offload traffic and optimize database performance. I've attached my detailed learning notes in the PDF below for anyone following along or looking for a quick RDS reference! 📄👇 🔜 What's next? Tomorrow kicks off a major milestone—Day 80. I’ll be starting a 2-Tier Application Deployment project, beginning with the foundational VPC and Security Group architecture. Consistency is key. Onward to Day 80! #DevOps #CloudComputing #AWS #RDS #198DayChallenge #LearningEveryday #DatabaseManagement #InfrastructureAsCode #TechCommunity

Cloud services are often viewed as interchangeable, with similar architectures and billing structures, but this assumption can obscure significant cost differences. I recently modelled the same workload pattern on AWS and OCI, utilising parallel stages, equivalent services, and consistent volume assumptions: approximately 10 TB processed per month and about 10 TB of internet egress to the public internet. The results were striking; monthly totals diverged sharply, with OCI being around 62% lower than AWS in this scenario. The primary factor driving this difference is the pricing and allowances for internet egress. AWS typically charges per GB after a small free allotment, while OCI often includes a substantial outbound allowance in many of its published tiers. For this specific pipeline, the illustrative annual cost gap is approximately $14K, a line item that can easily be overlooked since it doesn’t fall under compute. This issue extends beyond finance; it also involves architecture and data-path considerations. These numbers are illustrative, based on US public list pricing for internet egress, and can vary based on region, discounts, and data paths. A full breakdown is available in the comments, and corrections are welcome. How many pipelines like this are currently running in your stack? #OracleRetail #OCI #DevSecOps #DevBoxRemote

💭 What if backups could happen instantly without manual effort? I built an EBS Backup System using Amazon Web Services where a single trigger runs a AWS Lambda function to create snapshots of Amazon EBS volumes. 🚀 No servers. No complexity. Just serverless automation. 📌 Next step: Making it fully automated with scheduling & monitoring. Medium Blog link here: https://lnkd.in/gjW-hXfG #AWS #Lambda #CloudProjects #DevOpsJourney #Automation

How to give your #SearchBlox deployment access to multimodal foundation models on Amazon Web Services (AWS) — without juggling #API keys or per-call #billing surprises. #LLMS #AWS #Bedrock #EC2 #Cost #RAG https://lnkd.in/e45QK247

🛡️ Protecting Your AWS Resources with AWS Recycle Bin 🛡️ Accidentally deleted an EBS volume, snapshot, or AMI? We've all been there! 😅 AWS Recycle Bin is a game-changing data recovery feature that acts as your safety net in the cloud. Here's why it's essential for every AWS environment: ✅ Automatic Protection: Set up retention rules to automatically catch deleted EBS volumes, snapshots, and EBS-backed AMIs before they're permanently lost ✅ Flexible Retention: Configure retention periods from 1-7 days for volumes and up to 365 days for snapshots and AMIs ✅ Tag-Based or Region-Wide: Protect specific resources with tags or apply blanket protection across entire regions ✅ Simple Recovery: Restore resources with a single API call or console click - they return with the same ID and configuration ✅ Cost-Effective: No additional charges for the service itself - you only pay for the storage of retained resources ✅ Business Continuity: Minimize downtime and ensure your critical workloads stay protected against human error The best part? It integrates seamlessly with your existing AWS workflows and supports automation through APIs and CLI. Source: https://lnkd.in/gsQChbMH #AWS #EBS #CloudBestPractices #AWSRecycleBin #CloudOps #DevOps