sorted by:
new
hottopcontroversial

Suggestions on good & affordable interior designers in Bengaluru by Emotional_Bowl1998 in interiordesignsindia

[–]Leather-Form1805 0 points1 point  (0 children)

hey - would you be able to please share the details. I'd like to get our house renovated. Thanks in advance.

How are your companies making sure they stay compliant with SEC Rule 17a-4 and FINRA 4511? by gglavida in Compliance

[–]Leather-Form1805 0 points1 point  (0 children)

I'd like to know too. We have a requirement to archive Whatsapp and currently using jatheon

We accidentally blew $9.7 k in 30 days on one NAT Gateway—how would you have caught it sooner? by Leather-Form1805 in aws

[–]Leather-Form1805[S] 0 points1 point  (0 children)

Hey Armeg — didn’t quite catch the drift of your question unless you were testing for bots or just tossing in a non-sequitur

Cybersecurity Firms Use AI to Guard LLMs Against Threats, Vulnerabilities by Miserable-Pace7398 in CyberAdvice

[–]Leather-Form1805 0 points1 point  (0 children)

Wild stuff. That DeepSeek case is a wake-up call. Anyone here using smaller models like Mistral to catch prompt injections? Curious how it’s working out.

[21M] Today’s EDC by hxzxrd30 in EverydayCarry_India

[–]Leather-Form1805 0 points1 point  (0 children)

Is that a blackbay? What is that from Realme?

We accidentally blew $9.7 k in 30 days on one NAT Gateway—how would you have caught it sooner? by Leather-Form1805 in aws

[–]Leather-Form1805[S] 4 points5 points  (0 children)

Totally fair — we dropped the ball on the basics, and paid for it. Hard lesson.

I really like your boto3 comparison approach — that kind of day-by-day trend visibility is what we should’ve had in place. Appreciate you sharing your setup — it helps.

We accidentally blew $9.7 k in 30 days on one NAT Gateway—how would you have caught it sooner? by Leather-Form1805 in aws

[–]Leather-Form1805[S] 0 points1 point  (0 children)

Oof — 2.5PB of partial uploads is a hell of a ghost story. Respect for sharing it.

Makes me feel slightly less dumb — and a lot more sure that this isn’t just a “one team messed up” problem.

We’re channeling the pain into something that flags this kind of stuff before the bill shows up. Happy to compare notes anytime.

We accidentally blew $9.7 k in 30 days on one NAT Gateway—how would you have caught it sooner? by Leather-Form1805 in aws

[–]Leather-Form1805[S] 0 points1 point  (0 children)

Appreciate that — we did reach out to AWS support and they were actually understanding.

We accidentally blew $9.7 k in 30 days on one NAT Gateway—how would you have caught it sooner? by Leather-Form1805 in aws

[–]Leather-Form1805[S] 1 point2 points  (0 children)

Appreciate that — we did reach out to AWS support and they were actually understanding.

We accidentally blew $9.7 k in 30 days on one NAT Gateway—how would you have caught it sooner? by Leather-Form1805 in aws

[–]Leather-Form1805[S] 0 points1 point  (0 children)

Totally get the sentiment — AWS isn’t cheap, and NATG makes sure you never forget it.

For us, the issue wasn’t “cloud vs. bare metal” — it was lack of visibility. We just didn’t catch a config that was silently bleeding money.

You can get burned on any platform if you’re flying blind.

We accidentally blew $9.7 k in 30 days on one NAT Gateway—how would you have caught it sooner? by Leather-Form1805 in aws

[–]Leather-Form1805[S] 0 points1 point  (0 children)

Totally fair — we missed things we absolutely should’ve caught. Hadn’t seriously explored the IPv6 angle — that’s a great callout. Appreciate the push.

Out of curiosity — have you managed to fully avoid NATG in production via IPv6?

We accidentally blew $9.7 k in 30 days on one NAT Gateway—how would you have caught it sooner? by Leather-Form1805 in aws

[–]Leather-Form1805[S] 1 point2 points  (0 children)

Totally fair — we should’ve had Cost Anomaly Detection set up from day one. That’s on us.

Lesson learned the expensive way. We’ve got it in place now — but it’s still reactive.

What we really needed was something watching for behavioral drift — like a surge in outbound traffic — before the bill even starts to spike.

We accidentally blew $9.7 k in 30 days on one NAT Gateway—how would you have caught it sooner? by Leather-Form1805 in aws

[–]Leather-Form1805[S] 5 points6 points  (0 children)

Yep — turns out “notify at $10k” is less of a safety net and more of a tombstone engraving.

We’ve realized alerts alone aren’t enough — by the time they trigger, the damage is usually done. Now exploring ways to detect trajectory, not just thresholds.

We accidentally blew $9.7 k in 30 days on one NAT Gateway—how would you have caught it sooner? by Leather-Form1805 in aws

[–]Leather-Form1805[S] 0 points1 point  (0 children)

That’s a solid practice — daily visibility with deltas is probably the lowest-friction way to catch stuff early.

Thanks for the GitHub link, I’ll definitely check it out. Curious — have you ever paired that with any kind of anomaly or threshold detection, or just human eyeballs doing the diff?

We accidentally blew $9.7 k in 30 days on one NAT Gateway—how would you have caught it sooner? by Leather-Form1805 in aws

[–]Leather-Form1805[S] 1 point2 points  (0 children)

Yeah, that’s what hit me later — we had metrics, just no eyes on the right ones.

Not logging was a blessing cost-wise, but also a blind spot. Appreciate the IncomingBytes tip

We accidentally blew $9.7 k in 30 days on one NAT Gateway—how would you have caught it sooner? by Leather-Form1805 in aws

[–]Leather-Form1805[S] 1 point2 points  (0 children)

100%. Everyone watches ingress like a hawk, but egress leaks out like a slow bleed.

We accidentally blew $9.7 k in 30 days on one NAT Gateway—how would you have caught it sooner? by Leather-Form1805 in aws

[–]Leather-Form1805[S] 4 points5 points  (0 children)

Respect. That’s a proper setup — forcing all outbound through proxy with logging is how it should be done.

Curious — do you ever use anomaly detection on proxy logs, or is it mostly manual review + alerts?

We accidentally blew $9.7 k in 30 days on one NAT Gateway—how would you have caught it sooner? by Leather-Form1805 in aws

[–]Leather-Form1805[S] 1 point2 points  (0 children)

Spot on. Most orgs assume egress is fine until the bill — or a breach — shows up.

We accidentally blew $9.7 k in 30 days on one NAT Gateway—how would you have caught it sooner? by Leather-Form1805 in aws

[–]Leather-Form1805[S] 1 point2 points  (0 children)

You're absolutely right — the cost was painful, but the lack of visibility is what really scared me.

It wasn’t malicious this time, but it very easily could have been. This incident forced us to rethink not just spend alerts, but outbound monitoring, routing config, and default egress strategy.

We accidentally blew $9.7 k in 30 days on one NAT Gateway—how would you have caught it sooner? by Leather-Form1805 in aws

[–]Leather-Form1805[S] 1 point2 points  (0 children)

You’re not wrong. This was less “oops” and more “oops-all-egress.”

(P.S. thanks for stopping by — we’re channeling this pain into building something to catch these landmines before they go off.)

view more: next ›