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

11–20 of 284 posts

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

#11

Post by tux3 »

SOLAR_FIELDS wrote: post #4

You know what's still stupid? That if you have an S3 bucket in the same region as your VPC that you will get billed on your NAT Gateway to send data out to the public internet and right back in to the same datacenter. There is simply no reason to not default that behavior to opt out vs opt in (via a VPC endpoint) beyond AWS profiting off of people's lack of knowledge in this realm. The amount of people who would want…

That is price segmentation. People who are price insensitive will not invest the time to fix it

People who are probably shouldn't be on aws - but they usually have to for unrelated reasons, and they will work to reduce their bill.

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

#13

Post by dmart »

SOLAR_FIELDS wrote: post #4

You know what's still stupid? That if you have an S3 bucket in the same region as your VPC that you will get billed on your NAT Gateway to send data out to the public internet and right back in to the same datacenter. There is simply no reason to not default that behavior to opt out vs opt in (via a VPC endpoint) beyond AWS profiting off of people's lack of knowledge in this realm. The amount of people who would want…

VPC endpoints in general should be free and enabled by default. That you need to pay extra to reach AWS' own API endpoints from your VPC feels egregious.

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

#14

Post by hnlmorg »

rthnbgrredf wrote: post #3
cldcntrl wrote: post #2

> You don’t have to randomize the first part of your object keys to ensure they get spread around and avoid hotspots. Not strictly true.

Elaborate.

Not the OP but I’ve had AWS-staff recommend different prefixes even as recently as last year.

If key prefixes don’t matter much any more, then it’s a very recent change that I’ve missed.

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

#15

Post by simonw »

SOLAR_FIELDS wrote: post #8
simonw wrote: post #7

S3: "Block Public Access is now enabled by default on new buckets." On the one hand, this is obviously the right decision. The number of giant data breeches caused by incorrectly configured S3 buckets is enormous. But... every year or so I find myself wanting to create an S3 bucket with public read access to I can serve files out of it. And every time I need to do that I find something has changed and my old recipe d…

I honestly don't mind that you have to jump through hurdles to make your bucket publically available and that it's annoying. That to me seems like a feature, not a bug

Sure... but last time I needed to jump through those hurdles I lost nearly an hour to them!

I'm still not sure I know how to do it if I need to again.

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

#16

Post by dghlsakjg »

SOLAR_FIELDS wrote: post #8
simonw wrote: post #7

S3: "Block Public Access is now enabled by default on new buckets." On the one hand, this is obviously the right decision. The number of giant data breeches caused by incorrectly configured S3 buckets is enormous. But... every year or so I find myself wanting to create an S3 bucket with public read access to I can serve files out of it. And every time I need to do that I find something has changed and my old recipe d…

I honestly don't mind that you have to jump through hurdles to make your bucket publically available and that it's annoying. That to me seems like a feature, not a bug

I think the OPs objection is not that hurdles exist but that they move them every time you try and run the track.

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

#17

Post by cldcntrl »

hnlmorg wrote: post #14
rthnbgrredf wrote: post #3

Earlier quoted context omitted.

Elaborate.

Not the OP but I’ve had AWS-staff recommend different prefixes even as recently as last year. If key prefixes don’t matter much any more, then it’s a very recent change that I’ve missed.

That's right, same for me as of only a few months ago.

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

#18

Post by williamdclt »

hnlmorg wrote: post #14
rthnbgrredf wrote: post #3

Earlier quoted context omitted.

Elaborate.

Not the OP but I’ve had AWS-staff recommend different prefixes even as recently as last year. If key prefixes don’t matter much any more, then it’s a very recent change that I’ve missed.

Might just be that the AWS staff wasn't up to date on this

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

#19

Post by alFReD-NSH »

aaronblohowiak wrote: post #9

>VPC peering used to be annoying; now there are better options like Transit Gateway, VPC sharing between accounts, resource sharing between accounts, and Cloud WAN. TGW is... twice as expensive as vpc peering?

And vpc sharing is free. Cost and architecture are tied.

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

#20

Post by Hikikomori »

aaronblohowiak wrote: post #9

>VPC peering used to be annoying; now there are better options like Transit Gateway, VPC sharing between accounts, resource sharing between accounts, and Cloud WAN. TGW is... twice as expensive as vpc peering?

More than twice as same AZ is free with peering. But if you're big enough you can get better deals on cost.

But unlike peering TGW traffic flows through an additional compute layer so it has additional cost.

Post reply on HN