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

111–120 of 284 posts

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

#111

Post by otterley »

SOLAR_FIELDS wrote: post #87
otterley wrote: post #59

Earlier quoted context omitted.

AWS VPCs are secure by default, which means no traffic traverses their boundaries unless you intentionally enable it.

"The door is locked, so instead of suggesting to the end user that they should unlock the door with this key that we know how to give the end user deterministically, we instead tell them to drive across town and back on our toll roads and collect money from it" This has been a common gotcha for over a decade now: https://www.lastweekinaws.com/blog/the-aws-managed-nat-gatew...

Speaking solely on my own behalf: I don't know a single person at AWS (and I know a lot of them) who wants to mislead customers into spending more money than they need to. I remember a time before Gateway Endpoints existed, and customers (including me at the time) were spending tons of money passing traffic through pricey NAT Gateways to S3. S3 Gateway Endpoints saved them money.

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

#112

Post by hinkley »

cavisne wrote: post #91
bob1029 wrote: post #69

Earlier quoted context omitted.

I am also assuming that Amazon intends for the Deep Archive tier to be a profitable offering. At $0.00099/gb-month, I don't see how it could be anything other than tape.

http://www.patentbuddy.com/Patent/20140047261 Is tape even cost competitive anymore? The market would be tiny.

It's gone in cycles for as long as I recall and older devs around 2010 said it had been going on for as long as they could recall.

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

#114

Post by berlesi »

PaulDavisThe1st wrote: post #105

Can no longer login to my AWS account, because I never set up MFA. Want to set up MFA ... login required to request device. Yes, I know, they warned us far ahead of time. But not being able to request one of their MFA devices without a login is ... sucky.

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

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

#115

Post by browningstreet »

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…

Yeah, but they've been robotic for decades since.

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

#117

Post by [deleted] »

tester756 wrote: post #94
andrewmcwatters wrote: post #46

Earlier quoted context omitted.

This sort of thing drives me nuts in interviews, when people are like, are you familiar with such-and-such technology? Yeah, what month?

If you're aware of changes, then explain that there were changes over time, that's it

[deleted]

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

#118

Post by mdaniel »

time0ut wrote: post #35
afandian wrote: post #10

Earlier quoted context omitted.

Having experienced the joy of setting up VPC, subnets and PrivateLink endpoints the whole thing just seems absurd. They spent the effort of branding private VPC endpoints "PrivateLink". Maybe it took some engineering effort on their part, but it should be the default out of the box, and an entirely unremarkable feature. In fact, I think if you have private subnets, the only way to use S3 etc is Private Link (correct…

You can provision gateway endpoints for S3 and DynamoDB. They are free and considered best practice. They are opt-in though, but easy to enable.

And ECR, which I would guess impacts more folks than DynamoDB https://docs.aws.amazon.com/AmazonECR/latest/userguide/vpc-e...

And, as as added benefit, they distinguish between "just pull" and "pull and push" which is nice

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

#119

Post by andrewmcwatters »

tester756 wrote: post #94
andrewmcwatters wrote: post #46

Earlier quoted context omitted.

This sort of thing drives me nuts in interviews, when people are like, are you familiar with such-and-such technology? Yeah, what month?

If you're aware of changes, then explain that there were changes over time, that's it

You seem to be lacking the experience of what actually happens in interviews.

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

#120

Post by damieng »

hnlmorg wrote: post #53
crinkly wrote: post #38

Earlier quoted context omitted.

I just stick CloudFront in front of those buckets. You don't need to expose the bucket at all then and can point it at a canonical hostname in your DNS.

That’s definitely the “correct” way of doing things if you’re writing infra professionally. But I do also get that more casual users might prefer not to incur the additional costs nor complexity of having CloudFront in front. Though at that point, one could reasonably ask if S3 is the right choice for causal users.

I'd argue putting CloudFront on top of S3 is less complex than getting the permissions and static sharing setup right on S3 itself.
Post reply on HN