r/Cloud • • Jun 16 '26

Accidental AWS bill of ₹11 lakh while learning AWS as a student😭🥀

Post image
314 Upvotes

Student accidentally got hit with an ₹11 lakh AWS bill while learning AWS — looking for advice

I'm honestly freaking out right now and hoping someone here has been through something similar.

I'm a student and have been learning AWS while working on a small academic/personal project. Around March, I was experimenting with a Django backend and database setup. I thought I had cleaned everything up afterward, but recently I discovered that an Aurora/RDS setup had been running the whole time without me realizing it.

The result is a bill of over ₹11 lakh (~$13,000).

There was no business, no customers, no production workload, and no revenue involved at all. This was purely a learning project and a mistake on my part.

As soon as I found out, I:

- Opened a billing support case with AWS

- Explained the situation honestly

- Started deleting all unnecessary resources

- Tracked the majority of the charges to Aurora/RDS

AWS has replied to my support case and is reviewing it, but they haven't made a decision yet regarding any billing adjustment or credit.

I'm trying to stay hopeful, but the amount is way beyond anything I could afford as a student.

Has anyone here dealt with a similar situation, especially with a large accidental bill? Did AWS provide a waiver, partial credit, or some other form of relief?

Also, is there anything else I should be doing right now besides continuing to work with AWS Support?

I'd really appreciate hearing about any experiences or advice. Thanks.


r/Cloud • • Jul 16 '26

Early morning today

Post image
281 Upvotes

r/Cloud • • Aug 07 '25

Planning to Get Into Cloud Computing in 2025? Here’s What Actually Matters

223 Upvotes

Hey everyone, If you're thinking about getting into cloud computing this year, whether you're pivoting from another tech field, just getting started in IT, or looking to specialize, here’s a breakdown of what you should actually focus on. There’s a ton of buzz around cloud, but this post is meant to cut through the noise and help you start smart.

Start With the Basics. Understand the “Why” Before the “How” Don’t just jump into AWS tutorials. First, understand what cloud computing is and why it matters.

What is the cloud (IaaS, PaaS, SaaS explained simply) Difference between on-prem vs cloud What scalability, high availability, and elasticity really mean What a region, availability zone, and data center are How billing works in the cloud (very underrated but super important)

This foundational stuff will help everything else make way more sense later.

Pick One Cloud Provider and Stick With It (At First) You don’t need to know AWS, Azure, and GCP all at once. Pick one, go deep, and switch later if needed.

AWS is the most in-demand and has tons of learning resources Azure is great if you’re aiming for enterprise or Microsoft-heavy environments GCP is solid but has a smaller market share

Whichever one you pick, learn its ecosystem and terminology well. AWS EC2 = Azure VM = GCP Compute Engine. Same idea, different names.

Learn the Core Cloud Services First Focus on the essential services that are used in almost every architecture.

Compute: EC2, Lambda, App Services, GKE Storage: S3, Blob Storage, Google Cloud Storage Databases: RDS, DynamoDB, Cosmos DB, BigQuery Networking: VPC, Subnets, Security Groups, Load Balancers, Route 53 IAM (Identity and Access Management): Permissions, roles, policies

Don’t worry about every service under the sun. Master the core first.

Get Hands-On. Reading Docs Isn’t Enough Start building small cloud projects. The best way to learn is to deploy stuff yourself.

Deploy a static website on S3 or Azure Blob Spin up an EC2/VM and host a simple app Set up a Lambda function that runs on a schedule Create a basic multi-tier architecture (web + app + DB) Build a budget alert or cost dashboard

Use the free tier to experiment without getting billed (but always double-check usage).

Understand Networking and Security Cloud is someone else’s computer, and security is your job. Learn:

CIDR blocks, subnets, routing Inbound/outbound rules, NACLs, firewalls IAM roles, least privilege, MFA, access keys Shared Responsibility Model

Networking trips up a lot of people early on. Learn it slowly but thoroughly.

Learn Infrastructure as Code (IaC) Manually clicking through the cloud console is fine at first, but real cloud engineers write code for their infrastructure.

Start with Terraform Learn basic modules, variables, and deployment Try to recreate your cloud projects using IaC

This will help when you move into DevOps or want to scale your skills.

Certifications Help, But Back Them With Skills If you're job-hunting or new to tech, certs can help open doors. Start with:

AWS Certified Cloud Practitioner or Azure Fundamentals (AZ-900) if you're brand new AWS Associate Solutions Architect or Azure AZ-104 when you’re ready for more depth Google Associate Cloud Engineer for GCP folks

But remember: passing a cert isn’t the same as knowing the cloud. Use them as a learning structure, not a finish line.

Document and Share Your Work Make a GitHub repo. Push your Terraform code. Write simple blogs or walkthroughs of what you built. Show your understanding. Recruiters and hiring managers love this, and it helps you retain what you learn.

Join the Community and Keep Learning Cloud changes fast. Stay updated and involved.

Subreddits like r/aws, r/devops, r/cloudcomputing Discord servers, Twitter or LinkedIn threads Follow cloud advocates and engineers who share real tips Join cloud challenges like #100DaysOfCloud

You’ll learn a ton from just being around the community and seeing what others are doing.

Final Tip. Don’t Try to Learn It All at Once Cloud is huge. You’re not supposed to master every service or tool. Focus on building real stuff, solving problems, and learning consistently. Even 30 minutes a day adds up fast.

2025 is a great time to get into cloud. Tons of companies are hiring and expanding. Just make sure you’re learning the right way.

If you're learning cloud right now or unsure where to start, drop your questions or plan below. Happy to share resources or project ideas.


r/Cloud • • 27d ago

First-year Data Science student diving into Cloud Computing

Post image
211 Upvotes

Hey everyone!

​I’m a first-year data science student currently surviving on Python, Excel, analytics, and stats (goodbye basic calculus, you won't be missed lol).

​I just grabbed Cloud Computing: A Hands-on Approach by Arshdeep Bahga and Vijay Madisetti to figure out how all this backend magic actually works, but I could use a little direction from the community.

​As a total beginner to the cloud space, I’d love to know:

​Which cloud provider should I start with as a DS student? (AWS, Azure, or GCP?)

​What practical projects actually help bridge the gap between data science and cloud computing instead of just getting lost in documentation?


r/Cloud • • Dec 05 '25

Cloudfare outage!

Post image
197 Upvotes

r/Cloud • • Aug 10 '25

A cloud.

Post image
174 Upvotes

r/Cloud • • Jul 23 '25

Are these numbers realistic?

Post image
153 Upvotes

Curious to know if a person running their own company doing this is achievable. Are the numbers inflated/amount of work understated? How would one even get into doing this? In the comments the author also noted that his friend used to work at AWS, so how is that not a conflict of interest?


r/Cloud • • Aug 28 '25

Awesome Cloud Projects

127 Upvotes

Hey community, I am releasing a free & open source learning resource for AWS, GCP, and Azure. Over 800 projects, with code, to help you learn by doing with real examples.

I spent years building these projects (I called them cloud recipes) to learn myself, and eventually released a book years ago.

I had tons of extra content… life happened, I never found the time to polish them up to the standards I wanted for future publishing. Advancements in generative AI let me polish up and complete this body of work and I want to donate it to the cloud professionals community here.

Have a look, leave a comment, a suggestion, and I hope it helps or inspires someone to learn something new!

https://github.com/mzazon/awesome-cloud-projects


r/Cloud • • Jul 17 '26

Sun

Thumbnail
gallery
121 Upvotes

r/Cloud • • Jul 02 '25

Cloud certification & there impact!!

Post image
116 Upvotes

r/Cloud • • Oct 25 '25 Bravo

Most people learn AWS wrong. Here’s how to actually understand it.

92 Upvotes

When I started learning AWS, I thought I was making progress…
until someone asked me to design a simple 3-tier app and I froze.

I knew the services EC2, S3, RDS but I had no clue how they worked together.

What finally helped?

  1. Studying real-world architectures

  2. Understanding why each service fits where it does

  3. Rebuilding them myself in the AWS Console

Once I started connecting the dots from VPCs to load balancers to Lambda triggers AWS stopped feeling like 200+ random services and started making sense as one big system.

If you’re feeling lost memorizing definitions, stop.

Start by breaking down one real architecture and ask:
Why is this service here? and What problem is it solving?

Start with these architectures 👇 and go from there

because understanding how AWS fits together is where real learning begins.


r/Cloud • • Feb 09 '26

People actually working in cloud - what’s the part nobody tells students?

86 Upvotes

I'm currently a junior in college trying to get into cloud engineering and I was curious generally what the day to day job role was like. I was thinking working DevOps, and maybe on the operations side?

I met a guy a few months ago, who said his job was very laid back and he worked as a cloud engineer, I also heard that it can have a really good work life balance (I also know it depends on the company and what side yjy work on) so what is the work-life balance like for you guys?


r/Cloud • • Sep 08 '25

The mistake 90% of AWS beginners make...

82 Upvotes

When I first opened the AWS console, I felt completely lost...
Hundreds of services, strange names, endless buttons. I did what most beginners do jumped from one random tutorial to another, hoping something would finally make sense. But when it came time to actually build something, I froze. The truth is, AWS isn’t about memorizing 200+ services. What really helps is following a structured path. And the easiest one out there is the AWS certification path. Even if you don’t plan to sit for the exam, it gives you direction, so you know exactly what to learn next instead of getting stuck in chaos.

Start small. Learn IAM to understand how permissions and access really work. Spin up your first EC2 instance and feel the thrill of connecting to a live server you launched yourself. Play with S3 to host a static website and realize how simple file storage in the cloud can be. Then move on to a database service like RDS or DynamoDB and watch your projects come alive.

Each small project adds up. Hosting a website, creating a user with policies, backing up files, or connecting an app to a database these are the building blocks that make AWS finally click.

And here’s the best part: by following this path, you’ll not only build confidence, but also set yourself up for the future. Certifications become easier, your resume shows real hands-on projects, and AWS stops feeling like a mountain of random services instead, it becomes a skill you actually own.


r/Cloud • • Feb 07 '26

Is anyone else noticing the massive salary bifurcation for "Cloud Engineers" lately?

78 Upvotes

It feels like the "Cloud Engineer" title has completely split into two different jobs with the same name in 2026. On one side, you have the "ClickOps" admins doing manual console work and capping out around $90k; on the other, you have the actual Platform/SRE roles using Terraform, K8s, and Python starting at $160k+. Recruiters seem to be exploiting this ambiguity to lowball the engineering-heavy candidates by comparing them to the support-tier roles.

For a breakdown of how cloud roles (and pay bands) are diverging in 2026, see our guide: Cloud Engineer Salary shows exactly how and why the market has split.

If you're interviewing right now, make sure they aren't paying you IT Support wages for Distributed Systems architecture work; the gap between the two is widening fast.


r/Cloud • • Nov 16 '19

Hi. This is spam.

Post image
78 Upvotes

r/Cloud • • Jun 29 '26

I want to start learning cloud engineering from zero

72 Upvotes

hello guys as the title said i want to start cloud engineering and I have zero knowledge about IT , I can give it all the time that it need and I need you to give me advices about it or a course if you got one and thank you all .


r/Cloud • • May 19 '26

Anyone else quietly moving stuff OUT of Kubernetes?

71 Upvotes

Feels like every company eventually reaches:

“Why are we running this tiny internal service on a 40-layer orchestration platform?”

I’m seeing more teams move smaller workloads back to:

- ECS/Fargate

- plain Docker on VMs

- managed PaaS

- even systemd services

Not because Kubernetes is bad.

Because not everything needs:

- operators

- ingress drama

- Helm templating nightmares

- CRD ecosystems nobody understands

- 14 dashboards to debug one timeout

K8s is incredible at scale.

But I think a lot of orgs adopted it WAY before they actually needed it.

Curious if others are seeing the same thing internally.


r/Cloud • • Jun 26 '25

12-Month Cloud Security Challenge Just Dropped – Practice, Compete, and Get Certified

Thumbnail linkedin.com
68 Upvotes

r/Cloud • • Feb 27 '22

wow

Post image
68 Upvotes

r/Cloud • • Dec 10 '25

Cloud Sec Wrapped for 2025

Thumbnail linkedin.com
64 Upvotes

r/Cloud • • Sep 15 '25

Most people quit AWS at the start here’s what they miss...

60 Upvotes

When I first touched AWS, I thought it was just about spinning up a server.
Then I opened the console.
Hundreds of services, endless acronyms, and no clue where to even start.

That’s the point where most beginners give up. They get overwhelmed, jump between random tutorials, and eventually decide Cloud is too complicated.

But here’s what nobody tells you: AWS isn’t just one skill it’s the foundation for dozens of career paths. And the direction you choose depends on your goals.

If you like building apps, AWS turns you into a cloud developer or solutions architect. You’ll be launching EC2 servers, hosting websites on S3, managing databases with RDS, and deploying scalable apps with Elastic Beanstalk or Lambda.

If you’re drawn to data and AI, AWS has powerful services like Redshift, Glue, SageMaker, and Rekognition. These unlock paths like data engineer, ML engineer, or even AI solutions architect.

If you’re curious about DevOps and automation, AWS is the playground: automate deployments with CloudFormation or Terraform, run CI/CD pipelines with CodePipeline, and master infrastructure with containers (ECS, EKS, Docker). That’s how you step into DevOps or SRE roles.

And if security or networking excites you, AWS has entire career tracks: designing secure VPCs, mastering IAM, working with WAF and Shield, or diving into compliance. Cloud security engineers are some of the highest-paid in tech.

The truth is, AWS isn’t a single job skill. It’s a launchpad. Whether you want app dev, data, DevOps, security, or even AI there’s a door waiting for you.

But here’s the catch: most people never get this far. They stop at “AWS looks too big.” If you stick with it, follow the certification paths, and build projects step by step, AWS doesn’t just stay on your resume it becomes the thing that takes your career global.


r/Cloud • • Jan 17 '21

Please report spammers as you see them.

60 Upvotes

Hello everyone. This is just a FYI. We noticed that this sub gets a lot of spammers posting their articles all the time. Please report them by clicking the report button on their posts to bring it to the Automod/our attention.

Thanks!


r/Cloud • • Aug 20 '20

Thought that this might belong here

Post image
59 Upvotes

r/Cloud • • Oct 28 '25

💸 I cut 40% of our AWS bill in 90 Days. Sharing the boring tech playbook that every tech entrepreneur should know (but thinks they already do)

57 Upvotes

Most entrepreneurs think they have a revenue problem.
They actually have a cloud problem.

I’ve spent 20+ years building and fixing backend systems for startups. Almost every time I walk in, I see the same story:
A team racing to ship.
A few sleepless months of growth.
Then an AWS bill that quietly explodes into five figures.

Everyone says, “We’ll optimize later.”
But guess what? Later never comes. And then the runway’s too short.

Over the past few years, I’ve refined a 90-day playbook that consistently cuts 30–50% of cloud spend without touching performance.
It’s not magic. It’s not “reserved instance” tricks.
It’s just boring, disciplined engineering.

Here’s just six pieces of advice you need to know exactly how it works (and why it always does). 👇

1. Tag Everything Like You Mean It

Week 1 is pure detective work.
If you don’t know who owns a resource, you shouldn’t be paying for it.

Tag every EC2, S3, RDS, and container by environment, feature, and team.
Once you can actually see the spend, you’ll find ghost workloads — dev environments running 24/7, “temporary” experiments that never died, and backup policies older than your product.

Most startups discover 20–30% of their bill funds nothing at all.
Is yours one of them?

2. Stop Designing Like You’re Netflix

Startups love overkill.
“Let’s double the instance size. Just in case!”

No.
You’re not Netflix, and you don’t need hyperscale architecture at 100 users.

Rightsizing workloads (compute, databases, containers) is the single biggest win.
With cloud, you can scale up later.
But you can’t refund waste.

3. Storage: The Silent Budget Vampire

S3 and EBS grow like weeds.
Old logs. Staging backups. Endless snapshots “just in case.”

Set lifecycle rules. Archive cold data to Glacier or delete it.
If you’re scared to delete something, it means you don’t understand it well enough to keep it.

I’ve seen startups recover five figures just by cleaning up storage.

4. Dev Environments Should Sleep

This one’s so simple it hurts.
Your dev and staging servers don’t need to run 24/7.

Set schedules to shut them down after hours.
One client saved $8K a month with this alone.

Cloud doesn’t mean “always on.”
It means “always right-sized.”

5. Make Cost a Metric

You can’t fix what no one owns.
Cost awareness must live inside engineering, not finance.

The best teams track cost next to performance.
Every sprint review should really include team memmers asking:

“What does this feature cost to run?”

Once devs see the impact, waste disappears.
Accountability beats optimization.

6. Automate Guardrails

Okay, this one’s for the real pros.

The final step is relapse prevention.
Budget alerts. Anomaly detection. Automated cleanup.

Don’t wait for surprises in your invoice — build tripwires for waste.
Optimization without automation is a diet with no discipline.

What Happens After 90 Days

By the end of the first quarter, most teams see 40% savings and faster performance.
But that’s not the real win.

The real win is cultural:
Your team starts treating efficiency as part of good engineering. Not an afterthought like they did before.

When you design for scalability, flexibility, and accountability from day one, cloud costs stop being chaos and start being a competitive advantage.

TL;DR:
If you’re a startup founder, here’s your playbook:
✅ Tag everything.
✅ Right-size aggressively.
✅ Clean up storage.
✅ Sleep your dev environments.
✅ Make cost visible.
✅ Automate guardrails.

Don’t accept that cloud waste is inevitable. It’s just invisible until you look for it.
And once you do, it’s the easiest 40% you’ll ever save.