Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

AWS in 2025: Stuff you think you know that's now wrong

lastweekinaws.com

Post reply on HN
Print view View original

141–150 of 284 posts

Re: AWS in 2025: Stuff you think you know that's now wrong

#141

Post by no_wizard »

general1726 wrote: post #72

I think there is more of us who kind of degenerated from doing it the AWS way - API Gateway, serverless lambdas mess around with IAM roles until it works, ... - to - Give me EC2 / LightSail VPS instance maybe an S3 bucket let's set domain through Route53 and go away with the rest of your orchestrion AWS.

At what point is AWS worth using over other compute competitors when you’re using them as a storage bucket + VPS. They’re wholly more expensive at that point. Why not go with a more traditional but rock solid VPS provider?

I have the opposite philosophy for what it’s worth: if we are going to pay for AWS I want to use it correctly, but maximally. So for instance if I can offload N thing to Amazon and it’s appropriate to do so, it’s preferable. Step Functions, lambda, DynamoDB etc, over time, have come to supplant their alternatives and its overall more efficient and cost effective.

That said, I strongly believe developers don’t do enough consideration as to how to maximize vendor usage in an optimal way

Re: AWS in 2025: Stuff you think you know that's now wrong

#142

Post by daydream »

fodkodrasz wrote: post #107
MaKey wrote: post #98

Earlier quoted context omitted.

Yeah, your classic web hoster. Just today I uploaded a static website to one via FTP.

Really? If I remember correctly: My Static website served from S3 + CF + R53 by about 0.67$ / mo, 0.5 being R53 from that, 0.16 being CF, S3 being 0.01 for my page. BTW: Is GitHub Page still free for custom domains? (I don't know the EULA)

GitHub Pages are still free but commercial websites are forbidden.

Re: AWS in 2025: Stuff you think you know that's now wrong

#143

Post by icedchai »

SOLAR_FIELDS wrote: post #92
icedchai wrote: post #89

Earlier quoted context omitted.

If it were opt-out someone would accidentally leave it on and eventually realize that entire systems had been accidentally "backed up" and exfiltrated to S3.

What? The same is possible whether it's opt-in or opt-out. It's just that if you have the gateway as opt-out you wouldn't also have this problem AND a massive AWS bill. You would just have this problem.

No, with opt-in the VPC subnet is secure by default. Someone has to explicitly allow access to S3 (or anything else.)

Re: AWS in 2025: Stuff you think you know that's now wrong

#144

Post by nitwit005 »

no_wizard wrote: post #141
general1726 wrote: post #72

I think there is more of us who kind of degenerated from doing it the AWS way - API Gateway, serverless lambdas mess around with IAM roles until it works, ... - to - Give me EC2 / LightSail VPS instance maybe an S3 bucket let's set domain through Route53 and go away with the rest of your orchestrion AWS.

At what point is AWS worth using over other compute competitors when you’re using them as a storage bucket + VPS. They’re wholly more expensive at that point. Why not go with a more traditional but rock solid VPS provider? I have the opposite philosophy for what it’s worth: if we are going to pay for AWS I want to use it correctly, but maximally. So for instance if I can offload N thing to Amazon and it’s appropriate…

Your management will frequently be strangely happier to waste money on AWS, unfortunately.

Truly a marketing success.

Re: AWS in 2025: Stuff you think you know that's now wrong

#145

Post by danudey »

jp57 wrote: post #108

> Glacier restores are also no longer painfully slow. I had a theory (based on no evidence I'm aware of except knowing how Amazon operates) that the original Glacier service operated out of an Amazon fulfillment center somewhere. When you put it a request for your data, a picker would go to a shelf, pick up some removable media, take it back, and slot it into a drive in a rack. This, BTW, is how tape backups on times…

The most likely explanation is that they used a tape robot, such as the one seen here:

https://www.reddit.com/r/DataHoarder/comments/12um0ga/the_ro...

Which is basically exactly what you described but the picker is a robot.

Data requests go into a queue; when your request comes up, the robot looks up the data you requested, finds the tape and the offset, fetches the tape and inserts it into the drive, fast-forwards it to the offset, reads the file to temporary storage, rewinds the tape, ejects it, and puts it back. The latency of offline storage is in fetching/replacing the casette and in forwarding/rewinding the tape, plus waiting for an available drive.

Realistically, the systems probably fetch the next request from the queue, look up the tape it's on, and then process every request from that tape so they're not swapping the same tape in and out twenty times for twenty requests.

Re: AWS in 2025: Stuff you think you know that's now wrong

#146

Post by quesera »

TheP1000 wrote: post #49

API gateway timeout increase has been nice.

I don't see that in this post.

I just started working with a vendor who has a service behind API Gateway. It is a bit slow(!) and times out at 30 seconds. I've since modified my requests to chunk subsets of the whole dataset, to keep things under the timeout.

Has this changed? Is 30 secs the new or the old timeout?

Re: AWS in 2025: Stuff you think you know that's now wrong

#147

Post by danudey »

raffraffraff wrote: post #123
berlesi wrote: post #114

Earlier quoted context omitted.

Looks like something that you could solve easily through their support, no?

Support don't talk to you unless you pay for support

Easy, just log into your account and pay them for support.

Re: AWS in 2025: Stuff you think you know that's now wrong

#148

Post by [deleted] »

gigatexal wrote: post #132
gchamonlive wrote: post #80

Earlier quoted context omitted.

It's designed to be a declarative DSL, but then you have to do all sorts of filters and maps in any group of resources and suddenly you are programming in yaml with both hands tied behind your back

Yeah it’s just terrible. If Amazon knew what was good they’d just replace it with almost anything else. Heck just got all in on terraform and call it a day.

[deleted]

Re: AWS in 2025: Stuff you think you know that's now wrong

#150

Post by lysace »

oblio wrote: post #136
lysace wrote: post #121

Paid AWS support got a lot less capable on average during these two decades . :/ My recent interactions with them would probably have been better if they were an LLM.

They probably are an LLM and if they aren't, their higher management is pushing for them to be LLMs by 2027 at the latest.

I still get strong Hyderabad vibes from the copy/pasting plus the occasional original sentence.

Perhaps they trained the LLM using that data though.

(Small customer though: yearly AWS spend around 80k. Support is 10% of that.)

Post reply on HN